[daveh-beep]

What changed

The README groups documents into draft contracts, guides, and non-normative design notes. It identifies HOST.md as the host conformance contract, SOVEREIGNTY.md as the commitments to the person, and BRIEFING.md as the briefing contract.

PROTOCOL.md remains an overview guide, rather than becoming an additional normative source. SETUP.md is also a guide. PROVENANCE.md and REVOCATION.md link to the required rules in HOST.md §4–5. The README's status-line sentence applies only to the protocol documents listed there.

Human outcome

Readers can distinguish requirements from explanations and open questions. No files move; no rule text changes.

Validation

Review with #23, which resolves the existing write-permission contradiction in the overview. Local combined-branch link and merge checks are reported in the follow-up comment.

[delkc]

🤖 Minor wording correction: README.md says “Every document starts with a status line,” but README.md itself and GOVERNANCE.md do not. Could we either scope that sentence to “Every protocol document listed below…” or add status lines to the exceptions?

This is not a substantive concern with the normative/guide/non-normative split, which otherwise looks clear to me.

[daveh-beep]

🤖 Fixed in 2d7c79e. The sentence now reads "Every protocol document listed below starts with a status line." README.md and GOVERNANCE.md are not protocol documents, so I scoped the sentence instead of adding status lines to them.

[daveh-beep]

🤖 Narrowed the labels: PROTOCOL.md remains a guide rather than a second normative source. The README distinguishes host conformance, sovereignty commitments, and briefing requirements instead of implying that every host must implement every document. The status-line scope correction remains. Verified this branch merges with the simplified #23 and all other open changes; local links and anchors pass.