E.4.PFR:5 - Bias-Annotation
Scope. The assertion-first discipline is Universal within this pattern’s subject: every claimed relation starts as a readable assertion with its subject, relation function, basis, polarity, and current facts. The reusable row, dependency record, package manifest, and high-cost basis analysis are limited tools for a named framework-maintenance use whose next action needs them; none is a prerequisite for ordinary relation prose.
| Lens | Boundary |
|---|---|
| Gov | A row or analysis grants no authority, acceptance, permission, or reliance. |
| Arch | Assertions, relations, records, editions, publications, carriers, and access routes stay distinct. |
| Epist (Epistemological and Ontological) | A representation cites an assertion but neither creates the relation nor proves more than its bounded basis. |
| Prag | Stop after the direct assertion unless a named next action needs more structure; keep high-cost analysis exceptional. |
| Did | Lead with the readable assertion and introduce optional machinery only through a concrete receiving use. |
The first drift is relation-word overread: words such as depends, uses, supports, governs, or profiles are treated as if they settled relation function. Recover the exact subject assertion and blocked stronger readings.
The second drift is record prestige: a standardized row is required before the assertion can count. Keep the direct assertion as default and demand a named receiver for every row.
The third drift is software-package analogy: compatibility, endpoints, and access carriers are useful, but framework relations are not build imports, module calls, APIs, runtime routes, permissions, or performed Work.
The fourth drift is basis inflation: definition, citation, evidence, or later sufficiency is mistaken for actual formal-premise use or criterion selection, and every actual-use claim receives a complete analysis. Keep actual use exact and open analysis only for its high-cost receiver.