Transport & governed interchange

Charon

Active development

Moving information between systems requires clear contracts and a record of what happened. Charon’s governed data interchange foundation validates exchanges, applies defined policy and keeps transaction behavior traceable.

Current foundation

Validated exchange and transaction history.

The current deterministic library and command-line interface validate constrained profiles and apply allowlisted transforms and policy. A durable transaction journal records exchange activity. Fixture-based delivery proofs exercise these behaviors with controlled inputs and destinations.

Idempotency prevents a repeated request from becoming an unintended duplicate transaction. Bounded retry limits further delivery attempts; quarantine holds work that cannot proceed. Explicit replay records another pass through a transaction. This is transaction replay, separate from reconstructing an operational event.

Development direction

From fixture proofs to external transport.

Real external transports and broader integration proofs remain development work. Current validation establishes bounded library and CLI behavior; production authentication, secure cross-network delivery and deployment assurance are not yet established.

Architecture & independence

Wayfinder acquires and normalizes source evidence. Charon owns governed exchange and transaction behavior across system boundaries. Janus retains operational interpretation.

Charon’s current foundation also includes a bounded direct-bridge pattern that can be tested independently of a world model. That pattern is fixture validated; it does not require a mandatory Janus product stack.

How we describe development status