Components · History
History Timeline
What was recorded, in order, and what each entry invalidated. Chronology is shown; causality only where it was recorded.
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 |
|---|---|
| Recorded relations. | Chronology as causality. |
Anatomy
01 · Recorded chronologyOrder means recording time, not proof of causation.
02 · Dependency changesInvalidated items stay present as struck chips.
03 · Earlier assuranceA past verification is not a promise about current premises.
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 what an entry invalidated: “Approval of Mapping rule v3”.
Avoid
- Don’t reconstruct history from chat messages.
When not to use
Audit logs of every request. The timeline records work meaning.
Contract
A component without this contract may wear Lyotic’s style; it does not implement Lyotic.
| Semantic inputs | History entries with revision, time, kind, actor, text, invalidated |
|---|---|
| Allowed states | Any kinds: observation, claim, proposal, decision, approval, change, review, execution, verification |
| Forbidden states | Implying that one entry caused the next without a recorded relation |
| Evidence requirements | Is the record |
| Action scope | Not interactive |
| Meaning of authority | Shows who did what |
| External effects | None |
| Verification conditions | Old verifications stay without vouching for now (INV-12) |
| Failure and recovery | None |
| Transitions | Available from any mode |
| Accessibility | A reversed ordered list; invalidations are spoken as such |
| Observable events | None |
| Test conditions | Invalidations present when claims or approvals were superseded |
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
historyTimeline(state)