A construction project gets documented in a drawing set: title sheets, floor plans, elevations, mechanical schedules, electrical risers. Paxiom does the same. Each document below is a sheet in the binder. They were written for the build — to think on paper, to be reviewed, to keep the work honest. They're posted publicly because there's no good reason not to.
A founder's account of the agent economy, x402, the threat surface, and what Paxiom is building. Real math where math clarifies; plain explanation where it serves better. Read this first.
Open Document →Specifications for the five Phase 1 services. Architecturals, schedules, build sequence, risk register. Where to go for "how does Service 2 actually work" or "what's the build order across the gates."
Open Document →How AO routes verifiable Ethereum proof work across a distributed dispatcher topology. Components, message schemas, build order, benchmark expectations, and the boundary of the composability claim. The architectural foundation underneath the Phase 1 service catalog.
Open Document →What is recorded, where, and how to verify it independently of any Paxiom-operated infrastructure. On-chain events anchored to AO process state on Arweave. The architecture produces an audit trail as a byproduct of cross-chain coordination, not as a separate compliance overlay.
Open Document →Mechanical structure for recording, forwarding, and verifying audit events. Tooling that accelerates Phase 1 build by automating the audit cycle while preserving operator decision-making.
Open Document →The three-tier key architecture that secures everything the platform owns. Hot, warm, and cold tiers. Generation, signing, rotation, compromise response. Architecture is public; operational specifics aren't.
Open Document →Procedures for incident response and routine operations. Severity framework, first-response discipline, post-incident learning loop. The book to grab at 3am when something is broken.
Open Document →The next phase, planned. Healthcare and financial services as anchor verticals, ZK proofs on private inputs, compliance infrastructure, B2B commercial motion, the gates between Phase 1 and Phase 2 launch. A planning document, not yet a blueprint.
Open Document →The phased roadmap. What gets built first, what waits, what comes later, and why the order matters. The strategic map the rest of the drawing set hangs from.
Open Document →The Phase 0 substrate gates — HyperBEAM, sync committee verifier, and the Ethereum L1 reconstruction path — with acceptance criteria, evidence locations, and the exact operator commands or artifacts that close them.
Open Document →The documents shown are the public versions. Some operational specifics — particularly cold-tier key custody procedures, incident escalation contacts, and certain key rotation details — are intentionally not published. The architecture is open; the operator-only specifics live in private records. This is by design: a public surface that exposes attack-surface details would defeat the purpose of the architecture.
Read the Project Narrative. It explains the territory the platform exists in, why the bet is structured the way it is, and what the architectural choices imply. Everything else in the binder is downstream of the arguments made there.
If you have time for a second, read the Phase 1 Blueprint — it's where the abstract narrative becomes concrete services with concrete build sequence and concrete failure modes. The Operations Runbook and Audit Relay are the operator's view; the Key Custody & Identity blueprint is the security perimeter. The Build Map is the index of where everything sits in the longer arc.
The drawing set is generated and version-controlled. The public HTML files are the canonical version; revision history and source markup live in the project's GitHub repository. As documents revise, the previous versions are archived rather than overwritten — the audit posture extends to the documentation itself.
If a document references a sheet that doesn't exist yet, that's intentional. Future series — S-series for security audit posture, L-series for landscape and public surfaces, P-series for partnerships and standards engagement — will be added when the build reaches the phase where they're material.