RAHN v1.0.0 — Stable Architecture

[MHAlikhani]

RAHN v1.0.0 — Stable Architecture

Stable release · tag v1.0.0.

RAHN is a stateful execution architecture for evolving networks — it gives networks state, memory, causality, and verifiable evolution.

What v1.0 delivers

• Deterministic network state: interface-based topology, canonical serialization (format v2), content-addressed identity — byte-identical across machines and runs (test-enforced).
• Verifiable evolution: explicit recorded transitions, semantic diff, branches, fail-closed semantic merge, constitution-gated commits (including isolation constraints).
• Execution, safely: dependency-safe execution plans; simulation backend by default; opt-in isolated Linux namespace backend with structural host-safety guarantees.
• Memory: provenance-bearing observation records and asserted, status-labeled causal edges — with the honest boundary that edges are asserted, never inferred.
• Distribution: peer sync over content-addressed history with byte-identical merge-commit convergence; conflicts fail closed and persist.
• CI: rahn test with a deterministic report and exit-code contract.
• Stability contract (ADR 0019): semver via rahn-sdk (curated, doctested, surface-guarded API) and CLI contracts; IR format frozen for 1.x; stable extension model (backends, invariants, observations, sync).

Evidence

All claims are claim-status-marked in the white paper and stage reports (docs/research/stages/): single-machine measurements for state scaling (10–100k objects), observation ingestion, causal-graph operations, and sync transport; CI-validated namespace execution on a minimal scenario.

Explicit non-claims

No linearizability or cross-replica strong consistency; no causal inference or AI reasoning; no addressing/traffic control; no signed transitions or authenticated replicas; no binary-reproducibility verification.

Known limitations

See docs/research/limitations.md and docs/research/v1.0-review.md (carried-forward items: performance debts, single-machine measurements, minimal execution scenarios).

For downstream users

Build against rahn-sdk (see its crate docs). CLI contracts and the IR are stable for 1.x; breaking changes require MAJOR + migration notes.

Next

Post-1.0 development continues inside the extension model: addressing, traffic control, dataplane backends, signed transitions, log replication — each requiring its own ADR.

---

This discussion was created from the release RAHN v1.0.0 — Stable Architecture.