docs: position IOTA Trust Framework as candidate profile bindings#43
Merged
Conversation
Issue #30: the IOTA Foundation ships first-party components overlapping ANP's pillars — Notarization (Locked/Dynamic, exactly ANP's hash-on-chain/payload-off-chain model), Hierarchies (on-chain trust/ authority), under the Trust Framework umbrella. s13.2 documents them as candidate bindings for the profile's anchor primitive (Locked = terminal Objects, Dynamic = status-bearing anchors) and Trust-List resolution (s5.4), to be evaluated in the Phase-2 PoC with early Foundation engagement (s17). s15 positions them as primitives below ANP's contracting/mandate/dispute/settlement semantics, not competitors. Appendix C/D updated.
This was referenced Jun 10, 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
Twelfth and final PR of the v0.3 review wave.
Issue #30 — align with IOTA's first-party Notarization, Hierarchies, and Trust Framework: the IOTA Foundation ships building blocks that overlap ANP's pillars; ignoring them would mean re-implementing primitives the reference chain already provides — and missing the strategic signal that the Foundation builds adjacent functionality.
This PR documents the positioning and the evaluation mandate; the actual binding decision lands with the Phase-2 PoC, as the issue recommends.
Closes #30
Affected spec section(s)
§13.2, §15, §17 (Phase 2), Appendix C, Appendix D.
Trust impact
None today (documentation/positioning only). Flagged for the future: binding anchors to IOTA Notarization objects would make a first-party Alpha component part of the anchoring path on the reference profile — that trade-off (maturity vs. re-implementation) is exactly what the Phase-2 evaluation is scoped to decide.
Checklist
docs-checkpasses