Components · Decision
Decision Record
What was chosen, by whom, when, on which criteria, using which evidence, accepting which limits. Recorded then, never rewritten later.
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 |
|---|---|
| What was decided and why, as recorded at the time. | Reasons invented afterwards. |
Anatomy
01 · ChoiceThe recorded option, not an inferred preference.
02 · ProvenanceWho decided, when, and the exact evidence references.
03 · Accepted limitsThe limits and criteria as recorded at decision time.
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
- Record accepted limits (“Amazon reservations are not observable”).
Avoid
- Don’t treat a decision as an approval. They are different acts by possibly different people.
When not to use
Logging actions. That is the History Timeline.
Contract
A component without this contract may wear Lyotic’s style; it does not implement Lyotic.
| Semantic inputs | A decision with chosen, by, at, criteria, evidence, limits |
|---|---|
| Allowed states | One per decision point |
| Forbidden states | Editing a recorded decision in place |
| Evidence requirements | Cites the claims used |
| Action scope | Not interactive |
| Meaning of authority | Records who decided; not an approval |
| External effects | None |
| Verification conditions | None |
| Failure and recovery | A decision whose evidence breaks is flagged for review; the record stays |
| Transitions | Shown above the Impact Preview in authorize |
| Accessibility | A labelled section with a definition list |
| Observable events | None |
| Test conditions | Fields present |
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
decisionRecord(state)