fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 60102–60117

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 17:35:14 UTC

C.22.2:13 - Representation and Wording-Use Relation Continuity

C.22.2 names A.6.3.RT, A.6.4, E.17, F.9, E.18, and E.10 only when changed problem formulations, diagrams, functional descriptions, transformation-flow paths, wording, or PathSlice examples carry a current representation, bridge, retargeting, structural-reinterpretation, or wording-use claim. The card may preserve the local cue, reference, or problem-formulation follow-up reason, but it does not prove continuity or use-boundary inheritance by wording similarity.

Framing is not wording repair. A framing change applies when EntityOfConcern, effective ReferenceScheme, ClaimScope, viewpoint qualification, comparison relation, use-boundary inheritance, or honest next use changes. Wording-use repair is current only when wording, diagram, functional description, transformation-flow path, Bridge, retargeting, or another representation change alters the carried problem-side representation, EntityOfConcern, effective ReferenceScheme, ClaimScope, viewpoint qualification, comparison relation, governed next use, or subject-pattern cue. Ordinary wording cleanup triggers no representation-continuity relation and does not block a Thin ProblemCard.

Pattern or pattern familyWhen it matters for the cardC.22.2 use
C.22Problem-side record, ProblemProfile, and TaskSignature are being related.Keep TaskSignature minimal and apply representation-transition, bridge, retargeting, structural-reinterpretation, or wording-use patterns only when a current relation claim or use-boundary appears.
C.16, A.19, C.25, G.9, and G.11Characterization, characteristic, Q-bundle, parity, or freshness representation changes the selected entity or comparison relation.Preserve only the problem-card cue and apply the characterization, parity, bundle, or refresh relation named by value when that relation is being made.
C.29A mathematical representation preserves, coarsens, or retargets the EntityOfConcern or the problem-side representation.Use C.29 output and representation or wording-use relation references when structure changes entity interpretation.
C.18, C.19, and G.5Archive, pool, front, shortlist, selected set, method-family, or selected-set output uses transformed representations.Preserve source-set reference, criterion, and downstream use; keep selection semantics outside the card.
A.6.P, C.16.Q, E.10, E.17, F.9, E.18, A.10, G.6, B.3, A.21, E.16, and A.15Source wording, quality wording, multi-view, bridge, structural reinterpretation, evidence, provenance, assurance, gate, autonomy, method, or work relation is current.Keep the local cue only; apply the subject pattern for the claim being made, relation, or boundary before reusing readiness or relying on the transformed material.

C.22.2 may not treat changed-problem examples as governed relations unless the appropriate accepted FPF relation is named.