FPF Reference

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

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

    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 -> HolonDelimitationRelation@Context. Select for identity rule, bounded context, included or excluded entities, environment relation, selected-structure boundary, or current boundary condition.
    • Template B. B.1.2 Solution -> SystemAggregationRelation@Context. Select when aggregation depends on distinguishing admitted system parts from external crossing relations.
    • Template C. A.1 Solution -> SystemParticipationRelation@Context. Select when the current question connects the acting system to functioning, functional elements, roles, capabilities, methods, mechanisms, work plans, work occurrences, transformations, evidence, assurance, or temporal and dynamics aspects. Each linked value keeps its direct governing pattern.
    • 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 creation, change, maintenance, or another dated occurrence has happened and can be grounded through its performer, enacted method, affected referent, resources, outcome, time window, and evidence relation. The occurrence is the direct result; ResultProducingWorkSlot[] remains absent, while any planning, setup, authorization, or causal relation to other work returns to its direct governor.
    • 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-12 — upstream FPF commit 44dd8818 (github.com/ailev/FPF)