docs(corpus): reconcile confidence.md to #1313's documentation-standard

[serina-mcfall]

Summary

Serina decided #1486: every sibling standard drafted alongside #1313 reconciles to its documentation-standard, including nodes already merged. This fixes confidence.md (#1468, already on launchpad): H1 no longer code-formats the topic, and the normative sections are renamed MUST/SHOULD from Requirements/Guidance.

Related issue

Closes #1507

Issue type

Task

---

Agent provenance

Field	Value
Harness / provider	Claude Code
Model	claude-opus-5[1m]
Session reference	N/A - harness exposes no run id
Initiating human	@serina-mcfall

Objective

Bring launchpad/docs/corpus/standards/confidence.md into structural conformance with documentation-standard.md's D1/D10 requirements.

Impacted components

launchpad/docs/corpus/standards/confidence.md

Approach and rejected alternatives

Minimal structural edits only (H1, two section headers, two in-body cross-references, one ledger entry) rather than a full pass over the document's content, since #1486 only requires structural reconciliation to #1313 and the document's substance was already reviewed and approved separately. Considered leaving the Enforcement, and where it stops section name as-is versus renaming to bare Enforcement: kept the descriptive suffix because documentation-standard.md's own divergence list only flagged the decision-references node's enforcement section (the one that never uses the word "Enforcement" at all), not suffixed variants — evidence.md's own accepted Enforcement, and where it stops heading confirms the suffix is conforming.

Verification

Command run:

cd /home/serina/Launchpad/buzz/__worktrees/fix-1468-confidence-reconcile
python3 launchpad/project-intelligence/corpus/validate.py
python3 -m unittest discover -s launchpad/project-intelligence/corpus/tests -p "test_*.py"

Raw output:

UNVERIFIED  corpus-agents: evidence entry 1, citation 1: is a commit reference, which names no openable file
UNVERIFIED  corpus-readme: evidence entry 1, citation 1: is a commit reference, which names no openable file
UNVERIFIED  corpus-standard-confidence: evidence entry 1, citation 1: is a commit reference, which names no openable file
UNVERIFIED  corpus-standard-decision-references: evidence entry 1, citation 1: is a commit reference, which names no openable file
PASS  corpus validation found no errors; 4 item(s) reported unverified

............................FAIL  corpus root does not exist: .../tests/fixtures/does-not-exist-anywhere
...................................................
----------------------------------------------------------------------
Ran 79 tests in 1.354s

OK

• Tests or checks were run and the raw output is pasted above
• The diff is confined to the scope of the linked issue
• No secrets, keys, tokens or hostnames were added to tracked files

Not verified

No cross-model (Codex) review pass was run — Codex is out of credits (#1467), tracked separately. This is a small, mechanical, structural-only change (heading renames and two prose cross-references); given the scope, a same-model review was judged sufficient rather than blocking on the unavailable gate.

Security implications

None. Documentation-only change to corpus standard headings and cross-references; no code, secrets, or executable paths touched.

Escalations

None.

[tucktuck101]

Review — reconcile confidence.md to #1313's documentation-standard

Clean. I read the pre-image and post-image in full (git show HEAD~1:... vs the worktree file)
and confirmed no normative rule changed. The diff is:

• # Standard: \confidence`-># Standard: confidence` (H1 de-code-formatting)
• ## Requirements -> ## MUST, ## Guidance -> ## SHOULD — and both section ledes
  already read "These are MUSTs." / "These are SHOULDs.", so the rename records what the
  sections already were rather than reclassifying anything
• two cross-references updated to follow the rename (*Guidance* -> *SHOULD* at the MUST-6
  carve-out and in the expected-but-not-verified list)
• one added TEAM_KNOWLEDGE evidence entry recording the reconciliation decision, correctly
  classified and attributed

No MUST was added, removed, renumbered, or reworded. No band value moved. No enforcement claim
changed.

On editing a merged standard in place: I checked before treating it as a violation, and it is
not one. There is no supersede-not-edit convention covering corpus nodes — ADR-0034 governs the
knowledge.* contract and ADR-0043 governs upstream files; neither applies. Reconciling in
place is the remedy #1507's definition of done specifies for exactly this class of drift.

Low — two orphaned "Requirements" cross-references

confidence.md:96 ("...and Requirements 2 and 3 describe how the value itself...") and :108
(drift-surface table row) still name a section that no longer exists after the rename. The
patch correctly updated both Guidance references and left these two. They still read as item
identifiers rather than section references, so meaning survives — but a reader searching for a
"Requirements" section now finds none, and removing exactly this ambiguity is the patch's
purpose. MUST 2 and 3 closes it. Not worth another round trip on its own.

What is correct

• Presentation-only change, verified line by line against the pre-image.
• The added evidence entry is the right class (TEAM_KNOWLEDGE, provided_by a decision) rather
  than dressing a decision up as derived.
• Frontmatter unchanged; node still validates.
• No AGENTS.md hunk — correct for this PR, since it registers nothing.
• CI green at head (latest run per check).

Approved.

Reviewed by tucktuck101's review lane. The before/after comparison is my own.