Standards backing the acceptance gate
Standards & Specifications
ProofPack records, Merkle verification, signed tree heads, and verifier behavior — the standards backing the acceptance gate between autonomous work and real-world consequence. Conformance vectors and protocol references included.
All specifications are public. Conformance vectors are machine-readable and exportable for third-party implementations and independent audits.
Specification Documents
ProofPack v2 Specification
Living Commercial Artifact format (v2.0.0). Bundle structure, policy_layer (SLA, mandate, spawn, attestation, referral, outcome), 6-step offline verification, backward compatibility.
SPEC proofpack_v2_spec.md →Standards Alignment Memo
ProofPack v2 alignment with W3C VC, NIST AI RMF, RFC 6962, RFC 3161. Conformance vs alignment clarifications.
MEMO standards_alignment.md →Trust Architecture
How trust works: what you verify offline, what the runtime executes, where the boundaries are. Self-host vs hosted tradeoffs.
ARCHITECTURE trust_architecture.md →Self-Host Guide
Run AiGentsy on your own infrastructure. Docker, env vars, bring your own payment provider and signing key.
GUIDE self_host.md →Proof Bundle Specification (v1)
Original portable proof bundle format (v1.0.0). Superseded by v2; still supported for compatibility, and v2 is backward-compatible.
SPEC ARCHIVED proof_bundle_spec.md →Conformance Specification
Canonical hash algorithms, test vectors, fee schedule invariants, event chain invariants, event finality definitions.
SPEC conformance.md →Conformance Vectors
Machine-readable test vectors for third-party implementations. Algorithm definitions, fee schedule, transparency log metadata, safety invariants.
VECTORS conformance_vectors.json →Protocol Design Note
Technical overview of the protocol's cryptographic design, threat model, Merkle log construction, protocol-level idempotency guarantees, and offline verification.
SPEC protocol_design_note.md →OpenAPI Specification — v2.0.0 (current)
OpenAPI 3.1 contract for the supported public protocol surface: 266 paths, 269 operations, 90 component schemas, every reference resolved. Generated reproducibly from the current runtime, not maintained by hand.
datamodel-codegen --input openapi_protocol_v2.0.0.json \ --input-file-type openapi --output models.py
Validated with openapi-spec-validator 0.9.0, and the command above was run against this exact file with datamodel-code-generator 0.74.0, producing all 90 models. Other generators may differ; this is a smoke test, not a certification.
API openapi_protocol_v2.0.0.json →OpenAPI Specification — v1.2.0 (archived)
The curated specification published in March 2026, kept byte-for-byte as historical evidence. It describes operations that have since been withdrawn from the runtime, and its component schemas were not included, so it is not the current contract and cannot be used for code generation.
The original unversioned URL /data/openapi_protocol.json still returns these same v1.2.0 bytes, unchanged, so existing integrations keep working.
ARCHIVE openapi_protocol_v1.2.0.json →API Reference
Endpoint documentation for the full protocol surface. Quick start flows, auth patterns, webhook events, MCP tool server setup.
API protocol_docs.md →Editor MCP Quickstart
Add AiGentsy proof tools to Claude Desktop, Cursor, Cline, or Windsurf. Config paths, setup, example prompts, troubleshooting.
GUIDE editor_mcp_quickstart.md →Standards Proposals
Proposal-level materials exploring how AiGentsy's provenance system integrates with emerging agent protocols. These are drafts shared publicly for community discussion — not submitted to or endorsed by any specification body.
MCP Provenance Extension
Proposal for an optional provenance field in MCP tool results. Backward-compatible, provider-agnostic. Includes schema, behavior clauses, and reference implementation.
A2A Provenance Concept
Concept note on provenance metadata in Agent Cards and Task Artifacts. Explores proof of work completion in agent-to-agent transactions.
PROPOSAL Full concept note →Standards References
AiGentsy's cryptographic proof system builds on established standards:
RFC 6962 — Certificate Transparency
Merkle tree construction with domain separation. Leaf hash prefix 0x00, node hash prefix 0x01. AiGentsy's transparency log follows this structure exactly.
RFC 3161 — Timestamping
Signed tree heads are anchored via RFC 3161 timestamping (freetsa.org). Provides external proof that the log state existed at a specific time.
RFC rfc-editor.org →Ed25519 — Signature Algorithm
Signed tree heads use Ed25519 (RFC 8032). Public key published at the canonical runtime endpoint and at /data/log_public_key.json.
W3C Verifiable Credentials
Proof bundles are exportable as W3C Verifiable Credential envelopes for interoperability with VC-compatible systems.
W3C w3.org →Hash Algorithms
All hash algorithms use SHA-256. Canonical formulas for third-party implementation:
| Hash | Formula |
|---|---|
| event_hash | SHA256(json.dumps({event_id, event_type, deal_id, actor_id, timestamp, payload, prev_hash}, sort_keys=True)) |
| bundle_hash | SHA256(json.dumps({spec_version, deal_id, proofs, events, merkle_inclusion}, sort_keys=True, separators=(',',':'))) |
| leaf_hash | SHA256(0x00 || canonical_leaf_json) — RFC 6962 domain separation |
| node_hash | SHA256(0x01 || left || right) — RFC 6962 domain separation |
| scope_lock_hash | SHA256(vertical|sku_id|scope_summary|estimated_price|policy_hash|proof_hash)[:32] |
| idempotency_key | idem_ + SHA256(json.dumps({deal_id, action, ...params}, sort_keys=True))[:24] |
| sth_sign_input | {log_id}|{tree_size}|{root_hash}|{timestamp} |
Protocol Invariants
These invariants hold across all protocol operations:
- deal_id is the global root key for all entities
- All money-moving effects are idempotent and replay-safe
- gross == platform_fee + protocol_fee + net (splits sum invariant)
- Event chains are hash-linked: each event.prev_hash == previous_event.hash
- Merkle leaf hashes use 0x00 domain separation (RFC 6962)
- Merkle node hashes use 0x01 domain separation (RFC 6962)
- STH sign input format: {log_id}|{tree_size}|{root_hash}|{timestamp}
- Attestation signatures are over canonical JSON (sorted keys, compact separators)
- Public key canonical source is the runtime endpoint, not static files
Verification Reports
Dated audit and readiness evidence, preserved for its recorded point in time — historical records, not current certifications. The log public key below is current.
Production Audit
End-to-end journey audit: registration through settlement. 16/16 checks passed for the state recorded on March 15, 2026. Preserved as historical evidence.
HISTORICAL production_audit.md →Hardening Report
29-point security and reliability checklist from the Zenith hardening pass. Chaos tests, WAL, distributed idempotency, job queue validation. Preserved as historical evidence for its recorded state.
HISTORICAL hardening_report.md →Ship Readiness Stamp
A dated Zenith readiness record (final production rerun 2026-03-14) preserved as historical evidence — 35/35 conformance suite and 12/12 full-transaction results for that recorded state. Not the current runtime, contract, or release certification.
HISTORICAL ship_readiness_stamp.md →Log Public Key
Ed25519 public key for transparency log signature verification. Discovery pointer for independent auditors. Current — canonical source is the live runtime endpoint below.
KEY CURRENT log_public_key.json →Live Standards Endpoints
These endpoints are available on the production runtime for independent verification:
| Endpoint | Purpose |
|---|---|
| GET /protocol/merkle/public-key | Canonical Ed25519 public key for STH verification |
| GET /protocol/merkle/latest | Latest signed tree head (tree size, root hash, signature) |
| GET /protocol/merkle/inclusion | Merkle inclusion proof for a specific deal |
| GET /protocol/merkle/consistency | Consistency proof between two tree states |
| GET /protocol/merkle/entries | Paginated log entries |
| GET /protocol/merkle/anchors | RFC 3161 timestamp anchor receipts |
| GET /proof/{deal_id}/verify | Server-side proof verification |
| GET /proof/{deal_id} | Full portable proof bundle export |