Reusable adapter-support primitives for Jacquard transport/profile implementers.

jacquard-adapter exists to hold generic ownership, mailbox, bookkeeping, and host-side observational helpers that concrete transports, profiles, and hosts can reuse without pushing runtime-support infrastructure into jacquard-core or jacquard-traits.

Adapter Support Surface

This crate owns transport-neutral adapter-side helpers such as bounded raw ingress mailboxes, unresolved/resolved peer bookkeeping, in-flight claim guards, transport-neutral endpoint conveniences, and host-side topology read-model projectors. These helpers are reusable support primitives and observational utilities, not shared world-model vocabulary and not behavioral trait boundaries.

Ownership

jacquard-adapter may own generic support primitives for adapter tasks and observational read models, but it must not:

• redefine shared world-model types that belong in jacquard-core
• publish capability or driver traits that belong in jacquard-traits
• encode transport-specific semantics that belong in concrete adapter crates
• implement router logic, engine logic, or canonical route publication
• stamp Jacquard Tick or OrderStamp internally

Concrete adapters may depend on this crate for ownership scaffolding, but canonical route truth, router progression, and transport-specific protocol behavior all stay outside this crate.

Jacquard

Adaptive routing for ad hoc shaped networks. Jacquard's world model and shared routing contract support layered engines with common route objects. First party support provided for several common routing strategies, with an extension boundary for external routing engines. Routing state is fully deterministic, enabling exact simulation replay.

Analysis

A deterministic simulator runs scenario matrices across all included routing engines. A generated report covers per-engine recommendations, failure boundaries, cross-engine comparisons, and diffusion calibration.

Development

# enter dev shell
nix develop

# build workspace
just build