Maintain the authoritative Psyche Build roadmap and post-release control state

[BunsDev]

Outcome: completed roadmap-control handoff

Accountable owner: @BunsDev. Train: Portfolio control. Reconciled: 2026-09-14.

The roadmap-control setup is complete. Its successor is the standing register, delivered by #453 at cea1529a1c58898b5f8ccf08148626577c82188c.

The owner retains weekly and event-driven reconciliation, explicit outcome/PR mapping, drift escalation, source-first Beads repair, and evidence-backed closeout. This issue is the setup/evidence index, not a perpetual work queue.

All setup close criteria satisfied

• Governance enforcement: Enforce post-release branch governance and publication controls #31 retains the historical direct-push rejection proof; chore: drop the unsatisfiable approval gate on main #351 records the corrected bypass-free policy. The September 14 live read confirmed administrator enforcement, strict required TypeScript and Rust/iOS contexts, linear history and conversation resolution. Active main ruleset 21729943 has no bypass actors.
• Tracker reconciliation and repeatable drift checks: Reconcile Beads mirrors and normalize post-release priorities #237/Add repeatable Beads/GitHub mirror drift and priority validation #240 are delivered. Authenticated read-only validation reported 111 sources, 27 managed mirrors, 14 canonical outcomes, and 0 findings. Beads CLI was the pinned 1.2.2; no Beads source or generated mirror mutation occurred.
• Public documentation reconciliation: docs(release): mark v0.0.1 macOS support public #236 was superseded by docs(roadmap): publish the post-release critical path #245/Complete the post-release critical-path documentation and retire superseded release-doc work #238, not left as an active draft. docs: complete roadmap-control handoff for #195 #453 updates the current roadmap/execution snapshot and preserves separate publication, supported baseline, and incomplete operator acceptance.
• Every active outcome and open PR has an owner/train/gate/evidence mapping in the standing register or this final inventory below. Generated implementation families retain their configured source-owned targets.
• Every existing and future dated Markdown plan/spec, including nested directories, defaults to reference under the historical-record policy. There are no per-file overrides.
• The successor is explicit: @BunsDev owns the standing register's weekly/event-driven process; focused protected PRs and the existing sync/validator provide the change and drift mechanisms. No replacement perpetual issue, new runtime identity, or new credentials are introduced.

Immutable delivery and control evidence

PR #453: reviewed head d31fbb8a58605ae535407dda7b7a432c62140945, merge cea1529a1c58898b5f8ccf08148626577c82188c. Both required contexts passed in run 34817673491; independent read-only review and its focused documentation evidence are retained in the PR.

PR #454: final head 52cb1f662f6c9a101213b70b78684b741a9ecadf, protected merge c4fb84bc27b901fc40e7693433a1a0d8f2116818. All required contexts and native/iOS jobs passed in run 34824126721, and contributor acceptance 34824126789 passed on that head. Independent review, hosted-review dispositions, unchanged-patch proof after the base update, and the earlier unchanged-source lifecycle retry are retained in the PR. No admin override was used.

The #420 recovery record and protected apply/no-op proof remain in the merged roadmap. Recent scheduled sync 34761084154 succeeded at 8650344ce560ffcfe190ea99acc2010921409753; its retained summary and the preceding successful run are recorded with source identity. Recent sync health is not execution against the PR's exact head and is not packaged runtime acceptance.

Final inventory and separately gated rollout

All public outcome owners remain @BunsDev. The active macOS rollout is #196/#239 acceptance followed by #199 observed recovery. Independent iOS work (#200/#241/#280/#242/#435) and deferred identity/input work (#201/#253/#279/#246) retain their existing acceptance and authority boundaries.

The concurrent PRs were reconciled without discarding either implementation: #453's standing register was preserved; #454 delivered #197 / Portfolio scope retirement / @BunsDev with truthful retirement, preserved safety/control contracts, independent review, and exact-head required checks. #197 is now closed as not planned, not completed implementation; its delivered modules and evidence remain. #279 remains open/P2 with its stale macOS release milestone removed.

#452 independently merged as 1dbf44f09c5477e932dc63c692129ad3966a3a55; its Tracker maintenance changes were preserved in the final base update, not claimed as this work. At the final post-merge inventory there are 26 open issues and no open PRs. Read-only source/mirror validation still passes with 111 sources, 27 managed mirrors, 14 canonical outcomes, and 0 findings. No Beads state or generated mirror was changed.

The unavailable #450 proposal is excluded from active inventory; no replacement, deletion, or remote assignment is claimed.

Closure provenance and limits

GitHub's timeline records PR #453 as the closer at 2026-09-14T07:33:14Z. Its body contained a closing directive even though the intended procedure described manual closure. That automatic transition is not itself acceptance evidence. The post-merge inventory, policy read, and checklist reconciliation above establish the bounded setup result; no manual issue-close command or uninterrupted manual-only closeout sequence is claimed.

