Systems: Boundaries, Interactions, and AI

A system is more than a collection of parts. This essay explains boundaries, interactions, state, feedback, emergence, purpose, and why an AI model is only one component of an AI system.

A pile of parts is not yet a system. A list of employees is not yet an organization. A language model is not, by itself, the complete application that a user encounters.

The word system becomes useful when parts are related in ways that produce persistent behavior at the level of a whole.

A system is a bounded set of interdependent elements whose organization and interactions produce behavior over time within an environment.

This definition contains several commitments. A system has elements, but it cannot be understood from an inventory alone. It has a boundary, though that boundary depends partly on the question being asked. It has a state that can change. It interacts with an environment. Its overall behavior depends on relations among parts, not merely on the parts considered separately.

The word and its central idea

English system comes through Latin systema from Greek systēma, an organized whole composed of parts. Its roots carry the idea of things standing together rather than existing as an unrelated assortment.Etymonline: system

The term now covers very different objects:

  • the solar system;
  • a nervous system;
  • an ecosystem;
  • a legal system;
  • an organization;
  • a payment system;
  • a software system;
  • an AI system.

These examples do not share one material composition or one kind of purpose. What they share is an analytical form: distinguishable elements participate in relations that sustain some pattern of behavior at the level of a whole.

What must a system contain?

The smallest useful account of a system normally identifies:

elements
+ relations
+ a boundary

An account of how the system operates also needs:

state
+ rules or mechanisms of change
+ an environment
+ inputs and outputs
+ time

For an engineered system, further questions become central:

intended purpose
+ constraints
+ performance criteria
+ authority and responsibility

Engineering standards commonly define a system as interacting elements organized to achieve one or more stated purposes.ISO/IEC/IEEE 42020:2019

That purpose-centered definition is appropriate for engineered systems. It should not be projected onto every natural system. A climate system and a river system display organized behavior without needing intentions of their own.

A system is not an inventory

Suppose an online publishing operation contains an author, articles, Markdown files, a Git repository, a static-site generator, a deployment service, a domain, search engines, and readers.

The list tells us what might be present. It does not yet explain the system. The explanation begins with relations:

author ──writes──> article
article ──stored as──> Markdown
Git ──records──> revision
site generator ──transforms──> web page
deployment service ──publishes──> site
reader ──visits──> page
search engine ──indexes──> content

The system exists as an organized pattern of dependencies, transformations, permissions, and flows. If those relations disappear, the same objects may remain, but the publishing capability does not.

This is why a system is not simply the sum of its components. Organization is causally relevant.

How is a system different from a collection?

A collection is defined mainly by membership. A system is defined by interdependence and organization.

CollectionSystem
Answers which members are includedAnswers how elements interact
Members may remain independentChanges can propagate among elements
Removing one member may only change the countChanging one part may alter overall behavior
Does not require a shared capacityOrganization may create a capacity of the whole

One hundred chairs in a warehouse form a collection. Players, coaches, rules, training, communication, and matches may form a team system. A contact list is a collection of records. Communication, roles, authority, and feedback can turn a group of people into an operating organization.

Boundaries make system analysis possible

Everything is connected to something else. If every remote influence must be included, the system expands until it becomes indistinguishable from the world. A useful analysis therefore defines a boundary.

A boundary answers:

Which elements and relations belong to the system under study, and which belong to its environment?

Consider a coffee shop. An analysis of waiting time may include customers, ordering, baristas, equipment, and queue rules. An analysis of profitability may add rent, suppliers, delivery platforms, and pricing. A food-safety analysis may include storage, temperature control, cleaning, and regulation.

The coffee shop has not become three different objects. The analytical boundary changes because the question changes.

INCOSE describes the environment as the part of the outside world that significantly interacts with and affects a system, often as the source of inputs and destination of outputs. Defining the boundary and environment is therefore a basic step in systems thinking.INCOSE: Systems Thinking 101

The boundary is selected, but it is not arbitrary. A model cannot exclude a major causal influence merely because including it would make the diagram untidy.

Open systems exchange with an environment

An environment may provide information, energy, materials, users, prices, legal constraints, threats, and disturbances. A system may return products, decisions, services, waste, risk, and social effects.

environment
    ↓ input
system state and operation
    ↓ output
changed environment
    ↓ new input
continued operation

Most systems studied in biology, society, organizations, and computing are open in this sense. They depend on continued exchange.

A closed system is often an analytical idealization. It means that particular exchanges can be ignored for a particular purpose, not that the object has no relation to anything outside it.

Systems have state and history

A system is not only an architecture diagram. It occupies states, changes state, and carries effects from its history.

