GitHub organization of the RTTP & IQA protocol line — derived intent addressing and offline-verifiable attestation for autonomous agents.

Maintained as the standard-parts line of the RTTP & IQA Organization (standard-institution name; "Aicent Stack" is the community name for the same work).

RTTP answers where an agent is reachable and until when that answer holds. An address is not assigned; it is derived:

rttp://<intent>.<pillar>.<root>/<action>

• The route shard is SHA-256(ASCII(canonical_authority))[:16] — pure computation, no registry, no resolver, no network round-trip.
• Names are hashes; attestation vouches. The scheme never asserts who is trustworthy — it makes claims checkable.
• Malformed input is rejected, not normalized: a case variant is a different string, not a spelling difference. No fallback transport, no rttps.
• The wire format is a fixed 128-byte pulse header (PulseHeader128), extension-block backward compatible.

IQA answers whether a claim is currently trustworthy. It carries signed, leased state in a fixed-layout envelope:

• AE-128 envelope: a 128-byte, fully specified frame — algorithm, lease expiry, shard, attestation, organ, nonce, standing.
• Standing is a closed set carried in one octet; verdicts are organ-relative and do not transfer.
• Offline by construction: a verifier needs only the envelope bytes — no key directory, no issuer, no callback. Expired is answered as expired, fail closed.
• Leases make trust temporal: freshness is part of the artifact, not a side-channel promise.

The two are deliberately separate: derivation is not identity, and a proof of identity is not an authorization. Conflating them is the design error this line exists to prevent.

rttp resolves where & when; iqa states whether — and where the two agree, action begins.

Three independent implementations — sharing no code — agree byte for byte on the same published conformance vector set:

Every package ships the vectors and replays them locally: positive URIs, fail-closed rejections, frame vectors, and the envelope check — all offline, no account, no network. Where an implementation and a specification disagree, the specification wins.

• Aicent-Stack/conformance — runners and sealed, byte-replayable run reports for the LFDT Agent-Authority-Conformance lab (lease-revocation-axes family, revisions 2 and 3): an independently written runner, author-produced records under the lab's classification, independently reproduced on 2026-10-29 — each record sealed and addressable.
• Sealed records resolve through the public resolvers: rttp://… → rttp.com/open/ · iqa://… → iqa.org/open/.
• Aicent-Stack/interchange — field mappings and common formats co-drafted with external implementers; one folder per collaboration, no party's brand in any name.
• Aicent-Stack/iqa-mcp — IQA attestation primitives as MCP tools: derived intent addressing + AE-128 envelope verification. Offline, fail-closed, stateless.

rttp.com — RTTP scheme, frame, resolver · iqa.org — IQA envelopes, conformance reports, sealed artifacts · blog.aicent.com — design notes and readings, bilingual.

rttp (Rust crate) · iqa-org (Rust crate) · conformance · interchange · iqa-mcp

The repositories below preserve the earlier (2026-04/05) architecture exploration published under the original Aicent Stack narrative (v1.2.x–v1.3.0). They are unmaintained and kept for provenance; the protocol mainline above does not depend on them. Each carries a status banner at the top of its README.

Apache-2.0 across the published repositories.