C.30.TFS-REL:3 - Forces

Force	Tension
Transformation-flow relation vs architecture takeover	One E.18 TFS, one E.18.NET network, or a selected path or crossing can be essential, but none becomes all architecture ontology or an unnamed characteristic bearer.
Functional view vs transformation-flow view	A functional structure view may need a transformation-flow relation, but a required effect, path, crossing, valuation, or mathematical description is not a functional element or actual transformation by itself.
Structure precision vs work/change overread	E.18 gives selected structure, path, and flow-valuation objects; actual transformation, Work occurrence, and work results remain outside this record unless their own patterns admit those claims.
No-hidden-scalarization vs architecture scoring	E.18 set-return and no-hidden-scalarization discipline can inform architecture reasoning, but it does not by itself define a general architecture score.
Small relation vs unneeded non-architecture apparatus	A project often needs one use record, not a full C.29 lens card, evidence relation, assurance case, or decision record.
Flow-structure-owner stability vs C.30 integration	An actual architecture relation, selected structure, structural view, or conditional architecture-description use needs a trace to E.18 for one TFS or E.18.NET for one network without rewriting either owner as generic architecture adequacy theory.