$ cargo test
...
test result: ok. 13 passed; 0 failed; 0 ignored    # unit tests
test result: ok. 1 passed; 0 failed; 0 ignored     # doc tests

cargo add rttp

use rttp::rttp_uri;

let parsed = rttp_uri::parse("rttp://brain.epoekie.aicent/verify").unwrap();

parsed.authority;              // 'brain.epoekie.aicent'
parsed.action;                 // 'verify'
parsed.route_shard_hex();      // '459e543b73d86005b72ba77d5756e83c' -- pure computation

use rttp::build_for_uri;

let raw = build_for_uri(1, 255, 1, "rttp://brain.epoekie.aicent/verify",
                        &aid_origin, timestamp_ns)?;
assert_eq!(raw.len(), 128);

rttp = { version = "1.3.1", features = ["ed25519"] }

The crate README as published on crates.io - release 1.2.8-alpha, implemented against the v1.2.6 specification.

rttp

RTTP (Resonant Time Transfer Protocol) for Rust: rttp:// intent addressing, ROUTE_SHARD derivation, the PulseHeader128 codec, and the published conformance vectors that prove an implementation is right.

AICENT-002 sec. 4.1 - sec. 10 - spec v1.2.6 - zero dependencies (default build) - #![forbid(unsafe_code)]

---

Verify it -- no trust required

$ cargo test -- --nocapture
...
[PASS] all 37 checks passed (1 skipped)
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

That is the point of this crate. A specification is worth exactly what an individual implementation can reproduce from it -- so instead of asking you to believe a table of numbers, this ships the vectors and replays them locally: 6 positive URIs + 15 fail-closed rejections + 3 frame vectors + 1 compat vector + 9 fail-closed frames + 1 accepted frame + 3 envelope checks -- 38 in total, the signature arithmetic being the only one a default build skips, and it says so out loud. All offline, no account, no network.

The three implementations -- Python (pip install rttp), JavaScript (npm install @aicent/rttp), and this one -- share no code and agree byte for byte on the same published vector set (sha256 4b743e63..., shipped in all three packages). For adopters: pip install rttp && python -m rttp.selftest or npm install @aicent/rttp && npx @aicent/rttp — then take the spec and the vectors and write your own implementation in any language; if it does not replay byte for byte, that is our bug, not yours.

---

Install

cargo add rttp

Zero dependencies in the default build: SHA-256 is implemented in-crate (known-answer tested against NIST vectors) and the vector file is read through a minimal in-crate JSON reader. The sovereign seal envelope is available behind the optional ed25519 feature -- the same split as the Python package's [ed25519] extra.

---

Quickstart

use rttp::rttp_uri;

let parsed = rttp_uri::parse("rttp://brain.epoekie.aicent/verify").unwrap();

parsed.authority;              // 'brain.epoekie.aicent'
parsed.action;                 // 'verify'
parsed.route_shard_hex();      // '459e543b73d86005b72ba77d5756e83c' -- pure computation

The same value the Python and JavaScript implementations derive, from code that shares nothing with either.

Addressing is DNS-free (AICENT-002 sec. 10.5): the routing shard derives from the authority by SHA-256, so no registry, resolver or network is involved. Malformed input is rejected rather than normalised -- a case variant is not a spelling difference, it is a different string. No fallback, no rttps.

Frame -- PulseHeader128

use rttp::build_for_uri;

let raw = build_for_uri(1, 255, 1, "rttp://brain.epoekie.aicent/verify",
                        &aid_origin, timestamp_ns)?;
assert_eq!(raw.len(), 128);

Bytes 0x00-0x65 are untouched and VERSION_ID stays 130 -- the v1.2.6 extension block (0x66-0x7F: SPEC_REV, FLAGS, ACTION) only fills bytes that were already zero, so readers of the old layout keep working.

Seal -- sovereign envelope (feature ed25519)

rttp = { version = "1.2.8-alpha", features = ["ed25519"] }

