Define a profile
Declare the state box, authority epoch, ordering, visibility, retention, and reconciliation policy.
Application state with an explicit federation contract.
A proposed open protocol and Rust implementation for state boxes that declare authority, ordering, replication, visibility, retention, reconciliation, and freshness.
Each state class can carry its own authority, ordering, visibility, retention, and recovery rules.
Applications submit explicit transitions rather than relying on an undocumented global write path.
Reducers are intended to produce replayable state roots, projections, receipts, and bounded effects.
Relays deliver the representation permitted by a profile, with freshness, backpressure, and expiry treated as protocol concerns.
Checkpoints, replay, authority changes, and rejoin behavior are planned as inspectable acceptance cases.
Nix and NixOS roles are planned so multi-host experiments can be rebuilt and inspected.
The proposed flow keeps policy and evidence visible from submission through recovery.
Declare the state box, authority epoch, ordering, visibility, retention, and reconciliation policy.
Send a signed, typed transition through the application or relay boundary.
Run the deterministic reducer and record the resulting root, projection, receipt, or rejection.
Deliver only the profile-allowed representation while respecting freshness and resource bounds.
Use logs and checkpoints to inspect behavior, transfer authority when permitted, and rejoin a node.
This is a public proposal surface, not a claim that the planned implementation already exists.
Proposal / pre-implementation. Planned artifacts will be marked as they are published.
This page does not claim production deployment, adoption, audit completion, or performance results.
Design feedback is welcome when it is tied to a reproducible example or acceptance criterion.