FPF Reference

    DESCRIPTION-USE - Create or use a description without losing its subject

    Preface node heading:description-use-create-or-use-a-description-without-losing-its-subject:586

    What this page is

    This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

    Methodology

    Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

    Content

    • Situation and question. A description, view, dashboard, explanation, model, report, or publication is to be created, compared, transformed, or relied on. Ask which unresolved EntityOfConcern, viewpoint, representation change, lost structure, source set, or architecture use blocks the current use.
    • Template A. E.17.0 Solution -> EpistemeViewpointConformanceRelation occurrence, followed, when it obtains, by dependent U.View membership of that same episteme. Select for the generic describing case. Identify candidate episteme E under C.2.1 by its claim content, actual EntityOfConcern, and effective ReferenceScheme; resolve one exact U.Viewpoint episteme P and apply E.17.0's fixed predicate. Add a ClaimScope or BoundedModelUseStructure only when a separately governed relation makes that qualifier relevant to the current use; neither is episteme identity.
    • Template B. A.6.3.RT Solution -> RepresentationSchemeTransitionRelation@Context. Select when the same EntityOfConcern is being re-represented and a named receiving use relies on recovering the source representation, receiving representation, preserved claim or commitment, source-relation chain, representation-scheme delta, loss or recoverability, admissible use, and non-admissible downstream use. The relation records the concrete case; RepresentationSchemeTransition remains the method-pattern name.
    • Template C. C.33 Solution -> StructuralInformationAdequacyNote@Context. Select when the current question concerns what structure a description or view captured, lost, hid, and which wider source structure receives return for the declared architecture use.
    • Template D. E.17.ID.CR Solution -> ComparativeReviewUnit. Select only for bounded comparison over already available source epistemes or publications. It is not the generic description result.
    • Template E. C.30.AD Solution -> ArchitectureDescriptionUseCard@Project. Select when the subject is specifically an architecture description or view and its admissible architecture-use boundary is current.
    • Boundaries. Stop at the smallest result answering the current description-use question. Return when EntityOfConcern, effective ReferenceScheme, viewpoint edition, representation scheme, captured structure, source edition, comparison basis, or intended use changes. A ClaimScope or model-use qualifier reopens the branch only when its direct relation changes the use. A publication carrier does not become its subject, and a readable view does not become evidence, assurance, permission, decision, architecture, or work without the corresponding governed relation.
    • Result test. The potential result is exactly the E.17.0 conformance occurrence, A.6.3.RT transition occurrence, C.33 adequacy note, E.17.ID.CR review unit, or C.30.AD architecture-use card named by the selected template. Identify it under that direct Solution, then name the exact evaluation, decision, publication, architecture-description use, or other admitted receiving object it would answer and the relation, binding, or supported local claim that makes it this description use's result. Name a next comparison, repair, publication, or architecture use only when current; otherwise stop with the missing viewpoint, correspondence, structure, governor, or information.
    • Public coarsening. "Description use" restores to EpistemeViewpointConformanceRelation, RepresentationSchemeTransitionRelation@Context, StructuralInformationAdequacyNote@Context, ComparativeReviewUnit, or ArchitectureDescriptionUseCard@Project under the stated condition.

    Last Updated: 2026-07-29 — upstream FPF commit 2ada4136 (github.com/ailev/FPF)