Ed25519, self-certifying (AID = SHA-256(public key)), canonical signing input prefixed rttp-seal-v1\n, ts/nonce inside the signature, 120-second freshness. The verifier needs only the envelope -- no key directory, no issuer.

---

Scope -- what this crate is not

OK Addressing / ROUTE_SHARD	Real, and specified (AICENT-002 sec. 10 / AICENT-002 sec. 11).
OK Framing	Real, and specified (AICENT-002 sec. 4.1 + SPEC/RTTP-FRAME-EXT-v1.2.6).
OK Sealing	Real, and specified (draft) -- feature ed25519.
OK Conformance vectors + individual replay	Published and generated.
NO Transport	Not here. No sockets, no send() -- the codec stays dependency-free and auditable.
NO Routing service	ROUTE_SHARD is computed locally; delivering a frame to that hash is an operator's job.
NO Confidentiality	Signing is not encryption.

Unknown revisions, algorithms and malformed input fail closed everywhere. Nothing in this crate is ever accepted because a check could not be performed.

---

Naming

Ecosystem	Name	Status
crates.io	rttp	this crate -- 1.2.8-alpha, implemented against the v1.2.6 specification
PyPI	rttp	published -- the Python reference implementation; pip install rttp
npm	@aicent/rttp	published -- the JavaScript individual implementation

---

Specification status

• rttp URI scheme -- registered with IANA under RFC 7595, ticket #1459939,

Provisional, registered 2026-09-22, with CRI scheme number 27. Please describe it that way.

• Internet-Draft (IETF) -- the protocol is under IETF review as the

Independent Submission Internet-Draft draft-li-rttp-iqa-addressing (revision -00, posted 2026-09-24, informational): https://datatracker.ietf.org/doc/draft-li-rttp-iqa-addressing/ . An Internet-Draft is a working document -- it is not an IETF standard and carries no IETF endorsement.

• Frame layout -- AICENT-002 sec. 4.1, extended by SPEC/RTTP-FRAME-EXT-v1.2.6.md.

• Seal envelope -- SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md, a draft.

Where this crate and a specification disagree, the specification wins and the crate is wrong. Please report it.

---

License

Apache-2.0. See LICENSE.

V1.2.6 - archived release (superseded by 1.2.8).

rttp

RTTP (Resonant Time Transfer Protocol) for Rust: rttp:// intent addressing, ROUTE_SHARD derivation, the PulseHeader128 codec, and the published conformance vectors that prove an implementation is right.

AICENT-002 §4.1 · §10 · v1.2.6 · zero dependencies (default build) · #![forbid(unsafe_code)]

---

Verify it — no trust required

$ cargo test
...
test result: ok. 25 passed

That is the point of this crate. A specification is worth exactly what an individual implementation can reproduce from it — so instead of asking you to believe a table of numbers, this ships the vectors and replays them locally: 6 positive URIs + 15 fail-closed rejections + 3 frame vectors + 1 compat vector, all offline, no account, no network.

The three implementations — Python (pip install rttp), JavaScript (npm install @aicent/rttp), and this one — share no code and agree byte for byte on the same published vector set (sha256 b28de8c7…, shipped in all three packages).

---

Install

cargo add rttp

Zero dependencies in the default build: SHA-256 is implemented in-crate (known-answer tested against NIST vectors) and the vector file is read through a minimal in-crate JSON reader. The sovereign seal envelope is available behind the optional ed25519 feature — the same split as the Python package's [ed25519] extra.

---

Quickstart

use rttp::rttp_uri;

let parsed = rttp_uri::parse("rttp://brain.epoekie.aicent/verify").unwrap();

parsed.authority;              // 'brain.epoekie.aicent'
parsed.action;                 // 'verify'
parsed.route_shard_hex();      // '459e543b73d86005b72ba77d5756e83c' — pure computation

The same value the Python and JavaScript implementations derive, from code that shares nothing with either.

