PROCESS

Here is How to Build

Design

Rules

Rules make a whole

The first discipline showed that no rule stands alone, that making one rule calls others into being. Every discipline since has deepened a single rule, its five dimensions, its soundness, what it is. But a rule is never the end. Rules are placed beside and after one another until they form something larger than any of them, and that larger thing is what this last discipline is for. A rule is the unit; the whole is what the units build.

The world has names for a group of rules. A collection managed together is often called a rule set; a higher intent that rules serve is called a policy. These names are useful, and they are not wrong, but they describe a group of rules as a container or a heading, rules gathered under one label, rules listed beneath one aim. This book means something more by the whole. Not rules collected, but rules joined: placed in their positions, connected at their edges, made to agree, so that together they carry the work from end to end. A rule set is a list; the whole is a working structure, and the difference is the design that turns the one into the other.

Not everything in that structure is a rule, and the designer should not try to make it so. Much of the work is plain flow, steps done because the work moves through them, needing no rule because no requirement governs them. A rule is reserved for the points that must be governed, where a requirement says something must or must not be. The sound designer rules only what must be ruled, and lets the rest be the flow between. So the whole is not a wall of rules; it is the work, running, with rules set at the points that carry a requirement, and the rules placed so that, together, they make the work hold its shape from beginning to end.

The highest possible standard is to see that rules are built to form a whole, placing each where it belongs and ruling only what must be ruled, so the rules together carry the work from end to end rather than standing as a list of separate constraints.

Key Takeaway: No rule stands alone; rules are placed and connected until they form something larger, the whole the units build. The world calls a group of rules a rule set or a policy, but those name a container or a heading; this book means more, rules joined, placed, connected, and made to agree, so together they carry the work from end to end. And not all of the work is rules: the designer rules only the points that carry a requirement and lets the rest be the plain flow, so the whole is the work running, with rules set where they must be.

A rule is the unit; the whole is what the units build, rules joined and made to carry the work from end to end.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 8: The Whole · Section: Rules make a whole

MarvinPro | June 2026

marvinpro.com

The whole is sound when its rules agree

A rule is sound when its five dimensions agree. The whole is sound when its rules agree. This is the same truth at a larger scale, and it is the heart of this discipline. Just as five dimensions designed in isolation can each be defensible and still pull against each other, rules designed one at a time, each sound on its own, can still disagree when set side by side, and a whole built of sound rules that disagree is a whole at war with itself, exactly as a rule whose five disagree is at war with itself.

The shapes of disagreement between rules are worth knowing, for they are how a whole fails though every rule in it is sound. Two rules may contradict, one requiring what another forbids, so that whoever follows them cannot satisfy both. Two may overlap, both governing the same point in different ways, so the work is told two things at once. They may leave a gap, a requirement that falls between them, governed by neither, so the work passes through ungoverned where it should not. Or their moments may clash, one placed where it strands another, so that following them in order is impossible. In each, the rules are individually sound, and the whole is not, because the rules do not agree. The fault is not in any rule; it is in the space between them, where no single rule could see it.

So designing the whole is making its rules agree, the same discipline as making a rule's five agree, raised a level. You lay the rules side by side, as you laid the five dimensions side by side, and look for the pair that pulls apart, the contradiction, the overlap, the gap, the clash, and you mend it not by hardening one rule but by bringing the disagreeing rules into agreement, redesigning them as parts of one whole rather than as separate constraints. A whole whose rules agree carries the work cleanly from end to end, each rule taking it up where the last left off, none fighting another. That coherence, rules in agreement, is what makes a structure of rules a sound whole, and not merely a pile of sound rules.

The highest possible standard is to design the rules of a whole so they agree, laying them side by side to find any contradiction, overlap, gap, or clash, and mending it by bringing the rules into agreement, so the whole carries the work from end to end without any rule fighting another.

Key Takeaway: A rule is sound when its five agree; the whole is sound when its rules agree, the same truth a level up. Sound rules designed one at a time can still disagree when set side by side, and a whole of disagreeing rules is at war with itself. The shapes: rules that contradict (one requires what another forbids), overlap (both govern one point differently), leave a gap (a requirement governed by neither), or clash in their moments. The fault is in the space between rules, where no single rule could see it. Mend by bringing the rules into agreement, not by hardening one.

The whole is sound when its rules agree, and a whole of sound rules that disagree is at war with itself, just as a rule whose five disagree is.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 8: The Whole · Section: The whole is sound when its rules agree

MarvinPro | June 2026

marvinpro.com

What you can build

With this, the book is complete, and you can step back and see the whole of what it built. You began with a single rule and learned that it reads as one statement but is five decisions. You took each decision deep, the manner that carries the force, the moment that is a place in the structure, the reason that defends the rule when you are not there, the doer whose work it truly is. You learned what makes a single rule sound, that its five agree, and what a rule is, a requirement given form. And now you have learned that rules build a whole, and that the whole is sound by the same test as the rule, its parts agree.

This is one idea, held at every scale. A rule is parts that agree, the five dimensions made one. A whole is rules that agree, the many rules made one. The coherence that makes a rule sound is the coherence that makes a whole sound, and it does not stop at the whole you can see. The whole sits within a larger whole, and that within a larger one still, up to the full span of an area's work, and at every level the same truth holds: the parts must agree, or the structure is at war with itself. This book has stayed at the rule and the whole the rules make; the larger structures above are taken up in their own books. But you now hold the idea that governs all of them, that soundness, at any scale, is agreement among the parts.

