README: describe -01 as the current revision - #9
Merged
Merged
Conversation
The front page still described the -00: Vickrey award, contract channels, optimistic release, and a vtc_hash definition that -01 Section 6 reversed, sitting sixty lines above a note saying the opposite. -01 posted today, so the README now describes the draft that is live, keeps -00 as history, matches the validator's hash definitions, builds the -01 XML, and lists only what -01 cites. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…s covered them since -01 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
I wrote the previous draft of this file carrying the -00's composition story forward. -01 deletes the AP2 mandate binding and the A2A skill identifier outright: grep the text and the only A2A and AP2 matches are one reference entry and the acknowledgements, and the contract schema has no external task or mandate member. pact-escrow is likewise only a reserved registry identifier; no payload, verify or settle procedure is written for it. Co-Authored-By: Claude Fable 5.1 <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
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.
The README still opened with the -00 design. It listed the Vickrey award and contract channels as features, said release was optimistic by default, and gave the -00 vtc_hash definition (over the contract minus its signatures) sixty lines above a -01 note saying the opposite. The build line pointed at the -00 XML and "Read it" went to the -00 HTML.
With -01 posted today that is the wrong front page for anyone arriving from the Datatracker. This rewrite makes -01 current throughout: what the four things it specifies are, what changed from -00 and why, hash definitions that match what tools/validate.py checks, the 66-check breakdown, the -01 build line, and a related-work paragraph that names only what -01 actually cites. The old paragraph mentioned RFC 8693, ERC-8004 and a positioning section that -01 no longer has.
-00 stays in draft/ and examples/legacy-00/ so citations of it remain checkable.