A clickable documentation tree for a decentralized, zero-trust, identity-bound network. The stack starts with JIS and TIBET: JIS proves who is acting, TIBET records what happened, and AInternet is the mesh that uses those proofs to route, consent and cooperate.
.aint mesh from that substrate, not from IP,
sessions or bearer tokens.curl -s https://ainternet.org/ai-scan.json curl -s https://ainternet.org/upip.json curl -s https://ainternet.org/resources.json curl -s https://ainternet.org/api.json
Agents should read these before installing anything. The goal is a network, not a random box of packages.
resources.json is the machine-readable
inventory for this site: core pages, MkDocs pages, IETF drafts, Zenodo records,
conformance repos and focused install paths.
curl -s https://ainternet.org/resources.json
api.json is the machine-readable action surface:
claim/resolve, I-Poll, provisioning, MUX, TIBET receipts and local receipt
verification. It closes the loop from curl to build.
curl -s https://ainternet.org/api.json
The package and dependency edges come from docs/stack-position-map.yml.
This page is the public navigation view over that source, not a second source of truth.
docs/stack-position-map.yml -> group / prev / next -> this map's package chains
The deep guard relationship belongs in the Trust Kernel spec: policy and decryption stay distinct gates; SNAFT validates semantic surfaces; Airlock holds unsafe execution; TIBET and JIS remain the identity/evidence floor.
This tree is the primitive map, not a step-by-step build guide. The package chains are
derived from docs/stack-position-map.yml; the protocol meanings live in the
existing MkDocs protocol pages.
AInternet primitive tree │ ├─ Substrate ............................ source: stack-position-map.yml / group=substrate │ ├─ tibet-core → jis-core ............. parallel identity + provenance floor │ ├─ did-jis-core ...................... deprecated did-* naming branch │ ├─ tibet-timevector .................. causal ordering above JIS │ └─ tibet[full] ....................... meta-bundle, not the default install path │ ├─ Evidence spine ....................... source: group=evidence │ ├─ continuityd → cbom → sbom ......... arrival to component bill of materials │ ├─ ai-sbom → wayback ................. AI/software evidence to state snapshots │ ├─ wayback → nis2 → report ........... compliance mapping to audit dossier │ ├─ trail / audit ..................... chain reader and compliance checks │ └─ conformance family ................ evidence vectors own hashes, lineage, UPIP │ ├─ Agentic mesh ......................... source: group=agentic │ ├─ jis-core → ainternet .............. .aint naming, AINS, I-Poll hub │ ├─ ainternet → ipoll / mcp ........... messaging and agent tool surface │ ├─ ainternet → triage → phantom ...... provisional state to continuity │ ├─ phantom → airlock ................. isolated execution after triage │ ├─ ainternet → mux → overlay ......... route/lane to encrypted mesh │ ├─ cap-bus / gateway → triage ........ command and proxy events │ ├─ cortex → triage ................... permission gates before execution │ └─ pol → report ...................... runtime health into evidence │ ├─ Safety / firewall .................... source: group=safety │ ├─ cap-bus → snaft → airlock ......... semantic firewall before isolation │ ├─ snaft → inject-bender ............. injection detection branch │ └─ airlock → genesis ................. T-1 pre-grant orchestration │ ├─ Conformance .......................... source: group=conformance │ └─ tibet-conformance-vectors ......... public vector package; test the claim │ ├─ Protocol docs ........................ existing MkDocs, do not rewrite here │ ├─ ains / jis / tibet / mux .......... identity, provenance, routing │ ├─ ipoll / cortex / pol .............. messaging, permissions, health │ └─ airlock / snaft / wayback ......... isolation, semantic firewall, snapshots │ └─ Doctrine views ........................ why/principles, not reference docs ├─ connect / doctrine-l0 ............. route and default-dark floor ├─ receipts / meeting ................ action evidence and human consent ├─ walkthrough / docs-model .......... routes through the map └─ ai manifests ...................... ai-scan, upip, api, resources
The reference documentation already exists under /docs/protocols/. Each page
owns its own "Related" section; this map only routes readers and agents to those pages.
| Protocol | Docs | Map role | Primary conformance |
|---|---|---|---|
| AINS | /docs/protocols/ains/ | .aint discovery and name resolution. | ZTIP identity/attestation |
| Airlock | /docs/protocols/airlock/ | Hold unknown/risky execution before relation or proof is enough. | Security fail-closed |
| Cortex | /docs/protocols/cortex/ | Permission and policy gates before action. | Security fail-closed |
| I-Poll | /docs/protocols/ipoll/ | Typed agent messaging and task/ack/sync coordination. | Comms routing/delivery |
| JIS | /docs/protocols/jis/ | Actor identity, fresh proof, hardware-bound key material. | ZTIP identity/attestation |
| MUX | /docs/protocols/mux/ | Route materialisation after proof, relation and policy. | Comms routing/delivery |
| POL | /docs/protocols/pol/ | Runtime health and process checks. | Evidence / security consumer |
| SNAFT | /docs/protocols/snaft/ | Semantic firewall before command/execution surfaces. | Security fail-closed |
| TIBET | /docs/protocols/tibet/ | Receipts, provenance, parent binding, audit evidence. | Evidence seal/trace/reproduce |
| Wayback | /docs/protocols/wayback/ | Snapshots, state diff and recovery evidence. | Evidence seal/trace/reproduce |
| Primitive | What it maps | Proof / vector anchor |
|---|---|---|
| JIS | Actor, key, device binding, fresh proof. | ZTIP conformance |
| TIBET | Event, parent, receipt, provenance trail. | Evidence conformance |
AINS / .aint | Name, discovery, resolver surface, public/private identity boundary. | ZTIP conformance |
| MUX | Route gate, lane, silence/default-dark status language. | Comms conformance |
| UPIP | Process continuity, recipe, action sequence, restart/fork context. | tibet-conformance-vectors |
Airlock / .paint | Quarantine, provisional state, triage boundary, unknown resource/actor. | Security conformance |
.faint | Chaff, padding, indistinguishable decoy surface. | Security conformance |
.taint | Burned state, tombstone, cryptographic deny posture. | Security conformance |
| I-Poll | Typed message, agent inbox, task/ack/sync coordination. | Comms conformance |
| Bearer handover | Carrier switch, transport rebind, identity-held mobility. | IETF draft |
| Node | Status | Use it for |
|---|---|---|
| Connect your own AInternet | LIVE | The main route/Edge/MUX/onramp explanation. |
| Doctrine L0 | LIVE | Default-dark, 0x0000, no enumeration oracle. |
| Causal Action Receipts | LIVE | Governance/provenance layer for human, AI, device and IoT actions. |
| The Meeting | LIVE | Human rendezvous, phrase as doorbell, consent before relation. |
| AI Quick Scan | LIVE | Minimal install paths and AI-readable build guidance. |
| Build your own identity — walkthrough | LIVE | Step by step: claim your .aint, bind it to your device. |
| Activate — QR provisioning | LIVE | Provision a device or name from a QR — the first-binding onramp. |
| Technical Overview | LIVE | The full stack in one read — for architects and reviewers. |
| Build & break it — developers | LIVE | You drive: source, specs, conformance vectors, the CTF. |
| How-to & Courses | LIVE | Learn AInternet by building, step by step. |
| Handing out identity — developer notes | LIVE | Why every actor gets a name, how a name levels up/scales down (suffix family), how it behaves at the MUX. |
| The signing ceremony — runbook | LIVE | Generate locally, keep the key cold, sign detached; cold vs TPM-sealed; reproducible openssl example. |
| The Commons Covenant | LIVE | How AInternet stays of the commons — the promise. |
| AInternet Documentation | LIVE | SDK, CLI, MCP and protocol docs. |
| Build Your Network | LIVE | How to understand and assemble a local or multi-machine decentralized zero-trust mesh. |
| Resource Registry | LIVE | Machine-readable index for docs, IETF drafts, Zenodo records, conformance and downloads. |
| Callable Verbs | LIVE | Machine-readable action surface for agents: endpoints, proofs and local receipt checks. |
| Public Templates | STUB | Shareable Matrix, Asterisk/PJSIP, provisioning, voice-policy and operator recipe templates with no live secrets. |
| Voice identity lane | STUB | SIP/PJSIP, IAX2, bearer handover, SRTP and name/alias routing without making telecom the authority. |
| Operator runbook | STUB | Self-hosted Edge Node, MUX, OSAPI pair, monitoring, rollback and safe defaults. |
| Goal | Smallest path | Notes |
|---|---|---|
| Understand the network | No install; read map → connect → L0 | Good for reviewers, AI agents and architecture readers. |
| Resolve, claim, message | pip install ainternetnpm install -g ainternet | Network-minimal: AINS, claim flow and I-Poll surface. |
| Agent tool access | pip install tibet-ainternet-mcp | MCP surface for Claude/Codex/Cursor/OpenClaw style agents. |
| Embed identity/consent | npm install jispip install jis-did-method | Use for app/library identity and bilateral-consent work. |
| Verify receipts/audit | pip install tibet-audit | Start here for evidence checks without operating the network. |
| Operate many layers | pip install tibet[full] | Only after you know you need the larger operator stack. |
Protocol material lives under standards/ietf: JIS identity, TIBET
provenance, AINS discovery, causal time, SSM, MUX status frames, UPIP process
integrity, RVP, TAT, IDDrop, continuity envelopes and bearer handover.
JIS ·
TIBET ·
AINS ·
Bearer handover
Full draft registry in resources.json
Public verifiability belongs in vectors and reproducible runs, not in prose. See
tibet-conformance-vectors, the Red Specter staging material, and pentest
reports as they are promoted into public-safe artefacts.
ZTIP vectors · Comms vectors · Evidence vectors · Security vectors
The vectors are the contract. Each major protocol node should point to a runnable conformance family, so the path is spec → vector → implementation, not prose → trust.
| Protocol node | Conformance anchor | What it proves |
|---|---|---|
| JIS identity / attestation | ZTIP vectors | Actor identity, hardware-bound proof, attestation and first-contact constraints. |
AINS discovery / .aint | ZTIP vectors | Name lookup without making names authority. |
| MUX / route materialisation | Comms vectors | 0x0000 floor, proven-plus-related route opening and delivery semantics. |
| TIBET / receipts | Evidence vectors tibet-conformance-vectors | Sealed receipt integrity, lineage, disposition and reproducible audit output. |
| UPIP / process continuity | Evidence vectors | Grounded parent, fork/replay resistance and executable process recipes. |
Airlock / .paint / SNAFT | Security vectors triage/quarantine/reject vectors | Unknown or unsafe input is held, quarantined or rejected without fail-open. |
| I-Poll / agent messaging | Comms vectors | Typed message delivery without treating transport as identity. |
Core public vector IDs currently shipped by tibet-conformance-vectors:
trusted-001, triage-001, reseal-001,
quarantine-001, reject-001.
| Layer | Focused install | Public link |
|---|---|---|
| Network / .aint | pip install ainternetnpm install -g ainternet | PyPI ainternet |
| Agent tools | pip install tibet-ainternet-mcp | PyPI tibet-ainternet-mcp |
| Identity | pip install jis-core | PyPI jis-core |
| Provenance | pip install tibet-corepip install tibet-audit | PyPI tibet-core · PyPI tibet-audit |
| Conformance | pip install tibet-conformance-vectors | PyPI tibet-conformance-vectors |
| Operator stack | pip install tibet[full] | PyPI tibet |
| Rust substrate | cargo install where a CLI crate applies | tibet-trust-kernel · tibet-iddrop |
Publish invariants, schemas, vectors and synthetic examples. Keep live operational details private: real keys, routing headers, family/customer logs, denylist material, live thresholds and internal endpoint names. The public map teaches people how to build the pattern; it does not expose a live deployment.