docs: scope the Channel::Deliberate promotion submission path

[BunsDev]

Scope for threads-xpo, the daemon-side promotion-write path the merged seam
contract (#25) requires. Documentation only — it authorizes no implementation,
settles neither decision it identifies, and closes no bead.

Every claim verified against origin/main of each repository on 2026-09-16.

Why scope first

threads-xpo reads as one missing feature: the daemon never constructs
Channel::Deliberate. True — and the smallest part of the gap. The surrounding
machinery (a scratch tier, a reachable promotion module, an admission event, a
resolvable provenance anchor) is also absent, and two of those are blocked on
decisions rather than effort.

The encouraging half is larger than expected

The daemon's decision/audit/approval path is already channel-generic end to
end — the staged envelope carries channel as a required field and ~20
downstream sites pass it through rather than re-deriving it. ward_audit
persists it and the census classifier already decodes "deliberate", so the
value round-trips today, with no schema change and no migration.

The Threads validator is complete: ChannelNotCovered, the FamiliarCoherence
ceremony §3.1 recommends, and every RejectReason/WindowCloseReason the
contract names all exist. No new rejection vocabulary is needed.

Two blockers that are decisions, not tasks

Provenance has no resolvable anchor. RFC-0001 §5.6 requires
source_attestation to resolve to an event in the append-only audit log. The
daemon generates neither candidate — ward_updated has no construction site,
principal_authorized_write appears only in an allowlist and a test. It calls
exactly two audit constructors. The substrate's Attestation is anchored to a
redacted artifact file, not the log, and nothing reconciles the shapes.

No thread holds under Deliberate. PROTECTED_CHANNELS serves as both the
woven holds_under and the pattern predicate's required floor, so a
Deliberate request rejects before anything else matters. Appending to that
const is the wrong fix — pattern.rs states Deliberate coverage is a
per-thread choice, not a floor requirement, so widening it changes weave
coherence for every protected surface.

Once those land, the surface is small: five literals and one const in
threads_gate.rs, a dispatch arm, a handler, and an admission emission site.

Two corrections to the 2026-08-09 record

• Not every construction site is Mutation — store.rs:3444 builds
  Channel::Forced for the WARD-C6 compaction row.
• The cmem-r59 cross-reference threads-5mn calls phantom is real. That
  check read .beads/interactions.jsonl, a passive export of a Dolt database,
  so absence from the export was never absence from the board.

Tracking

Filed threads-vd8 (provenance decision, P1), threads-7gw (coverage decision,
P1), threads-dr2 (daemon reachability, P2), and wired threads-xpo to depend
on all three. threads-55s carries a re-sequencing recommendation, deliberately
not applied — unblocking it needs its acceptance criterion split, which is
the maintainer's call.

Verified: agent-check.sh fast and full both exit 0.

🤖 Generated with Claude Code