system
instrumentality that combines interrelated interacting artifacts designed to work as a coherent entity
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
Enable an AI agent to recognise an engineered physical system, assess whether its interacting artifacts can perform their intended joint function, and determine which operations or changes are justified.
A system, in this physical artifact sense, is an engineered combination of interrelated, interacting artifacts arranged to function as a coherent entity for an intended purpose.
It can be Trace an intended function through the artifacts, interfaces, and external services needed to deliver it.; Assess readiness for a specified operating mode using constituent conditions and integration evidence.; Identify which system functions may be affected by a failed constituent or disrupted interface.; Evaluate whether a proposed replacement or reconfiguration requires renewed integration checks.; Determine prerequisites for startup, shutdown, isolation, maintenance, and return to service.; Compare observed joint performance with the acceptance criteria for the assembled configuration..
Distinguishing features
Its artifacts have designed interactions that contribute to an identifiable joint function; proximity or shared ownership alone does not establish a system.
Its functional boundary identifies what participates in collective operation and what supplies external services or environmental conditions.
Assessing the constituents separately does not establish system readiness; their connections, compatibility, and coordination also require assessment.
The selected level of description owns a joint function across constituent artifacts, even when a constituent could itself be modelled as a device, machine, or subsystem.
The term refers here to an engineered physical instrumentality, rather than any organised collection of concepts, institutions, or biological structures.
Scope
+ The intended joint function that makes several artifacts one system
+ System boundaries, constituent roles, and dependencies on external systems
+ Interfaces and exchanges through which artifacts interact
+ System operating modes, coordination, and performance constraints
+ Integration evidence, failure propagation, and conditions for safe intervention
- Naturally occurring biological systems, including lymphatic and urinary systems
- Political and institutional arrangements, including parliamentary systems
- Abstract mathematical systems and conceptual classification systems
- Detailed internal construction of constituent devices, machines, or tools
- Product-line identities, commercial catalogue records, and individual-unit histories as separate models
- Standalone software systems without an engineered physical artifact assembly
Characteristics
- Joint function
- Declared system-level functions with observable success criteria Provides the basis for deciding whether the artifacts form a coherent instrumentality and whether it works.
- Boundary and constituent roles
- Included artifacts and subsystems, their functional roles, and explicitly external entities Separates system responsibilities from assumptions about its surroundings.
- Interface dependencies
- Connected endpoints, exchange type, direction, compatibility conditions, and dependency strength Makes the interactions that enable joint operation inspectable.
- Operating mode
- Declared modes such as isolated, starting, operating, degraded, stopping, or maintenance; applicability must be established Determines which constituent states and actions are currently valid.
- Delivered functional performance
- Function-specific measures and units, such as throughput in items/h or response time in s, where applicable Tests the joint outcome rather than assuming that healthy constituents imply adequate performance.
- External service requirements
- Required utilities, inputs, supporting systems, and acceptable supply conditions Identifies dependencies that can prevent operation even when internal artifacts are serviceable.
- Verified configuration
- Constituent versions, interface arrangements, settings, and the evidence applicable to that combination Prevents evidence from one assembled configuration being assumed valid for another.
- Functional readiness
- Unknown, unavailable, restricted, or ready against declared function and mode criteria Supports decisions about operation without reducing readiness to a count of working parts.
Analytical facets
- substance
- material
- origin
- manufactured
- agency
- inert
- mobility
- portable
- scale
- handheld
- affordances
- graspable
Also called
+109
Where this came from
oewn:2024 · CC BY 4.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 5 bundles · 9 layers · 15 findings · 27 questions.
Functional unity and boundary Establishes why the artifacts constitute one system and where that system ends.
A collection of artifacts becomes meaningful as this registered thing through designed interaction and joint function.
Joint purpose
Identifies the outcome that the artifacts are designed to deliver together.
Collective function
Record the intended joint outcome and the interactions needed to produce it.
- What observable outcome are the artifacts designed to produce together? definition
- Which interactions distinguish this system from a collection of independently useful artifacts? boundary
System of interest
Selects the level of aggregation and separates constituents from the operating environment.
Membership and nesting
Record constituent roles, nested subsystems, and external dependencies at the selected boundary.
- Which artifacts belong inside the selected boundary, and what functional role justifies each inclusion? boundary
- Which required services or connected systems remain outside that boundary? boundary
- What design or operational evidence establishes this level as the system of interest? provenance
Interfaces and integration Describes how constituent artifacts connect and the conditions under which their interactions work.
Constituents can be individually suitable while their assembled interfaces prevent coherent operation.
Interaction paths
Makes the exchanges between constituents and across the system boundary explicit.
Exchange contracts
Record relevant transfers of energy, material, information, or mechanical load and their compatibility requirements.
- What passes across each function-critical interface, between which endpoints, and in which direction? definition
- What limits, units, tolerances, or timing conditions must each exchange satisfy? measurement
Assembled compatibility
Relates integration evidence to the actual combination of constituents and settings.
Configuration validity
Identify the configurations for which interface compatibility and joint operation have been demonstrated.
- Which constituent versions, connections, and settings are covered by the available integration evidence? provenance
- Which proposed substitutions or connection changes require compatibility checks before operation? action
Coordinated operation Captures the modes, sequencing, and shared constraints needed for artifacts to operate together.
Coherent operation depends on compatible states and coordinated transitions across the assembly.
Modes and transitions
Defines system modes through required constituent states and transition prerequisites.
Collective state
Record how constituent states establish a system mode and what permits a change of mode.
- Which combinations of constituent states establish each supported system operating mode? definition
- What sequencing, permissions, and interlocks, if any, govern startup, shutdown, and mode changes? action
Joint performance
Assesses delivered function under shared resource limits and external operating conditions.
System operating envelope
Record measurable acceptance criteria and the combinations of load, supply, and environment under which they apply.
- Which system-level measures demonstrate successful joint operation, and what are their acceptance limits and units? measurement
- Which shared-resource limits or constituent bottlenecks constrain the assembled system under its intended load? measurement
- What external supply and environmental conditions are assumed by those performance criteria? boundary
Failure containment and intervention Connects constituent and interface failures to collective consequences and justified interventions.
Interaction can transmit failures, defeat apparent redundancy, or make a local maintenance action affect the whole system.
Failure propagation
Traces loss or corruption of constituent contributions through dependent functions.
Functional loss and containment
Record affected functions, propagation paths, and evidenced isolation or redundancy arrangements.
- Which joint functions are lost or degraded when each critical constituent or interface fails? definition
- What evidence supports claimed containment or redundancy, including dependencies shared by backup paths? provenance
- Under what established conditions may the remaining assembly continue operating? action
Intervention and restoration
Determines how maintenance or change affects the connected assembly and its return to service.
Isolation and requalification
Record cross-boundary isolation needs and checks required to restore confidence in joint operation.
- Which connected artifacts, supplies, stored energies, or control paths must be addressed before the proposed intervention? action
- Which interface and system-function checks must pass after reconnection, replacement, or reconfiguration? action
- What evidence establishes that the restored configuration meets its applicable operating and safety criteria? provenance
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- This entry covers the generic artifact kind, not a particular product model or installed unit, and excludes biological, political and purely abstract senses.
- There is no defensible capacity, dimension, power requirement or operating range for this broad kind; measurements require a specified application and system boundary.
- The named standards are recalled references, not researched citations; applicable editions, legal requirements and sector-specific standards need verification.
- Which of these check these first hold for the sense of system this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Mechanical systems
- Electrical systems
- Electronic systems
- Hydraulic systems
- Pneumatic systems
- Electromechanical systems
- Which of these kinds and varieties hold for the sense of system this model covers, and on what evidence? provenance
Standards and regulation
Recalled without web access and unsourced; every item is a lead to verify.
- ISO/IEC/IEEE 15288, issued jointly by ISO, IEC and IEEE, defines system life cycle processes applicable to engineered systems.
- ISO/IEC/IEEE 42010, issued jointly by ISO, IEC and IEEE, specifies requirements for architecture descriptions of systems and other entities.
- IEC 61508, issued by the International Electrotechnical Commission, addresses functional safety of electrical, electronic and programmable electronic safety-related systems where applicable.
- Which of these standards and regulation hold for the sense of system this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Combining generation, distribution and protection equipment to supply electrical power.
- Integrating pumps, valves, actuators and controls to transmit hydraulic power.
- Coordinating heating, ventilation and cooling equipment to maintain indoor conditions.
- Integrating sensors, controllers and actuators to control industrial processes.
- Combining communication equipment and transmission links to carry information.
- Which of these real-world use hold for the sense of system this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Interface incompatibility can prevent components from exchanging power, material or information correctly.
- Failure of a shared power supply, controller or other dependency can disable multiple components simultaneously.
- Faults can propagate between connected components and produce cascading loss of function.
- Feedback instability or poorly coordinated controls can cause oscillation, unsafe motion or operation outside intended limits.
- Incorrect configuration, maintenance or replacement parts can defeat safeguards or introduce hazardous interactions.
- Which of these failure modes and hazards hold for the sense of system this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Applicable electrical, machinery, pressure-equipment and conformity-assessment requirements vary by jurisdiction and application.
- Which of these regional variation hold for the sense of system this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- component - A component is considered as a constituent of a larger entity; a system is considered through the coordinated function of its interacting constituents.
- assembly - An assembly emphasizes parts joined together; a system emphasizes their interactions and collective function, even when its parts are spatially distributed.
- machine - A machine performs work through mechanisms; a system can incorporate several machines or consist of artifacts whose collective function does not require mechanical work.
- subsystem - A subsystem is itself a system considered within a larger system boundary; the distinction depends on the chosen scope.
- lymphatic system - A lymphatic system comprises biological structures and processes, so it uses a biological sense of system rather than this engineered-artifact sense.
- urinary system - A urinary system comprises organs involved in urine production and elimination, rather than designed, interacting artifacts.
- parliamentary system - A parliamentary system organizes political institutions and authority, rather than physical artifacts operating together.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of system this model covers, and on what evidence? provenance
What the second pass must settle
- Does an existing Vercy world model already cover this engineered physical sense of system, requiring a link instead of a separate publication?
- How does the registry distinguish system from assembly, apparatus, machine, and installation when the same artifact grouping satisfies several descriptions?
- Where should the physical-system boundary fall for software-controlled or human-operated assemblies, especially when software or operator action is essential to coordination?
- Which primary sources should establish the general systems-engineering terminology, and which standards apply only to particular system families?
- What evidence threshold should distinguish declared compatibility, demonstrated integration, and readiness for a particular operation?