FPF Reference

    A.19.SOURCE-SET-SPACE-SUBSTRATE:4.5 - Operational declaration sequence (fail-closed)

    Preface node heading:a-19-source-set-space-substrate-4-5-operational-declaration-sequence-fail-closed:24503

    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

    When declaring one substrate-bearing line, proceed in this order:

    1. Entry test. Confirm that the line really needs source-set plus search/outcome-space plus relation/posture discipline. If it only needs CharacteristicSpace typing, use A.19. If it only needs publication or policy, apply the governing pattern that carries that publication or policy question.
    2. Recover the active source set. State SourceSetFamily. If several same-family source sets or set results are simultaneously live, fill SourceSetRef? or cite the neighboring governing pattern that makes that identity unique.
    3. Recover the space refs. Point SearchSpaceRef and OutcomeSpaceRef to already-declared CharacteristicSpace.
    4. Choose the ref-to-ref relation kind. Declare sameDeclaredSpaceAs only when both refs truly resolve to one declared space. Declare distinctDeclaredSpaceFrom only when they truly resolve to two distinct declared spaces. Do not leave this to reader inference.
    5. State the source-to-outcome relation. Give direction, mode, and carrier explicitly. If one named OutcomeMapRef or another declared interpretive qualifier carries the relation, cite that qualifier explicitly. If not, state the carrier directly in prose.
    6. State the posture. Declare whether the line is transparent for current use or qualified by loss, metric/model dependence, transition dependence, uncertainty, learning/adaptation, or instability under refresh.
    7. Add only the fields that are really doing work. Add composition, derived-view, base-palette, metric, transition, or bridge qualifiers only when the current case actually depends on them.
    8. Run the boundary check. If the line starts deciding publication metadata, shortlist identity, live candidate policy, enactment policy, or interpretive-view organization, stop and apply the pattern that governs that question.

    Fail-closed rule. Do not treat the line as declared substrate if any of steps 1-5 remains unresolved. Incomplete recovery is a real defect here, not one stylistic omission.

    Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)