Skip to content
Coven Threads Docs

coven-threads documentation

coven-threads is OpenCoven's protected-authority validator, imported by the trusted coven daemon.

5 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.

coven-threads is OpenCoven's protected-authority validator, imported by the trusted coven daemon. The daemon owns authentication and effects; Threads defines whether protected-surface state permits a write. Its contracts target RFC-0001 §5, while the delivery ledger records unresolved daemon conformance findings.

If you are new here, read concepts.md first. Everything else assumes its vocabulary.

The October 30 decision handoff consolidates all eight criteria, #100/#86 wording and residual decisions, later native durability evidence and the newer Cave repin limits. It prepares Val’s review without adopting the proposed wording or accepting #13/#14.

Historical status checkpoint (2026-09-13 UTC)

  • Phase 0 (design) — [FROZEN]. The design doc specs/PHASE-0-DESIGN.md is frozen at v0.2 (2026-07-14, tag v0.2-phase0-design), with Nova sign-off and an RFC-0001 §5 round-trip verified.
  • Phases 1–2: [FROZEN; IN RELEASE TAG]; Phase 3: [ENGINEERING FROZEN]. Coven v0.4.3 includes the daemon integration and pins Threads to c102844. This is release-source provenance, not verification of deployed configuration or current-checkout compatibility. Phase 3 retains the decided .weave envelope and lossy one-way .af export semantics.
  • Phase 4: [FROZEN] (2026-07-17). The four Cave surfaces and their recorded human gates are complete under threads-986.17. The daemon-adapter follow-up threads-v3g and degraded-familiar follow-up threads-k9s are closed. See the delivery ledger for merge evidence.
  • Phase 5: [ACTIVE]. Identity, protected-route, and seven-scenario retired-corpus engineering are accepted in OpenCoven/coven#885, OpenCoven/coven#887, and OpenCoven/coven#888. Global deployed-history closure remains open in OpenCoven/coven#886; the accessible deployed profile was inventoried read-only on 2026-09-15 and holds zero opened veto windows, which narrows that root without closing it. Under the adopted solo-maintainer policy, Val may author and self-review; agent evidence supplies neither Val's coherence acceptance nor the subsequent scoped freeze. See the engineering handoff, phases.md, and the E2E contract.

Baseline main protection is active under the authorized solo-maintainer policy. The separate privacy job and four-target pinned-daemon lane are required checks. The latest-main schedule remains advisory. The Automation Authority Profile v1 is a separate shipped schema/reference-validator contract, not evidence of daemon adoption or a replacement for the Rust gate.

These docs describe frozen and active contracts without amending them. Use the delivery strategy for sequencing, the ledger for delivery evidence, and the dated readiness review for findings and remaining acceptance obligations. The September 14 reliability handoff records the later fixture corrections, accepted diagnostics, and unresolved native causes without replacing the root acceptance record.

Who this is for

  • Operators / principals who want to understand what protects a familiar's identity surface and what the failure modes look like.
  • Contributors who need the vocabulary bound correctly before touching code (start with concepts.md; the metaphor-referent binding rule is not optional).
  • Reviewers checking conformance claims against RFC-0001 §5.

Table of contents

Doc What it covers
concepts.md The vocabulary (Thread, Weave, Strand, Channel), the two-compaction contract, the five channel-survival invariants, the descriptor-vs-predicate anti-pattern. Read this first.
architecture.md Where coven-threads sits in the stack, the end-to-end enforcement flow, the ward.audit store, relationship to RFC-0001 and coven/docs/SAFETY-MODEL.md.
authority-model.md Gate 4 fail-closed as a conformance requirement, the three verdicts (Permit / DegradeToProposal / Reject), the thread tension state machine and repair path.
automation-authority-profile.md Operation-specific automation authority, approvals, proposal-only downgrade, replay/TOCTOU, privacy, and portable vectors.
channels-and-strands.md The four channels of load, the five strand types, which strands each channel structurally requires, WARD-C1–C7.
phases.md Phase 0 → 5 with honest status labels: what is frozen, what is implemented, what is active, what is blocked.
strategy.md Workstream order, canonical owners, closure evidence, and release prerequisites. GitHub issues and Beads retain task status.
Readiness review Dated landscape, documentation corrections, and engineering recommendations for the open review gates.
Native reliability handoff September 14 fixture corrections, accepted diagnostics, exact source receipts, and remaining engineering/operator boundaries.
Deployed audit-census September 15 read-only disposition of the accessible deployed profile for threads-980 / OpenCoven/coven#886: zero opened veto windows, and the scope limits of that negative.
Promotion-path scope September 16 scope for the Channel::Deliberate submission path (threads-xpo): what is already channel-generic, the two decisions that gate it, and the implementation surface.
Ward-state emission decisions September 16 decisions for threads-vdv: what ward_version is, what backs principal_authorization, and the descriptor-strength limit of that binding.
E2E contract Real-daemon topology, eight required journeys, deterministic time, and blocker-closure evidence.
faq.md Anticipated questions, answered honestly with sources.
glossary.md Every named term, one line each, alphabetical, with links to depth.

Normative sources

These docs are descriptive. When they disagree with a normative source, the source wins, in this order:

  1. RFC-0001 (familiar-contract/rfcs/RFC-0001-familiar-contract.md) governs familiar identity and Ward requirements.
  2. Frozen or active decision records under specs/ govern Threads semantics, including the Phase-5 and versioned automation authority contracts.
  3. Public Rust contracts and conformance vectors in crates/coven-threads-core define the implementation surface.
  4. Explanatory material under docs/ describes those contracts without amending them.

The coven-grimoire Ward Layer Spec Brief §9 is the cited canonical home of WARD-C1–C7. coven/docs/SAFETY-MODEL.md describes the daemon boundary; it does not replace the source precedence above.

Diagrams in diagrams/ are legibility aids derived from the design doc; they are not authoritative (see diagrams/README.md).

Historical plans and reports

The July status report, ApplyAudit design, and ApplyAudit implementation plan preserve earlier checkpoints. Do not execute their completed tasks or treat their old counts as current acceptance. Rendered diagrams, the PDF, and slides are explanatory snapshots, not release evidence.

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

Esc