E.17.2:3 - Forces · fpf.tools

Force	Tension
Reuse vs exact edition	Teams need stable families, while conformance depends on exact claim-bearing viewpoint editions.
Small core vs subject breadth	Four viewpoints should remain learnable without pretending that safety, mission, data, deployment, and every domain concern are the same four things.
Holon-centered view vs concern objects	A view can concern one holon while its claims designate Methods, transformations, local system-role kinds, assignments, capabilities, and structures through exact relations.
Familiar engineering language vs kind precision	`functional view` should remain readable without turning `functional`, `view`, or a diagram label into an intrinsic kind by spelling.
Direct authoring vs generated descriptions	Both can yield conforming views; neither route establishes conformance by itself.
Cross-view comparison vs invented links	Comparable views need exact direct relations, not a universal correspondence record or matching diagram positions.
Viewpoint reuse vs publication reuse	Many unpublished epistemes can conform to the same viewpoint, and each episteme may later have many publication forms; packaging must not redefine membership.