#196/#239 remain open and incomplete for packaged operator evidence. #199 recovery and #435 unknown mobile effects remain open. No physical iOS/TestFlight availability, new release acceptance, protocol conformance, or completion of broad desktop decomposition follows from this control handoff.

Rollback: any withdrawal of the standing successor requires a reviewed protected PR and an explicit accountable replacement; reopen this setup issue if that successor is removed. Do not modify generated mirrors, revert delivered runtime work, or infer support from issue state.

[BunsDev]

Additional P0 metadata reconciliation

Before candidate freeze, remove the remaining legacy openclaw keyword from package.json and verify the repository description, package metadata, README, release notes, application identity, Homebrew Cask, and public documentation consistently identify the product as Psyche Build / OpenCoven. Track the implementation in Beads under this outcome; this is release metadata cleanup, not a reason to expand product scope.

[BunsDev]

Roadmap reconciliation update

#203 is now a P0 release-infrastructure outcome: make desktop_only: true verification independent of iOS-only gates while retaining shared validation. It blocks #31/#194/#196 and is represented in #202's delivery graph, active outcomes, Stage 2 ownership, and support/acceptance contracts.

The PR reconciliation now also includes #202 itself. Package metadata cleanup is implemented in #202: the legacy openclaw keyword is replaced with opencoven, linked active documents are included in package output, and dependency versions remain unchanged.

[BunsDev]

2026-08-25 roadmap reconciliation

The current roadmap state is merged on main as 5f4b7b05579e98cd283cb2d1c43a48d49330b4b5 via #245.

• docs(release): mark v0.0.1 macOS support public #236 is closed as superseded.
• Complete the post-release critical-path documentation and retire superseded release-doc work #238 is complete and closed by docs(roadmap): publish the post-release critical path #245.
• feat: publish Beads planning to a managed GitHub Project #248/fix: harden public Beads synchronization #249 delivered the managed Beads Project mirror, bounded two-query GraphQL dry-run path, drift validation, protected main-only environments, mutation fencing, and sanitizer hardening.
• fix: isolate git_log from untrusted repository Git config #247 is merged as 94d8eebb198d8363cf418604e0a21d98f6838293, closing the repository-config command-execution path in desktop Git-log inspection while preserving bare repositories.
• Reconcile Beads mirrors and normalize post-release priorities #237/Add repeatable Beads/GitHub mirror drift and priority validation #240 remain open for public acceptance/evidence reconciliation; [psyche-310] Make desktop-only release verification independent of iOS #206 / psyche-310 is still open and their complete canonical-outcome/priority evidence is not yet closed.
• Enforce post-release branch governance and publication controls #31 and Close the v0.0.1 runtime acceptance and stabilization baseline #196/Produce the v0.0.1 operator acceptance manifest and stabilization evidence #239 remain the active P0 governance and operator-observed stabilization gates.

Canonical current documents: docs/ROADMAP.md, docs/POST-RELEASE-EXECUTION.md, docs/RELEASE-ACCEPTANCE.md, and docs/SUPPORT-MATRIX.md.

[BunsDev]

Roadmap reconciliation — Psyche program extension

Two focused child outcomes have been added without replacing this roadmap or docs/POST-RELEASE-EXECUTION.md:

• Create a root agent entrypoint and deterministic repository check contract #252 — root agent entrypoint and deterministic repository check contract;
• Adopt Psyche through a versioned compatibility canary and incremental adapters #253 — versioned Psyche compatibility canary and incremental adapters.

Draft PR #254 implements the initial documentation/verification foundation at head 264a5f68e64cbdc393c1f4a15b6c770da6bdbd5a.

Sequencing remains unchanged:

• Close the v0.0.1 runtime acceptance and stabilization baseline #196 stabilization, Harden Psyche Build operations, diagnostics, and recovery #199 maintained control plane, and Deliver the Psyche Build iOS internal beta and continuity loop #200 iOS acceptance retain their declared priority/critical path;
• Reduce Psyche Build desktop architectural concentration #197 decomposition should expose stable seams that a future adapter consumes;
• Psyche mapping may proceed now;
• immutable pinning waits for OpenCoven/psyche#11;
• ownership-sensitive adoption waits for OpenCoven/psyche#12;
• no unreleased protocol work becomes an implicit support prerequisite for v0.0.1.

This is a roadmap extension and contract clarification, not a new competing control plane.

[BunsDev]

2026-08-28 control-plane wave

A structured repository-readiness wave is now in flight:

