Standards
Open standards edited by TunnelMind. Each is published as a versioned RFC-style document with a public comment window, a GitHub repository for proposals and objections, and a commitment to transfer editorial control to a neutral body once external adoption and standards-track recognition justify it. None is a paid product.
The reconciliation layer above all roots of trust. One verdict, keyed on an Ed25519 key, that reconciles what the key can prove about itself (its attestation tier across roots — a bare self-attestation or a RATS/EAT hardware token) against what the network has seen its subject do (Scry × Sigil × GhostRoute × Tracker). Surfaces over-claim contradictions no single root can. Ships as a self-verifying receipt with an RFC 6962 inclusion proof and witness cosignatures — verifiable offline, no call back to TunnelMind.
Open identifier standard for entities that observe, profile, or act against users, devices, and networks. Free resolution, permanent canonical identifiers, signed observations. CVE-style editorial model.
Open protocol for agent behavioral attestation. AIT capability tokens, witness-signed event chains, hash-linked attestation blocks, portable compliance receipts. Independent verification via reference verifier and TypeScript wrapper.
The wire shape every TunnelMind sensor speaks when submitting a first-party observation to the corpus. Compact-JSON canonicalization, Ed25519 signature over the record, producer-agnostic (Familiar today; commodity sensors, contribute-and-earn third parties, and future microkernel devices in future). Single canonical schema URL pins forward compatibility.
IETF RATS Entity Attestation Token (RFC 9711) serialization profile for ATAP receipts plus Scry cross-lens enrichments. Six TunnelMind-specific claims layered on top of standard EAT claims; ATAP receipt rides as a submodule with its original witness signature preserved.
A per-customer, append-only, hash-chained ledger of an agent’s verdict receipts, with Ed25519 signed checkpoints and regime-mapped signed exports (EU AI Act Art.12, DORA, NYDFS Part 500, HIPAA, PCI DSS, SOC 2) in signed_json / CSV / EAT / STIX. You pick the regime, retention, and format; an auditor verifies the chain independently against the published receipt key.