Skip to content
Coven Threads Docs

Delivery strategy

Workstream order, canonical owners, closure evidence, and release prerequisites. GitHub issues and Beads retain task status.

11 min read

Current status, 2026-10-28: Phases 0–4 remain frozen and Phase 5 remains active. The four accepted September root dossiers retain their recorded scope. Coven #1305 repaired the Set B durability defect on main; the latest published Coven v0.4.10 predates that repair. Cave #5256/#6187 delivered the qualified 30-day window at its older producer pin. Current-head execution, inspected deployment and Val’s #13 → #14 decisions remain separate. The current eight-item packet records full source tuples, receipts, unknowns and residuals. Earlier dated checkpoints below are historical evidence.

Finish the real-daemon authority boundary before declaring Phase 5 complete or expanding its authority claims.

Planning baseline: 2026-09-11; repository rollout updated 2026-09-13 (UTC). Native reliability checkpoint: 2026-09-14 (UTC). This is an explanatory delivery strategy, not a new normative contract, task tracker, or approval. GitHub #31 and its linked issues own cross-repository work; Beads owns local task status. The delivery ledger records implementation evidence, and the readiness review records the findings behind this sequence. The September 12 continuation refreshes the daemon head, landed checkpoints, and remaining evidence owners. The execution checkpoint records the subsequent advisory-lane landing and exact-current-checkout daemon result. The boundary remediation packet records the later Windows, identity-replay, and bounded-auto contributions. The current decision records their subsequent main landings and the advisory provenance correction. The engineering acceptance handoff records the later three root closures, required-lane activation, and remaining historical audit obligation. The September 14 reliability handoff records subsequent fixture corrections and accepted operation-level diagnostics. Use those observations for further native cause discrimination; do not mistake diagnostic acceptance for a runtime repair or a new pin.

Starting position

