Composing the Whole

Sústēma, Systems Engineering, and the Sociological Cost of the Engineering Box

James Wolstencroft · July 2026

Archē · Paper I of III

Abstract

Contemporary discourse treats almost everything as a system: markets, ecosystems, institutions, and software are all read through the same structural lens. That habit feels timeless, but the word it borrows, sústēma, began as a name for a handful of specific arrangements, musical, poetic, astronomical, and only later swelled to cover the whole of reality. This paper traces that swelling from Aristotle’s hylomorphism through the Cold War’s forced adoption of a rigorously mechanistic systems engineering, to its culmination in Model-Based Systems Engineering (MBSE), and asks what got left outside the box when the system became an engineering problem rather than a philosophical one. Two threads run underneath the whole argument without being followed to their ends here: the deep history of the emergent whole, and the deep history of the trace that lets us track it. Both are picked up, respectively, in the two papers that follow.

1. A borrowed word outgrows its origin

The system was not always everything; it was, first, a small number of very particular things.

The English “system” descends from the ancient Greek sústēma (σύστημα), an organised body, a whole made of several parts, or a musical scale, itself a compound of syn- (together) and histanai (to cause to stand), rooted in the reconstructed Proto-Indo-European steh₂- (to stand). Borrowed into Late Latin as systema, the word named specific, bounded arrangements: harmonies, poetic compositions, sets of celestial bodies, troops in formation. It was not, in antiquity, a universal category. The Greeks did not force every phenomenon into a systemic box; they reserved the word for the cases where an evident, organising unity was already visible. The pan-systemic habit, the assumption that markets and biomes and software architectures are all the same kind of thing, is a modern acquisition, not an ancient inheritance, and it is worth remembering how recently the word had to be stretched to carry it. By the 1610s “system” described the whole universe; by the 1630s, a set of correlated principles; by the 1680s, the vital anatomy of the animal body. Each expansion moved the word further from its original, modest referents and closer to the totalising instrument it has since become.

2. The whole before it had a name

Long before “system” meant everything, Greek philosophy had already noticed that a whole can hold a property absent from every one of its parts.

Aristotle, in the Metaphysics, asked what turns a heap of matter into a unified thing with its own properties, and answered with form: a compound is not its elements plus nothing, but its elements plus an organising principle that the elements do not, by themselves, possess. The example that has outlived every gloss on it is a single syllable. Dissolve it and its letters survive; the syllable does not. Aristotle drew the same conclusion about flesh, and Galen later gave the mechanism a name, krasis di’ holōn, a total mixture from which an entirely new substance, in principle even a perceiving one, arises out of non-perceiving parts. This is the first and oldest evidence that a system, properly understood, is not merely additive, and it deserves the full weight of its own history rather than a passing mention here. That history, the tiger, the syllable, the total mixture, and the nineteenth-century thinkers who finally gave it a name, is the subject of the paper that follows this one, Génesis.

3. The whole traced backward

A system that can produce an unanticipated whole immediately raises a second question: how is that whole’s origin recovered?

The Greeks called the residue of a higher reality upon a lower one an ichnos, a trace; the Romans called it a vestigium, a footprint. Plato used the word to describe the traces that persisted in his cosmos before the Demiurge imposed order upon it; his dialogue the Meno went further still, distinguishing a fleeting “true belief” from stable “knowledge,” and insisting that only aitias logismos, a reasoned tracing of cause, converts one into the other. That single distinction is arguably the oldest surviving statement of a requirement for a traceable system: an isolated fact is not yet knowledge until it is tethered to its origin. Plotinus, Cicero, and Augustine each extended the trace into new territory, mystical, political, theological, and by the nineteenth century the same concept had been formalised into the instruments that anchor modern measurement and modern engineering alike. That lineage, from ichnos to the Requirements Traceability Matrix, is exhaustive enough to warrant a paper of its own; it is the subject of Ichnos, the third paper in this sequence. What matters here is only the shape of the debt: systems engineering did not invent traceability. It inherited a two-thousand-year-old epistemology and mechanised it.

4. The Cold War forces the system into a box

Sústēma stopped being a philosophical category and became a rigidly mechanistic one when the geopolitics of the twentieth century demanded it.

The nineteenth-century thinkers who inherited Aristotle’s insight, discussed fully in Génesis, still treated emergence as a genuine feature of reality, something a system could do that its parts, examined separately, could not predict. That appreciation was abruptly sidelined after the Second World War. Confronted with intercontinental ballistic missiles, the Apollo programme, and early networked defence computing, the United States military and aerospace sectors needed a paradigm that could scale, and irreducible complexity was not something a procurement schedule could accommodate. Early systems engineering borrowed its rigour directly from metrology: following the 1875 Treaty of the Metre, physical measurement was already required to trace to a common reference through an unbroken, documented chain. In the 1960s, a “software crisis” of chronic, runaway project failure pushed the same logic onto system design. At the 1968 NATO Software Engineering Conference the decision was made to import hardware-manufacturing rigour into software; in 1969 the U.S. Air Force issued MIL-STD-499, the first formal systems engineering management standard, paired with a Waterfall model that mandated strict, linear progression from requirement to deployment. The ancient vestigium had become the Requirements Traceability Matrix; the ancient sústēma had become an engineering deliverable.

