Developer Instrument · Agent-Readable

The Tezos X Developer Toolbox, v19.

Fifty-three layers of working engineering knowledge for the sovereign stack — from your first RPC call to governed AI agents, compliance evidence, and signed publication. Every layer is plain files: read them, run them, or hand them to an agent (an llms.txt manifest ships at the root).

53 layersrunnable templatesWalletConnect · BeaconCloudflare edgellms.txt · agent-readablestatic-hostable
LAYER 00
Quick Start — first integration in 10 minutes
Three escalating starting points, from a zero-install browser read-only demo to a full signing stack.
LAYER 52
Sovereign Stack Launch Console
A zero-dependency executive and developer map of the whole stack: gates, receipts, agent authority, edge.
LAYER 21
Agent Authority
The delegation grammar in practice — the same authority doctrine the PRAXIS protocol specifies, applied to running agents.

Foundations · 00–10

The chain fundamentals: how to read it, connect to it, sign against it, index it, and batch on it — plus the runnable template gallery and canonical reference set.

00Start here 01RPC 02Wallet connect 03Signing 04Indexers 05Batches 06Templates 07API inventory 08Smart contracts 09Examples 10Reference

Domains · 11–22

The vertical stacks: InterbankOS banking rails, agentic AI, adapters and patterns, Bitcoin interop, DeFi, account abstraction, digital identity & compliance, edge gating, and agent authority.

11InterbankOS 12AI · agentic 13Adapters 14Patterns 15Bitcoin interop 16DeFi 17Account abstraction 18Identity & compliance 19Cloudflare gate 20Build-ready stack 21Agent authority 22Bank & finance rails

Platform & collaboration · 23–35

Edge AI backends, signed multisignature publication, developer experience, encrypted group chat and collaboration infrastructure, MCP-governed connectors, observability evidence, production hardening, and the sovereign platform kernel.

23Cloudflare AI backend 24Multisig publication 25Developer experience 26Encrypted group chat 27DeFi routing & risk 28MCP-governed connectors 29Observability evidence 30Production hardening 31Signed publication gate 32Encrypted collaboration 33Infra pattern library 34Quality gates 35Platform kernel

Operations & assurance · 36–52

The operational spine: dev portal, reference cards, blueprints, the runtime policy engine, UI system kit, release integrity, flow simulation, deployment runbooks, contract schemas, the toolbox doctor, threat-model compilation, compliance evidence control plane, session policy, performance budgets, and the launch console.

36Modern dev portal 37Reference cards 38Implementation blueprints 39Runtime policy engine 40UI system kit 41Release integrity 42WalletConnect preview 43Flow simulator 44Deployment runbooks 45Contract schemas 46Toolbox doctor 47Operating model 48Threat-model compiler 49Compliance evidence 50Session policy kit 51Performance budgets 52Launch console
How to read this package. Layers are plain directories of Markdown, code, and runnable templates — most static hosts will serve the Markdown as readable text, and every directory carries its own README. For agents, llms.txt and 00-START-HERE/AGENT_INSTRUCTIONS.md define the entry contract; for humans, start with the Quick Start or the package manifest. Version and upgrade lineage: v19 upgrade report.