From 44216ec4175c923a46933d8ca0b2d2db27a55345 Mon Sep 17 00:00:00 2001 From: Serina Mcfall Date: Thu, 27 Aug 2026 12:28:14 +1200 Subject: [PATCH] docs(corpus): reconcile the confidence standard to #1313's documentation-standard Per Serina's decision on #1486: every sibling standard drafted alongside #1313 reconciles to it, including nodes that had already merged before the decision was recorded. This one (#1309, PR #1468) merged 2026-08-26. D10 -- H1 was "# Standard: `confidence`", code-formatting the topic. Changed to "# Standard: confidence", matching the plain-text convention every other reconciled standard uses. D1/D3 -- the normative sections were named "Requirements" and "Guidance" rather than "MUST" and "SHOULD". Renamed both, and updated the two in-body cross-references that named the old section by name. Recorded the reconciliation as a ledger entry attributed to #1486. Signed-off-by: Serina Mcfall --- launchpad/docs/corpus/standards/confidence.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/launchpad/docs/corpus/standards/confidence.md b/launchpad/docs/corpus/standards/confidence.md index 820fbe4e159..7a241325bdd 100644 --- a/launchpad/docs/corpus/standards/confidence.md +++ b/launchpad/docs/corpus/standards/confidence.md @@ -68,9 +68,12 @@ evidence: - statement: "An INFERENCE whose citation supports the subject of the claim but not the choice the claim makes is a decision in disguise, and belongs in TEAM_KNOWLEDGE attributed to whoever decided it." entry_class: TEAM_KNOWLEDGE provided_by: "launchpad-26/buzz#636 cross-model final review, relayed in the #1309 task brief: a second INFERENCE on AGENTS.md was rejected as laundering an unsourced policy choice into a class that made it look derived, and was reclassified to TEAM_KNOWLEDGE attributed to the issue's definition of done" + - statement: "Per Serina's decision on launchpad-26/buzz#1486, this node reconciles to #1313's documentation-standard: the H1 no longer code-formats the topic, and the normative sections are named MUST and SHOULD rather than Requirements and Guidance." + entry_class: TEAM_KNOWLEDGE + provided_by: "launchpad-26/buzz#1486, decided 2026-08-27" --- -# Standard: `confidence` +# Standard: confidence What the `confidence` number on an evidence entry means, when it is required, how an author picks one, and what a reader may conclude from it. @@ -145,7 +148,7 @@ it feels about right, and a reader — or a generated view, or a later agent — as calibrated and reasons onward from it. The number then carries more weight than anything that produced it. Everything below is aimed at that. -## Requirements +## MUST These are MUSTs. The first two are enforced mechanically. Requirement 3 is a MUST that no check reaches — see *Enforcement, and where it stops*. The rest are enforced by @@ -170,7 +173,7 @@ review, and a reviewer who lets one through has approved a defect. it to TEAM_KNOWLEDGE and name who decided. See *Reasoning versus deciding*. 6. **A number MUST NOT be moved because someone pushed back on it.** Re-verify the claim or reclassify the entry. Adjusting the number to settle an argument records agreement - where there was none. Re-encoding an existing value onto the band values in *Guidance* + where there was none. Re-encoding an existing value onto the band values in *SHOULD* is not a move under this rule, but do not tell yourself nothing changed: snapping to a peg preserves the assessment while it can and does alter the entry's **rank** against its neighbours, which is the one thing the number legitimately does. So the record must @@ -181,7 +184,7 @@ review, and a reviewer who lets one through has approved a defect. in the same edit.** A number that outlived the reasoning it rated is worse than no number, because it still looks current. -## Guidance +## SHOULD These are SHOULDs. Depart from them with a reason. @@ -384,7 +387,7 @@ edge to make first. **Expected but not verified when this node was written:** -- **The bands in *Guidance*, and the values `0.8` / `0.6` / `0.4`, are not derived from +- **The bands in *SHOULD*, and the values `0.8` / `0.6` / `0.4`, are not derived from anything.** They are a proposed convention for keeping values coarse, offered because unbounded precision is the observed failure. No study, no sample, and one authored INFERENCE in the corpus to look at. `0.8` was chosen to match that entry and the other