A website may be healthy, building, partially deployed, unavailable because of DNS, or updated in a repository while production still serves an earlier release. The same components and nominal connections can therefore produce different outcomes at different moments.

A simple dynamic description is:

current state + input + transition rules
                    ↓
             next state + output

Time delays matter. A page may be live before a search engine indexes it. A product may improve before public expectations change. A policy may appear effective in the short term while accumulating a long-term cost.

Ignoring delay turns a dynamic system into a misleading snapshot.

Feedback changes subsequent behavior

Feedback occurs when an output or consequence returns as an influence on later system behavior.

Negative feedback counteracts a deviation. A thermostat detects a falling temperature, turns on heating, and later turns it off as the room returns to range. Negative feedback often supports stability.

Positive feedback reinforces a change. More engagement may produce more recommendation exposure, which produces more engagement. Positive feedback may create growth, lock-in, polarization, or collapse.

The words positive and negative do not mean good and bad. They describe whether the loop amplifies or counteracts change.

Delayed feedback can cause overshoot and oscillation. Missing feedback can allow a system to optimize a proxy long after the proxy has stopped representing the intended result.

Emergence comes from organization

“The whole is greater than the sum of its parts” is a familiar systems slogan. It is suggestive but imprecise.

What the inventory omits is organization: spatial arrangement, causal interaction, timing, feedback, and constraints. Those relations allow a whole to display properties that isolated parts do not display.

  • A single vehicle does not constitute a traffic jam; many mutually constraining vehicles can.
  • A single market participant does not determine a market price; structured interaction among many participants may produce one.
  • A single neuron does not perform the full cognitive work of a nervous system; organized neural activity supports higher-level capacities.
  • A molecule does not have the thermodynamic temperature of a macroscopic body; temperature characterizes a collective state.

Systems biology likewise studies components in the context of their interactions and the constraints imposed by the whole.Stanford Encyclopedia of Philosophy: Philosophy of Systems and Synthetic Biology

Emergence should not be used as a label for mystery. An emergent property still calls for an explanation of arrangement, interaction, scale, constraint, and time.

Does every system have a goal?

No. Purpose, function, and intention must be distinguished.

An engineered payment system is built for stated purposes. An organization may pursue several partly conflicting objectives. A heart performs a biological function that can be explained through physiology and evolution without attributing intention to the organ. A solar system displays lawful behavior without pursuing a goal.

Even in designed systems, four things can diverge:

stated purpose
designer intention
metric actually optimized
outcome actually produced

A recommendation service may claim to improve user satisfaction while optimizing clicks. Higher click-through rates may coexist with lower trust, worse information quality, or compulsive use.

A system should therefore be evaluated by its operation and effects, not only by its declared purpose.

System, structure, mechanism, process, and model

These terms answer different questions.

TermCentral question
SystemWhich elements interact within which boundary, producing what behavior?
StructureHow are elements arranged, connected, and layered?
MechanismThrough which causal organization is an outcome produced?
ProcessIn what temporal sequence do activities and transformations occur?
FunctionWhat capacity or contribution does a whole or part provide?
OrganizationHow are people, roles, rules, and authority coordinated?
NetworkWhat topology is formed by nodes and links?
ModelHow is the object represented for understanding, explanation, or prediction?

A publishing system has a structure of repositories, builders, and servers; a mechanism that converts Markdown into HTML; a process of drafting, review, commit, build, and deployment; and a function of making content reliably accessible.

The system is the object under study. A system model is a selective representation of that object. A diagram may omit details usefully, but success in the diagram does not guarantee success in the world.

Systems, entities, and ontology

An entity analysis asks which particular object is being referred to. A system analysis asks how entities and relations are organized into behavior over time. An ontology specifies which kinds of entities and relations a domain recognizes.

entity: an identifiable object
relation: a way objects are connected
system: organized objects and relations operating over time
ontology: an account of the recognized kinds and relations

A system can itself be treated as an entity. A payment system may have an owner, version, status, service boundary, and lifecycle. At a lower level, the same system contains account, order, fraud-control, channel, and settlement subsystems.

Something can therefore be a system at one level and a component of a larger system at another. The relevant level depends on the question.

Related discussions appear in “What Is an Entity? Identity, Reference, and AI Systems” and “What Is Ontology? From What Exists to What AI Can Represent”.

Subsystems and systems of systems

Complex systems are often nested:

component
    ↓
subsystem
    ↓
system
    ↓
larger system

A payment interface may belong to an order-and-payment subsystem, which belongs to an e-commerce platform, which participates in a broader commercial and logistics environment.

A system of systems joins systems that can still operate and be managed with substantial independence. Urban mobility, for example, may involve roads, buses, rail, navigation, ticketing, traffic control, taxis, and ride-hailing platforms. No single component completely determines the whole, yet their interactions shape citywide movement.

