E.18.3:3 - Forces · fpf.tools

Force	Tension
Transformation-flow richness vs universal-parent drift	E.18 is rich enough to explain many route-shaped transformation cases, but narrative, abduction, grounding, improvement, and public practical-use cards or walkthroughs are not transformation-flow merely by shape.
Flow card usefulness vs work-order overread	A path or flow card can guide a next FPF use, but it does not authorize performed work or decide launch readiness.
Neighboring values vs ontology absorption	Method, work, evidence, gate, decision, architecture, publication, and currentness values can connect to a flow position after the value is independently identified and any claim about it is shown to obtain from current facts or evidence under an applicable definition or test, without becoming transformation-flow kinds.
Demonstrative slices vs actual traces	A path slice may show a traversal for learning or review; actual project history may branch, pause, retry, or skip that traversal.