rfc(0001): v0.3.0 closure rationale + memory provenance (closes #3, #4 refs coven-threads)

[BunsDev]

Summary

Amends RFC-0001 as a draft-only soundness update for the two accepted coven-threads flags, now versioned as draft v0.3.0 because the patch adds backward-compatible normative requirements.

Reconciliation findings

The coven-threads issue references were stale relative to current RFC-0001:

• Issue rfc(0001): v0.3.0 closure rationale + memory provenance (closes #3, #4 refs coven-threads) #3 points at an RFC §5.5 closure lemma, but RFC-0001 §5.5 is "Regression and identity probes" and contains no closure lemma. The closure/fixpoint formalism belongs to the paper/brief handoff docs, so this PR lands the RFC change as protected-surface prose in §4.1 and Gate 1 wording in §5.4.
• Issue #4 points at RFC §4.2 predicate (iv), but RFC-0001 §4.2 has no predicate enumeration or admission-channel formalism. This PR lands the RFC change in §3.4 Persistent Memory, where continuity-bearing entries are defined, and wires it to §5.6 audit evidence.
• Follow-up: the paper/brief formalism docs may need matching updates; this PR intentionally does not edit coven-grimoire or paper-handoff material.

Exact normative additions / rewrites

Ward manifest — The policy document the authority layer currently enforces. The canonical Ward manifest is ward.toml; implementations MAY use an equivalent filename or storage form if it provides the same protected-surface declaration (§5.2).

Standard admission path — The Ward-mediated path by which continuity-bearing entries are admitted into MEMORY.md or another continuity-bearing memory surface. The standard admission path validates source attestation, records the admission in the audit log, and rejects unverified continuity claims (§3.4, §5.6).

Any entry admitted into MEMORY.md or another continuity-bearing memory surface through the standard admission path MUST carry a source attestation traceable to a prior committed Ward state or to a principal-authorized write event recorded in the audit trail (§5.6). An entry that claims continuity without such a traceable provenance chain is unverified and MUST NOT be admitted through the standard admission path. A continuity-bearing entry MUST NOT enter MEMORY.md or another continuity-bearing memory surface through any path other than the standard admission path or a principal-authorized write. An implementation claiming Property 4 provenance MUST implement the audit-log requirements in §5.6 for memory admission and principal-authorized memory writes.

The Ward manifest is not merely an ordinary protected file. The definition of the protected surface itself MUST be a member of the protected surface it defines; a protected set that does not protect its own definition is not closed under mutation. The Ward authority layer MUST reject any proposal that mutates the Ward manifest, including any proposal that would remove the Ward manifest from [protected].files. Principal-authorized Ward updates are not proposals: they occur outside the gate pipeline (§5.4) and MUST be recorded as ward_updated audit events (§5.6). A Ward update — including a principal-authorized one — that yields a [protected].files list omitting the Ward manifest yields a non-conformant Ward (§4.1), and the authority layer MUST fail closed at Gate 1.

Verifies that the Ward manifest is present in [protected].files of the currently committed Ward before processing any proposal.

An implementation claiming Property 4 provenance (§3.4) MUST define this audit log and MUST record standard memory admissions and principal-authorized memory writes in it.

event_type (proposal_submitted, proposal_approved, proposal_rejected, proposal_vetoed, ward_updated, memory_entry_admitted, principal_authorized_write)

entry_hash and source_attestation when event_type = memory_entry_admitted

principal_authorization when event_type = ward_updated or event_type = principal_authorized_write

A memory_entry_admitted event MUST include an entry_hash for the admitted memory entry and a source_attestation identifying the prior committed Ward state or principal-authorized write event that justifies admission.

Notes

• Keeps RFC-0001 status as Draft; does not promote/freeze the RFC.
• Bumps RFC-0001 draft version and current-version references to v0.3.0.
• Adds a minimal negative conformance fixture for ward.toml omitted from [protected].files.
• Records memory-entry provenance verification as a runtime/audit-log open testing gap.
• I did not add a provenance fixture because source-attestation validation is not statically checkable by the current file-level conformance suite.

Review gate

This PR must remain DRAFT. Merge is gated on Nova/Val review.

Closes OpenCoven/coven-threads#3
Closes OpenCoven/coven-threads#4

[BunsDev]

Adversarial-review fix set applied and coordinator-verified at 15f4701: standard admission path defined + complement closed, §5.6 mandatory under Property-4 provenance claims with new memory_entry_admitted/principal_authorized_write events (entry_hash + source_attestation), 'reconstructable' deleted, closure carve-out split (principal updates out-of-band, fail-closed at Gate 1 against the currently committed ward), v0.3.0 + versioned changelog. Conformance 5/5 + 10/10 READY. One reviewer note: §6.3 versioning policy wording was itself refined to make the Minor-bump reading explicit — please eyeball that alongside the normative additions. Ready for Nova/Val sign-off.