5. The culmination: Model-Based Systems Engineering

As systems engineering’s own artefacts grew too large to manage as documents, the discipline replaced the document with the model.

By the time cyber-physical systems combined millions of interconnected software nodes with physical hardware, the document-centric approach that MIL-STD-499 had formalised collapsed under its own weight: specifications became unwieldy, traceability matrices became unmanageable spreadsheets, and text drifted quietly away from the systems it was meant to describe. The industry’s answer was Model-Based Systems Engineering, defined by INCOSE in 2007 as the formalised application of modelling to system requirements, design, analysis, verification, and validation from the conceptual phase onward. Its working language, SysML, gave engineers a shared graphical vocabulary for architecture, behaviour, and constraint, and its practical results have been genuinely substantial: the Silesian Phoenix student rover project, for instance, used structured MBSE to catch interface incompatibilities during design review rather than during physical integration, and the coupling of SysML models to virtual and augmented reality now lets stakeholders walk through a system before a single part is machined. None of this is in dispute. What is in dispute is what the model was quietly asked to replace.

6. Modelling for the sake of modelling

A discipline built to eliminate ambiguity is exposed to a pathology of its own: the model becoming the object of the engineering effort rather than the system it represents.

Industry retrospectives are candid about this failure mode, and explicit in warning against it: don’t start modelling for the sake of modelling. Three symptoms recur often enough to be named. Shelfware is the first: SysML models that took thousands of hours to build and are then never touched by a downstream developer, because they are legible only to the specialists who built them. “Death by SysML” is the second: instead of functioning as a lingua franca across disciplines, the language’s steep learning curve creates a priesthood of modellers isolated from the mechanical and software engineers they were meant to serve. The illusion of completeness is the third and most dangerous, because it is invisible from inside the model. A tool that enforces structural rigour and visual tidiness manufactures a psychological confidence that the system is now fully understood, even though no model can compute shifting political requirements, human error, or the kind of emergence discussed in Génesis. When the model demands more energy than the system it describes, the discipline has defeated its own purpose: the map has displaced the territory.

7. What the engineering box left outside

The deepest cost of forcing every system into a hard-engineering frame is not technical; it is sociological, and it was diagnosed decades before MBSE existed.

Working at Lancaster in the 1970s and 1980s, Peter Checkland applied hard systems engineering, the direct precursor to MBSE, to management and organisational problems and watched it fail, consistently and for a structural reason: hard methods assume the system’s objective is given, agreed, and quantifiable, which is true of a missile intercept and false of a hospital, a university, or a government department. Checkland’s Soft Systems Methodology named three casualties of the hard-systems assumption. The first is Weltanschauungen, the worldviews and cultural contexts of the people inside the system, for which SysML has no native syntax; it forces a single source of truth onto a situation actually governed by several contested ones. The second is aporia itself, the productive perplexity that Plato’s Meno treats as a precondition of real learning; an engineering discipline built to eliminate ambiguity strips human systems of the elasticity that ambiguity provides. The third is emergence, flattened: MBSE’s parametric simulations remain reductionist at heart and cannot model organisational morale, institutional decay, or systemic corruption, none of which trace back to a block in an Internal Block Diagram. Checkland’s conclusion still holds: forcing a sociological reality into an engineering box does not tame its complexity. It only ignores the parts that refuse to fit.

8. Limitations and open problems

This paper deliberately does not close two of its own arguments, because they are owned elsewhere.

The claim that Aristotelian hylomorphism anticipates modern emergence theory is asserted here but not defended; its full evidentiary chain, from Pliny’s tiger through British Emergentism, is the task of Génesis. Likewise, the claim that aitias logismos is a philosophical ancestor of the Requirements Traceability Matrix is stated but not proven; the complete philological and metaphysical lineage is the task of Ichnos. A further limitation is more fundamental: this paper diagnoses the sociological cost of the engineering box without proposing a remedy, a restraint deliberate rather than accidental, since the remedy belongs to a different series entirely.

Boundary notes

This paper supplies the widest lens only: the word’s own history, the shape of the engineering box it was forced into, and the sociological remainder that the box could not hold. The deep history of the emergent whole, previewed in section 2, belongs to Génesis. The deep history of the trace, previewed in section 3, belongs to Ichnos, which carries the lineage forward to the Requirements Traceability Matrix and, from there, directly into the reconciliation problem that opens Building the Tekmerium.

References

• Aristotle. Metaphysics, Book VII (Zeta).
• Plato. Meno; Timaeus.
• Galen. On the Elements According to Hippocrates.
• Metre Convention (Treaty of the Metre), Paris, 1875.
• MIL-STD-499, “Systems Engineering Management” (1969).
• INCOSE Systems Engineering Vision, MBSE definition (2007).
• Checkland, P. Soft Systems Methodology: A Thirty-Year Retrospective.
• Wolstencroft, J. Génesis; Ichnos (this series).
• Wolstencroft, J. Reasoning in the Fog (Building the Tekmerium, unpublished at the time of writing).