NodeKind::Dissent exists — "A preserved minority position (machloket) — rejection never deletes" —
and MACHLOKET is catalogued with no gates. Nothing in the vault fixtures or the docs uses it, so it
is a kind without a workflow.
A first-principles peer that proposes alternative models produces exactly its content: the reframings
that were considered and not adopted. Those are worth keeping for the reason the Talmudic rule keeps
them — a rejected position that turns out to be right is recoverable only if it was written down, and
a record showing only what survived gives a false impression of how reliable the remainder is.
The grading spec says the same thing about deliverables:
§7.6: Findings that were tested and abandoned SHOULD appear in the deliverable. A report listing
only what survived gives a false impression of how reliable the remainder is.
Two pieces:
- A workflow: a rejected alternative becomes a
Dissent node linked to the claim it lost to,
rather than being dropped. This is mostly documentation and skill guidance, not code.
- Promote
MACHLOKET, possibly: a claim that reached review_ready through a contested
examination, with no Dissent recorded anywhere, may be a claim whose alternatives were never
written down. That is a weaker signal than the other gates and might be Unassessed rather than a
block — worth deciding before implementing.
Court Mode is the other half: a packet that renders what was considered and rejected is a stronger
artifact than one that renders only the surviving line, and §7.6 arguably requires it.
NodeKind::Dissentexists — "A preserved minority position (machloket) — rejection never deletes" —and
MACHLOKETis catalogued with no gates. Nothing in the vault fixtures or the docs uses it, so itis a kind without a workflow.
A first-principles peer that proposes alternative models produces exactly its content: the reframings
that were considered and not adopted. Those are worth keeping for the reason the Talmudic rule keeps
them — a rejected position that turns out to be right is recoverable only if it was written down, and
a record showing only what survived gives a false impression of how reliable the remainder is.
The grading spec says the same thing about deliverables:
Two pieces:
Dissentnode linked to the claim it lost to,rather than being dropped. This is mostly documentation and skill guidance, not code.
MACHLOKET, possibly: a claim that reachedreview_readythrough a contestedexamination, with no
Dissentrecorded anywhere, may be a claim whose alternatives were neverwritten down. That is a weaker signal than the other gates and might be
Unassessedrather than ablock — worth deciding before implementing.
Court Mode is the other half: a packet that renders what was considered and rejected is a stronger
artifact than one that renders only the surviving line, and §7.6 arguably requires it.