Components · Evidence and interpretation
Evidence Unit
One observation in relation to one proposition: supports, refutes, or not enough. Supporting evidence is not a verification mark.
Overview
This compact example shows the component inside the shared contract. The detailed galleries below exercise its edge states without granting additional authority.
States
Lifecycle and freshness are independent of epistemic strength. Source records report observations; evidence units retain their three relation states. The surrounding claim demonstrates all six epistemic states without relabeling a source or an evidence relation.
Each example is checked against its full resolver plan. Explore with a pointer or keyboard; Escape folds evidence back. The source rows and their citations light together.
Freshness
Freshness belongs to an observation, not to the strength of a claim. Unknown age is still, not a loading state.
Withheld fields
Permission boundaries remain visible as “withheld · reason”. The withheld value is absent, including from hidden content and accessibility labels (INV-10).
Anatomy
- 01 Relation glyph and words
- The neutral support glyph, refutation glyph and insufficient ring each retain a text label.
- 02 Citation
- The source and field refer to a specific observation, paired by data-ly-key.
- 03 Relation note
- The explanation says why this observation bears on this proposition.
- 04 Missing or withheld information
- An omission keeps its reason; the renderer never invents a replacement verdict.
Usage and avoid
Use: preserve what the fields mean
5,400 Produced Quantity and 1,620 Available to Sell answer different questions. Review the meanings before proposing a correction (INV-19).
Avoid: turning a model score into a fact
0.82 is an observation about the classifier. Keep the proposed alias inferred, and keep insufficient evidence visible (INV-01, INV-20).
Contract checks and limits
Running negative controls…
The live checks do not validate the truth of fixture data, motion quality, assistive-technology announcements or equivalence to the film. Review those separately at 1440px and 390px, in both themes and with reduced motion.
Contract
A component without this contract may wear Lyotic’s style; it does not implement Lyotic.
| Semantic inputs | An observation reference, a relation and a note |
|---|---|
| Allowed states | supports, refutes, insufficient |
| Forbidden states | “Proves”, or a relation to a claim it was not evaluated against |
| Evidence requirements | Is the evidence |
| Action scope | Presentation only; no external writes or authority changes |
| Meaning of authority | None |
| External effects | None |
| Verification conditions | None |
| Failure and recovery | An unavailable observation is disclosed. Only the caller may re-evaluate the evidence relation |
| Transitions | None; lives inside a Claim Block |
| Accessibility | Relation in text beside its glyph |
| Observable events | None |
| Test conditions | INV-01 |
Accessibility
Preserve native names, reading order, keyboard exploration, focus continuity and text-based state. Reduced motion removes spatial movement without removing evidence or status meaning.
Code
const unit = evidenceUnit(claim.evidence[0], input); list.append(unit); unit.update(nextEvidence, nextInput);
Reference and verification
Compare card rhythm to scene 02 at 24 seconds and meaning lenses to scene 04 at 49 seconds. The film is a visual reference, not evidence that an action has been verified.
For integration, walk Inventory mapping on both paths. The Work Object Shell must pass its plan to enable local Claim Block exploration; legacy two-argument calls remain non-authorizing and show evidence directly.