docs: reconcile enforcement-basis & profile wording (review follow-up)#44
Merged
Conversation
…ow-up) Consistency pass closing drift surfaced by a Codex review of the v0.3 draft — the four enforcement `basis` values (ruling, uncontested_ assertion, mutual_settlement, formula_split) landed across separate PRs and left a few enumerations and preconditions out of sync. No new normative behavior; only wording reconciled to the already-intended design. - §6.2.1: the 'trustless enforcement' precondition summary no longer presupposes an arbiter/asserter signature + bond + window (which excludes mutual_settlement and formula_split); it now states the basis-determined signature, the clause-determined bond, and the basis-determined window condition. The uncontested-path bond check is conditioned on 'where the dispute clause requires one'. - §9.4 (C1): the 'required signer is determined by outcome.basis' rule now enumerates all four bases, not just ruling/uncontested_assertion. - §9.4: the mandatory asserter/challenger bond rule is scoped to the optimistic profile; the small-claims OPTIONAL-bond line is made an explicit override (resolving its conflict with the uncontested-path bond check used on the small-claims happy path). - §7.4: amend-from-EXECUTED result state clarified — escrow persists, Thread re-enters EXECUTED once the adjusted escrow matches; no fresh execute needed. State-diagram amend edge annotated to match. - §6.2 (m5): coarse 'enforced' status no longer tied to 'a final ruling' — covers any §6.2.1 basis. - README: post-quantum selection criterion reworded to PQC *pairing* at the binding layer (the actual hard filter, always satisfiable), demoting account-level PQC roadmap to a graded nice-to-have — aligns with DLT_EVALUATION.md's graded-vs-hard split. - DLT_EVALUATION.md: stale 'SPEC §13.4 needs this caveat' note updated (the Hedera caveat is already there since the #6 change). - Appendix C: dropped a stray 'Appendix D' cross-ref from the #30 entry; added a changelog line for this pass.
This was referenced Jun 13, 2026
iret77
added a commit
that referenced
this pull request
Jun 15, 2026
Drop the -draft suffix now that the June 2026 review wave (issues #4–#30, PRs #32–#43) and the Codex consistency follow-up (#44–#46) have landed and a grounded Codex re-review converged clean. Bumps the SPEC.md front matter, README badge + status line, the roadmap Phase-1 note, and the Appendix C heading from v0.3-draft to v0.3. Status remains 'Draft (Concept) — not a final standard'; only the version identity is finalized. anp_version was already 0.3.
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 & why
Post-review consistency pass on the v0.3 draft, closing 8 findings from an independent Codex review. The four enforcement
basisvalues (ruling,uncontested_assertion,mutual_settlement,formula_split) and the small-claims / amend / milestone features landed across separate PRs (#33, #36, #40, #41), leaving a handful of enumerations and preconditions out of sync. No new normative behavior — every change reconciles wording to the design already intended; each finding was grep-verified against the text before adopting.mutual_settlementandformula_split. Now states the basis-determined signature(s), clause-determined bond, basis-determined window condition.outcome.basis" listed onlyruling/uncontested_assertion. Now enumerates all four bases.amend-from-EXECUTEDresult state was ambiguous (re-execute needed?). Clarified: escrow persists, Thread re-entersEXECUTEDonce the adjusted escrow matches — no freshexecute. Diagram edge annotated.enforcedstatus tied to "a final ruling" — now any §6.2.1 basis.Appendix C gains one changelog line documenting this pass.
Affected spec section(s)
§6.2 (m5), §6.2.1 (enforcement paths + precondition summary), §7.4 (amend state + diagram), §9.4 (assert-and-wait, bond rule, C1, small-claims), Appendix C; README.md; DLT_EVALUATION.md.
Trust impact
None. No trust root moves and no normative behavior changes — these are wording reconciliations so the four enforcement paths, the two dispute profiles, and the amend lifecycle read consistently across the document. The small-claims bond scoping makes the already-intended "optional bonds for micro-value Threads" survive a literal read of the §6.2.1 uncontested-path check; it does not change what any conformant implementation would do.
Checklist
docs-checkpasses