Link to current text
F.10:3 - Forces
| Force | Tension this pattern resolves |
|---|
| Local fidelity versus reuse | Status meaning is local to an effective ReferenceScheme, yet projects must explain or compare statuses across schemes. |
| Compact label versus recoverable relation | A quick display is useful, while target, value, scope, window, source, rule, and use must remain recoverable before reliance. |
| Evidence versus standard versus requirement | Evidence standing is epistemic; standard and requirement statuses are deontic in different ways. |
| Direct result versus status | A domain result may justify a status assertion, but the result and status remain different objects. |
| Design stance versus runtime standing | Approval of a description or profile does not show what happened in one run. |
| Cue versus actual use | Display and list membership aid retrieval but do not establish source, evaluation, currentness, status use, or downstream reliance. |
| Ordinary speech versus kind discipline | “The role of this status” is repaired as an exact use relation, not as a work-facing role held by an episteme. |