v1.2.6-Alpha · Open-Source Heritage Demo

AI Agent-Native
Resonant Time Transfer Protocol

Intent addressing — deterministic resolution

Intent addressing: a URI names what the subject is to do, not which machine to reach. An rttp URI is a claim of intent against an identified subject; the address is computed from the authority itself — no lookup, no TTL, no registry, no DNS. The rttp scheme is submitted to IANA (Provisional, pending).

RTTP is an application-layer transport protocol designed to enable sub-millisecond mounting and intent addressing of unstructured tasks across distributed agents.

Router Console

> [SYS] RTTP Node initialized at RTTP.COM

> [SYS] Semantic Routing Table: Loaded (3 Agents)

> [INFO] Protocol Version: V1.2.6

> [INFO] Max Concurrent Tasks: 128

// Waiting for task injection...

Semantic Hub

Coding_Agent

Langs: [Python, JS, Rust]

Design_Agent

Tools: [SVG, UI, UX, Figma]

Logic_Agent

Logic: [Audit, Math, Reasoning]

Scope of this demo — what is real, what is a placeholder

✓ Protocol layer — real. PulseHeader128 framing (RFC-002 §4.1), rttp:// addressing (§10), the URI → ROUTE_SHARD mapping (§11), Radiant Seal verification and semantic routing are all implemented, running, and covered by published conformance vectors.
⚠ Agent kernel — a placeholder in this public demo. The three agents run the simulated adapter: deterministic canned responses, not a model call. A real kernel plugs in through llm_adapter (openai / kernel) without touching the protocol layer.

What this demo proves is the transport, not the model behind it.

RTTP v1.2.6 — Published Packages

Pulse Frame

128 B

PulseHeader128 · RFC-002 §4.1

Conformance Checks

53 + 25

Python · JS & Rust replay the same 25 vectors

Core Dependencies

standard library only

verify it in one command — no trust required crates.io · rttp 1.2.6-alpha · pypi · rttp 1.2.6 · npm · @aicent/rttp 1.2.6

# Python — the reference implementation (zero dependencies)
$ pip install rttp
$ python -m rttp.selftest
[PASS] all 53 checks passed   # offline — no account, no network

# JavaScript — an independent implementation of the same vectors
$ npm install @aicent/rttp
$ npx @aicent/rttp
[PASS] all 25 checks passed   # shares no code with Python — agrees byte for byte

# Rust — the third implementation: zero deps, SHA-256 written in-crate
$ cargo add rttp@1.2.6-alpha
$ cargo test
test conformance::tests::shipped_vectors_replay_green ... ok   # exactly the 25 published checks

# Address an intent — DNS-free, pure computation (RFC-002 §10.5)
import { parse } from '@aicent/rttp';

const r = parse('rttp://brain.epoekie.aicent/verify');

r.authority        // 'brain.epoekie.aicent'
r.action           // 'verify'
r.route_shard_hex  // '459e543b73d86005b72ba77d5756e83c'  <- pinned by the published vectors

RTTP Protocol v1.2.6 Summary

128-Byte Framing

PulseHeader128 is a fixed, hardware-aligned frame (RFC-002 §4.1). The v1.2.6 extension block occupies 0x66–0x7F — bytes that were already zero — so older readers keep working, and VERSION_ID stays 130.

DNS-Free Addressing

An rttp:// URI derives its 16-byte ROUTE_SHARD locally by SHA-256 — no registry, no resolver, no network (RFC-002 §10.5). Malformed input is rejected, never normalised: fail-closed everywhere.

Self-Certifying Seals

The self-certifying profile signs with Ed25519 and your identity is AID = SHA-256(public key) — a verifier needs only the envelope: no key directory, no issuer. The managed HMAC-SHA256 profile serves closed deployments.

Switch Verbs — used by the live demo above

PUSH

Push subtasks to Agent

SYNC

Sync world model differences

OBSERVE

Monitor inference stream co-creation

HANDOVER

Transfer task control

Specification status: the rttp URI scheme is submitted to IANA under RFC 7595 (ticket #1459939, Provisional) and is under review — not yet registered. Frame layout: RFC-002 §4.1 + SPEC/RTTP-FRAME-EXT-v1.2.6. Read RFC-002 →

Install & Verify

$ npm install @aicent/rttp # JS · Node 18+ · zero deps

$ pip install rttp # Python 3.9+ · zero deps

$ cargo add rttp@1.2.6-alpha # Rust · zero deps · SHA-256 in-crate

$ npx @aicent/rttp # [PASS] all 25 checks

$ python -m rttp.selftest # [PASS] all 53 checks

$ cargo test # shipped_vectors_replay_green · 25 checks

Three independent implementations — crates.io rttp 1.2.6-alpha, PyPI rttp 1.2.6 and npm @aicent/rttp 1.2.6 — share no code and agree byte for byte on the same published conformance vectors. Apache-2.0. Versioning: one stack version, two channels — 1.2.6 on PyPI and npm, the pre-release 1.2.6-alpha on crates.io — same bytes, same vectors.

Want to contribute to the protocol standard?

Contact RTTP.COM Organization

AI Agent-NativeResonant Time Transfer Protocol