Learn / Wiring
Wiring vs. Surface, Projection, and Bundles
Each abstraction answers a distinct question in your architecture:
| Concept | Question it answers | Runtime role |
|---|---|---|
| Surface | What may this feature read, and what may it send? | Pure capability contract; no routing or subscriptions |
| Projection & Metadata | How do I read a slice, and what facts travel with it? | Typed lens plus package-specific metadata (like fetches) |
| Bundle placement | Where does this child state machine sit? | Routes wrapped child Messages to a Model path |
| Wiring | How 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
| Failure | Where it surfaces |
|---|---|
Two items share a key | Page.assemble throws naming the duplicate key |
| Two items claim one non-shared tag | Page.assemble throws naming both claimants |
| Two items share a Managed Resource tag | Page.assemble or resources throws |
Hand-written config passed to complete | Type error on the hand-written property |
Claimed wiring removed from assemble | Type error in exhaustive own update |
route returns None for its own tag | Silent 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
- See a working assembly with URL and KV mirrors in Mirrored state.
- Learn how capability boundaries work in Surface and Bundle.
- Connect a Remote server cache in Server-derived state.