Reframe TTP as the machine-isnad chain-trust protocol - #64
Merged
Merged
Conversation
None of what issue #46 asked for existed: not TrustChain, ChainActor, TransmissionLink, the trust roles, the verification levels, the classification table, chain continuity, or latent defects. The isnad primitive was implemented in src/isnad.mjs but the specification never described what it was for. SPECIFICATION.md gains a Chain Trust Model section carrying all of it — the layering across TTP, SCIM-RE, RAP, Execution Exchange, CortexTrace and ExecutionReceipts; thirteen chain primitives; eight trust roles with the normative boundary language that a TrustVerifier must not make execution decisions and a TrustValidator must not execute protected actions; seven verification levels from local evaluation to privacy-preserving proof; graded classification; seven chain-continuity states; eleven latent defects. The README leads with the framing sentence the issue specified and the layer table, so the distinction is visible before the specification. Two pieces are backed by code rather than left as prose. The classification vocabulary maps onto the nine execution responses already implemented — CLASSIFICATION_POSTURE, postureFor and withinPosture — so a response cannot step outside the posture its classification permits; answering TRUST_REJECTED with a reroute is how a graded protocol degrades into a boolean one that always says yes. TRUST_UNKNOWN is not neutral, and an unrecognised classification is treated as unknown rather than waved through. Chain continuity and latent defects are exported vocabularies checked against the spec. 199 tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Closes #46.
None of what #46 asked for existed. Not
TrustChain,ChainActor,TransmissionLink, the trust roles, the verification levels, the classification table, chain continuity, or latent defects. The isnad primitive was implemented insrc/isnad.mjs, but the specification never explained what it was for.SPECIFICATION.md→ new Chain Trust Model sectionTrustVerifierMUST NOT make execution decisions, aTrustValidatorMUST NOT execute protected actionsThe README leads with the framing sentence the issue specified plus the layer table, so the distinction is visible before anyone opens the spec.
Two pieces are backed by code, not left as prose
The classification vocabulary maps onto the nine execution responses already implemented, which is a better fit than it first appears:
TRUST_ACCEPTEDTRUST_ACCEPTED_WITH_CONTROLSTRUST_REVIEW_RECOMMENDEDTRUST_CONTRADICTEDTRUST_DEFECTIVETRUST_REJECTEDTRUST_UNKNOWNwithinPosture()enforces it: answeringTRUST_REJECTEDwith a reroute is how a graded protocol degrades into a boolean one that always says yes.TRUST_UNKNOWNis not neutral, and an unrecognised classification is treated as unknown rather than waved through.Chain continuity and latent defects ship as exported vocabularies checked against the spec.
199 tests.
🤖 Generated with Claude Code