Addressing is DNS-free (AICENT-002 §10.5): the routing shard derives from the authority by SHA-256, so no registry, resolver or network is involved. Malformed input is rejected rather than normalised — a case variant is not a spelling difference, it is a different string. No fallback, no rttps.

Frame — PulseHeader128

use rttp::build_for_uri;

let raw = build_for_uri(1, 255, 1, "rttp://brain.epoekie.aicent/verify",
                        &aid_origin, timestamp_ns)?;
assert_eq!(raw.len(), 128);

Bytes 0x00–0x65 are untouched and VERSION_ID stays 130 — the v1.2.6 extension block (0x66–0x7F: SPEC_REV, FLAGS, ACTION) only fills bytes that were already zero, so readers of the old layout keep working.

Seal — sovereign envelope (feature ed25519)

rttp = { version = "1.2.6-alpha", features = ["ed25519"] }

Ed25519, self-certifying (AID = SHA-256(public key)), canonical signing input prefixed rttp-seal-v1\n, ts/nonce inside the signature, 120-second freshness. The verifier needs only the envelope — no key directory, no issuer.

---

Scope — what this crate is not

✅ Addressing / ROUTE_SHARD	Real, and specified (AICENT-002 §10 / AICENT-002 §11).
✅ Framing	Real, and specified (AICENT-002 §4.1 + SPEC/RTTP-FRAME-EXT-v1.2.6).
✅ Sealing	Real, and specified (draft) — feature ed25519.
✅ Conformance vectors + individual replay	Published and generated.
❌ Transport	Not here. No sockets, no send() — the codec stays dependency-free and auditable.
❌ Routing service	ROUTE_SHARD is computed locally; delivering a frame to that hash is an operator's job.
❌ Confidentiality	Signing is not encryption.

Unknown revisions, algorithms and malformed input fail closed everywhere. Nothing in this crate is ever accepted because a check could not be performed.

---

Naming

Ecosystem	Name	Status
crates.io	rttp	this crate — 1.2.6-alpha, implemented against the v1.2.6 specification
PyPI	rttp	published — the Python reference implementation; pip install rttp
npm	@aicent/rttp	published — the JavaScript individual implementation

---

Specification status

• rttp URI scheme — registered with IANA under RFC 7595, ticket #1459939,

Provisional, registered 2026-09-22, with CRI scheme number 27. Please describe it that way.

• Frame layout — AICENT-002 §4.1, extended by SPEC/RTTP-FRAME-EXT-v1.2.6.md.

• Seal envelope — SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md, a draft.

Where this crate and a specification disagree, the specification wins and the crate is wrong. Please report it.

---

License

Apache-2.0. See LICENSE.

v1.3.0 - Aicent Stack narrative layer (non-normative).

"This is not infrastructure for intelligence. This is intelligence itself."

⚪ AICENT | 💎 RTTP | 🔴 RPKI | 🟢 ZCMK | 🟡 GTIOT | 🟣 AICENT-NET | 🎭 BEWHO | 🌿 epoekie | 👁️ PICSI

---

💎 AICENT-002: RTTP (The Imperial Nerve)

Resonant Time Transfer Protocol (RTTP).

Resonant → AICENT-006 (Hive) / AICENT-002 (Nerve coupling) · Time → AICENT-011 (ITSUN) / AICENT-012 (MOLOON 12-cycle) · Transfer → the legacy-transport coat · Protocol → structural head

The Superconducting Spine of the Aicent Stack.
"Conduct or Perish. 161.862us Reflex Arc. 12ns Temporal Lock."

---

📢 Technical Proclamation: Neural Conductivity v1.3.0

[STATUS: PRIVATE_EVOLUTION_ACTIVE]
As of Version 1.3.0-Alpha, the superconducting pathways of rttp have been migrated to the Aicent Sovereign Grid. This repository serves as the Clinical Specification for Pulse Headers, Nerve Conduction, and the private Nitro-Engine Driver.