Surface Present in the repository Not established by that fact
Rust core Typed validation, approvals, identity predicates, audit schema/migrations, .weave portability, and conformance suites Authentication, filesystem effects, or every daemon route
Automation Authority Profile v1 Schemas, reference validator, Rust port (#82/#84/#89), exact vectors, downstream pin (#1472) and signed decision producer (#1602) Production Runtime Authority certification or credential issuance; the landed decision producer has no production caller
Repository quality Pinned toolchain/actions, Cargo baseline, Nextest, informational coverage, required secret/privacy guards, and four-target daemon compatibility Immutable checker authority, installed-binary conformance, or a coverage ratchet
Governance Adopted solo-maintainer policy, required PRs, resolved conversations, and six strict required checks GitHub-enforced independent review or either Phase-5 human decision
Downstream integration Accepted current-route identity, protected proposal, and seven-case corpus engineering at 226bfcc8 Deployed historical-audit closure, live Cave acceptance, long-run reliability, or human approval

The core's three verdicts and the automation profile's four outcomes answer different questions. Do not add an automation approval outcome to the Rust gate or infer daemon adoption merely because a reference vector passes.

Sequence and exit evidence

1. Finish the bounded documentation and privacy landing

Owner: authenticated maintainer under the solo-maintainer merge policy. Public tracking: governance ledger #46, privacy rollout #40, and rollout issue #39. Beads: threads-6qw records initial governance; threads-1e9 records the authorized solo-maintainer revision; threads-chk records the landed ledger; threads-t6t records the separately authorized privacy required-check activation. GitHub records remain usable without access to a local Beads database.

#46 merged at 91ff511609cfb717bf71c3cafe07c0cbb2a2a317, recording active protection and its authorized solo-maintainer revision. #40 merged at 7168dae10f6b59bad8bc653b95f51911334ded74, adding the separate privacy job and approved historical source correction. Their final heads passed required checks before normal merges. No independent GitHub review is claimed.

#47 merged at 3ff49c02abe5693a58529265fca5bf253f4f4844, reconciling their overlapping SECURITY.md and docs/phases.md wording with the broader audit. Keep the original dated evidence distinct from later landing and policy changes, and preserve the remaining acceptance gates.

Exit evidence is recorded human authorization, resolved conversations, and normal landing after the required checks at the accepted head. Privacy policy guard was subsequently added to the ruleset on 2026-09-12 under separate human authorization. The original four required checks and all other rule settings were preserved. This completes the bounded rollout, not the daemon acceptance work below. A required scanner job is not tamper-proof enforcement against changes to the checker or calling workflow.

2. Preserve accepted root scope and refresh evidence

Current disposition: All four roots are closed within their accepted scope. Val closed #886 on the September 15 workstation census with zero opened windows; that is not global deployed-history closure. #1305 repaired the later power-loss defect and Cave #5256 completed its qualified window. Use the October 28 ledger for current work. The dated sequence below preserves historical engineering plans; stale open-work descriptions do not authorize duplicate implementation.

Owners: daemon integration lane and Cody for implementation; Echo for predicate/audit/replay review; Sage for evidence mapping. Tracking: OpenCoven/coven#1022, OpenCoven/coven#931, OpenCoven/coven#976, OpenCoven/coven#977; threads-8pz. The integration PRs are now landed checkpoints, not invitations to build parallel implementations.

The original September 12 target was ea3f455aa66bb92880d95f57eeb7ca8d845b7fe6, against main aa527d2dbcd1edcda470483c1a91a519f24e8406. That checkpoint left the shared branch untouched. The separate draft OpenCoven/coven#1022 initially composed both parents at 65766b89b4c945d325853cefdd05f364ee87cbac; that head's exact-current-Threads Linux observation and native macOS boundary targets pass, with retained failure history in the execution checkpoint. Those receipts remain historical; review the landed paired contribution below rather than reviving an obsolete head. Preserve the clock (OpenCoven/coven#968), protected-intake (OpenCoven/coven#933), and typed-terminal (OpenCoven/coven#932) checkpoints already landed on main. Reconcile overlapping component commits; do not merge every historical branch or restore #27's rejected null-close approach.

Obligation Existing work owner Required closure evidence
Identity binding from classification through replay OpenCoven/coven#885; threads-okc Accepted and closed at 226bfcc8, including the ordinary-write final-binding repair and all known intake/replay classes
Every approval ceremony reaches supported intake Daemon acceptance OpenCoven/coven#884; landed OpenCoven/coven#1022, OpenCoven/coven#972, OpenCoven/coven#1029, and #57 Accept exact-head native/current-core proof of both auto variants and the human paths; preserve protected floors and reject injected positive envelopes. #13 is the downstream acceptance gate, not the implementation owner
Complete submission/opening/typed-close chain OpenCoven/coven#886; threads-980 Supported nine-case matrix and global read-only census landed; actual deployed inventory and evidence-backed disposition remain required
Protected proposals never become writes OpenCoven/coven#887; threads-dgg Accepted and closed after full nine-route matrix; distinct protected writes stay disabled, and client source/fixture proof is not live Cave acceptance
Retired-Ward schedulability OpenCoven/coven#888; threads-zav Accepted and closed after all seven actual corpus cases, true worker contention, original red/fix/green, and 13 required typed closes
Final authority snapshot matches committed bytes OpenCoven/coven#977; threads-8pz.13 Named authority-change interleavings, intended-file atomicity, audit agreement, and recovery/rollback evidence
Native startup reliability and artifact provenance Named repair OpenCoven/coven#1027; final fixture consolidation OpenCoven/coven#1029; broader OpenCoven/coven#884 and OpenCoven/coven#1000 Preserve the original failure and exact native repair receipt; verify later heads separately, including launch/exit origin and dependency state. OpenCoven/coven#1001 is closed for measurement, not reliability

The landed terminal checkpoint's legacy-window recovery target is not supported scheduled publication. OpenCoven/coven#969 has since merged; the supported scheduled producer now commits identity evidence, and threads-vpp.2 supplies the missing valid-to-valid replay proof. OpenCoven/coven#972 subsequently landed at 8bab50f6, after the publication foundation OpenCoven/coven#1022 at 2de5aaa8; broader acceptance still belongs to OpenCoven/coven#888. OpenCoven/coven#1019 supplied synthetic budget interpretation, not the later native repair. Keep those earlier receipts dated rather than calling them current blockers.

The paired #57 / OpenCoven/coven#1029 contribution is now on main: Threads merge 1fe26a12609ec11744808af3f4209df475ecf8d8 and Coven merge abcf926500d5dcf2dbec2f8d3bfd15a7b393c619. Coven pins corrected core 0021fd2662d0b82328371ee3a6957d645f776fda, including registry mixed-batch refusal. Core 2c7a305e, daemon d01136f7, and owner base 8d48bf79 identify earlier checkpoints, not the final composed source. Use the paired pull requests' exact-head acceptance and preserve pin ancestry; repeat affected proof when either side changes. The new region is strictly bounded output formatting, not a reason to downgrade protected memory or migration policy. The next work is the unresolved root evidence, not another fixture integration. The earlier 84b8dcc7 authority target passed natively, but its dedicated CLI startup gate failed. The OpenCoven/coven#1030 deadline repair now passes all six original native CLI cases. The subsequent OpenCoven/coven#1031 correction removes a reproduced redundant store checkpoint/reopen without widening the fixture or production deadlines. Final native run 34703393798 passes the whole workspace and authority target. Preserve both failed runs, the same-runtime documentation-only comparison, and the corrected-source proof; none establishes the longer-term reliability target by itself.

The all-ceremony proof above is broader than OpenCoven/coven#888's requirement for a minimal valid retired-Ward case. Keep the corpus remediation in threads-zav; do not silently expand its acceptance criteria or assign implementation work to the human gate. The shared daemon lane owns the broader route coverage needed for #13.

For each of the four root blockers, retain a pre-fix red, the production fix, an exact-head green, a lower-level regression, and migration/rollback notes. Test existence, a serialized diagnostic retry, or an engineering recommendation does not close the blocker. If supporting every ceremony requires changing a canonical contract, obtain that decision rather than silently narrowing #13.

3. Maintain current-checkout compatibility

Owners: Sage and the release/governance maintainer. Tracking: #31, completed rollout #64/#65, and e2e/compatibility.toml.

The reviewed daemon pin is 226bfcc89ff6cad4bc9cc9618dad6fea970ecf58; its committed core is 0021fd2662d0b82328371ee3a6957d645f776fda. The manifest is ready and the dedicated PR/main lane requires all four daemon targets. #65 normally landed, then the sixth strict required context was activated under the authorized engineering scope. The separate latest-main schedule remains non-blocking.

First-attempt Linux run 34786471550 passed with actual clean current Threads 56cd22ba, tree-identical to reviewed a1545cf. Its 104 / 44 / 38 / 33 target results and 112 complete E2E pairs were inspected independently. The first draft's unready-manifest refusal and original failure receipts remain recorded. Future pin changes still need normal protected-main selection, exact-source acceptance, and preserved failure evidence. A mutable main ref is not a pin.

The required topology is:

current Threads checkout -> reviewed Coven SHA -> supported daemon request
  -> ephemeral files / SQLite / pending state -> scheduler / replay / restart

Prove the Cargo override is active before running J1-J8, and fail the job when it is not. Retain exact invocation, dependency state, sanitized artifacts, and run/attempt identity. A committed historical Threads dependency cannot stand in for the pull request's checkout.

Follow the E2E rollout contract: observe the non-required lane, prove intentional red cases and stable diagnostics, then require pinned Linux daemon acceptance. Keep the existing non-blocking scheduled coven/main canary separate. The TOML declaration alone does not create a required check.

The daemon-observation.yml workflow now supplies that advisory schedule and manual full-SHA candidate runs. It records exact revisions and overlay resolution, rejects any dependency edge not pointing to the current Threads checkout, and fails visibly when the selected daemon lacks threads_e2e. It landed through #49, #50, and #51 and is active on the default branch. #56 subsequently landed at 1a3a88e4, closing #54's provenance gap: configuration identity/bytes and the final metadata lockfile are rechecked at command boundaries. Its fresh post-merge run exercised 110 real-daemon scenarios against immutable Coven 08ebe853, with the actual local override and complete artifacts inspected. This does not claim hermeticity or detect transient changes restored between commands. The execution checkpoint records the first bounded successful observation and the retained setup failures. Those earlier observations did not authorize a new required check or pin: the subsequent #64/#65 rollout recorded that decision separately. Neither rollout supplies a Phase-5 freeze.

4. Complete resilience and human acceptance

Owners: daemon lane for native processes; Charm for Cave; maintainer for measurement and enforcement. Tracking: #31 and OpenCoven/coven-cave#5256.

Run the scheduled native OS matrix and real-daemon Cave project. Browser acceptance must cover stale/disconnected state, reconnect, and daemon-owned approval outcomes without optimistic client authority. A disappearing pending item is not proof of a committed write.

Use the existing targets: 8/8 critical journeys, 4/4 remediation dossiers, 99.5% first-attempt success over 30 days, and the documented latency budgets. These are acceptance targets, not measured accomplishments. Retry-success must not erase a failed first attempt. Introduce a coverage floor only from observed data.

5. Request the reserved decisions and reconcile release metadata

Owner: Val for human coherence acceptance, then scoped freeze/reaffirmation and release-metadata decisions. Agent lanes prepare engineering evidence. Tracking: #13, #14; threads-uqx.9, threads-uqx.10.

Present the eight-item coherence mapping, accepted commits, remaining exceptions, and rollback evidence. Val's coherence decision must identify its accepted scope; the freeze decision follows that gate. An agent persona, account name, commit trailer, or green check cannot supply either decision.

The adopted solo-maintainer Phase-5 policy records Val's approval under #59 of the self-review model. Val may author and self-review without inventing a second human reviewer. This adoption changes review ownership only; it does not accept the implementation, reaffirm the historical #14 freeze for new revisions, or close an engineering gate.

Before publishing a Threads release, reconcile the license texts and package metadata through an explicit maintainer decision, and distinguish the 0.2.0 unreleased changelog from downstream release ancestry. Do not rewrite frozen decisions or promise Cargo 0.1.x compatibility for exhaustive public changes.

Keep adjacent work separate

The promotion-seam contract merged in #25 is language-only. Decision 2 of the September 17 maintainer record closed threads-xpo and threads-lm4; they are not owners of open implementation work. The admission-channel fix landed through #72 and Coven #1260. Future runtime adoption belongs to Coven and requires its own scoped evidence. Local bead mirror state is unknown here because Beads is unavailable; do not infer an upstream issue ID or a promotion command.

Automation-profile consumers need their own owner-specific adoption evidence. The trusted runtime adapter remains Coven-owned. Neither this work nor threads-5rr authorizes a new identity model, audit store, or audit event. Independent planning can proceed, but it cannot bypass an unresolved phase freeze or expand protected-write authority.

Documentation and rollback discipline

Keep source precedence unchanged: RFC-0001, decision records, public contracts and vectors, then explanatory docs. Update current status at the top of the ledger; retain historical results with dates and exact revisions instead of relabeling them as current. Link completed plans to this strategy and leave them historical.

Document each boundary-changing PR's objective, non-goals, canonical sources, authority/privacy/compatibility impact, exact commands/results, downstream status, and rollback. Preserve Ward backups and ambiguous pending/applying evidence. A downgrade must not restore unvalidated writes, discard unresolved claims, or weaken typed terminal evidence.

Rendered unchanged from docs/strategy.md at 6d6f59a (2026-11-12). The repository is the source; this site is a reading surface.

Esc