So you can build. You can design a rule that is whole, five decisions made one. You can place rules so they form a whole that is sound, many rules made one. And you can carry the same discipline upward as far as the work goes, knowing that whatever the scale, a sound structure is one whose parts agree. That is what this book set out to give: not a list of rules to follow, but the judgement to design rules, and the wholes they build, that hold together because every part of them was made to serve the same work. The rules of design are themselves only the beginning; what they build is the work itself, made to hold.

The highest possible standard is to design at every scale by the one test the book has taught, that the parts agree, building rules that are whole and wholes that are sound, and carrying that discipline upward through every larger structure the work forms.

Key Takeaway: The book is complete, and it is one idea at every scale: a rule is parts that agree (the five made one), a whole is rules that agree (the many made one), and the larger structures above hold by the same test, taken up in their own books. Soundness, at any scale, is agreement among the parts. So you can build: a rule that is whole, a whole that is sound, and the same discipline carried upward as far as the work goes. The book gives not a list of rules but the judgement to design rules, and the wholes they build, that hold together.

Soundness is agreement among the parts, at every scale: a rule made of agreeing dimensions, a whole made of agreeing rules.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 8: The Whole · Section: What you can build

MarvinPro | June 2026

marvinpro.com

A real example

Take the rules of the example one last time, and see them as a whole. There was never only one rule. There were three messages, each its own rule, and the rule that watches for an emerging issue and sends the case down another path, and the rules that govern what each team does when the case arrives. Apart, each is a sound rule, five decisions in agreement. Together, they are a whole, and the whole is sound only if they agree with one another as well as within themselves.

And they were made to agree. The first message rule ends where the second begins, the moments placed so the case passes cleanly from one to the next, no gap where a step of the work goes untold, no overlap where two rules tell the customer the same thing twice. The rule that routes an emerging issue does not contradict the ordinary message rules; it sits at the fork and sends the case onto a different path before the ordinary rules would have fired, so the two paths never fight over the same case. The reasons agree, every rule serves the one purpose, that the customer hear the same clear word, so no rule pulls toward a different end. Laid side by side, the rules carry the case from first contact to resolution without a contradiction, a gap, or a clash between them. That is what makes them a whole and not a pile: not that each is sound, but that together they agree.

Had they not, the whole would have failed though every rule was sound. A second message timed before the first would have stranded the case. A routing rule that fired too late would have let an emerging issue run down the ordinary path. A reason in one rule that served speed where the others served consistency would have pulled the whole apart at that seam. None of these is a fault in a single rule; each is a disagreement between rules, visible only when the rules are seen together. The whole held because the rules were designed not only to be sound, but to agree, and the same is true of every structure above this one, as far up as the work reaches.

A whole is sound when its rules agree, each taking the work up where the last left off, none fighting another, all serving one purpose.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 8: The Whole · A real example

MarvinPro | June 2026

marvinpro.com

The Whole

A rule never stands alone. Rules are placed and connected until they form something larger, and that whole is what the units build. The world calls a group of rules a rule set or a policy, but those name a container or a heading; this book means more, rules joined, placed in their positions, connected at their edges, made to agree, so that together they carry the work from end to end. And not all of the work is rules: the designer rules only the points that carry a requirement and lets the rest be the plain flow, so the whole is the work running, with rules set where they must be.

The whole is sound when its rules agree, the same truth that makes a rule sound, raised a level. Sound rules designed one at a time can still disagree when set side by side, and a whole of disagreeing rules is at war with itself, just as a rule whose five disagree is. Rules may contradict, overlap, leave a gap, or clash in their moments, and each fault lives in the space between rules, where no single rule could see it. So designing the whole is making its rules agree: laying them side by side, finding the pair that pulls apart, and mending it by bringing the rules into agreement, not by hardening one. A whole whose rules agree carries the work cleanly from end to end, each rule taking it up where the last left off.

This is one idea held at every scale. A rule is parts that agree, the five dimensions made one. A whole is rules that agree, the many rules made one. And it does not stop: the whole sits within a larger whole, up to the full span of an area's work, and at every level soundness is the same, the parts agree, or the structure is at war with itself. This book has stayed at the rule and the whole the rules make; the larger structures above, and the deviations from the rule that are their own study, are taken up in their own books. But you now hold the idea that governs them all.

So the book is complete, and you can build. You can design a rule that is whole, five decisions made one; place rules so they form a whole that is sound, many rules made one; and carry the same discipline upward as far as the work goes, knowing that at any scale a sound structure is one whose parts agree. That was the aim throughout: not to hand you rules to follow, but to give you the judgement to design rules, and the wholes they build, that hold together because every part was made to serve the same work. Begin with one rule, made whole. Build from it a whole, made sound. The work that results is the proof of the method, and the method is simple, design the parts to agree.

The whole is rules made to agree, and soundness at every scale is one thing: the parts serve one work, and so they hold.

MarvinPro · PROCESS · Here is How to Build · Design · Rules · Discipline 8: The Whole · Chapter Outcome

MarvinPro | June 2026

marvinpro.com

Think Simple.