FPF Reference

    Finding the Acting or Changed System

    A.1.SCR · Stable · Part A practitioner application pattern · Normative unless marked informative · Part A - Kernel Architecture Cluster

    About this pattern

    This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

    How to use this pattern

    Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

    Type: Part A practitioner application pattern Status: Stable Normativity: Normative unless marked informative

    Plain name. Find the system that acts or is intended to change.

    Mint or reuse. This pattern introduces no U-kind, relation kind, result kind, or application-record kind. A.1.SCR is a PatternID. It tests one exact U.Entity under the already admitted U.System kind only when a current engineering decision depends on systemhood.

    Use this when. Use this pattern when a decision depends on which exact system acts, is intended to change, carries a capability, persists through a lifecycle, or is being considered or designated as the project system-of-interest—and the proposed subject is still unclear. Ask: Which exact system acts or is intended to change here, and what decision depends on treating it as a system?

    Relations

    A.1.SCRbuilds onHolon Ontic Foundation (U.Holon and Admitted Holon Kinds)
    A.1.SCRbuilds onRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims
    A.1.SCRcoordinates withProject, Process, and Case Recovery through Work, Method, and Transformation
    A.1.SCRcoordinates withUsing the System-Thinking Long Mantra
    A.1.SCRcoordinates withNeeded Relation Claim Derivation and Relation-Kind Admission
    A.1.SCRcoordinates withUnified Lexical Rules for FPF
    A.1.SCRcoordinates withLocal-First Unification Naming Protocol
    A.1.SCRbuilds onU.Capability: System Ability Envelope and Measures
    A.1.SCRbuilds onU.Method: Reusable Way of Doing with Explicit Applicability
    A.1.SCRbuilds onU.MethodDescription: Description Episteme for a Way of Doing
    A.1.SCRbuilds onU.Transformation: Bounded Change Under Conditions
    A.1.SCRbuilds onU.Work: Dated Performed Work Occurrence
    A.1.SCRbuilds onU.WorkPlan: The Schedule of Intent
    A.1.SCRbuilds onStructure and Structural Views (STRUCT-CAL)
    A.1.SCRbuilds onU.Episteme: Constitution, Empirical Grounding, and Edition Relations
    A.1.SCRbuilds onTransformation Flow Structure
    A.1.SCRbuilds onFinding the Acting or Changed System
    A.1.SCRbuilds onProject, Process, and Case Recovery through Work, Method, and Transformation
    A.1.SCRbuilds onUsing the System-Thinking Long Mantra
    A.1.SCRbuilds onNeeded Relation Claim Derivation and Relation-Kind Admission
    A.1.SCRcoordinates withDiscovering Systems That May Bear Consequences
    A.1.SCRcoordinates withHolon Ontic Foundation (U.Holon and Admitted Holon Kinds)
    A.1.SCRcoordinates withRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims
    A.1.SCRoutline parentHolon Ontic Foundation (U.Holon and Admitted Holon Kinds)
    A.1.SCRoutline prev siblingBounded Model-Use Structure and DDD Bounded-Context Recovery
    A.1.SCRoutline next siblingDiscovering Systems That May Bear Consequences
    A.1.SCRexplicit referenceRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims
    A.1.SCRexplicit referenceU.Capability: System Ability Envelope and Measures
    A.1.SCRexplicit referenceSystem-Role Kinds and Assignments
    A.1.SCRexplicit referenceU.SystemRoleAssignment - Contextual System-Role Assignment
    A.1.SCRexplicit referenceU.Method: Reusable Way of Doing with Explicit Applicability
    A.1.SCRexplicit referenceU.MethodDescription: Description Episteme for a Way of Doing
    A.1.SCRexplicit referenceU.WorkPlan: The Schedule of Intent
    A.1.SCRexplicit referenceU.Work: Dated Performed Work Occurrence
    A.1.SCRexplicit referenceU.Transformation: Bounded Change Under Conditions
    A.1.SCRexplicit referenceU.Episteme: Constitution, Empirical Grounding, and Edition Relations
    A.1.SCRexplicit referenceStructure and Structural Views (STRUCT-CAL)
    A.1.SCRexplicit referenceTransformation Flow Structure
    A.1.SCRexplicit referenceU.PromiseContent (Promise Content)
    A.1.SCRexplicit referenceU.Commitment (Deontic Commitment Relation)
    A.1.SCRexplicit referenceU.SpeechAct (Communicative Work Kind, Occurrences, and Records)
    A.1.SCRexplicit referenceGranted Permission, Exercise, and Non-Prohibition
    A.1.SCRexplicit referenceProject, Process, and Case Recovery through Work, Method, and Transformation
    A.1.SCRexplicit referenceUsing the System-Thinking Long Mantra
    A.1.SCRexplicit referenceSystemRoleAssignment and Performed-Work Attribution Check
    A.1.SCRexplicit referenceThe Agential Role & Agency Spectrum
    A.1.SCRexplicit referenceHolon Ontic Foundation (U.Holon and Admitted Holon Kinds)
    A.1.SCRexplicit referenceDiscovering Systems That May Bear Consequences
    A.1.SCRexplicit referenceUnified Lexical Rules for FPF
    A.1.SCRexplicit referenceLocal-First Unification Naming Protocol

    Content

    Practitioner entry

    Use this when. Use this pattern when a decision depends on which exact system acts, is intended to change, carries a capability, persists through a lifecycle, or is being considered or designated as the project system-of-interest—and the proposed subject is still unclear. Ask: Which exact system acts or is intended to change here, and what decision depends on treating it as a system?

    First useful move. State the claim, the proposed actor or change bearer, and what you will decide differently if it is or is not a system. If the phrase already names Work, a Method, capability, transformation, episteme, structure, or a direct relation and your decision does not depend on systemhood, name that object and leave through its subject pattern. Apply the complete A.1 criterion only in the system-dependent branch.

    First-minute recognized case. A maintenance decision asks whether Pump-37 or the larger pumping assembly must be isolated before repair. The exact pump has identified constituents, obtaining part relations and assembly, a reidentification rule across seal replacement, a composition-grounded pumping characteristic, and governed boundary/interface facts. Its organization can causally participate in pumping and maintenance Work while preserving identity. The first result is: Pump-37 is the recognized U.System whose boundary controls this isolation decision.

    Subject-pattern and proposed-system readings. “We develop the surgeon's mastery” ordinarily names the person, one holder-dependent U.Capability, training Work, or evaluation. Keep those subject-pattern readings. If the source instead proposes the physically or operationally realized whole SutureControl-M17, identify that exact U.Entity and evaluate it—not a substituted surgeon or capability—under the already admitted U.System kind. Choose the reading on which the current decision depends.

    Near-identical non-system case. PumpKit-37 contains parts of the same types and carries the same product label, but its constituents are not assembled by the required part relations, it has no composition-grounded pumping characteristic, and it cannot participate in the plant installation while preserving pump identity. The first result is: the kit is not the pump system; the current subjects are the material collection and its description.

    Honest unknown case. WorkshopController-9 is an exact boxed device, but the team cannot recover its internal assembly, reidentification rule, or operating boundary. The evaluation is unknown and names those missing inputs; the decision that assumes an acting controller remains blocked. The entity itself satisfies or fails the criterion independently of current knowledge.

    What this buys. A real actor, change bearer, lifecycle subject, capability holder, or project system-of-interest decision gets a tested identity and boundary. A direct Work, Method, capability, structure, episteme, or relation question leaves immediately without an unnecessary A.1 evaluation. Continue through A.1.STM only if the practitioner still cannot connect this recognition result to the project's outside use; recognition alone does not open the long map.

    Not this pattern when. If the subject and its admitted kind are already clear, use the subject pattern of the claim. If service or access wording hides a promise, participant, bearer, permission, Work occurrence, status, evidence, or direct relation, begin with A.6.P §4.11a. Enter A.1.SCR from that route only when the repaired claim itself depends on whether the exact entity recovered by A.6.P—an exact bearer or access-providing arrangement—is a system. If only a name for an already recoverable object is unclear, use F.18.

    Problem frame

    Familiar nouns can pull attention toward the wrong system or erase a supported proposed-system reading. Mastery may name a capability or the exact physical/operational whole SutureControl-M17. Session may name Work, an interval, a record, or GameSessionWhole-GS204. Access may name promise, permission, state, bearer, Work, or InternetAccessArrangement-CA17. Program may mean code, a Method, an intended designator, a deployed realization, or a run. The engineering cost is a wrong actor, identity boundary, change bearer, capability holder, or project system-of-interest—and the same error occurs when a convenient neighboring referent replaces the exact entity before A.1 evaluates it.

    A.1 is the pattern for constructive recognition under admitted holon kinds. This child does not relax or duplicate that criterion. It tells the practitioner when the complete test is worth doing, permits an immediate subject-pattern exit when it is not, and returns one result tied to a concrete decision.

    Problem

    Without this conditional route, practitioners commonly:

    1. classify every unusual noun before asking what the decision needs;
    2. treat wording, physical embodiment, a system-role label or assignment, or a record as proof of systemhood;
    3. stop at a list of PatternIDs without naming the actor or change bearer;
    4. infer designation as the project system-of-interest from recognition or from being affected by Work;
    5. reject a system reading without naming the actual Work, Method, capability, structure, episteme, or relation that remains useful.

    Forces

    ForceTension
    Useful entry vs classification ritualA.1 is rigorous, but many subject-pattern questions do not depend on systemhood.
    Familiar wording vs exact identityA noun can retrieve a case but cannot identify an entity, boundary, or kind.
    Physical grounding vs kind collapseEmbodiment helps locate a subject but does not identify it with a local system-role kind or assignment, capability, Work, or description.
    Project intent vs actual existenceA designator or selection among alternatives is not yet an acting system.
    Positive action vs honest uncertaintyMissing construction facts must block the affected decision without creating a third ontic state.
    Reusable cases vs taxonomyThe examples teach one move but do not form a common kind.

    Solution

    State the system-dependent decision

    Start with four plain statements:

    1. the claim you are trying to use;
    2. the exact entity proposed as actor, change bearer, capability holder, persistent subject, or project system-of-interest;
    3. the decision or action that would differ if this entity were or were not a system; and
    4. the observation, boundary fact, or construction fact that would settle that difference.

    Do not use bare system candidate as a working noun. Before referent recovery say the proposed system reading of the phrase. Once an actual referent is identified, say the exact U.Entity being evaluated under the already admitted U.System kind. Say an alternative being considered for designation as the project system-of-interest only when one named project plan or decision compares possible referents.

    Take the subject-pattern exit first

    Before testing systemhood, ask whether the current decision already concerns one of these objects:

    Current objectSubject pattern or exit
    Holder-dependent capabilityA.2.2
    Local system-role kind or obtaining system-role assignmentA.2 and A.2.1
    Reusable way of doing or its descriptionA.3.1 and A.3.2
    Intended workA.15.2 U.WorkPlan
    Dated performed occurrenceA.15.1 U.Work
    Actual bounded changeA.3.4 and the exact transformation pattern
    Claim-bearing model, rule, report, code, or other epistemeC.2.1
    Selected structure or transformation-flow structureA.22 or E.18
    Promise, commitment, speech act, or permission resultA.2.3, A.2.8, A.2.9, or A.2.8.PER
    Service/access referent, status, evidence, evaluation, delivery, acceptance, or other relationA.6.P §4.11a and then the exact subject pattern

    If this result answers the decision, stop here. Name the object, its subject pattern, and what you can now do. Do not apply A.1 as a recurring project ritual.

    If a needed relation has no current governor, state the exact participants and blocked receiving use, return missing-governor[...], and continue under A.6.RCD. Do not substitute relatedTo, a graph edge, or a local bundle.

    Apply A.1 only when systemhood remains load-bearing

    When the decision still depends on systemhood, recover all six A.1 constructive components. A.1 supplies the criterion.

    A.1 componentPractical recovery question
    Exact entityWhich one entity is being tested, and what identity rule distinguishes it from its name, description, parts, environment, and successor?
    Exact constituentsWhich entities actually constitute it rather than merely being nearby, listed, sampled, or described with it?
    Constructive part relations and assemblyWhich obtaining part relations and assembly make these constituents this whole?
    Reidentification ruleWhich changes preserve it, and which replacement, disassembly, completion, or termination ends it?
    Composition-grounded whole-level characteristicWhich characteristic follows from the actual assembly rather than from a label, plan, measurement, or one constituent?
    Possible participation in a larger constructive assemblyWhich boundary, interfaces, relevant characteristics, and identity-preservation conditions satisfy the applicable governed construction rule?

    Then apply the already admitted U.System condition: the whole has an actual physical or operational organization through which it can causally participate in Work or transformation while preserving identity. A system-role assignment, capability, Work occurrence, plan, codebase, or description may provide evidence for these conditions.

    Return one decision-bearing result

    DispositionRequired first result
    Subject-pattern resultExact object or relation, the claim needed for the decision, the cited subject pattern's concrete contribution, and the action now possible; no A.1 test.
    System recognizedExact system, identity and boundary, decisive construction facts, acting-eligibility basis, and the system-dependent next use.
    Proposed system reading rejectedExact non-system subject or relation, its subject pattern, and the action that remains possible.
    Evaluation unresolvedExact U.Entity, missing A.1 component or kind-specific condition, needed information, and the decision that stays blocked.

    SubjectPatternLocator locates the cited pattern; in ordinary prose, cite its PatternID. Add exact predicate or defining-content references, including a defining episteme edition or ClaimGraph, only when the governing claim or a named receiving use requires them (C.2.1 §4.2.4).

    After one candidate bearer is recognized, rejected, or left unresolved, use A.1.CSD only when the current question is which other Systems may undergo relevant changes and that discovery can change a named decision or investigation. A.1.SCR does not generate the bearer set or qualify consequence paths; it supplies only the load-bearing recognition result or blocker.

    These are response forms, not a schema. Persist a classification assertion or evaluation-result episteme only when another use must inspect or cite it; C.2.1 is then the pattern for that episteme. true | false | unknown describes an evaluation and changes no kind extent.

    Add only the neighbors used now

    After the first result, add only claims consumed by the decision. Shared extent, one carrier, a common label, or co-occurrence establishes none of their identities or relations.

    Keep service/access recovery independent

    When service or access wording is the unresolved phrase, start in A.6.P §4.11a. A.6.P names the exact service-provision Work, Method, PromiseContent, system-role assignment, bearer, access-providing arrangement, permission, status, or direct relation. Use A.1.SCR only if the repaired sentence makes a separate system-dependent assertion about the exact entity recovered there—an exact bearer or access-providing arrangement.

    “My service stopped” does not by itself say that a system stopped. Service-provision Work may have ceased, an exact deployed or physical bearer may have stopped or become unavailable, an access-providing arrangement may be proposed as the exact system whose functioning stopped, or promised availability/fulfilment may have failed. Use A.1.SCR only to test a separately proposed exact bearer or access-providing arrangement when its system boundary matters to the decision.

    Preserve the project system-of-interest bridge

    The primary expression is project system-of-interest, inherited from systems engineering without adding target, aim, or goal semantics. systemOfConcern may serve as a historical systems-engineering Plain synonym for that same designation.

    A project plan or decision may designate one system as the project system-of-interest. Keep six questions separate:

    1. identify the exact actual system, or keep a merely intended future referent as a designator in plan, decision, or description content;
    2. name the plan or decision that designates it and the intended change or use;
    3. admit composite project Work only after A.15.1 and A.15.6 qualifications hold;
    4. state each actual work-to-referent, transformation, production, evaluation, delivery, acceptance, or later-use fact under its own governor;
    5. test any SystemOfInterestSystemRole interpretation and any A.2.1 system-role assignment separately; and
    6. when the recognized system must be reconnected to the long dependency from outside use through architecture, Work, change, and recursive builders, use A.1.STM to name the needed final result, retain supported answers, and read backward to the first unsupported dependency. Take that question to the subject pattern whose entry accepts it, and return the answer or a named stop.

    For a claim about a particular dated Work occurrence, first identify every actual performing System and recover its A.13 core. Independently admit that occurrence under A.15.1 from its performance history, at least one Method actually followed, temporal extent, and at least one locally declared containing-System relation. Apply this branch to the occurrence being asserted, whether it is Work represented on the map or a separately asserted Work of using the map. After admission, add F.6 only when the receiving claim also needs precise assignment-bound attribution through that performer's same obtaining assignment. A Work-only claim may stop after admission.

    Infer no project designation from system recognition, affectedness, familiar wording, a system-role label, or shared realization. If the decision needs the unsupported compound project-selection truth, preserve missing-substrate[project-selection-conjunction] until one constructor substrate and edition define that claim.

    Use physical grounding without cross-kind identity

    Ask what physically or operationally exists, where its boundary lies, and what preserves or ends its identity. This pressure helps test a proposed system reading and reject description-only substitutes. It does not identify a system with a local system-role kind, system-role assignment, capability, Work, transformation, Method, plan, evidence, or description. Do not import BORO categories, unrestricted composition, or a new 4D record.

    Archetypal Grounding — Seven Heterogeneous Worked Cases

    Each row states whether the A.1.SCR trigger actually fires. The rows are examples.

    Source phraseFirst useful result and routeNext move and governed additionsNear miss or stop
    “We develop the surgeon's mastery.”Keep the surgeon's capability, training Work, and evaluation under their subject patterns. If the phrase instead proposes the physical or operational whole SutureControl-M17, identify that exact entity and use A.1 only when its systemhood changes the decision.Add training Method, dated Work, evidence and evaluation, and any actual change only when the named decision needs those claims; keep the subsystem and capability distinct.Curriculum, badge, report, system-role kind or assignment, capability, surgeon, and SutureControl-M17 are not interchangeable; do not substitute the surgeon before evaluating the exact proposed whole.
    “We release a game session.”Keep composite dated Work, interval, and session record under their subject patterns. If the phrase instead proposes GameSessionWhole-GS204, identify that exact operational whole and use A.1 when its boundary, persistence, or acting eligibility matters.Recover every actual performer's A.13 core and admit Work only with the full independent A.15.1 basis and exact work-part relations; add F.6 afterward only when this claim also needs precise assignment-bound attribution. Evaluate the operational whole through its constituents, assembly, authoritative-state continuity, larger-game compatibility, and acting eligibility. Keep player systems, deployed installation, rule episteme, interval, activities, and records separate.A label, shared interval, lobby record, or rules document establishes neither systemhood, Work, parthood, nor identity between the Work and the operational whole.
    “We sell internet access.”Start in A.6.P with promise, permission, state, bearer, commercial relation, or other subject-pattern readings. If the phrase instead proposes InternetAccessArrangement-CA17, preserve that exact entity and use A.1 only when the arrangement's systemhood matters.Add Method or MethodDescription, WorkPlan, permission, provisioning Work, system-role assignment, commitment, status, evidence and evaluation, fulfilment, and acceptance only when the named decision needs those claims; evaluate the arrangement separately from its gateway and status.No U.Access or generic AccessRelation; credentials, system-role labels or assignments, endpoints, promises, plans, evidence, connections, states, and bearers remain distinct and cannot replace the exact arrangement before A.1 evaluation.
    “We develop a program.”Distinguish code/episteme, computational Method, intended designator, deployed realization, and run. Use A.1.SCR only when a decision depends on the deployed realization acting, persisting, or changing as a system.Add MethodDescription, planned or actual Work, transformations, and project system-of-interest designation only when the named decision separately asserts them.Code, algorithm, deployed system, run, and project designation are not one object.
    “The salon creates a hairstyle.”Name the client whose hair is affected and the selected hair structure/characteristics. Use A.1.SCR only if the client-as-changed-system boundary matters.Add hairdressing Method, description, dated Work, transformation, affected-referent facts, and acceptance only when the named decision needs them.Stop at the selected hair structure and characteristics when they answer the decision.
    “The surface needs a grind.”Name the workpiece or containing holon and the surface state, structure, and characteristics. Usually leave through those subject patterns without A.1.SCR.Add grinding Method, treatment Work, transformation, measurement, and acceptance only when the named decision needs them.A finish label is not an independent system, Work, or transformation.
    “The batch moves through the flow.”Name the material batch under its collection or holon rule and separately the selected TransformationFlowStructure or FlowValuation. Use A.1.SCR only if a decision depends on whether the batch is an acting or changed system.Add movement/treatment Work, transformations, transfer relations, path/valuation, and evidence under their subject patterns.Recover an acting collective under A.1 only if that claim is current; for a claim that Work was performed, name its actual performer.

    Enumeration-integrity rule. The seven rows have different subjects, kinds, relations, entry decisions, and exits. Add a later example by showing its exact decision, subject, subject pattern, route, and stop.

    Scale-free and difficult-noun recognition stress

    Use the same six A.1 constructive components and acting-eligibility condition for every exact entity below. The table supplies bounded fixtures, not shortcuts or a system taxonomy. true means the supplied inputs determine satisfaction; false means a required component fails; unknown names the missing input and blocks system-dependent reliance. Evaluation creates no kind membership or neighboring claim. For the sixth component, each positive fixture below states one local larger-assembly condition and the exact fixture fact that meets it. These fixture conditions are inputs to this evaluation, not universal rules, new relation kinds, or grounds for any neighboring claim in the third column.

    Exact U.Entity evaluated under U.SystemFixture resultClaims that remain separate
    Pump #37true by reference to A.1:5.1: constituents, assembly, reidentification, whole-level pumping characteristics, larger-system compatibility, and acting eligibility pass.Capability, assignment, inspection Work, Method, causal participation, and transformation.
    Raven-17true in this bounded fixture: its skeletal, muscular, respiratory, nervous, wing, and feather constituents stand in obtaining biological part and organization relations; continuity of the same living raven through ordinary material turnover reidentifies it; flight and homeostasis are whole-level characteristics. The construction rule stated here for the larger Aviary-3 admits a living bird constituent only when it can cross the 1.5 m gate, remain within the 5 kg perch load, and retain organism identity through entry and exit; the fixture gives Raven-17 a 1.2 m span, 1.1 kg mass, and the same-living-raven continuity rule, so those conditions pass. Its physical organization is acting-eligible.Capability or causal interaction may be current; no work-facing assignment, Method, or Work follows.
    Engineer-4true in this bounded fixture: the exact embodied person has nervous, sensorimotor, metabolic, and musculoskeletal constituents under obtaining organism relations; continuity of the same living person through ordinary cellular turnover and changes of job, clothing, or tools reidentifies Engineer-4, while replacement by another person does not; coordinated perception, movement, and self-regulation are whole-level characteristics. The construction rule stated here for the larger BridgeInspectionTeam-2026 admits an exact person constituent only when the person can use the team's spoken Channel-BR4 and Harness-H2 interfaces without changing personal identity; the fixture states that Engineer-4 can use both interfaces and remains the same person across the required clothing and tool changes, so those conditions pass. The physical organization is acting-eligible.Job title, capability, assignment, Method, dated Work, causal participation, and transformation each need a subject pattern.
    runtime whole DispatchAgent-12true only in this bounded runtime fixture: one runtime process, authoritative state carrier, control loop, and tool adapters stand in obtaining control, data, and tool-link relations; continuity of the declared process boundary and authoritative-state lineage reidentifies the same running instance, while a separately initialized lineage does not; dispatch behaviour is whole-level. The construction rule stated here for the larger DispatchPlatform-DP4 admits one runtime whole only when its input boundary implements DispatchInput-v3, its adapters implement ToolPort-v2, and an allowed reconnect preserves the same authoritative-state lineage; the fixture supplies those two interface matches and that lineage-preserving reconnect, so the conditions pass. The operational organization is acting-eligible. Code or a model file is another object.The word agent establishes no capability, assignment, Method, tool-call Work, or transformation.
    InspectionRobot-R7true in this bounded fixture: its chassis, sensors, controller, power unit, and drives stand in obtaining mounting, power, and control relations; the maintenance rule preserves identity across allowed component replacement but not replacement of the whole; sensing and motion are whole-level characteristics. The construction rule stated here for the larger PlantInspectionCell-7 admits one robot constituent only when mount M-R7, 48 V power, and InspectBus-v2 control interfaces all match and allowed component replacement preserves robot identity; this fixture supplies all three matches and the stated maintenance identity rule, so the conditions pass. Its physical/computational organization is acting-eligible.Inspection capability, contact, assignment, Method, Work, and workpiece change remain separate.
    BridgeInspectionTeam-2026; near miss: roster episteme BridgeInspectionRoster-2026true for the coordinated organization in this bounded fixture: named inspectors, equipment, and coordinating artifacts stand in obtaining membership, assignment, and coordination relations; the charter-and-coordination continuity rule reidentifies the team through permitted member substitution; inspection capability is whole-level. The construction rule stated here for the larger BridgeRenewalOrganization-2026 admits one coordinated team constituent only when its charter boundary exposes InspectionReportPort-BI and EquipmentHandover-BI and permitted member substitution preserves team identity; the fixture supplies both obtaining interfaces and the charter continuity rule, so the conditions pass. Independently grounded work-facing participation supports acting eligibility. false for BridgeInspectionRoster-2026: the episteme lists names but supplies no obtaining assembly or whole-level acting characteristic, so the proposed system reading for that exact roster and boundary fails.The team's assignments and Work are independently grounded; the roster gains no capability, Method, Work, causal position, or transformation from its content.
    exact Moon; neighboring tide case follows CoastalBasin-5true for the Moon in this bounded fixture: its crust, mantle, and core are exact constituents under obtaining material-part and gravitational-cohesion relations; continuity of the same gravitationally coherent astronomical body through ordinary surface impacts and mass exchange reidentifies it; orbital and gravitational characteristics are whole-level. The construction rule stated here for the larger EarthMoonOrbitalAssembly-1 admits one astronomical body constituent only when a direct dynamics account gives it a bound Earth-orbiting position and the body's boundary and identity survive the ordinary impact and mass-exchange range; the fixture independently supplies that bound-orbit fact and the stated identity rule for the exact Moon, so the conditions pass. Its physical organization is acting-eligible. That direct dynamics fact, not systemhood, may separately give it an actor-side position. CoastalBasin-5 is instead identified by its shoreline, inlet, depth range, and persistence rule for the tide-related change; this row does not decide that bearer's systemhood, and generic water identifies neither one referent nor a system.Moon systemhood, causal participation, and the basin's tide-related transformation are separately governed; none implies a TransformerSystemRole classification, a system-role assignment, Method, or Work.
    SutureControl-M17, beside SuturingCapability@Surgeon-4true in this bounded fixture: NeuralController-17, ExocortexAid-3, and SensorimotorCircuit-4 are exact constituents under obtaining part and control relations; continuity of the learned-control profile through the allowed component-replacement rule reidentifies the whole; coordinated suture-control behaviour is whole-level. The construction rule stated here for the larger Surgeon-4-plus-tools assembly admits this control whole only when its boundary exposes matching NeuralLink-N17, AidControlPort-A3, and SensorimotorLoop-S4 interfaces and allowed replacement preserves the learned-control profile; the fixture supplies all three interface matches and that profile-continuity fact, so the conditions pass. Its physical or operational organization is acting-eligible.Capability, surgeon, system-role kind or assignment, training Method or Work, evidence, evaluation, and physical change remain distinct; no U.Mastery is admitted.
    GameSessionWhole-GS204, beside Work, interval, and record readingstrue in this bounded fixture: Player-A-GS204, Player-B-GS204, ClientRuntime-A-GS204, ClientRuntime-B-GS204, ServerRuntime-GS204, AuthoritativeStateCarrier-GS204, and two named client-server links are exact constituents under obtaining part/link relations and the stated session assembly; authoritative-state continuity plus the reconnect/terminal-close rule reidentifies the whole; interactive game-state evolution is whole-level. The construction rule stated here for the larger GameServiceAssembly-6 admits one session whole only when both links implement GameLink-v4, the server exposes SessionAuthority-v2, and reconnect keeps the same authority lineage until terminal close; the fixture supplies those link, authority, and lineage facts, so the conditions pass. Its operational organization is acting-eligible.Performer systems, assignments, play Work, interval, record, release, Method, causal interaction, and transformations remain distinct.
    InternetAccessArrangement-CA17, beside promise, permission, state, bearer, Work, and evidence readingstrue in this bounded fixture: CustomerTerminal-CA17, Gateway-7, ProviderEdge-CA17, LinkCarrier-CA17, and RouteController-CA17 are exact constituents under obtaining part/link relations and one operational assembly; circuit/account continuity plus allowed failover reidentifies the arrangement; end-to-end packet exchange is whole-level. The construction rule stated here for the larger ProviderDeliveryAssembly-CA17 admits this arrangement only when the terminal, gateway, provider-edge, carrier, and route-controller interfaces keep the same circuit/account through allowed failover and jointly meet availability at least 99.9%, latency at most 60 ms, and throughput at least 100 Mb/s; the fixture supplies those interface, continuity, and measured-threshold facts, so the conditions pass. Its operational organization is acting-eligible. A bare access-availability state has no constituents or assembly and fails only if substituted as the exact proposed whole; its bearer and state claim remain separately governed.A.6.P remains the pattern for promise, permission, provider/consumer participation, status, capability, Method, intended or dated Work, evidence, fulfilment, and acceptance. Gateway-7 remains a separately identified constituent and bearer; no U.Access, generic access relation, assignment, Work, or transformation follows.
    Across all rows, first preserve the exact entity named by the proposed system reading. Do not replace it with a neighboring person, capability, Work occurrence, interval, record, endpoint, state, or bearer before A.1 evaluation.

    Bias-Annotation

    Bias pressureMisreadingCorrection
    Noun-induced systemhoodSession, service, program, or another familiar noun is treated as proof of a system.State the decision and proposed subject; use the subject-pattern exit or apply A.1 only when systemhood matters.
    Classification ritualEvery unfamiliar phrase receives the complete A.1 test.Stop after an exact Work, Method, capability, structure, episteme, or relation answers the decision.
    Temporary reading becomes ontologyRepeated testing creates a candidate kind or third ontic state.Keep one exact U.Entity; evaluation does not create kind membership.
    Physical-realization identityShared material or extent identifies system, local system-role kind or assignment, capability, Work, transformation, Method, plan, evidence, or description.Apply each object's direct identity rule.
    Project-designation overreadA recognized or affected system is automatically called the project system-of-interest.Require one named plan or decision designation; keep system identity, system-role-kind interpretation, and system-role assignment separate.
    Example-taxonomy pressureThe seven rows are read as one kind.Read each through its own decision, subject, route, and stop.

    Conformance Checklist — Practical Checks

    IDCheck
    CC-A1-SCR-1The current claim, proposed actor/change bearer, and system-dependent decision are named before any A.1 test.
    CC-A1-SCR-2A direct Work, Method, capability, transformation, episteme, structure, or relation result exits immediately when it answers the decision.
    CC-A1-SCR-3The complete six-component A.1 criterion and acting eligibility are applied only when systemhood remains load-bearing.
    CC-A1-SCR-4The first result names the direct object, recognized system, rejected reading, or unresolved evaluation and a concrete next move or stop.
    CC-A1-SCR-5unknown remains epistemic and changes no world-side kind membership.
    CC-A1-SCR-6Add a neighboring claim only under its subject pattern and only when the named decision needs that claim.
    CC-A1-SCR-7Service/access ambiguity begins in A.6.P §4.11a and returns here only for a separate system-dependent claim about the exact entity recovered there—an exact bearer or access-providing arrangement.
    CC-A1-SCR-8A missing relation preserves exact participants and dependent use and records the established A.6.RCD result missing-governor[...].
    CC-A1-SCR-9Project system-of-interest designation follows a named plan or decision; recognition, affectedness, system-role-kind interpretation, and system-role assignment neither establish nor replace it.
    CC-A1-SCR-10Physical grounding creates no cross-kind identity or unrestricted composition.
    CC-A1-SCR-11The seven noun cases and the scale-free stress fixtures state their exact entities, subject-pattern alternatives, result semantics, and blocked inferences; they form no kind or closed enumeration.
    CC-A1-SCR-12No new candidate, session, access, mastery, situation, relation, restoration-record, or bundle ontology is introduced.

    Common Anti-Patterns and Exact Repairs

    Anti-patternWhy it failsRepair
    Complete A.1 test before the decision is knownClassification work may change nothing.State what depends on systemhood; take the subject-pattern exit when it does not.
    Pattern list without an actor/change bearerThe reader still cannot act.Name the exact subject and concrete decision.
    Temporary reading treated as a kindEvaluation position becomes ontology.Keep one exact U.Entity under an admitted kind test.
    Unknown as a third ontic stateMissing information becomes world-side indeterminacy.Name the missing input and blocked decision.
    Neighbor bundleDifferent identity laws disappear.Return the subject first, then separately governed claims needed now.
    Physical-realization identityCo-location or one embodiment merges kinds.Apply each identity rule and relation governor.
    Project designation inferredRecognition or affectedness is mistaken for designation as the project system-of-interest.Name the plan or decision; test any system-role kind and system-role assignment separately.
    Software service treated as systemSource-domain metonymy silently chooses a bearer.Begin in A.6.P, name the exact referent, and enter here only for a system-dependent claim.

    Consequences

    The pattern makes full system recognition more useful by applying it only where identity and boundary change an engineering decision. It also makes subject-pattern results productive: Work, Method, capability, structure, episteme, and relations can close their own questions. The cost is that the practitioner must state the decision and may need to stop when construction facts or a relation governor are missing.

    Rationale

    The smallest reusable repair is a conditional MethodDescription, not a new kind or universal router. A.1 supplies the system-recognition predicate. A.1.SCR contributes a working situation, subject-pattern result, complete-test branch, decision-bearing results, project-designation guard, and migration cases. This prevents ontology work from becoming a ritual, prevents a familiar noun from selecting an actor or project system-of-interest, and prevents a convenient neighboring referent from erasing an exact proposed-system reading before evaluation.

    Extent-sensitive identity remains useful because it forces the practitioner to state what exists and survives change. Unrestricted composition and category import remain rejected. The seven cases demonstrate transfer across domains without asserting a common kind.

    SoTA-Echoing

    Informative. These sources provide bounded pressure on the practitioner route. A.1 and the named subject patterns remain authoritative for kinds, relations, and pass conditions.

    SourceUseful pressure for this patternDispositionA.1.SCR action, stop, or limit affected
    R5 Systems Thinking and R6 Systems Modeling guides, current and historical formsSystems practice keeps a project system-of-interest and its outside use visible before internal design, but source wording often slides among the system, its function, role, service, bearer, and project designation.Adopt decision-first attention; adapt the designation; reject lexical identity.A.1.SCR:0 and 4.1 first name the exact decision and proposed entity. Section 4.7 requires a separate plan or decision for project-system designation and requires A.1.STM for a still-missing outside-use dependency; outside-before-inside does not become part of the A.1 kind criterion.
    R5/R6 scale-free physical-action and nonliving-actor passagesThe same recognition question must work for engineered, living, artificial, human, collective, and natural wholes without treating intelligence, employment, or biology as the admission test.Adopt the scale-free test; reject anthropomorphic and family-specific shortcuts.A.1.SCR:4.3 applies the same six A.1 components and acting-eligibility condition. Section 5.1 replays that test across all families, then leaves capability, causal position, assignment, Method, Work, and transformation to their subject patterns.
    R5/R6 mastery, session, internet-access, and service passagesEach phrase carries a useful proposed physical or operational whole alongside rival capability, Work, interval, record, promise, permission, state, bearer, and service-delivery readings. The source traditions do not agree on one default referent.Adapt the proposed-system readings; reject word-induced systemhood and service normalization.A.1.SCR:4.2 takes a subject-pattern exit first; 4.6 begins unresolved service/access wording in A.6.P; sections 5 and 5.1 preserve each rival reading and evaluate only the exact U.Entity named by the proposed-system branch. Missing referent or construction facts stop the system-dependent use.
    Florio and Linnebo, Introduction to Constructional Ontology, 2024Construction choices affect identity and require constructors, inputs, and construction-sensitive distinctions.Adapt as a conditional recognition and stopping test.Only the system-dependent branch in A.1.SCR:4.3 recovers constituents, obtaining relations, assembly, reidentification, whole-level characteristics, and larger-assembly applicability. Missing information about a required component returns unknown; the source does not authorize a new candidate kind or a classification ritual.
    Deutsch, Constructor Theory, 2012Possible transformations depend on substrate attributes and constructor conditions, not on a written task alone.Adapt larger-assembly applicability; reject actuality from description.A.1.SCR:4.3 and 5.1 require the governed applicability and compatibility facts used by the current fixture. A plan, Method description, constructor label, or task proves neither assembly, acting participation, Work, nor transformation.
    Partridge, BORO Ontology, C-FORS 2025Four-dimensional identity pressure asks what exists through change and across extent.Reject wholesale categories; retain the identity probe.A.1.SCR:4.8 asks for the exact entity, boundary, reidentification, and construction facts while forbidding identity between a system and its system-role kind, capability, Work, or description merely from shared extent. No unrestricted composition or BORO category is imported.

    The conditional method assembled here—state the decision, close with an exact subject assertion when possible, apply the complete A.1 test only when systemhood remains load-bearing, and use the Method described in A.1.STM for a recognized project subject only when the outside-use dependency is still missing—is a scoped FPF synthesis of these pressures, not an external consensus claim. Reopen the synthesis if A.1 changes its constructive criterion, A.6.P changes the service/access recovery boundary, A.15.6 changes project designation, or later cross-domain evidence defeats the scale-free decision method or one of its explicit stops.

    Relations

    • Builds on: A.1 for the complete constructive criterion, admitted holon kinds, acting eligibility, and true | false | unknown evaluation discipline.
    • Leaves directly through: A.2.2, A.3.1, A.3.2, A.3.4, A.15.1, A.15.2, A.22, C.2.1, E.18, and the exact relation pattern when systemhood is not load-bearing.
    • Service/access first use: A.6.P §4.11a; A.1.SCR applies only to a separate system-dependent claim about the exact entity recovered there—an exact bearer or access-providing arrangement.
    • Uses for projects: A.15.6 for the actual and intended system distinction, plan or decision designation of the project system-of-interest, separate tests of the system-role kind and assignment, project-relevant network selection, and missing-substrate[project-selection-conjunction]; A.1.STM only when the returned recognition result must re-enter the system-thinking long map.
    • Uses for missing relations: A.6.RCD with exact participants, receiving use, and missing-governor[...].
    • Coordinates with: A.1.CSD when a returned bearer result opens the separate question of which other Systems may undergo relevant changes; A.1.STM for the separate long-map use after recognition; and E.10 for lexical triggers.
    • Does not replace: A.1, direct kind patterns, relation patterns, A.6.P, or F.18 designation recovery.

    A.1.SCR:End

    Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)