Components · Consequence
Impact Preview
What will change and what will be preserved, values today and in future runs, reversibility and notifications. Planned, not happened: proposed values are dashed.
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 planned effect. | That the effect happened. |
Anatomy
01 · Intended changesDashed proposed values; observed values are not overwritten.
02 · Preserved scopeAs prominent as Changes, with a reason for each preserved value.
03 · Downstream factsReversibility, notifications and future runs are explicit or marked missing.
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
- Show what is preserved as prominently as what changes.
- Include future runs: one setting can affect every later sync.
Avoid
- Don’t judge importance by the number of fields changed.
When not to use
Changes that are small, reversible and delegated. No ceremony for them.
Contract
A component without this contract may wear Lyotic’s style; it does not implement Lyotic.
| Semantic inputs | A proposal with changes, effectsNow, futureRuns, preserved, reversible, notifications |
|---|---|
| Allowed states | Any proposal awaiting approval |
| Forbidden states | A preview without preserved values; solid strokes on proposed values |
| Evidence requirements | Current values come from observations |
| Action scope | Not interactive |
| Meaning of authority | None; sits beside the Authority Gate |
| External effects | None |
| Verification conditions | Its items become the checks of the later verification |
| Failure and recovery | A change since the version shown is tagged “changed since v3 by Dana” |
| Transitions | Appears in authorize; stays until executed |
| Accessibility | Headed sections; arrows have a text equivalent |
| Observable events | None |
| Test conditions | impact.changes, impact.preserved, impact.reversibility, impact.notifications |
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
impactPreview(proposal)