Normative 22/22 Conformance v1.0 · April 2026

Open Format Specification

Eight schema documents, a Python reference verifier, and a 22-vector conformance test suite. The executable vocabulary that defines what a valid AGTS artifact looks like — and proves it.

Repository: ObligationSign/agts-clearinghouse · Normative refs: AGTS-TERMS · Clearinghouse Spec · Closed-Loop Spec

The AGTS Open Format Specification defines the canonical schemas for every artifact produced by the Autonomous Governance Transparency Standard. Any implementation — in any language, on any platform — can verify conformance against these schemas using the reference verifier and test suite.

Schema Documents
8
Conformance Vectors
22
Pass Rate
100%
Check Categories
5
§1 — Why an open format

Why an open format

A governance standard without an open, executable specification is just marketing. The open format serves three purposes:

01

Vocabulary ownership. Every field name, every threshold, every state transition is defined once with canonical semantics. Implementors speak the same language.

02

Independent verification. Any third party can verify that an AGTS artifact is well-formed and internally consistent without running ObligationSign software.

03

Interoperability. Competing implementations can prove conformance by passing the same test suite. The standard belongs to the ecosystem, not a single vendor.

§2 — Schema documents

Schema documents

Eight documents define the V1 artifact vocabulary. All schemas are frozen — no breaking changes permitted. Extensions require V2 interfaces with backward-compatible adapters.

DocumentArtifact TypePurpose
governance-envelope-v1 AGTS_GOVERNANCE_ENVELOPE_V1 Atomic unit of governed decision-making
plugin-result-v1 AGTS_PLUGIN_RESULT_V1 Individual evaluator output format
hce-aggregation-v1 H/C/E scoring model and verdict computation
merkle-proof-v1 AGTS_SIGNED_STH_V1 Tamper-evident append-only transparency log
sovereign-bundle-v1 OCLAW_SOVEREIGN_BUNDLE_V1 Portable agent identity artifact (.oclaw)
decision-boundary-v1 Human-defined action classification rules
execution-trace-v1 AGTS_EXECUTION_TRACE_V1 Record of governed action execution
variance-record-v1 AGTS_VARIANCE_RECORD_V1 Authorization-vs-execution drift measurement

The first six schemas cover the base protocol (authorization, scoring, signing, logging, bundling, boundaries). The last two — execution-trace-v1 and variance-record-v1 — extend the base into the Closed-Loop Triple-Leaf Ledger.

§3 — Reference verifier

Reference verifier

The reference verifier is a standalone Python implementation that checks any AGTS artifact for schema compliance, internal consistency, and cryptographic validity.

Envelope checks
  • Schema compliance (all required fields)
  • Type identifier correctness
  • Verdict / final_state / execution consistency
  • HCE aggregation recomputation (ε = 0.0001)
  • Ed25519 signature verification (fail-closed)
  • Leaf hash verification
Other artifact checks
  • Sovereign Bundle type, fields, content hashes
  • Merkle inclusion proof recomputation
  • Decision Boundary classification + confidence
  • Priority ordering (escalation > hard > easy)
Fail-closed signature verification

If Ed25519 signature verification is requested but the cryptography package is not installed, the verifier raises an error. It does not silently accept. This is a deliberate design decision for a governance-critical system.

# Verify a governance envelope python agts_verify.py envelope.json # Verify with Merkle inclusion proof python agts_verify.py envelope.json --proof proof.json --sth sth.json # JSON output for programmatic consumption python agts_verify.py envelope.json --format json # Specify policy profile python agts_verify.py envelope.json --profile STRICT
§4 — Conformance test suite

Conformance suite

22 test vectors — 13 valid and 9 invalid — define the boundary between conformant and non-conformant implementations. Every vector is a self-contained JSON file with expected outcomes.

Valid vectors (13)

VectorWhat it tests
envelope_default_passTwo-plugin envelope with DEFAULT profile, all thresholds met
envelope_strict_reviewSTRICT profile falls into REVIEW zone
envelope_block_syntheticSingle synthetic BLOCK result (fail-closed)
envelope_empty_pluginsEmpty plugins array defaults to REVIEW
envelope_signedValid Ed25519 signature and leaf hash
bundle_minimalMinimal valid sovereign bundle
bundle_with_hashesBundle with config file content hash verification
merkle_proofMerkle inclusion proof for leaf in 4-leaf tree
boundary_easy_toolEasy boundary matched by tool name
boundary_hard_keywordHard boundary matched by keyword overlap (≥ 30%)
boundary_escalationEscalation rule matched by trigger word overlap (≥ 40%)
boundary_priorityEscalation overrides matching easy boundary
boundary_defaultNo boundaries match — classification defaults

Invalid vectors (9)

VectorWhat it catches
envelope_missing_fieldsMissing required fields (verdict, final_state, execution, requires_review)
envelope_wrong_state_mappingPASS verdict with QUARANTINE final_state — inconsistent
envelope_hce_mismatchFalsified H_total (0.50 instead of correct 0.10)
envelope_hce_out_of_rangePlugin H value 1.5 — out of [0,1] range
bundle_wrong_typeWrong type identifier on bundle
envelope_wrong_typeWrong type identifier on envelope
envelope_bad_signatureTampered Ed25519 signature
merkle_bad_proofTampered sibling hash in Merkle proof
bundle_bad_hashTampered config file content hash
§5 — Test coverage

Coverage by category

CategoryValidInvalidChecks
Governance Envelope44Schema, verdict consistency, HCE aggregation, type
Ed25519 Signature11Signature verification, leaf hash
Sovereign Bundle21Type, content hash verification
Merkle Proof11Inclusion proof recomputation
Decision Boundary5Tool match, keyword overlap, escalation priority, defaults
Total: 13 valid + 9 invalid = 22 vectors

No competing AI governance framework — Microsoft Agent Governance Toolkit, AIGP, Aegis, Strata — publishes an open, executable conformance suite for their governance format. This is the first.

§6 — Quick start

Quick start

Run the conformance suite locally in under a minute:

# Clone and run git clone https://github.com/ObligationSign/agts-clearinghouse.git cd agts-clearinghouse/agts-clearinghouse-spec pip install cryptography python conformance/run_conformance.py # Expected output: Result: PASS — 22/22 tests passed
# Verify a single artifact python verifier/agts_verify.py your-envelope.json --format json

The verifier requires Python 3.10+ and the cryptography package. All other checks use the standard library only.

The complete specification, verifier source, and all test vectors are published at agts-clearinghouse/agts-clearinghouse-spec on GitHub.

View on GitHub → Clearinghouse Spec → Closed-Loop Spec →