feat(spec): fact discipline at assertion time; review conduct rules - #963
Merged
Conversation
Three rulings from the walkthrough of the observed session: Facts are measured before they're asserted — a conduct rule in the discussion and research session guidelines, upstream of every document check: a fact-shaped statement about the codebase is run before it enters the conversation, because a conversation reasoned over a false premise stays poisoned however well the document is corrected later. The write-time and conclusion checks remain as backstops. Review is additive by default — a shared hard rule on all three review agents and the findings-application step: propose missing content, never rework sound content; wrong content (whatever wrote it) is removed or corrected in place, never explained — no correction notes, no mention of review, cycles, or process. Growth from pulling missed source material in is the loop working; the convergence flag now fires only when growth pairs with the churning trend — later cycles reviewing earlier cycles' writing — and drops the construction-under-delivered framing. Specifications are numbered — topic content lands as numbered ### sections with decimal #### subsections, and one-home references cite the section (§3.2) instead of restating it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
leeovery
force-pushed
the
spec-fact-discipline
branch
from
August 20, 2026 10:42
eb3dca7 to
9d04691
Compare
The numbering rule becomes the ruled scheme: sections are stable — the number is the address, not the position; wrong content edits in place, new knowledge appends (3.4 within its section, ### 7. at the end), and a mid-sequence slot-in renumbers carefully with every displaced number and § reference updated in the same approved edit. The document's furniture (Working Notes, an epic's Dependencies, Corrigenda) sits outside the numbering, and the § reference grammar lives once, in the one-home paragraph. The fact bullets open capitalised like their list siblings and settle the citation question — a figure attributed to a document is a citation; measure it before adopting it as this session's fact — and guidelines.md's Facts-vs-assumptions bullet carries the measured bar instead of the weaker label-it one. Rule 9 names the one-home carve (restating a homed fact is wrong content, not sound content) and the Working Notes exemption. The input agent's New-topic bullet knows sections are numbered; docs/research-and-discussion says the discipline starts at assertion, not review. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The escalation diagnostic was a hand-drawn templated fence the stack edited three times without adopting — the displays-are-engine-rendered rule applied at the first touch. It becomes render convergence-diagnostic: the judgment (trend classification, finding titles, root-cause hypotheses, stream labels) rides as the payload; the counts, the signed review-growth arithmetic, and every advisory flag — the four trend flags, spec-review's churn-growth warning and >25% growth note — are computed and drawn by the surface, wrapped through the callout helper. Section C of convergence-analysis.md is now a payload spec and a fetch; the file's last templated fence goes and its ratchet pin with it. Catalogue, usage banner, render suite (head/streams/signed growth/flags/validation matrix), and a simulation render land alongside. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Three rulings from the portal walkthrough discussion:
###sections with decimal####subsections (### 3. Sweep Scope/#### 3.2 …), and one-home references cite§3.2instead of restating. This is the shape the portal spec invented and Lee liked; it was never the prescribed norm until now.Gates: conventions lint + prose corpus + typecheck green; no engine or recipe changes on this branch.
Stacks on #962. Part 9 of the idea-40 stack.
🤖 Generated with Claude Code