Outcome	Progress	Exact next gate
#252 / #198 clean contributor-agent loop	PR #258 adds the root agent router, repository manifest, deterministic bootstrap, fast/full checks, and contract tests	Exact-head CI, clean Linux/macOS evidence, and contributor pnpm-pin reconciliation
#244 / #198 security-community floor	PR #259 adds security/support/conduct policy, CODEOWNERS, PR/issue forms, redaction and contract tests	Exact-head CI; enable/confirm private vulnerability reporting; decide code-owner enforcement/inbox
#31 branch governance	Required checks now report enforcement_level: everyone; active ruleset 21729943 requires approval, last-push approval, and thread resolution	Remove or explicitly justify the remaining BunsDev pull_request bypass; code-owner review is still false
#237 / #240 tracker drift	#206 is now proven stale source state: #203 is complete, #204 merged, protected run 32629730508 passed	Transition authoritative Bead psyche-310 to done and let sync close the mirror; finish P0 mapping

This wave deliberately avoids product/runtime rewrites. It strengthens the control plane first, preserves Psyche Build as the coding cockpit rather than a second canonical protocol authority, and leaves all still-unproven gates open.

[BunsDev]

Roadmap-control reconciliation — tracker stage complete

#237 is now closed completed. The control-state changes since this issue's 2026-08-24 snapshot are material:

• psyche-310 / [psyche-310] Make desktop-only release verification independent of iOS #206 and psyche-3i9 / [psyche-3i9] Ship Psyche Build v0.0.1 for macOS #207 are both source-first closed;
• Add repeatable Beads/GitHub mirror drift and priority validation #240's repeatable drift-validation outcome is closed completed;
• feat: add repeatable tracker drift validation #263 merged the bounded source↔mirror validator and has successful exact-head CI on its final rebased head;
• a current query finds zero open generated issues labeled priority:P0;
• chore: establish the agent repository contract #260/chore: establish the security and community floor #261 merged the repository-agent and community/security floor;
• docs: freeze the Psyche compatibility mapping #262 merged the Psyche compatibility map while keeping tracker/process/UI identifiers explicitly product-local rather than protocol identity;
• docs: add contributor repository and architecture map #270 now addresses the remaining explicit repository/architecture-map slice of Complete Psyche Build open-source readiness #198.

Therefore #237 should no longer appear as current P0/stabilization work in the next docs/ROADMAP.md reconciliation. #195 remains open because #31 governance, the remaining public-doc/control snapshot reconciliation, and the other close criteria are independent outstanding obligations.

[BunsDev]

2026-08-28 roadmap-control reconciliation

The readiness/control wave has advanced beyond the current docs/ROADMAP.md wording and the live issue should be treated as authoritative until the snapshot is repaired.

Now complete

• Reconcile Beads mirrors and normalize post-release priorities #237 — Beads/mirror reconciliation: closed completed.
• Add repeatable Beads/GitHub mirror drift and priority validation #240 — repeatable tracker drift validation: closed completed.
• chore: establish the agent repository contract #260 — root repository/agent contract: merged.
• chore: establish the security and community floor #261 — security/community floor: merged.
• docs: freeze the Psyche compatibility mapping #262 — Psyche compatibility/current-state mapping: merged; Adopt Psyche through a versioned compatibility canary and incremental adapters #253 remains open for the future immutable profile/canary/adapters.
• feat: add repeatable tracker drift validation #263 — source↔mirror drift validator: merged.
• test: isolate sanitizer performance guard #269 — sanitizer CI timing isolation: merged without threshold relaxation.
• docs: add contributor repository and architecture map #270 — contributor repository/architecture map: merged.
• ci: prove the clean contributor loop #271 — credential-free Contributor Acceptance workflow: merged.

Active bounded closure work

• fix: keep the full contributor gate clean #272 — fixes the first clean-room Contributor Acceptance failure by keeping Cargo output outside the checkout while preserving exact cleanliness checks. Awaiting executable exact-head evidence, not colleague review.
• docs: finish contributor readiness policy #273 — finishes contributor scope/design/evidence policy and classifies dated docs/superpowers/ records conservatively as historical reference material. It should merge only after fix: keep the full contributor gate clean #272 is in main and its exact head includes the repaired full gate.

Still a genuine external control-plane blocker

#31 remains open. Live ruleset 21729943 still has CODEOWNER review disabled and an always-on RepositoryRole bypass; required-check enforcement is also reported as non-admin on the branch-protection surface. The current GitHub connection exposes ruleset reads but no mutation action, so repository documents cannot substitute for the actual settings change.

Snapshot repair

The next docs/ROADMAP.md controlled update should stop describing #237/#240 as future conditional closure, mark the repository/community foundation through #271 as delivered, preserve #198 until clean-room/live-settings evidence is complete, and keep #253 explicitly downstream of the Psyche publication/ownership gates rather than presenting compatibility mapping as conformance.

[BunsDev]

