AAC Federation
A single checkout on Signetify is not one system making one decision. It is the meeting point of several independently-governed ones — payments, fraud, tax, identity, model providers, and increasingly the buyer’s own agent — each with its own rules, its own regulator, and its own idea of what it is allowed to do.
The Authority Attestation Chain is how they meet without anyone having to trust everyone.
The four rules
- No contract, no interaction. Two parties that have not pre-signed a pairwise contract are denied by default — not warned, denied.
- Both sides must permit. An action happens only if both parties’ rules allow it. Agreement is the default; disagreement is a stop.
- Authority only narrows. What is permitted at a boundary is the intersection of both sides’ permissions — never the union. Crossing a seam can only ever reduce what you may do.
- Contracts are immutable until amended openly. No authority is negotiated at runtime. Amendments are themselves governed and recorded.
Look at it yourself
The point of the machinery is that you do not have to take our word for it.
Federation seams →
Every boundary where Signetify meets another governed system, and the pairwise contract that governs it — payment providers, the agent gateway, and the tenant-facing control planes.
Domain constitution →
The rules Signetify itself is bound by at every seam, and the global constitution it counter-signs as an adopting tenant.
Verify a posture envelope →
Paste a posture envelope and check its hash and signature. Verification runs entirely in your browser — nothing is sent to us, so our servers are not part of what you are trusting.
Signed contracts use FIPS-204 ML-DSA-65 with BLAKE3 digests, implemented natively in the Signet core. Contract sources are committed in this application at app/aac/pairwise-contracts/. Questions about a specific seam: contact us.