A Three-Layer Analysis (TLA) of Livy, History of Rome, Book 1
1. Question
Why does the growth of Rome depend more on whom it integrates after conquest than on conquest itself?
2. Abstract
The growth of Rome depends more on whom it integrates after conquest than on conquest itself because conquest is only the temporary output of a military application. What strengthens Rome is the post-conquest integration process. This process converts the people, land, cities, temples, military force, and communal order of another OS into the infrastructure, Execution Layer, external APIs, and subordinate relations of the Roman OS.
Conquest means the confirmation of military superiority over another OS. However, conquest alone does not make Rome larger in a functional sense. Even if Rome defeats an enemy, victory does not return as operational resources to the Roman OS if the conquered land rebels, the population separates from Rome, urban functions collapse, temple order is broken, and land, water, and boundaries become unmanageable. In that case, victory creates occupation costs, rebellion risk, logistical burden, and governance failure.
In OS Organizational Design Theory R1.30.16.00, an application is a policy, project, or measure selected and activated by the OS according to its purpose. Its result depends on its fit with the Execution Layer. Also, “mapping between application and Execution Layer” means designing which Execution Layer should carry which application. Therefore, after conquest, the important question is not “Did Rome conquer?” The important question is “How does Rome map the people, land, cities, institutions, and military force obtained through conquest into its own Execution Layer?”
From this viewpoint, the growth of Rome is not mere territorial expansion. The growth of Rome is the ability to convert the components of another OS into the Execution Layer, infrastructure, alliances, subordinate relations, military resources, and urban order of the Roman OS.
3. Method
This study follows the structure of Three-Layer Analysis, or TLA.
In Layer 1, this study organizes facts from Livy, History of Rome, Book 1, such as the surrender of Collatia, postwar public works after the wars with the Sabines and the Old Latins, the renewal of the treaty with the Latins, the armed gathering of Latin youths, and the reorganization of Romans and Latins into mixed military units.
In Layer 2, these facts are connected to structures such as the state OS, other OSs, military applications, the Execution Layer, mapping between application and Execution Layer, external APIs, subordinate relations, H, M, T, and Execution Layer fit.
In Layer 3, this study explains why the growth of Rome depends not on “whether Rome conquered,” but on “whom Rome integrated into which layer after conquest.”
4. Layer 1: Fact
In Livy, History of Rome, Book 1, Rome fights surrounding communities, accepts surrender, makes treaties, and converts the space created after conquest into urban development.
First, there is the surrender of Collatia. The people of Collatia are asked whether they are an independent people. After this is confirmed, they hand over their people, town, fields, water, boundaries, temples, household goods, and all things belonging to gods and humans into the power of the Roman people. The king then accepts this surrender.
Here, surrender is not mere defeat. The people, town, land, water, boundaries, temples, property, and sacred and secular order of Collatia are reconnected to the Roman OS. What is integrated after conquest is not only land or military force. It is the whole order of a community: people, city, fields, water, boundaries, temples, property, and sacred and secular order.
Second, there are the postwar public works after the wars with the Sabines and the Old Latins. After fighting the Sabines, Tarquinius captures the towns of the Old Latins one by one and controls all Latium. After that, peace comes to Rome. With energy greater than that used in war, Rome begins public works: walls, drainage works, and preparation of the site for the temple of Jupiter.
Here, the result of war is converted into urban infrastructure, defense, drainage, religious order, and preparation for future development. The result of conquest or control does not become growth by itself. It becomes growth for the Roman OS only when the postwar space is converted into urban infrastructure, defense, drainage, religious order, and future development.
Third, there is the renewal of the treaty with the Latins and the reorganization into mixed units. Tarquinius claims rights under an old treaty and renews the treaty with the Latins. After that, the young men of Latium are ordered to gather under arms on a fixed date. They are then reorganized into mixed units of Romans and Latins.
Here, conquest, subordination, and treaty are not only relations of domination. They are connected to the reorganization of the Execution Layer for a military application. Post-conquest integration also means converting human resources into the Execution Layer of a military application. The growth of Rome depends on whether Rome can convert the human resources of a hostile OS into execution units of the Roman OS.
5. Layer 2: Order
In Layer 2, conquest is the output of a military application. A military application confirms military superiority over another OS. However, whether this output becomes growth for the Roman OS depends on the design of post-conquest integration.
In OS Organizational Design Theory R1.30.16.00, an application is a policy, project, or measure selected and activated by the OS according to its purpose. Its function is to obtain external resources and return them as operational resources to the OS. Therefore, even if the application of war produces an output, it does not become growth unless that output returns as operational resources to the OS.
Execution Layer fit means whether the resources, skills, culture, structure, and historical conditions needed to run an application are present. If the Execution Layer does not fit the application, results decline, burden becomes excessive, motivation decreases, and resources from other applications are consumed.
Therefore, the question after conquest is this: “For which application will Rome use the conquered land and people as an Execution Layer?” Will the conquered population be mapped to agriculture, taxation, military service, urban defense, alliance maintenance, road construction, drainage works, or temple construction? Will the conquered city be integrated as a defense base, supply base, religious base, alliance base, or administrative base? Without this design, conquered land becomes a burden, not a resource.
The design of external APIs and subordinate relations is also important. In OS Organizational Design Theory R1.30.16.00, an external API means a connection specification through which a state OS connects with another OS. It includes treaties, peace agreements, truces, alliances, envoys, and violation judgments. A subordinate relation means a connection specification that defines the relationship between a higher OS and a lower OS. It institutionalizes domination, subordination, tribute, and protection between OSs.
From this viewpoint, post-conquest integration is not mere occupation. It is the question of how the conquered OS is connected to the Roman OS through external APIs, subordinate relations, or alliance relations.
The surrender formula of Collatia shows this structure well. In that formula, people, town, fields, water, boundaries, temples, household goods, and all things belonging to gods and humans are transferred into the power of the Roman people. This is not the taking of only one part of another OS. It is the reconnection of another OS’s life base, land, water, boundaries, religious order, and property order to the authority structure of the Roman OS.
The renewal of the treaty with the Latins and the reorganization into mixed units also show how Rome integrates the human resources of another OS into the Execution Layer of a military application. The young men of the conquered or subordinated side are not merely enemies or subjects. They are repositioned as components that execute the Roman military application.
At this point, H, M, and T become important.
H, or Human Resource Governance, controls personnel placement, role performance, reward and punishment trust, institutional control, and non-institutional control. After conquest, Rome must decide who remains, who is moved, who becomes a local ruler, who is used as a soldier, and who is treated as an ally or subordinate. If this design fails, the conquered land becomes an unstable factor instead of a resource.
M, or Maturity, is the maturity by which the Execution Layer understands institutions, military discipline, tribute, and urban order, and controls its own behavior. T, or Trust, is the degree of acceptance toward the decision-making of the ruling side. It is the driving energy by which the Execution Layer moves voluntarily. The health of the ruled side is organized as M × T.
Therefore, post-conquest integration is harder than military victory. Victory itself is the output of a military application. But to integrate people, cities, land, temples, military force, treaties, and subordinate relations into the proper layers after conquest, the Roman OS needs H on the OS side and M and T on the Execution Layer side.
6. Layer 3: Insight
The growth of Rome depends more on whom it integrates after conquest than on conquest itself because conquest is only the temporary output of a military application. What strengthens Rome is the post-conquest integration process. This process converts the people, land, cities, temples, military force, and communal order of another OS into the infrastructure, Execution Layer, external APIs, and subordinate relations of the Roman OS.
Conquest means the confirmation of military superiority over another OS. However, conquest alone does not make Rome larger in a functional sense. Even if Rome defeats an enemy, victory does not return as operational resources to the Roman OS if the conquered land rebels, the population separates from Rome, urban functions collapse, temple order is broken, and land, water, and boundaries become unmanageable. In that case, victory creates occupation costs, rebellion risk, logistical burden, and governance failure.
From this viewpoint, the growth of Rome is not mere territorial expansion. The growth of Rome is the ability to convert the components of another OS into the Execution Layer, infrastructure, alliances, subordinate relations, military resources, and urban order of the Roman OS.
The surrender of Collatia in Livy, History of Rome, Book 1, clearly shows this problem. The people of Collatia confirm that they are an independent people. Then they hand over their people, town, fields, water, boundaries, temples, household goods, and all things belonging to gods and humans into the power of the Roman people. The king accepts this surrender.
Here, surrender is not mere defeat. The people, town, land, water, boundaries, temples, property, and sacred and secular order of Collatia are reconnected to the Roman OS.
This formula is important because it clearly shows what is integrated after conquest. What is integrated is not only military force or land. It is the whole order of the community: people, town, fields, water, boundaries, temples, property, and all things belonging to gods and humans. In other words, Rome does not take another OS only as a physical territory. Rome takes it as a complex system that has life, religion, property, boundaries, and communal order.
This is close to the design of subordinate relations in OS Organizational Design Theory R1.30.16.00. A subordinate relation is a connection specification that defines the relationship between a higher OS and a lower OS. It institutionalizes domination, subordination, tribute, and protection between OSs. If the T or M of the subordinate side is low, the subordinate side may formally submit but fail to cooperate in execution. Rebellion, suspension of tribute, rejection of subordination, or hollow subordination can occur.
Therefore, post-conquest integration is not a simple process of “we won, so we rule.” It is a design question. What kind of subordinate relation should be created? How much autonomy should remain? Who should become the local manager? Which land should be used as Roman resources? Which residents should be integrated as soldiers, taxpayers, citizens, allies, or members of subordinate communities? Which temples and rituals should be preserved? Which order should be connected to the Roman order? These designs determine the value of conquest.
Livy Book 1 also shows that post-conquest integration is related not only to conquered land, but also to infrastructure conversion inside the Roman OS. After the war with the Sabines, Tarquinius captures the towns of the Old Latins one by one and controls all Latium. After peace comes to Rome, public works begin with even greater energy than the war itself. Walls, drainage works, and the site of the temple of Jupiter are prepared.
This shows that the result of war is converted into urban infrastructure, defense, drainage, religious order, and preparation for future development. After Rome gains a security margin through war, it turns that margin into urban development. In other words, external victory is converted into internal consolidation infrastructure. Rome grows not because it defeats enemies, but because it connects the time and resources after victory to the reconstruction and strengthening of Rome’s urban OS.
The renewal of the treaty with the Latins and the reorganization into mixed units also matter. Tarquinius claims rights under an old treaty and renews the treaty with the Latins. After that, the young men of Latium are ordered to gather under arms on a fixed date. Then Roman and Latin soldiers are reorganized into mixed units. Here, conquest, subordination, and treaty are not merely relations of domination. They are connected to the reorganization of the Execution Layer for a military application.
This structure shows the principle of Roman growth. Rome does not simply defeat another OS and stop there. It integrates the human resources of the defeated side into its military Execution Layer. In other words, the young men of the conquered or subordinated side are converted from enemies into components that execute the next Roman military application. This is why Roman expansion proceeds not merely as destruction, but as the multiplication of the Execution Layer.
However, this integration does not always succeed. If a treaty or subordinate relation is one-sided and imposed through fear or pressure, it does not form T on the Execution Layer side. Even if the conquered side is formally integrated into Rome, it will not function as an Execution Layer if its M and T are low. Rebellion, non-execution of orders, hollow subordination, and independent field action can occur.
OS Organizational Design Theory R1.30.16.00 also defines treaties, peace agreements, and truces as external APIs that control, stop, or end violent connection with another OS. Their failure condition is that the agreement does not reach the field and is not executed.
Therefore, post-conquest integration tests H, M, T, and Execution Layer fit.
First, H, or Human Resource Governance, is tested. After conquest, who remains? Who is moved to Rome? Who becomes the local ruler? Who is used as a soldier? Who is treated as a senator, noble, ally, or subordinate? If this design of personnel, roles, rewards, punishments, and institutional operation fails, the conquered land becomes an unstable factor instead of a resource.
Second, Execution Layer fit is tested. For which application will conquered people and cities be used? Military service, agriculture, taxation, urban defense, alliance maintenance, roads, drainage, or temple construction? If the mapping between application and Execution Layer is wrong, results decline, burden becomes excessive, motivation falls, and other resources are consumed.
Third, M, or Maturity, is tested. If the conquered side cannot understand Roman institutions, military discipline, tribute, and urban order, and cannot control its own behavior, integration does not work. If a low-M group is forcibly integrated, the Roman OS only increases its control costs.
Fourth, T, or Trust, is tested. If the conquered side does not trust the Roman OS and receives rule only as coercion, it does not function as an Execution Layer even if it formally submits. In OS Organizational Design Theory, the health of the ruled side is organized as M × T. Therefore, how Rome treats residents and allies after conquest is not merely a moral issue. It is a control variable that determines the execution power of the Roman OS.
For this reason, the growth of Rome depends more on whom it integrates after conquest than on conquest itself. Conquest is an operation that opens another OS. Growth depends on how Rome connects the contents of that OS to its own OS.
Will enemy soldiers be killed, or turned into allied forces?
Will residents be enslaved, or remain as subordinate communities?
Will land be plundered, or managed as fields, water, and boundaries?
Will temples be destroyed, or connected to Roman authority together with sacred and secular order?
Will local elites be removed, or repositioned as senators, allies, or local rulers?
A mature state OS decomposes the components of another OS after conquest and repositions them into the proper layers. Human resources are connected to H. Residents are connected to the Execution Layer. Land, water, walls, and cities are connected to infrastructure. Treaties and subordinate relations are connected to external APIs. Military cooperation is connected to the Execution Layer of applications. Temples and rituals are connected to legitimacy and T.
An immature state OS does not have a post-conquest integration design. It ends victory with plunder, destruction, threat, or revenge. This may look like victory in the short term, but it does not return as OS resources in the long term. Rather, it produces rebellion, distrust, occupation costs, and Execution Layer mismatch.
Therefore, the growth of Rome depends not on conquest itself, but on whom Rome integrates after conquest and how it integrates them. Conquest is the output of a military application. Growth depends on whether that output can be converted into the infrastructure, Execution Layer, external APIs, subordinate relations, H, M, and T of the Roman OS.
7. Implications for the Present
This structure can also be applied directly to modern organizations.
In modern companies, M&A, business acquisition, hiring, business alliances, departmental integration, and project integration have the same structure as post-conquest integration. What matters is not merely that a company “bought,” “absorbed,” “signed,” or “hired.” What matters is what happens after that. Who is placed in which role? Which institutions are kept? Which customer base is used? Which culture is integrated? Which Execution Layer is created?
Even if a company buys another company through M&A, the acquisition does not become growth if key people leave, the front line resists, the customer base is lost, system integration fails, and cultural conflict expands. Rather, the acquisition creates integration costs, lower trust, front-line exhaustion, and management burden.
This is the same problem as how Rome integrates conquered land.
A mature organizational OS decomposes the components of the other OS after acquisition or integration and repositions them into the proper layers. Human resources are connected to H. Front-line teams are connected to the Execution Layer. Customer bases are connected to infrastructure or application resources. Contractual relations are connected to external APIs. Culture, trust, and brand are connected to T.
An immature organizational OS has no integration design. It is satisfied with the fact that it bought the company or signed the contract, and it leaves the front line alone. As a result, capable people leave, customers move away, the front line becomes silent, systems fail to connect, and expected results do not appear.
Therefore, in modern organizations as well, growth is not determined by “what was acquired.” Growth is determined by “how it was integrated after acquisition.” This is the same structure as Roman conquest.
8. Conclusion
The growth of Rome depends more on whom it integrates after conquest than on conquest itself because conquest is only the temporary output of a military application.
Conquest itself confirms military superiority over another OS. However, if that output does not return as operational resources to the Roman OS, it does not become growth. If the conquered land rebels, the population separates, urban functions collapse, and land, water, and boundaries become unmanageable, victory becomes a burden rather than a resource.
The growth of Rome depends on how it integrates the components of another OS after conquest. People, cities, land, water, boundaries, temples, property, sacred and secular order, military force, treaties, and subordinate relations must be connected to the proper layers of the Roman OS.
A mature state OS decomposes the components of another OS after conquest and repositions them into the proper layers. Human resources are connected to H. Residents are connected to the Execution Layer. Land, water, and cities are connected to infrastructure. Treaties and subordinate relations are connected to external APIs. Military cooperation is connected to the Execution Layer of applications. Temples and rituals are connected to legitimacy and T.
An immature state OS has no post-conquest integration design. It ends victory with plunder, destruction, threat, or revenge. As a result, it produces rebellion, distrust, occupation costs, and Execution Layer mismatch.
Therefore, the growth of Rome depends not on conquest itself, but on whom Rome integrates after conquest and how it integrates them.
9. Sources
Titus Livius, History of Rome, Book 1, translated by Satoshi Iwaya, Kyoto University Press, 2008.
OS Organizational Design Theory_R1.30.16.00