v0.2.0: draft-laxsharma-pact-02, examples, terms profile and reference implementation - #11
Merged
Merged
Conversation
…ed Delivery Standalone repository fixes ahead of -02; the posted -01 text is unchanged. - pactcore: signatures_ordered() (sorted by the Section 9.1 normalized kid, ties by the raw kid, code point order); ECDSA signatures are emitted and accepted only in the low-S form, with the P-256 and P-384 group orders as constants. - facilitator: an unsorted signature set is refused as signatures-unordered (422, Section 13.1) after the signer-identity check, recorded as CHOICES C9; --problems exports the problem-type table for the registry section. - validate: the delivery_hash checks include the Delivery signature, as facilitator.py always did; identifier normalization and the assurance constraint are imported from pactcore (exact decimal, no 1e-9 slack), and each worked bound is checked from both sides one cent apart; V-07 is the draft's own vector (a trailing "/" only; Section 9.1 folds scheme and host, not the path); four checks added: the curve orders proved by computing n*G, and vectors V-21 (unsorted set) and V-22 (high-S). 66 checks become 71. - examples: verdict.json and challenge.json delivery_hash recomputed over the signed Delivery. -01 prints this digest only truncated, and the truncated value matches neither construction. - schemas: bid.schema.json and cfb.schema.json removed; -01 withdrew the sealed-bid procedure and its examples were already quarantined. - Makefile builds -01; both READMEs updated. Gates: tools/validate.py 71 passed; tools/measure.py five paths with money balanced, 24 refusals and 2 acceptances, the third-party-signer case still refused as unexpected-signer.
Revision -02 of the Internet-Draft, built from plan version 2 of 16 September 2026 after the dispatch@ thread. The document now specifies records, digests, signer rules, a state machine over a Facilitator-signed event trace, the five endpoints and the Merkle commitment; settlement terms are carried by reference to a profile (URI, bundle digest, opaque parameters) and the -01 terms become a non-normative example profile in Appendix A. Work Attestation is renamed Outcome Record; every response is a signed Contract Status; contract trees work across Facilitators; media types move to the vendor tree; no registries. Gates: xml2rfc text and HTML build clean (stream warning only); no line over 72 columns; idnits 0 errors, 0 flaws (remaining warnings are the vendor-tree media type names read as FQDNs and aligned columns in artwork); scope lint zero party-directed requirements and zero Facilitator rules about value. Digests in Section 15 and the figures are placeholders until the 0.2 examples exist; the validator count in Section 16 likewise.
Schemas for every -02 object (Status and Outcome Record new, attestation gone), the bonded-restitution profile bundle with seven vectors, examples minted from public seeds with real Ed25519 signatures, a Facilitator on the signed event trace with trees and lapses, the validator at 103 checks and the harness at ten paths, 40 refusals and 5 acceptances. Every digest in Section 15 is read from examples/ by the build. pactcore.jcs now formats numbers as RFC 8785 requires; it printed the float one as 1.0, so the -01 spec_hash and vtc_hash were never the digests a conforming canonicalizer computes. Vector V-25 pins it. Figures wider than 72 columns are folded per RFC 8792.
… profile bundle A mechanical cross-reference of the -02 text against the schemas, the reference implementation, the examples and the profile bundle, plus five read-only reviews, found about a hundred inconsistencies. All are fixed here. Text: Table 2 restructured (event, where recorded, members) with the Verdict admissibility rule stated once (DELIVERED or WINDOW_OPEN with none standing, or DISPUTED answering a pending Challenge); pending Challenge defined; instants pass when the clock reads them or later; clock-driven entries precede posted records; window-opened shares the `at` of the entry it follows; a named Verifier may answer its own Challenge; the manifest value form and the two profile facts in 12.1 restated; figures regenerated from examples/ with only signatures and parameters elided; 14.1 forbids jwk, jku, x5c, x5u, x5t, x5t#S256, crit and any unprotected header (V-26); signature-invalid and signature-missing are 400; retrieval and issued_at in the capability document; the -01 verification fund is posted by the Seller, following the -01 figure; "proof of nonconformance" replaces "fraud proof". Schemas: strict timestamps, uri patterns, evidence and proof members, facilitator document (issued_at, retrieval, settlement_bindings, endpoints), arbiter withdrawn. Code: pactcore rejects the forbidden header members and unprotected headers, norm() folds only scheme and host; facilitator implements the admissibility rule, the clock ordering, object-conflict on a differing child record, rollback on a profile invariant failure; profile admission order and Seller-posted fund; two admission vectors appended to the bundle (nine vectors); validate 107 checks; measure 44 refusals, 5 acceptances. Every digest was re-minted after the profile README gained its departures section, and mapped into the text by script.
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 this changes
Revision -02 of draft-laxsharma-pact, with the 0.2 schemas, the examples, an example terms profile and the reference implementation. The draft remains an individual submission with no standing: no working group has adopted it and the IETF has not endorsed it.
The document now specifies only the records, their digests, the signer rules, a state machine over a Facilitator-signed event trace, five endpoints and the Merkle commitment. Settlement terms are carried by reference: a profile URI, a digest over the profile bundle, and parameters the document never reads. The -01 liability member is gone and its figures become the parameters of the example profile in
profiles/bonded-restitution/. The Work Attestation becomes the Outcome Record, every accepted request is answered with a signed Contract Status,delivery_hashcovers the Delivery's signature, signature sets are sorted,algnames are the fully specified ones of RFC 9864, media types move to the vendor tree, and the two requested registries are withdrawn. Examples are minted from public seeds with real Ed25519 signatures, and every digest in Section 15 is read fromexamples/by the build.The -01 printed
spec_hashandvtc_hashvalues that no conforming RFC 8785 canonicalizer computes, because ours serialized the number one as1.0. Appendix B says so and vector V-25 pins the rule.Why
Two readers on dispatch@ observed in September 2026 that -01 made who owed whom the subject of the document. They were right.
Sections affected
All of them; Appendix B lists every change. Removed: the
bid,cfbandattestationschemas andexamples/attestation.json.python3 tools/validate.pypasses (107 checks withcryptography)xml2rfc --text draft/draft-laxsharma-pact-02.xmlbuilds