Expand description
Plug-point trait surfaces.
Each module exposes one plug-point: an author-facing trait
(Plugin<Surface>), the #[repr(C)] vtable the boundary uses, an opaque
handle type, and the per-T static vtable factory wired through the
Tag<T> pattern from custom_data::custom_data_vtable and
actor::actor_vtable.
The infrastructure modules at the crate root (boundary, host,
manifest, macros, panic, loader) are deliberately separated from
these per-surface modules so the “how plug-ins work” mechanism stays
orthogonal to the “what plug-ins implement” surface set.
Modules§
- actor
- Actor plug point.
- book
- Boundary-owned handles for order book payloads.
- commands
- Order command envelopes and their boundary-owned handle wrappers.
- controller
- Controller plug point.
- custom_
data - Custom-data plug point.
- instrument
- Boundary-owned handle for
InstrumentAny. - option_
chain - Boundary-owned handle for
OptionChainSlice. - strategy
- Strategy plug point.