FPF Reference

    SYSTEM-IN-CONTEXT - Make the current system question explicit

    Preface node heading:system-in-context-make-the-current-system-question-explicit:631

    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 candidate system is named, but the current system question is not yet explicit. Ask whether the needed first result concerns identity and environment, composition, participation and functioning, selected structures, intended creation or change, or creation or change that has already occurred.
    • Template A. A.1 Solution -> exact candidate-side holon-recognition result | exact direct delimitation claim. Select first when an exact U.Entity candidate must be tested under an already admitted holon kind: recover the six world-side constructive components and the kind-specific condition, while keeping satisfaction or failure separate from true | false | unknown evaluation and any optional classification assertion. Select a direct delimitation, environment, selected-structure, or boundary-condition pattern when that narrower claim—not candidate holon recognition—is current; A.1 introduces no omnibus delimitation or boundary-crossing relation kind.
    • Template B. B.1.2 Solution -> SystemAggregationRelation@Context. Select when aggregation depends on distinguishing admitted system parts from external crossing relations.
    • Template C. direct subject pattern Solution -> exact relation claim involving the System. Select after holon recognition when one particular relation is current—for example a role assignment, functioning, method enactment, work participation, selected structure, evidence use, or assurance relation. Open the direct owner of that relation; the examples do not define one family, and A.1 supplies no omnibus system-participation result.
    • Template D. C.30 Solution -> ArchitectureQuestionCard@Project. Select when the system is identified and selected structures or architecture relations are now current.
    • Template E. A.15.2 Solution -> U.WorkPlan. Select when planning intended system creation or change is current.
    • Template F. A.15.1 Solution -> U.Work. Select only when one world-side dated performed occurrence is current. Ground that occurrence through its exact performedBy RoleAssignment, enactsMethod relation, temporal extent, containing System, and affected referent; add actual bindings and performed resource-use facts only as separately obtaining relations needed by the use. An assertion or description may designate those facts, but a log, ticket, record, or carrier is neither the occurrence nor a Work individual. Actual change, outcome or result, evidence, production, delivery, and acceptance remain separately governed.
    • Template G. A.15.PROD Solution -> local production-work participation | entity-identity inception | production-completion claim | exact blocker. Select only after the exact A.15.1 work occurrence and the direct subject-governed method, change, identity-specification, or completion-criterion basis are current. Work, actual change, output, result, identifier allocation, or a last visible step alone establishes none of the three production claims; missing work granularity, direct governor, criterion, applicability, boundary fact, composition basis, or required substrate remains an exact branch-local blocker.
    • Boundaries. Stop at the smallest result that answers the current question. Return when system identity, context, parthood, participation, selected-structure question, intended work, or performed-work evidence changes. Wrong-turn recovery restores system, environment, part, participation, architecture, plan, performed work, and description as separately governed values. A diagram box is not a system boundary by shape, a functioning description is not the functioning system, and a work record is not a system part merely because it appears inside one project view.
    • Public coarsening. "System in context" restores to the exact selected result under its selection condition.

    Last Updated: 2026-07-28 — upstream FPF commit 17edd955 (github.com/ailev/FPF)