rfc(0001): v0.3.1 — definitional completions and cross-reference pointers

[BunsDev]

RFC-0001 v0.3.1 (draft patch)

Lands the two definitional nits from the v0.3.0 re-review round (threads-auu), plus the version-ref sweep.

Patch classification (§6.3): clarifications only — both items complete cross-references to obligations that already exist in v0.3.0 text. No new requirements; no conformance-suite changes needed.

Normative text (clarifying)

• §1.1 NEW-N-3 — standard admission path definition now names the §3.4 loop-origin authorization step the path already performs. Previously the definition enumerated attestation/audit/rejection but omitted origin gating.
• §5.6 NEW-N-1 — the evidence-field SHOULD-list now carries (MUST — see below) pointers on the three bullets upgraded by the following paragraph, and the principal_authorization bullet's condition now includes loop-originated memory_entry_admitted events (matching the MUST paragraph verbatim).

Version sweep → v0.3.1

RFC header/abstract/§6.1/§6.3/§10.1/footer + §11 changelog entry; CHANGELOG.md [0.3.1]; README badge; SPEC.md; docs/faq.md (4); rfcs/README.md (4, incl. tag URL); docs/ward-deep-dive.md (current claims only — historical "v0.3.0 closed two earlier gaps" kept); validators/validate.js banner+PASS strings; tests/conformance/README.md; validators/README.md. PROVENANCE.md and changelog history untouched.

Verification

• bash tests/conformance/run-conformance.sh → 5/5 positive, 10/10 negative, READY
• node validators/validate.js examples/minimal → PASS, banner/claim now v0.3.1
• residual v0.3.0 grep: historical references only

Stacking

Based on docs/conformance-version-sweep (PR #5) to avoid re-conflicting the version-sweep files. Retarget to main once #5 merges. Tag v0.3.1 at merge.

Gates: fresh-context Nova-lane review → Val approval. Do not merge before both.

Bead: threads-auu

[BunsDev]

Fresh-context Nova-lane review — verdict: PASS

Reviewed at pinned 78fc5d3 (diff vs base f1e58b0) in a detached worktree; base cleanliness verified first (710036e..f1e58b0 doesn't touch the RFC, so every normative delta is this PR's).

a. Patch classification — SOUND. §1.1 addition lifts its wording from unchanged §3.4 ("MUST additionally carry explicit human authorization before admission… regardless of attestation validity"); §5.6 annotations are pure pointers to a byte-identical MUST paragraph (confirmed against 710036e). Nothing smuggled; PATCH per §6.3 is correct.

b. Internal consistency — CONSISTENT. Word-by-word: the principal_authorization bullet now covers exactly the three MUST cases (ward_updated, principal_authorized_write, loop-originated memory_entry_admitted) — no over/under-inclusion. §1.1 step order matches §3.4's provenance-vs-authorization split.

c. Version sweep — COMPLETE. Residual v0.3.0 grep: historical positions only (CHANGELOG history, §11, deep-dive "closed two earlier gaps").

d. Conformance — GREEN. 5/5 positive, 10/10 negative, READY; validator banner+PASS strings now v0.3.1.

e. Changelog/§11 — ACCURATE.

Findings

• Blocking: none.
• A-1 (pre-existing, surfaced not created): the RFC defines falsifiable validation for source_attestation (§5.6 referent-resolution) but none for principal_authorization beyond presence-on-event. Candidate future MINOR / deep-dive open question. Not blocking a PATCH.
• A-2: root FAQ.md:88 stale "v0.1 compliance" anchor, missed by both sweeps (root FAQ.md ≠ docs/faq.md). Fixed in follow-up commit cfbd1bd — reanchored to "RFC-0001 conformance"; CHANGELOG updated.
• N-1 (pre-existing, out of diff): positive/05-tier-rich-ward/CASE.md cites "the v0.2 RFC frame" where §5.3 would age better.

Remaining gate

Val approval → merge (retarget to main first if #5 merges before this) → tag v0.3.1.

Bead: threads-auu. A-1/N-1 recorded there as follow-up candidates.

[BunsDev]

Superseded: PR #4 merged as f70c796 (v0.4.0) beneath this stack — main re-swept the version claims and rewrote the validator, so both this PR and base PR #5 are version-stale. The two definitional nits (§1.1, §5.6) were NOT absorbed by v0.4.0 and remain valid; re-cutting them against main as draft patch v0.4.1 per the new §6.3, carrying the surviving PR #5 salvage (negative/09 CASE.md 'warning only' falsehood, also unabsorbed). Nova-lane PASS on this diff (issuecomment-5041608668) transfers in substance; the re-cut gets a fresh review. Bead: threads-auu.