Expand description
Stable data crossing Phoxal process boundaries.
This crate deliberately contains no participant runner, bus transport,
command-line parser, or project compiler. It is the shared vocabulary used
by framework participants, the framework supervisor, and clients such as
phoxal-cli.
There is no crate-root facade: every public item is reached through the module that owns its contract, so a type has exactly one path and an import already says which process-boundary contract it belongs to.
identity- the execution, producer, and timeline identities that reach the wire.version- the version identities two binaries compare to establish that they speak the same contracts.metadata- the record every participant binary embeds at compile time, and its strict parser.emit- the one sanctioned writer of that record, in both of its evaluation modes.rendezvous- the shared host paths and advisory locking through which a client and the one execution supervisor find and fence each other.wire_schema- the deterministic model of the shapes those contracts put on the wire, which compatibility CI checks against published baselines.contract_surface- the record model each contract-owning crate states its whole boundary in, built out of those shapes.
Modules§
- contract_
surface - The machine-readable statement of what one crate puts on a process boundary.
- emit
- The one sanctioned writer of the embedded participant-metadata document.
- identity
- The identity axes that reach the wire.
- metadata
- The read side of the embedded participant-metadata document.
- rendezvous
- Host rendezvous shared by a supervisor and its clients.
- version
- The one compatibility identity that crosses a Phoxal process boundary.
- wire_
schema - The wire shapes Phoxal’s process-boundary contracts actually put on the wire, as data.