F.10:2 - Problem
Status vocabulary is useful because it is compact. It is dangerous because the same label often hides different objects and claims:
- Modality collapse. Validated is read as evidence standing, standard approval, requirement satisfaction, and release permission at once.
- Target collapse. The status does not say whether it concerns a claim, quantity, method description, standard edition, clause, system-role assignment, work result, publication, gate record, or another exact target.
- Result collapse. A measurement, proof, conformance verdict, requirement-evaluation result, or assurance result is renamed as a generic status instead of retained under its direct governor.
- Window and scheme loss. Status is asserted without the effective ReferenceScheme, ClaimScope, conditions, edition, or relevance window that makes contradiction and freshness checkable.
- Source and display collapse. A badge, list row, dashboard tile, screenshot, certificate view, or generated summary becomes the status source or status use by visibility.
- Design-run substitution. Standard approval is read as runtime satisfaction, or runtime evidence as approval, without an exact interpretation relation and evaluation rule.
- Bridge overread. Shared spelling, a common family label, an F.17 row, an F.18 NameCard, or an F.9 Bridge is treated as the direct explanation, status application, or target result.
- Episteme use drift. A report, standard, model card, dashboard cell, or requirement document is said to hold an “evidence role”, “status role”, or “standard role” rather than participate in an evidence-use, status-use, source-use, standard-use, or requirement-use relation.