Acceptance and evidence

    Record acceptance, assign open actions and retain the evidence behind this handover.

    Repository review: . Public operational reference; acceptance remains to be recorded by the receiving owner.

    Acceptance checklist and open decisions

    Use this as an agenda for the outgoing and receiving owners. Record names, dates, evidence links and dispositions in the restricted transfer record. These are checks to complete, not statements that the transfer has happened.

    Handover acceptance evidence
    AreaRequired evidence
    Ownership and accessNamed accountable owners/deputies; approved successor access; account, billing, domain and recovery ownership verified; restricted configuration inventory delivered.
    Reproducible websiteSuccessor runs locked install, tests and build from the identified commit and explains generated outputs and archive dependencies.
    Reproducible modelPython 3.11, Java 21 and pinned Jena/upstream evidence available; catalogue generation/check and reviewed candidate pin demonstrated; affected model gates pass; local reload/projection effects understood.
    Release and recoverySupervised CI release, matching live source commit, changed-route/asset check, scoped rollback exercise and an agreed incident/recovery plan. Any resource publication uses a complete archive and separately reviewed deletion preview.
    Participant servicesCurrent enablement and service ownership read back; canary signup/approval/acknowledgement/onboarding and comments tested without unintended effects; domain and website-allowlist entitlement cases distinguished; parked-operation inspection/resolution understood.
    Operations and dataAlert delivery demonstrated; logs, queues and the 15-minute reconciliation rule verified; certificate expiry/renewal owners and receipt-key continuity confirmed; retention, backup coverage, isolated restore evidence and recovery objectives accepted.
    Microsoft and intakeLive authority and organisation isolation verified across the intended workspaces; inbox and onboarding scopes distinguished; actual contribution states reconciled; alternative route for blocked participants demonstrated.
    Teams approval botCurrent bot/flag/approver-group configuration and credential ownership confirmed; ADR-0088's proposed status reconciled; authorised journey and authenticated non-approver refusal evidenced.
    Scheduled automationActual host and schedule identified; one active owner; provider/Microsoft access verified; checkpoints and a recent audited outcome handed over.
    Content and NotebookLMSource/archive/asset and export inventories complete; notebooks usable by successor; human review and publication status retained.
    Recorded commitmentsEach ADR-0089–0094 action has a current disposition, confirmed owner, evidence and next review date, or an explicit agreed exclusion from this transfer.
    Formal acceptanceReceiving owner records accepted scope, date, evidence, remaining risks, action owners and review dates before outgoing access is retired.

    The remaining governance work includes the exact Property Pack review/version, source-count reconciliation, named decision owner, reviewer dispositions and recorded determination. Wider SPDTF lifecycle/ratification policy remains proposed. Do not report model generation, schema comparisons, pull-request/module reviews or a handover meeting as formal approval.

    The remaining operational work is to verify current account access, live integration enablement, deployment/recovery evidence, alert recipients, backup restoration, scheduler activation and notebook continuity. No current live census of private submissions, provider subscriptions or account ownership is asserted by this page. Assign an owner and next action to each unresolved item instead of silently treating it as complete.

    Reconcile the recorded October commitments

    ADR-0089–0094 are all dated and remain proposed. They retain actions drawn from earlier calls, correspondence and workspace inspection; they do not establish today's completion status or adopt new governance. During transfer, reconcile each action with its recorded owners, confirm any successor assignment and retain the current disposition, evidence, next action and review date privately. Record an explicit scope exclusion where agreed. Do not reproduce private correspondence or submissions here.

    Recorded commitments to reconcile with their owners
    RecordAction and completion evidence
    ADR-0089 — technical governanceConfirm the internal technical subgroup's authority and Terms of Reference, distinguish its remit from cross-scheme coordination, and align training with the agreed responsibilities. Retain the confirmed remit, approved document version and reviewed training.
    ADR-0090 — Property Pack reviewReconcile delivery of the requested status update and the exact candidate, reviewers, deadline and decision route. Resolve the recorded 442/451 source-count question through a versioned crosswalk and retain the determination. Preserve the record that the 8 October update was missed; do not reset that historical date or infer later completion.
    ADR-0091 — schema change and migrationReconcile the PR-based process/training example, modular-schema comparison and independent reviews of current PRs. Retain identified inputs, recorded differences, the reviewed example and an explicit compatibility/cutover decision. A training example does not approve or merge a PR.
    ADR-0092 — tenant-independent contributionReconcile mortgage submissions, permissions and dispositions against the private intake record, including both previously recorded contributions from one organisation. Distinguish the dictionary and fictional JSON example from a JSON Schema or model incorporation. Evidence the requested status report and a working feedback route without OPDA Microsoft tenant access.
    ADR-0093 — industry sessions and outreachReconcile review of the already-shared toolkit, session order/dates/facilitation, outreach ownership and distribution/branding permissions. The record confirms the toolkit link was delivered and seen on 5 October; it does not confirm its review. Retain reviewed assets, organiser confirmations and authorised distribution.
    ADR-0094 — content ownership and approvalConfirm the intended website and cleanup scope, name content owners and reconcile the requested sitemap/copy approval control with its recorded owners. Retain versioned review and approval outcomes. The referenced external website must not be assumed to be this repository or treated as authority for unrelated publication.

    Source map and maintenance of this handover

    This page was checked against the repository sources below. Paths identify what an authorised successor should inspect in the checkout; private operational contents and correspondence are deliberately not reproduced. Recheck the implementation and dated evidence after material changes.

    Open the repository, setup and architecture README, command catalogue, release workflow, participant integration and recovery decision, onboarding decision and NotebookLM maintenance decision. These links follow main; use the accepted release commit when investigating historical behaviour.

    Sources for the procedures and limitations above
    SubjectRepository source
    Contributor rules, commands and architectureAGENTS.md, README.md, Makefile, package.json, astro.config.mjs, src/content.config.ts, DESIGN.md.
    Release and assurance.github/workflows/deploy-aws.yml, site-release.yml, site-assurance.yml, infra.yml; scripts/classify-ci-changes.mjs, scripts/site-cache-release.mjs, scripts/write-release-manifest.mjs.
    AWS and recovery boundariesconfig/aws/site-stack.yaml, operations-stack.yaml, participant-identity-stack.yaml, working-group-interest-stack.yaml, comments-stack.yaml; ADR-0038, ADR-0040 and ADR-0079.
    Semantic authority and generatorsADR-0063, ADR-0065, ADR-0066, ADR-0067, ADR-0068, ADR-0075, ADR-0077; tools/opda-gen/src/opda_gen/ and its Jena resolver; scripts/build-with-data.mjs, src/data/property-pack/, scripts/property_pack_catalogue.py, scripts/property_pack_candidate.py, scripts/_lib/property_pack_candidate_validation.py.
    Workspaces, intake and scheduled agentADR-0070, ADR-0072, ADR-0085, ADR-0087; src/agents/working-group-inbox/domain.mjs, config/agents/working-group-inbox/, scripts/working-group-inbox-agent.mjs, src/approval-onboarding/settings.mjs and invitation.mjs.
    Entitlement, participant recovery and Teams approvalsADR-0085; ADR-0088's flag/decision-status conflict and dated confirmation; config/aws/auth-session/identity.mjs, scripts/website-allowlist.mjs, scripts/onboarding-review.mjs, src/approval-onboarding/index.mjs, receipt-protection.mjs, config/aws/hubspot-approval-stack.yaml, config/aws/teams-approvals/ and teams-approvals-stack.yaml.
    Recorded October commitmentsdocs/adr/: ADR-0089 (technical remit), ADR-0090 (Property Pack status and determination), ADR-0091 (schema process/migration), ADR-0092 (contribution access/intake), ADR-0093 (industry outreach) and ADR-0094 (content owners/approval). All remain proposed, dated 11 October 2026.
    Evidence, marketing and NotebookLMsource/README.md, src/data/resources-manifest.json, scripts/publish-resources.sh, scripts/marketing/; ADR-0081; docs/notebooklm/, preparation/execution scripts and scripts/verify-notebooklm-execution.mjs.

    Maintain this route alongside changes to commands, deployment, ownership boundaries or toolchains. Update the review date only after checking the affected sources. Keep operational secrets in their authorised owner systems and record acceptance separately from this public reference. The shared site print stylesheet supports a printable copy; a saved copy must retain its review date and status.