Skip to content
Coven Threads Docs

Glossary

Every named term, one line each, alphabetical, with links to depth.

9 min read

One line per term; the link points at the doc that defines it in depth. Where a term is a metaphor word, the parenthetical is its bound referent (the metaphor-referent binding rule, concepts.md).

  • Advisory probe (AdvisoryProbeResult): a model-judgment signal (semantic drift, confidence score, pattern match) collected in AdvisoryProbes; Gate-3 supplementary evidence only, structurally never authoritative and never a fallback authority for a gated path (Phase 5). → Phase-5 decisions
  • ApprovalPath: the promotion ceremony for a proposal-eligible target: AutoRegression, FamiliarCoherence, HumanApproval, or HumanApprovalWithRationale; orthogonal to Channel and never derived from it. Protected targets cannot be promoted through this pipeline. → Approval paths
  • ApprovalPathKind: the field-free variant of ApprovalPath, used to validate the label round-trip; the display labels auto / familiar_review / human_review / human_required are a daemon wire contract, rejected at load on drift (Phase 5). → Phase-5 decisions
  • AuditTrail (strand) — provenance strand: first-seen timestamp plus a reference into the ward.audit event log. → channels-and-strands.md
  • Channel — (axis of load a thread must hold under): Deliberate, Forced, Serialization, or Mutation. → concepts.md
  • ContentHash (strand) — hash commitment to a protected surface's content; structural floor on Mutation and Forced. → channels-and-strands.md
  • Coven Cave: the cockpit UI that renders weaves, threads, and strands, and forwards proposal approvals (Phase 4, frozen 2026-07-17; OpenCoven/coven-cave#3223). It is not approval authority. See Phase 4.
  • coven daemon — the shipped Rust trust boundary; every client is untrusted for enforcement purposes (coven/docs/SAFETY-MODEL.md). → architecture.md
  • DegradeToProposal (verdict): a fray on a covered channel or a missing required strand kind; no direct write. The daemon may stage proposal-eligible targets, but MUST reject proposals touching protected surfaces. → Authority model
  • Delayed apply — the only permitted veto-window semantics: the proposal stages pending-visible, and the daemon writes only after the deadline passes with no veto and a matching live evidence replay; provisional apply (write-then-rollback) is forbidden (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • Deliberate (channel) — familiar-initiated, principal-gated compaction (promotion, dreaming, flush); the consented half of the two-compaction contract. → channels-and-strands.md
  • Descriptor — see PatternDescriptor.
  • Dreaming sweep — the consented, curated memory consolidation that flows through the gates as a proposal; contrast auto-compact. → concepts.md
  • evidence_replay_hash: Blake3 commitment on ProposalClassification over materialized diff and region evidence. Matching this field alone does not prove identity binding or final live authority; those remain daemon obligations. See replay requirements and implementation limits.
  • Fail-closed — every unknown (surface, thread, channel, panic) resolves to Reject; a conformance requirement per RFC-0001 §5.4, not a feature. → authority-model.md
  • Forced (channel) — runtime-initiated context compaction with no familiar cooperation available; governed by WARD-C1–C6. → channels-and-strands.md
  • Frayed (tension state): a recorded strand failure, repairable in place; MUST surface to the operator. It yields DegradeToProposal on a covered channel; an uncovered channel rejects. → Frayed threads
  • Gate 4 — RFC-0001 §5.4's final canonical diff check before apply; the real security boundary; MUST NOT be skippable. → authority-model.md
  • Gate-shaped receiver: what coven-threads is to the daemon: the typed entry point (validate_fail_closed) for identity-surface mutation requests. → architecture.md
  • Holds (tension state): no recorded fray or snap. A permit still requires writer binding, channel coverage, structural strand requirements, and acceptable contextual weave coherence. → Holds
  • IdentityInvariantDeclaration / IdentityInvariantSet — a typed declaration compiled from a retired Ward v0.1 identity string (name, person, pronouns, purpose, Coven membership), and the set that compiles declarations into predicate-authoritative checks; unsupported declarations fail closed, and the strings themselves are never authority (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • Loom — what Ward's four gates are in weave vocabulary: the fixed structure threads run through — gates are not threads. → concepts.md
  • ManifestEntry (strand) — membership in an external, Merkle-rooted hash manifest; the reference point that survives when the context window itself is under threat. → channels-and-strands.md
  • MaterializedDiff — the computed before/after state of every surface a proposal would modify; the only input a surface-region predicate may see (pure function, replayable at the Gate-4 deadline) (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • Mutation (channel) — the default write path: direct client mutation via the daemon; every thread holds under it or the daemon rejects. → channels-and-strands.md
  • MutationRequest: one attempted write carrying surface, writer, channel, and optional identity_context; it grants no authority of its own. → Requests and threads
  • PatternDescriptor — the derived, non-authoritative structural summary of a pattern predicate, for humans and tools; MUST NOT be gated on. → concepts.md
  • PatternPredicate — the authoritative coherence test over a weave's threads; enforcement gates on the predicate, never the descriptor. → concepts.md
  • Permit (verdict): writer bound, thread holds under the channel with required strands, and contextual weave coherence accepts the target. The daemon owns the authorized write and audit, not the library. → Permit
  • ProposalClassification — the append-only record produced at proposal intake: channel, affected surfaces and regions, path-tier floor, required ApprovalPath, and evidence_replay_hash; the type ships in coven-threads-core, the classifying scheduler is daemon-owned (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • Protected surface — an identity-bearing file or field (SOUL.md, MEMORY.md, identity fields) that threads bind to as a typed surface. → concepts.md
  • RegionEvidence — the output of SurfaceRegionPredicate::materialize: which region a diff touched, its tier floor, and deterministic replay bytes; feeds ProposalClassification and the Gate-4 deadline replay (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • Reject (verdict) — the mutation must not happen; always carries a typed, audit-legible reason. → authority-model.md
  • Repair — restoring a frayed strand in place (thread returns to Holds); a snapped thread instead requires a fresh authority ceremony. → authority-model.md
  • Serialization (channel) — export/import round-trip, format-mediated, Ward-external; governed by WARD-C7. → channels-and-strands.md
  • SerializationMarker (strand) — the C7 strand: format version + contract hash committing to the serialization contract; required on Serialization-channel threads. → channels-and-strands.md
  • Signature (strand) — signing-key commitment: provenance that survives even where hashes could be recomputed. → channels-and-strands.md
  • Snapped (tension state) — terminal severance; surface read-only until a fresh authority ceremony; maps to Reject. → authority-model.md
  • Strand — (fiber inside a thread: hash | signature | manifest entry | audit trail | serialization marker); a thread survives a channel iff its strands survive that channel. → concepts.md
  • SurfaceRegion — (typed semantic region above SurfaceId): a daemon-replayable area within or across surfaces (e.g. tool defaults, heartbeat behavior), classified from materialized diffs; region evidence rides on the proposal classification, not on new threads, and any promotion or reclassification applies forward only (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • SurfaceRegionPredicate — the authoritative extractor for a surface region: materialize is pure over a MaterializedDiff and gated on; describe yields a derived descriptor that is never gated on (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • SurfaceRegionRegistry — the daemon-held list of region predicates, run in stable registration order at proposal intake to populate ProposalClassification.affected_regions (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • Tension — a thread's standing under load: Holds, Frayed, or Snapped. → authority-model.md
  • Thread — (authority relationship: surface → writer); one per (surface, writer) pair; the object every gate check interrogates. → concepts.md
  • Two-compaction contract — Deliberate and Forced are distinct channels with distinct survival requirements; invariant #3 of the design. → concepts.md
  • Verdict — the gate's answer to a mutation request: Permit, DegradeToProposal, or Reject. → authority-model.md
  • VetoWindow — a delayed-apply window with a duration and a min_visible floor: the proposal must be visibly pending at least min_visible before the window may close, and nothing writes before the deadline (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • Ward — RFC-0001 §5: the normative spec (separation, tiers, gates, probes, audit) that coven-threads implements. → architecture.md
  • ward.audit — the single daemon-owned audit store: an append-only table inside coven.sqlite3 (spelled ward_audit in SQL). → architecture.md
  • WARD-C1–C6 — the six compaction-interlock invariants governing the Forced channel; canonical home: coven-grimoire Ward Layer Spec Brief §9. → channels-and-strands.md
  • WARD-C7 — survives-serialization: export→import yields equivalent tension state or fails visibly; numbered sibling of C1–C6, canonical in the same §9. → channels-and-strands.md
  • Weave — (enforced pattern of threads across a familiar or Coven); coherent iff its pattern predicate holds; the primary object Coven Cave renders. → concepts.md
  • weave_hash — Merkle commitment over a weave's threads in canonical (surface_path, writer_id) order. → channels-and-strands.md
  • WindowCloseReason — the explicit typed reason on every veto-window close event: applied, vetoed, evidence_diverged, revalidation_failed, or superseded; deadline expiry triggers revalidation and is never terminal by itself — there is no proposal_expired (Phase 5). → PHASE-5-APPROVAL-SEMANTICS.md
  • Writer — the authority-side endpoint of a thread: the identity proposing writes to a surface (WriterId). → concepts.md
Esc