The active workstream is the RTTP & IQA dual-pillar protocol line. This is the GitHub organization of the RTTP & IQA Organization (standard-institution name); "Aicent Stack" is the community name for the same work.
RTTP — Resonant Time Transfer Protocol (rttp://) — derived intent addressing. IANA "URI Schemes" registry, Provisional, CRI 27. An address is computed, not assigned: rttp://<intent>.<pillar>.<root>/<action>, route shard = SHA-256(ASCII(canonical_authority))[:16] — no registry, no resolver, no network round-trip; malformed input is rejected, not normalized.
IQA — Identity Quality Assurance (iqa://) — offline-verifiable attestation. IANA "URI Schemes" registry, Provisional, CRI 28. Signed, leased standing carried in the AE-128 envelope; verification needs only the bytes — no key directory, no issuer, no callback. Expired is answered as expired, fail closed.
rttp resolves where & when; iqa states whether — and where the two agree, action begins.
- Specification:
draft-li-rttp-iqa-addressing— revision -02 (40 pp., 2026-11-01), Independent Submission, under ISE review. An Internet-Draft is a working document; it is not an IETF standard and carries no IETF endorsement. - Sites: rttp.com · iqa.org · blog.aicent.com · aicent-docs (curated article index)
| repository | what it is |
|---|---|
rttp |
the addressing scheme, Rust implementation (crates.io rttp · PyPI rttp · npm @aicent/rttp) |
iqa-org |
attestation standing and envelopes, Rust implementation |
iqa-mcp |
the primitives as MCP tools — offline, fail-closed, stateless |
conformance |
sealed, byte-replayable conformance run records and merged vector families; report pages at iqa.org/conformance/ |
interchange |
multi-party interchange work, co-drafted with external implementers |
aicent-docs |
the curated article index — 78 pointers into the reading line, never mirrored |
manifesto |
the founding text — narrative frozen, pointer page |
The full statement of the two pillars — wire formats, trust lease, refusal vocabulary, and the frozen pillar archives — lives in the organization profile README.
The earlier Aicent Stack story — the sovereign-AI organism, the Genesis releases (v1.2.x–v1.3.0-Alpha), the RFC pillar architecture (RFC-000 through RFC-015), and the register it was written in — is frozen exactly as published. It is preserved, unmodified, in the pillar repositories, on the pillar sites, and in the original organization README kept verbatim at FROZEN-GENESIS-README.md. No new claims are made under that narrative, and it is not the active workstream; the protocol line above is the only live engineering effort in this organization.
Frozen pillar repositories: epoekie · aicent · rpki · zcmk · gtiot · aicent-net · bewho · cmtn · sascar · itsun · moloon · dioon · picsi · MAXCAP · aicent-stack · aicent-demo
Apache-2.0 across the published repositories. The frozen pillar repositories remain the work of their authors, credited in-repo.