Components · Verification
Verification Result
What was checked, when, what was preserved, and what could not be observed. Verified within a stated scope, never beyond it.
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 verified scope only. | Resolution of the whole Case. |
Anatomy
01 · Named scopeThe result names the action or explicitly provided scope.
02 · Check evidenceOnly recorded results tick; pending is not a measured percentage.
03 · Unobservable rowUnobservable checks remain inconclusive and outside the assurance.
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
- List what could not be observed.
- For read-only sources, verify “unchanged and relation confirmed”, never “write succeeded”.
Avoid
- Don’t turn the result green before every check has a result.
When not to use
Execution acknowledgements. A 200 is not a verification.
Contract
A component without this contract may wear Lyotic’s style; it does not implement Lyotic.
| Semantic inputs | A verification with checks, time and premises |
|---|---|
| Allowed states | pending, verified, failed, inconclusive |
| Forbidden states | “Verified” with a failing check; unobservable counted as passed |
| Evidence requirements | Each check is a read-back or a comparison |
| Action scope | Not interactive |
| Meaning of authority | None |
| External effects | None |
| Verification conditions | Is the verification; time-bound (INV-12) |
| Failure and recovery | A failed check moves back to recover |
| Transitions | verify → compact resolved; a premise change re-opens it |
| Accessibility | Pass, fail and not observable are spoken, not only drawn |
| Observable events | None |
| Test conditions | INV-11, INV-12 |
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
verificationResult(state.verifications[0])