Components · Handoff
Handoff Packet
The record a new owner starts from: goal, state per axis, what was observed, what is not confirmed, assumptions, decisions, what was executed, open loops, the authority they need. Built from contract fields; there is no summary to trust.
Overview
This compact fixture shows the renderer inside the shared contract. The richer gallery below exercises additional states without changing the resolver’s authority.
States
Each state is live and resolved from contract fields. The indicator checks both the complete Representation Plan and the rendered DOM. Missing coverage is reported separately.
| May claim | Must not claim |
|---|---|
| The state as of the packet’s revision. | A summary’s word for it. |
Anatomy
01 · Snapshot identityRevision, policy, resolver and next owner establish the boundary.
02 · Contract stateObservations, decisions, effects and open loops are separate fields.
03 · Remaining obligationsUnobservable checks and required authority travel with the work.
The live specimen above follows these regions in reading order. Change a state to inspect the same anatomy under a different work condition.
Usage and avoid
- Let the receiver read “this is done, this remote outcome is unknown, this action is allowed with your authority”.
Avoid
- Don’t hand over “the last agent said it was nearly done”.
When not to use
Status reports for stakeholders; those are projections of the packet.
Contract
A component without this contract may wear Lyotic’s style; it does not implement Lyotic.
| Semantic inputs | The EBSRC input and plan; the next owner |
|---|---|
| Allowed states | Any Case state |
| Forbidden states | Free-text summaries as the record (INV-18) |
| Evidence requirements | Every row comes from a contract field |
| Action scope | Not interactive |
| Meaning of authority | Lists the authority the next owner needs, and what their role allows |
| External effects | None |
| Verification conditions | Remaining verification is an open loop |
| Failure and recovery | Inaccessible evidence re-evaluates the claims that relied on it |
| Transitions | The handoff mode of the Shell |
| Accessibility | An article with headed rows |
| Observable events | None |
| Test conditions | INV-18; handoff.packet |
Live boundary check
Use “Test a forbidden control” below the gallery. The checker receives an intentionally invalid, detached specimen and reports INV-03. No unsafe control is inserted into the live Work Case. This tests a boundary rather than teaching an unsafe success state.
In the Work Case
The same renderer below runs inside the existing anchored Work Object Shell. These are illustrative fixture states, not live business operations.
Accessibility
Keep action names, reasons, scope and state available to keyboard and assistive technology. Background updates preserve focus and control identity; reduced motion keeps the same semantic result.
Code
handoffPacket(state, plan, { to: 'Mina (Operations)' })