Learn / Wiring

Wiring vs. Surface, Projection, and Bundles

Each abstraction answers a distinct question in your architecture:

ConceptQuestion it answersRuntime role
SurfaceWhat may this feature read, and what may it send?Pure capability contract; no routing or subscriptions
Projection & MetadataHow do I read a slice, and what facts travel with it?Typed lens plus package-specific metadata (like fetches)
Bundle placementWhere does this child state machine sit?Routes wrapped child Messages to a Model path
WiringHow does a top-level integration join the runtime?Routes flat parent Messages, startup, and streams

Surfaces and Wirings meet in two places: Module collects both contracts to validate ownership, and Remote reads a Surface's projections (via metadata) to build its subscription fetches.

Failure and recovery

FailureWhere it surfaces
Two items share a keyPage.assemble throws naming the duplicate key
Two items claim one non-shared tagPage.assemble throws naming both claimants
Two items share a Managed Resource tagPage.assemble or resources throws
Hand-written config passed to completeType error on the hand-written property
Claimed wiring removed from assembleType error in exhaustive own update
route returns None for its own tagSilent drop; catch with message parity tests

Because the assembly output is derived purely from the list, fix the offending wiring line and re-derive the config.

Next