A.1.SCR:5 - Archetypal Grounding — Seven Heterogeneous Worked Cases
Each row states whether the A.1.SCR trigger actually fires. The rows are examples.
| Source phrase | First useful result and route | Next move and governed additions | Near 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.
A.1.SCR:5.1 - Scale-free and difficult-noun recognition stress
Apply the same six A.1 constructive components and acting-eligibility condition to each exact entity below. The table supplies bounded fixtures. true means the supplied inputs determine satisfaction; false means a required component fails; unknown names the missing input and blocks system-dependent reliance. For the sixth component, each positive fixture states one local larger-assembly condition and the fact that satisfies it. Establish other claims needed by the current decision under their subject patterns.
Exact U.Entity evaluated under U.System | Fixture result | Case-specific fact or next use |
|---|---|---|
Pump #37 | true by reference to A.1:5.1: constituents, assembly, reidentification, whole-level pumping characteristics, larger-system compatibility, and acting eligibility pass. | |
Raven-17 | true: 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. | |
Engineer-4 | true: 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. | |
runtime whole DispatchAgent-12 | true for this runtime whole: 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. | |
InspectionRobot-R7 | true: 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. | |
BridgeInspectionTeam-2026; near miss: roster episteme BridgeInspectionRoster-2026 | true for the coordinated organization: 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. |
exact Moon; neighboring tide case follows CoastalBasin-5 | true for the Moon: 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. | Use the dynamics account for the Moon’s causal participation; identify CoastalBasin-5 as the subject of the tide-related change. |
SutureControl-M17, beside SuturingCapability@Surgeon-4 | true: 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. | Evaluate the proposed SutureControl-M17 whole; use the subject-pattern exit in :0 for a claim about the surgeon’s capability. |
GameSessionWhole-GS204, beside Work, interval, and record readings | true: 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. | Identify the play Work, interval or session record separately when that is the selected subject; this fixture tests the operational session whole. |
InternetAccessArrangement-CA17, beside promise, permission, state, bearer, Work, and evidence readings | true: 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. | Use A.6.P for service/access recovery. Gateway-7 remains a separately identified constituent and bearer. |
Across all rows, first preserve the exact entity named by the proposed system reading.