This creates coordination problems that cannot be solved by optimizing one subsystem alone.

Are systems discovered or constructed?

Both descriptions capture part of the truth.

Real interactions, dependencies, feedback loops, and constraints are not invented merely by drawing a boundary. Traffic congestion, ecological exchange, institutional authority, and software calls have real effects.

Yet the choice of boundary, scale, state variables, and level of abstraction depends on what the investigator needs to explain. The same person can participate in biological, family, legal, organizational, economic, and information systems.

A useful position is:

Interactions are constrained by reality; system boundaries and levels are selected for inquiry and action.

The model must remain answerable to observed behavior. A convenient boundary that excludes decisive effects is a bad boundary.

System boundaries also carry values and power

Boundary choices determine what becomes visible.

When a system defines who counts as a user, which outcomes count as benefits, which harms count as externalities, which metric receives optimization pressure, and who may change the rules, it embeds practical and political judgments.

A delivery platform that measures only completed orders per hour may improve its internal efficiency while moving safety risk, waiting pressure, and road danger onto workers and the public.

The system did not eliminate the cost. Its measurement boundary excluded the cost.

Systems analysis therefore asks more than whether an operation is efficient:

  • Efficient for whom?
  • Which outcomes are measured?
  • Who absorbs failure and delay?
  • Who has authority to change the objective or boundary?
  • Which effects appear only in a larger system?

What is an AI system?

An AI system is not synonymous with an AI model.

A deployed language-model application may include:

users and operators
+ interface
+ prompts and context
+ one or more models
+ retrieval and knowledge sources
+ memory and state
+ tools and external services
+ orchestration and control flow
+ identity and permissions
+ runtime infrastructure
+ logging and evaluation
+ human review
+ outcome feedback

The model performs part of the inference. The surrounding system decides what reaches the model, which external state is available, which tools may run, whose authority applies, how outputs are checked, and what changes in the world.

The OECD definition describes an AI system as a machine-based system that infers from inputs how to produce predictions, content, recommendations, or decisions that can influence physical or virtual environments. Its explanatory material describes a model as a core component of such a system.OECD: Updated Definition of an AI System

NIST emphasizes that AI systems are sociotechnical: their benefits and risks emerge from technical components together with operators, users, other systems, and the social context of deployment.NIST AI Risk Management Framework

A model can answer while the system still fails

A language model may generate a correct article draft. Publishing that article reliably requires a larger system to:

  • resolve the intended article and language versions;
  • read repository rules;
  • modify the correct files;
  • preserve identity and authorization boundaries;
  • validate the build;
  • commit and push with the correct repository identity;
  • wait for deployment;
  • verify the live pages, canonical URLs, language links, and sitemap.

Failure can occur at any boundary. The model may be correct while retrieval supplies stale facts. The plan may be correct while a tool targets the wrong entity. The code may build locally while deployment fails. The page may be live while search metadata is missing.

Therefore:

Model capability does not by itself establish system reliability.

Evaluation must match the system boundary. A model benchmark measures a model under specified conditions. It does not automatically measure the complete product, workflow, organization, or real-world outcome.

A practical method for analyzing a system

  1. State the question. Are you trying to explain, design, improve, control, or evaluate the system?
  2. Draw the boundary. What belongs inside, what belongs to the environment, and why?
  3. Identify elements. Include people, software, physical objects, rules, institutions, data, and resources.
  4. Map relations and flows. Track information, material, money, authority, and dependency.
  5. Describe states and transitions. What states can occur, and what changes one state into another?
  6. Find feedback loops. Which consequences reinforce or counteract earlier behavior?
  7. Examine delays. When do outputs and consequences become observable?
  8. Separate goals from metrics. What outcome is intended, and what variable actually receives optimization pressure?
  9. Locate constraints and authority. Who can change which element, rule, or boundary?
  10. Inspect excluded effects. Which people, costs, and risks appear only when the boundary expands?

A final definition

A system can be defined as:

A system is a bounded whole in which interdependent elements operate through some organization and rules, change state over time, interact with an environment, and thereby produce behavior or capacities at the level of the whole.

For designed systems, that account must also include purpose, constraints, metrics, authority, and responsibility.

A system is not merely many things placed together, and it is not merely an architecture diagram. It exists as organized interaction: changes in one part affect others, relations alter outcomes, and the condition of the whole constrains what its parts can do.

Identifying entities tells us what is present. Understanding a system tells us how those entities operate together and why the observed result occurs.

References

If this was useful, subscribe via RSS.

Content is open for citation with attribution; please link back to the source.