Portfolio reconciliation — 2026-08-30

Canonical documentation reconciliation is open in #282 against main at f12b753424f2444466aadbd70f8213768a657031.

Support truth

• The latest supported public release remains macOS v0.0.1 from 57c6c71bd5264fde960b062e95de278c8438c94f.
• Repository package/changelog metadata identifies 0.0.2, but it is an unreleased candidate until immutable publication, assets, install/upgrade evidence, and an owning support transition exist.
• iOS remains Planned; merged source/simulator/composition work does not establish TestFlight availability.

Delivered foundation

• Reconcile Beads mirrors and normalize post-release priorities #237, Complete the post-release critical-path documentation and retire superseded release-doc work #238, Add repeatable Beads/GitHub mirror drift and priority validation #240, and Land the minimum security, ownership, support, and contribution floor #244 are complete.
• fix: keep the full contributor gate clean #272 repaired the clean-checkout full gate without weakening the worktree-cleanliness invariant.
• docs: finish contributor readiness policy #273 completed contributor scope/design/evidence policy and historical-plan classification.
• docs: freeze the Psyche compatibility mapping #262 merged only the current-state compatibility mapping slice of Adopt Psyche through a versioned compatibility canary and incremental adapters #253.
• feat(mobile): share guarded remote action state #274 merged one guarded host-scoped iOS action store/client as f12b7534; no support claim changed.

Current order

1. Close the v0.0.1 runtime acceptance and stabilization baseline #196/Produce the v0.0.1 operator acceptance manifest and stabilization evidence #239 remain the product P0 stabilization critical path.
2. Enforce post-release branch governance and publication controls #31 proceeds in parallel as the live governance P0 gate; branch protection still reports enforcement_level: non_admins.
3. Harden Psyche Build operations, diagnostics, and recovery #199/Define support bundle v1 schema, bounds, and automatic redaction #243 operations and Complete Psyche Build open-source readiness #198 final clean-room/live-settings evidence.
4. Extract an atomic iOS host-readiness state machine from PR #193 #241 atomic iOS readiness.
5. Define and prove secure single-use iOS invite authentication #280 focused invite-authentication slices from draft/source PR feat: add secure iOS invite authentication #264.
6. Discovery/reconnect + physical same-LAN proof.
7. Wire production ritual publication and execution before restoring mobile controls #242 publication → execution → capability-gated controls.
8. Immutable TestFlight acceptance under Deliver the Psyche Build iOS internal beta and continuity loop #200.
9. Reduce Psyche Build desktop architectural concentration #197 after stable Close the v0.0.1 runtime acceptance and stabilization baseline #196/Harden Psyche Build operations, diagnostics, and recovery #199 seams.
10. Non-blocking Converge Psyche Build on protocol-owned identity and Psyche orchestration #201/Adopt Psyche through a versioned compatibility canary and incremental adapters #253/Introduce a capability-negotiated Coven launch adapter without persisting prompts #279 convergence and Deliver post-release cross-platform Vim and keyboard-mode parity #246 input parity.

Active PR disposition

• feat: add support bundle v1 contract #278: changes requested under Define support bundle v1 schema, bounds, and automatic redaction #243 for fail-closed terminal privacy, collector-conflict truth, authoritative action vocabulary, and bounded normalization.
• Route desktop agent launches through Coven #277: design correction required under new Introduce a capability-negotiated Coven launch adapter without persisting prompts #279; raw prompts must leave argv/persistent launch metadata, and Coven compatibility/capability must be negotiated.
• feat: add secure iOS invite authentication #264: draft source material only under new Define and prove secure single-use iOS invite authentication #280 after Extract an atomic iOS host-readiness state machine from PR #193 #241; extract focused R3 slices instead of merging 32 commits / 37 files.

No generated Beads mirror body was manually edited. #282 makes these states and dependency gates test-enforced in the roadmap, execution contract, and support matrix.

[BunsDev]

Portfolio addendum — PR #281

A new #199 child PR opened after the reconciliation snapshot: #281, the debug-authorized rendering stress harness for generated task #230. It is changes requested, not merge-ready.

Open findings: compile/register the process-spawning commands only behind the stated debug boundary (or approve an explicit design change), validate the invoking webview rather than a window label for cycle authority, and handle launcher spawn errors deterministically. Generated #230 remains Beads-owned and its mirror body was not manually edited.

[BunsDev]

Tracker-integrity hardening landed through #330 as c2a8da8d241a6d10d47116d64c399efa40854bcc. The validator now checks canonical render hashes, legacy/current managed markers, malformed active and closed outcome references, duplicate/obsolete metadata, bounded redaction, and makes missing/stale hash drift repairable through the supported synchronizer. This is implementation evidence for the roadmap/control-state outcome; it does not close the broader issue.