Formations

A football formation is not eleven players doing the same thing.

It is a structured arrangement of eleven different roles – different positions, different responsibilities, different skills – with defined relationships between them. The striker is not a defender who happens to be standing further forward. The goalkeeper is not a midfielder who stayed back. Each role exists because the problem of winning requires something the other roles cannot supply, and the team succeeds not because any one player is exceptional but because the roles fit together in a way that addresses the whole problem.

Most organizations think about AI the way a naive manager thinks about hiring: find the smartest available model, give it the task, and assume that capability will produce results. The equivalent mistake in football would be to sign eleven world-class strikers and call it a team. The individual quality is real. The collective output is not.

The insight that has been building across this series – that group intelligence requires engineered conditions, that good decisions require structured disagreement, that conclusions require adversarial challenge before they can be trusted – applies as directly to artificial reasoning systems as it does to human ones. A single model, however capable, is a single voice. It suffers from the same failure modes as a room where one person dominates: it optimizes for the answer that seems most plausible rather than the answer that has survived the most rigorous challenge.

The unit of AI reasoning that addresses this is not the model. It is the formation.

What a formation actually looks like

A formation is a structured composition of reasoning roles, each with a different orientation, different tools, and different success criteria, arranged so their outputs challenge and refine each other before anything is committed.

Consider a formation designed for a business evaluation – assessing whether to proceed with a potential acquisition.

A research role gathers evidence: financial statements, market data, competitive positioning, customer references, regulatory context. Its job is breadth and accuracy. It is not trying to form a view. It is trying to surface what is true and what is uncertain.

A hypothesis role synthesizes an initial thesis from that evidence: a provisional go or no-go, with the reasoning made explicit and the key assumptions named. Its job is to produce something specific enough to be challenged – not a vague balance of considerations but a committed position that can be tested.

An adversarial role is given the hypothesis and tasked explicitly with breaking it. Not with finding counterbalancing considerations – with finding the strongest possible case that the hypothesis is wrong. What has been assumed that might not be true? What evidence has been weighted too heavily? What has not been checked that should be? Its job is not to be helpful to the hypothesis. Its job is to stress-test it.

A constraint role checks the hypothesis against hard boundaries: regulatory requirements, capital constraints, integration complexity, existing commitments that limit flexibility. Some of these constraints are binary – the deal either satisfies the requirement or it does not. A constraint role does not reason about whether constraints should apply. It checks whether they are satisfied.

A synthesis role integrates the adversarial challenge and the constraint check into a revised recommendation – one that has absorbed the strongest objections and still holds, or that names the specific point where it does not and explains what would need to be true for it to recover.

These are not five models doing the same task with slight variations. Each has a genuinely different function, different inputs, and different criteria for success. The adversarial role is not trying to produce a good answer – it is trying to break the hypothesis role's answer. The constraint role is not being creative – it is checking fixed boundaries. The synthesis role takes responsibility for a recommendation, rather than merely summarizing. A binding commitment still requires explicit authority.

The right tool for each role

One of the more important implications of the formation approach is that not every role requires the same kind of reasoning system.

The constraint role can use a mathematical solver rather than a language model. A solver such as HiGHS searches a formal model of constraints and objectives. Preserve what it establishes: feasibility, optimality within the model, infeasibility, or an unresolved result. A timeout is not proof that no solution exists, and a correct formal result still depends on the problem being modeled appropriately.

The point is not that mathematical solvers are superior to language models. The point is that different roles in a formation call for different tools, and the formation is the right level at which to ask the tool question. The question is not "which model should we use?" The question is "what does this problem actually require? what roles need to exist? what tools are right for each role?"

This shifts reasoning from a procurement decision – which model is best – to a design decision – which formation fits the problem. Design decisions produce better outcomes because they require explicit reasoning about the structure of the problem, not just the capability of the available tools.

The parallels are old

The formation concept is not new. It has been independently discovered in every domain that requires reliable collective reasoning under pressure.

A surgical team is a formation. The surgeon, anesthetist, scrub nurse, and circulating nurse have different roles, different training, different tools, and different responsibilities at each phase of an operation. The quality of the outcome depends not on the individual excellence of any one member but on the reliability of the handoffs between them.

A commercial aircraft crew is a formation. Pilot and co-pilot have overlapping responsibilities specifically so that each can catch errors the other might make. Standard operating procedures define who speaks when, who checks what, who has authority at each moment. Aviation's safety record is not primarily a product of individual pilot skill. It is a product of crew resource management – the discipline of treating the crew as a system with defined roles, not as a collection of individuals.

A securities trading floor is a formation. Analysts, traders, risk managers, and compliance officers each see a different slice of the same market. Their different orientations – finding opportunity, executing trades, managing exposure, enforcing rules – are not redundant. They are complementary, and the quality of the outcome depends on all four being present and communicating.

In each case, the formation succeeds not because the individuals are exceptional but because the structure channels their different capabilities toward the same goal with defined interfaces between them.

Formation

The Reflective platform's intelligence layer, Formation, is built around this formation concept. Formation composes roles appropriate to each problem: researchers surface evidence, hypothesis roles take explicit positions, adversarial roles stress-test them, constraint roles check hard boundaries, and synthesis roles produce recommendations with full provenance. Those recommendations still require authorization before they become binding commitments. Adversarial pressure is built into the formation. The same insight that Articles 5 and 6 traced through human decision-making is encoded as architecture.

The formation approach is not specific to Formation. Any reasoning system that takes the previous essays seriously – that takes seriously the insight that good collective judgment requires structured conditions, adversarial challenge, and defined synthesis – will arrive at something similar. The formation is not a product feature. It is a design principle.

The design question

The question that formations make visible is not "which model is best?" That question leads to benchmarks, leaderboards, and procurement decisions that miss the point.

The question is: what structure does this problem require? What roles need to exist? Where does adversarial pressure need to be built in? What constraints are hard and require a different kind of reasoning than the soft judgment calls? Where does synthesis need to happen, and who has authority to turn a selected recommendation into a commitment?

These are design questions. They require reasoning about the structure of the problem before selecting the tools. They improve reliability by matching the arrangement of roles to the demands of the problem.

The next essay addresses the question that this architecture immediately raises: where does human judgment remain irreplaceable inside a well-designed formation, and why does the answer to that question matter more than any choice of model?

This is the eighth essay in a series exploring how organizations reason, decide, and govern the gap between intent and execution.

Core thesis: The useful unit of AI reasoning is the formation – a structured arrangement of complementary roles with adversarial pressure and defined synthesis – not the individual model. The idea you can't unsee: The question isn't which model. It's which formation. Vocabulary shift: "which model?" → "which formation?" Connects to: Article 6 (Institutionalizing Disagreement), Article 7 (Business Truths), Article 9 (Human Judgment) Version: 1.0 / 2026-06-29