C.30.ASV:3 - Forces · fpf.tools

Force	Tension
View usefulness vs view overread	Views make architecture discussable, but a useful description episteme, diagram, or publication form can be mistaken for architecture, selected structure, view membership, proof, or decision.
Structure kind vs viewpoint	A structure kind classifies selected structure; one exact viewpoint episteme states the rules under which the same candidate episteme is a view. They often appear together but are not the same object.
TEVB template reuse vs architecture-specific structure	E.17.2 distinguishes four useful authoring positions but supplies no current family or viewpoint references. Only a materialized project-local declaration supplies exact reusable `U.ViewpointRef` values; architecture-specific structure kinds are defined beside them and alter neither the resolved P editions nor declaration membership.
Small triage vs full view record	Many cases need only the structure kind under consideration and next architecture use; the full description-plus-conformance record is justified only when it changes action.
Multi-view correspondence vs single-view shortcut	Architecture work often needs relations among functional, flow, control, module, information, work, evidence, scale, and placement views; one favored diagram cannot carry all claims.
Hidden structure vs practical compression	A useful view omits something; omitted structure becomes a problem only when subsequent action relies on it.