Components · Execution
Execution Trace
Work-meaningful steps per target, and the Case’s control state. Never an aggregate “success” over partial results.
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 |
|---|---|
| Per-target execution state. | Aggregate success over partial results. |
Anatomy
01 · One row per targetEach target retains its own outcome and supporting note.
02 · Measured activityOnly an in-flight request spins. Unknown stays still.
03 · Stop boundaryStop requested and Halted describe different local guarantees.
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
- One row per target, always.
Avoid
- Don’t show a progress bar for the Case; progress is per target.
When not to use
Logs. The trace shows work-meaningful steps, not every request.
Contract
A component without this contract may wear Lyotic’s style; it does not implement Lyotic.
| Semantic inputs | Executions per target; control state |
|---|---|
| Allowed states | Any execution value per target; running, stop-requested, halted |
| Forbidden states | A single “done” for many targets; a spinner for an unknown outcome |
| Evidence requirements | States come from the executor and adapters |
| Action scope | request-stop while running |
| Meaning of authority | Stopping needs no approval; it blocks new runs only |
| External effects | Stop does not undo accepted remote work (INV-05) |
| Verification conditions | Hands off to verification when every target has an outcome |
| Failure and recovery | Unknown, partial or failed moves to recover |
| Transitions | execute → verify, or execute → recover |
| Accessibility | An ordered list; each row names its target |
| Observable events | ly-action request-stop |
| Test conditions | INV-05, INV-06; execution.perTarget |
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
executionTrace(state, plan)