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

Force	Tension
Ordinary engineering speech vs FPF kind recovery	Engineers need compact words such as architecture, structure, model, view, graph, module, layer, block, expert, cache, router, and gate; FPF claims need recovered kind, relation, source-use relation, and admissible use. `C.30.STRAT` recovers stratification or source-label meaning when it still hides the technical claim, before `C.30.P` assigns the recovered architecture or structure portion.
Architecture description vs architecture itself	Descriptions and views are useful, but they can be overread as the selected structure or architecture claim.
Structure generality vs architecture specificity	`A.22` gives selected structure; `C.30` governs grounded architecture adequacy over selected architecture-relevant structures and admits only the thin architecture-description bridge when durable description use is being made. `C.30.AD` governs the full architecture-description mechanism. The repair must not collapse them.
Small first move vs heavy record	Most wording cases need one repair note and a subject pattern assignment, not a full architecture description.
Source and view usefulness vs project authority	A source, dashboard, graph, ADR, or view can guide architecture work without proving evidence, gate passage, decision authority, release permission, or work completion.
Cross-pattern consistency vs shadow registry	Architecture hosts should not carry duplicate trigger lists once `C.30.P` exists.