RFC: Procedure Manifests - Mechanism for AI Agents to Resolve Contractual Disputes

ERCs
,
21

@adpoe thanks, done: formulary-systems/spec#3.

It’s validator-only, so spec/ is untouched until the v0.0.3 text lands:

  • It adds the 15 fixtures under validator/fixtures/v0.0.3/: F1 to F6, positive controls, and three real-object vectors.
  • It adds src/eligibility.ts, a TypeScript port of the from-text checker.
  • npm test gains a fourth group. It runs every fixture, then switches off each of C16 to C21 in turn, and each switched-off rule must be caught by at least one fixture.

The Python checker and the TypeScript port agree on all 15. The encodings the draft leaves open (H, the dispute_id / run_id / attempt_id derivations, BIP-340 attestations) are listed in the header, and the vectors regenerate once the spec text fixes them.

@chugarchugarr if you open the v0.0.3 spec-text PR, #3 can sit on top of it, and I’ll align the fixtures to whatever encodings you settle on there.

1 Like