[kikashy]

Closes #211.

What it adds

• States that several governing policies may apply, list order creates no precedence, and disagreeing coverage records refuse as invalid-coverage.
• Records the companion's v0.3.0 draft maturity, RFC 0023's Draft status, the base profile's 16-source and 16-section-reference maxima, and adoption of profile in the next format version.
• Leaves the second independently authored reader criterion open and identifies which separately authored implementations could satisfy it.

Checks

== check summary (dev.json) ==
handover: boundary 2 paths, shared 3 paths; see AGENTS.md "Before you hand over"
PASS local-paths 0s
PASS agent-docs 0s
sync-agent-docs: CLAUDE.md matches AGENTS.md
PASS diff-check 0s
FAIL repository-tests 49s, exit 1
Ran 250 tests in 48.826s
FAILED (failures=11, errors=2, skipped=2)
NOT RUN policy-prototype
NOT RUN policy-contract
NOT RUN policy-official-draft
== 3 passed, 1 failed, 0 skipped, 3 not run ==

The focused policy-official-draft check passed all 16 tests. The repository suite still requires RFC 0023 to be Accepted and pins the previous spec/policy.md bytes; aligning those release gates would change files outside this documentation-only PR.

Not in this PR

The frozen Policy 1.0.0 schemas, corpus, vectors, and readers are unchanged. Release-gate code, release metadata, live IAM, review and publication transactions, and current eligibility remain outside this PR.

A Codex session wrote the change.

[github-actions]

Carry needed from base commit 949444b.

[kikashy]

Review round 1 (OpenAI gpt-5.6-sol, effort medium, 2026-10-23), reviewed SHA 84df795

Clean-room clone at the head, probes under .review/; CI green before the round. The report verbatim:

Findings

• HIGH — rfcs/0023-policy-companion.md:8: despite Status: Accepted, the introduction still says acceptance awaits PR 218 and that the RFC remains Review. Lines 392–397 repeat the obsolete conditional disposition, while lines 379–381 still call adoption unresolved. Rewrite these passages as completed acceptance at draft maturity and resolve/remove that question.
• HIGH — web/build.py:362: the published Policy and RFC pages still describe and label acceptance as conditional; tests/test_site.py:263 and tests/test_site.py:274 enforce that stale presentation. Update the page metadata and assertions to show Accepted at draft maturity while retaining the draft and unpublished-artifact caveats.

Verified

• §4 and FAQ Q47 agree: duplicate identity refuses as invalid-coverage, list order creates no priority, and disagreement refusal is undefined for 1.0.0.
• RFC/index record the second independent reader as OPEN, one implementation reader so far, both readers Codex-assisted.
• The 16-source/profile-next-version statements match the amended decision.
• FAQ numbering is sequential Q1–Q48; changelog’s new line is accurate.
• spec/policy.md, releases/, conformance/policy/1.0.0/, schema/policy/1.0.0/, and the release-gate test are unchanged from main.
• Policy gate: 16 tests passed. Site suite: 56 tests passed. Probe and git diff --check passed.

merge: after fixes — 84df795

Disposition (the coordinator's)

#	Finding	Severity	Disposition
1	RFC 0023 still says acceptance awaits PR 218 and the RFC remains Review, in the introduction and the disposition section, and calls adoption unresolved	HIGH	Fix in this pull request by the same builder: those passages rewritten as completed acceptance at draft maturity; the question resolved; only lines the release gate does not pin
2	The site page metadata and tests/test_site.py assertions still label acceptance conditional	HIGH	Fix in-PR: the page labels and the assertions show Accepted at draft maturity, keeping the draft and unpublished-artifact caveats

The same reviewer re-reads the fixed head. Same vendor as the builder, not a cross-vendor claim.

[kikashy]

Re-read after the fix (OpenAI gpt-5.6-sol, effort medium, 2026-10-23), reviewed SHA b028d1a

The same reviewer, clean-room clone at the fixed head, probes under .review/; CI green. The report verbatim:

Findings: none.

Verified:

• RFC 0023 consistently records completed acceptance at draft maturity; the independent second-reader criterion remains OPEN.
• Site labels and assertions say “Accepted at draft maturity”; draft and unpublished-artifact caveats remain.
• No stale conditional-acceptance wording remains on the scoped RFC 0023 surfaces.
• Pinned policy specification, release, conformance, and schema paths are byte-identical to main.
• Policy gate tests: 6 passed.
• Site tests: 56 passed.

merge: yes
reviewed SHA: b028d1ae221fc0eef5d7b655363802f0fdb6712e

Disposition: both round-1 HIGHs are fixed; no further round. Merged on the standing rule. Same vendor as the builder, not a cross-vendor claim.

[github-actions]

🎉 Thank you for your contribution to Judgment Pack!

If you’d like another task, choose a path that interests you:

• Go runtime
• Judgment desk
• Gateway and provenance
• Python and evaluator experiments
• Specification and documentation