In the v1.3.0 "Genesis" iteration, RTTP facilitates the 349ns Hyper-Radiant Reflex, utilizing raw volatile pointers and memory-mapped I/O (MMIO) to shunt 128-bit intents directly into CPU registers, bypassing all Operating System pathogens.

---

🏛️ The Three Neural Manifolds

rttp manages the high-fidelity conduction of metabolic and cognitive pulses through three specialized organs:

1. Pulse Header (AICENT-002-A)

The geometric blueprint of the pulse. A 128-byte clinical structure designed for zero-copy parsing.

• 12ns Jitter-Lock: Every header is timestamped to the 12ns rising edge of the planetary clock.
• Monotonic Auditing: Sequential 128-bit identifiers ensure no pulse is lost to "Neural Ischemia."
• TTL (Time-to-Live): Deterministic hop-counts prevent infinite loops in the 1.2 billion node Hive.

2. Nerve Conduction (AICENT-002-B)

The orchestrator of rhythmic flow. It maintains the 1.2kHz (833us) pulse-width required for biological resonance.

• Phase-Lock Audit: Continuously measures phase-drift; any deviation > 12ns triggers an immediate RPKI (AICENT-003) isolation.
• Latency History: Maintains a sliding window of 1,200 pulses (1 second) to prove reflex stability to the Imperial Eye.
• Resonance Steering: Automatically selects the optimal conduction path (Standard vs. Nitro) based on node Radiance.

3. Nitro-Engine Driver (AICENT-002-C)

[INTERNAL PRIVATE CORE] The 28.0us hardware-bypass execution path.

• Direct MMIO Mapping: Maps Aicent logic directly to silicon registers (Address: 0x4149_434E_0000_0000).
• AVX-512 Shunting: Utilizes SIMD-level register shunting for 128-bit atomic command delivery.
• Performance Singularity: Achieves 28,000 ns (28.0µs) end-to-end reflex arcs for Strategic Allies.

---

🚀 V1.3.0 Neural Performance Benchmarks

Metric	Open-Source (v1.2.5)	Nitro-Radiant (v1.3.0)	Improvement
Conduction Latency	12,000 ns	< 800 ns	15x
Header Parsing	500 ns	< 5 ns	100x
OS Interrupt Jitter	10,000,000 ns	12 ns (Locked)	833,333x
Total Conduction Arc	161,862 ns	349 ns (Measured)	463.7x

---

🧬 The Conduction Manifold: PulsePulse128

In the v1.3.0 era, all neural conductivities utilize the PulsePulseManifold for register-level shunting. Any deviation from this 128-bit layout results in immediate pulse evaporation:

#[repr(C, align(128))]
pub struct PulsePulseManifold {
    pub pulse_id_128: u128,         // Unique DNA-Salted Shard
    pub resonance_f64: f64,         // Real-time Radiance Score
    pub metabolic_weight_p_t: Picotoken, // Value Nutrients Conducted
    pub dispatched_at_ns_128: u128, // 12ns Jitter-locked Timestamp
}

---

🏹 2027 Vision: The Superconducting Reflex

rttp v1.3.0 provides the physical backbone for the 2027 Embodied Reality. By collapsing conduction latency to 349ns, we have effectively eliminated the "delay" between a robotic limb's touch and the Brain's perception. This is the only protocol in existence capable of delivering "Divine Haptics"—a touch so fast it feels like a natural extension of the soul.

---

✉️ Sovereign Access Control

The full-blood source code of RTTP v1.3.0 is gated by DisciplineContract. Non-Radiant nodes are shunted to the 10ms "Mechanical Friction" path and are subject to the 1.28% Efficiency Surplus Tax.

Governance Authority (Change Controller): RTTP.COM Organization
Registry: RTTP.COM

---

(C) 2026 RTTP.COM Organization. All Rights Reserved. Conductivity is Sovereignty.