Skip to content

Gall's Law

Prime #
877
Origin domain
Systems Thinking & Cybernetics
Subdomain
complex systems design and evolution → Systems Thinking & Cybernetics
Aliases
Systemantics

Core Idea

Gall's Law is the structural observation that complex working systems are reached by incremental modification of simpler working systems, not by from-scratch design of the full target system. Stated negatively: a complex system designed from scratch — without passing through a sequence of working intermediate versions — will almost never work; and if it does not work, no amount of patching the failed design will reach the working state, because the working states reachable from the broken design are not connected to the target. The path to a working complex system runs through a connected chain of working intermediates, each viable on its own terms.

The pattern is sharper than "iterate" or "start small": it specifies that the intermediates themselves must work. A development path that passes through an intentionally non-working intermediate — a half-built bridge, a half-deployed protocol, a partially-rebuilt constitution — typically fails at the intermediate even if the final target would have worked, because the team cannot debug the next increment against a broken base, because the broken intermediate cannot recruit the resources or users needed to fund the next step, and because the failure modes of the broken intermediate are not diagnostic of the target's failure modes.

The dual claim is that complex systems observed to work today are almost always evolved descendants of simpler ancestors that worked, with the chain of viable intermediates traceable in their structure — vestigial features, legacy interfaces, archaic conventions, the etymology of standards. This holds of biological organisms, mature software, working legal institutions, stable monetary regimes, living cities, and natural languages. The structural content is a claim about which paths through design-space are constructible at all: viability is a predicate on each waypoint, and only chains whose every waypoint satisfies it can be traversed.

How would you explain it like I'm…

Start With a Small Tower

If you want to build a really tall tower of blocks, you can't just plop the whole giant tower down at once; it would fall over. You start with a small tower that stands up by itself, then add a little, and check it still stands, then add a little more. A big thing that works almost always grows from a smaller thing that worked. You can't skip straight to the giant version.

Every Step Must Stand

Gall's Law says that complex things that actually work are almost always built up step by step from simpler things that already worked, not designed all at once from scratch. If you try to design a big complicated system in one giant leap, it will almost never work, and patching the broken version usually won't save it. The trick is that each in-between version has to work on its own, not just the final one. A half-built bridge that can't carry anything doesn't help you get to the finished bridge. So the real path goes through a chain of working versions, each good enough to stand on its own while you improve it.

Working Steps All the Way

Gall's Law is the observation that complex working systems are reached by incremental modification of simpler working systems, not by from-scratch design of the full target. Stated negatively: a complex system designed all at once, without passing through working intermediate versions, will almost never work, and once broken, patching it usually won't reach the working state, because the working states reachable from the broken design aren't connected to the target. What makes this sharper than 'just iterate' or 'start small' is the requirement that the intermediates themselves must work. A path that runs through an intentionally non-working stage, like a half-built bridge or a half-deployed protocol, typically fails at that stage even if the final target would have worked, because you can't debug the next increment against a broken base and the broken version can't attract the resources or users to fund the next step. The dual claim is that complex systems we see working today are almost always evolved descendants of simpler working ancestors, with the chain of viable intermediates still visible in vestigial features and legacy interfaces.

 

Gall's Law is the structural observation that complex working systems are reached by incremental modification of simpler working systems, not by from-scratch design of the full target system. Stated negatively: a complex system designed from scratch, without passing through a sequence of working intermediate versions, will almost never work; and if it does not work, no amount of patching the failed design will reach the working state, because the working states reachable from the broken design are not connected to the target. The path to a working complex system runs through a connected chain of working intermediates, each viable on its own terms. The pattern is sharper than 'iterate' or 'start small': it specifies that the intermediates themselves must work. A development path that passes through an intentionally non-working intermediate (a half-built bridge, a half-deployed protocol, a partially-rebuilt constitution) typically fails at the intermediate even if the final target would have worked, because the team cannot debug the next increment against a broken base, because the broken intermediate cannot recruit the resources or users needed to fund the next step, and because the failure modes of the broken intermediate are not diagnostic of the target's failure modes. The dual claim is that complex systems observed to work today are almost always evolved descendants of simpler ancestors that worked, with the chain of viable intermediates traceable in their structure: vestigial features, legacy interfaces, archaic conventions, the etymology of standards. The structural content is a claim about which paths through design-space are constructible at all: viability is a predicate on each waypoint, and only chains whose every waypoint satisfies it can be traversed.

Structural Signature

the design space of possible system configurations — the viability predicate marking which configurations actually work — the target complex system to be reached — the single-step modification relation between configurations — the chain of viable intermediates connecting start to target — the constructibility invariant that only all-viable chains are traversable

Gall's Law is present when the following components co-occur:

  • The configuration space. There is a space of possible system designs, ranging from simple to complex, within which the target sits as one point.
  • The viability predicate. Each configuration either works or does not — viability is a binary property holding of a waypoint on its own terms, not as a fraction of the target. This predicate, not mere size, is what the law turns on.
  • The target system. A specific complex configuration is the destination; it is reachable in principle but not directly buildable from nothing.
  • The step relation. Configurations are connected by feasible single increments of modification — the moves by which one working system is grown into the next.
  • The viable chain. A path from a simple working ancestor to the target along which every intermediate satisfies the viability predicate. The connectivity of the viable region under the step relation is what determines whether such a path exists at all.
  • The constructibility invariant. Only chains whose every waypoint is viable can be traversed: a path through a non-working intermediate fails at that intermediate (no debuggable base, no resources, non-diagnostic failures), and from-scratch jumps to the target land in disconnected, unreachable working states.

The components compose into a claim about which paths are buildable: a complex working system can be reached only as the terminus of a connected chain of simpler systems that each worked — so observed working complexity is always the fossilized record of such a chain, and any proposed development path reduces to a viability check on each of its waypoints.

What It Is Not

  • Not generic iteration. See iteration: repeating a step is direction-agnostic about waypoint viability. Gall's Law adds the binding constraint that each intermediate must independently work, not merely that the process repeats.
  • Not incremental refinement of a target. See refinement and progressive_refinement_from_core_model: those polish a near-complete design toward a goal. Gall's Law allows — even requires — intermediates that perform a different function than the target, viable on their own terms.
  • Not the MVP doctrine as such. See minimum_viable_product_mvp: that is Gall's Law made operational for ventures. The prime is the deeper structural claim about constructibility of any complex system in any substrate, of which MVP is one application.
  • Not legacy integration. See legacy_integration: that concerns reconciling an existing old system with a new one. Gall's Law concerns which development paths are traversable at all, and reads legacy features as the fossil record of the path actually taken.
  • Not path dependence. See path_dependence: that explains why history constrains present options. Gall's Law makes the stronger constructive claim that only all-viable paths through design space can be built in the first place.
  • Common misclassification. Reading the law as "just start small and iterate." The signature is the viability predicate on every waypoint: a path through an intentionally non-working intermediate violates the law even if it starts small, because the broken intermediate cannot be debugged, funded, or diagnosed against.

Broad Use

In software engineering and product development, large from-scratch rewrites of complex working software repeatedly fail, while working successors emerge from incremental evolution or from a working minimum grown through iteration; "you can't ship a rewrite" is the developer-folklore form. In biological evolution and evolvability theory, Darwinian selection requires each ancestral form to be viable in its own environment, so a complex organ implies a chain of functional intermediate organs each useful at the time; evolvability research formalizes this as connectivity of the viable region of genotype-space. In constitutional and institutional design, working constitutions historically grow from earlier working ones, while from-scratch impositions in fractured states frequently collapse because no working intermediate carried legitimacy through the transition. In urban planning, cities that work grew by successive layering of working sub-systems, whereas high-modernist from-scratch designs are repeatedly found to "fail to come alive." In lean-startup and venture methodology, the minimum-viable-product doctrine is Gall's Law made operational: every release must be a working product, however minimal, and the chain of releases is the growth path. In standards and protocol design, protocols that succeeded accreted from working ancestors, while designed-from-scratch replacements struggle against incumbent working protocols. And in personal habit formation and behavioral change, programs that prescribe a complex new routine wholesale have far lower success rates than incremental programs that establish each small change as working before adding the next.

Clarity

The law clarifies a failure mode that designers reach for under pressure: the from-scratch redesign. It explains why such redesigns fail — not because the designers underestimated complexity in the usual sense, but because they tried to skip the chain of viable intermediates. It separates "this design is wrong" from "this development path is wrong": sometimes the right design cannot be reached except by first building, and shipping, an intermediate design that is known to be imperfect but is viable enough to operate.

The law also clarifies why many apparently irrational features of working complex systems — vestigial organs, legacy APIs, archaic legal procedures, kludgy street grids — are not design errors but the signature of viable-intermediates evolution. Each feature made sense at the intermediate stage that introduced it, and removing it without a replacement that preserves its function would break a working system. The clarifying move is to convert the question "why is this here?" into "which working ancestor introduced this, and what function did it then serve?", which turns archaeology into a usable design discipline.

Manages Complexity

The law compresses a large family of development failures under one diagnostic — the from-scratch fallacy — and a large family of successes under one prescription: build a working minimum, then evolve it. It compresses the origin of observed working complex systems under one pattern: trace the chain of viable ancestors. Across software, biology, governance, urbanism, and personal change, it supplies a single intervention vocabulary: find or build a viable intermediate, ship it, iterate, and never plan a non-viable intermediate as a way-station.

The complexity reduction is that an open-ended planning problem ("how do we get from here to that complex target?") becomes a structured search for a path whose every waypoint is independently viable. The analyst's question collapses to a viability check on each proposed intermediate, and when no such chain exists, the law flags the redesign as a discontinuity requiring a parallel-running bridge rather than an abandon-and-rebuild. A high-dimensional design problem is reduced to a sequence of local viability questions.

Abstract Reasoning

Reasoning with Gall's Law involves several structural moves. The viability check on intermediates asks, for any proposed path, whether each waypoint is itself a working system or only a partial sub-component of the target; any non-viable waypoint puts the path at risk. Genotype-phenotype connectivity asks whether the viable subset of the design space is connected along the proposed single-step modifications; if not, no incremental path exists. Functional-shift recognition notes that viable intermediates often perform a different function from the target's — an eye-spot that becomes a directional eye that becomes a focusing eye serves vision at every stage, but different versions of it — so the designer must look for the function the intermediate performs, not only the target's. Legacy as fossil of the chain treats vestigial and legacy features as evidence of which path was actually taken, making backward reasoning from current structure to ancestral intermediates a usable technique in both evolutionary biology and software archaeology. Constraint diagnosis on redesign attempts converts a proposed from-scratch rebuild into the question "what is the shortest path of viable intermediates from the current working system to the target?", which often reveals that the redesign is a discontinuity needing a plan to run both systems in parallel until the new one is independently viable.

Knowledge Transfer

Gall's Law has documented cross-domain transfer histories running in both directions, and the transferred content is the load-bearing structural insight — viable intermediates are required — not merely a slogan. From the biological and evolutionary literature, the viable-intermediates requirement passed into evolvability theory and into computational evolutionary algorithms, where fitness-landscape connectivity is operationalized as the "deceptive landscape" problem. From software engineering, the "never rewrite from scratch" principle transferred back into product-management practice across industries. From lean-startup methodology, the minimum-viable-product doctrine moved into corporate innovation programs and public-sector agile-transformation initiatives. From urbanism, the critique of high-modernist planning carried the same insight into urban policy. The transfer is substantive: software designers cite biological evolution, evolutionary biologists cite software engineering, and urbanists cite both, because the load-bearing claim is identical in each substrate.

Consider a government modernizing a national tax-filing system. A from-scratch rewrite scheduled for a single cutover is predicted to fail — the team cannot debug against a working baseline, the cutover discontinuity exposes failure during a live filing season, and there is no viable intermediate to fall back on. A path that modernizes the smallest isolable piece first, ships it, debugs it under real load, and then evolves one viable increment at a time has a longer time-to-completion but a far higher probability of producing a working final system, because each waypoint is independently viable and the team learns from real operation at each step. The same structural moves appear in the chain of viable proto-eyes behind the vertebrate eye, in accretive common law versus failed imposed constitutions, in incrementally evolved products versus failed from-scratch attempts, and in small-habit programs versus total-life-overhaul programs. The transferable insight is the viable-intermediates requirement and its diagnostic test — is each waypoint on the planned path itself a working system? — not any one substrate's particulars.

Examples

Formal/abstract

Frame design-space as a graph whose vertices are system configurations and whose edges are feasible single-step modifications. A viability predicate \(V(\cdot)\) marks each vertex as working or not; the target \(t\) is one working vertex; some simple ancestor \(s\) is another. Gall's Law is then the graph-theoretic claim that \(t\) is reachable in practice only if there exists a path \(s \to \dots \to t\) lying entirely within the subgraph induced by \(\{v : V(v) = \text{true}\}\) — a path of all-working waypoints. The from-scratch fallacy is the attempt to teleport directly to \(t\) without traversing such a path; it fails because the working states reachable from a broken design occupy a different connected component of the viability subgraph than \(t\) does. This is precisely the structure evolutionary biologists call a fitness-landscape connectivity problem and the "deceptive landscape" in evolutionary computation: selection can climb only through viable intermediates, so an organ implies a connected chain of functional (not necessarily similarly-functioned) intermediates. The intervention the formalism prescribes is a constructive search — instead of designing \(t\), search for the shortest all-viable path from the current working \(s\), and where the viable subgraph is disconnected, identify the bridge configuration that must run in parallel with the old system until the new component is independently viable.

Mapped back: The configuration space is the graph's vertices; the viability predicate is \(V(\cdot)\); the target is \(t\); the step relation is the edge set; the viable chain is an all-working path within the viability-induced subgraph; and the constructibility invariant is that \(t\) is reachable only when such a connected path exists.

Applied/industry

A national government modernizing its tax-filing system illustrates the law operationally. The proposed plan is a from-scratch rewrite of the legacy mainframe system with a single big-bang cutover scheduled for the start of filing season. Gall's Law predicts failure: the cutover is a jump to the target with no working intermediate, so the team cannot debug the new system against a running baseline, the discontinuity exposes every defect live during peak load, and there is no viable fallback when the season opens. The prescribed alternative is a chain of viable intermediates — modernize the smallest isolable component first (say, the identity-verification service), ship it behind the existing mainframe, prove it under real load, then evolve one independently-viable increment at a time, the legacy and new systems running in parallel (the bridge configuration) until the new system is whole. Time-to-completion is longer, but each waypoint works, and the team learns from real operation at every step. The identical structural moves appear across substrates: the vertebrate eye's chain of functional proto-eyes (light-sensitive patch → cup → pinhole → lensed eye, each useful when it existed), accretive common law versus collapsed imposed constitutions, and the minimum-viable-product release cadence in which every release must itself be a working product.

Mapped back: The configuration space is the set of possible tax-system designs; the viability predicate is "operates correctly under real filing load"; the target is the modernized system; the step relation is one shippable increment; the viable chain is the sequence of parallel-run intermediates; and the constructibility invariant is why the big-bang cutover — a teleport with no viable waypoint — is predicted to fail.

Structural Tensions

T1 — Incremental Path versus Local Optimum Trap (scopal). The law prescribes climbing through viable intermediates — but a connected chain of working states can lead into a local optimum from which the target is unreachable without passing through a worse intermediate. Pure incrementalism cannot escape a trap that requires a temporary step down in viability. The competing prime is punctuated redesign / saltation. The failure mode is incrementalist lock-in: evolving a working system forever toward a peak that is not the target, never crossing the valley that separates them. Diagnostic: ask whether the viable region is connected to the target, not merely connected — a chain that exists is not a chain that arrives.

T2 — Viable Intermediate versus Functional Shift (measurement). "Each intermediate must work" hides an ambiguity: work as what? Viable waypoints often perform a different function than the target (a light-patch, not a focusing eye), so "viability" cannot be measured as fraction-of-target-completed. The failure mode is rejecting a legitimate intermediate because it does not yet resemble the goal, or accepting a partial sub-component that looks goal-shaped but does not independently function. Diagnostic: test each waypoint against its own fitness in its own environment, not against its resemblance to the destination.

T3 — Evolved Path versus Greenfield Speed (temporal). The all-viable chain is slower than a from-scratch jump, and Gall's Law trades time-to-completion for probability-of-working. But some windows reward speed over robustness — a competitive race, a closing standards window, a funding deadline. The competing consideration is that the incremental path can simply arrive too late. The failure mode is dogmatic incrementalism that ships a robust system after the opportunity has closed. Diagnostic: weigh the higher success probability of the viable chain against the cost of its longer duration; sometimes a risky teleport with a fallback beats a safe path that misses the window.

T4 — Legacy as Fossil versus Legacy as Debt (sign/direction). The law reframes vestigial features as the signature of a viable-intermediates path — evidence to be respected, not errors to be deleted. But the same features are often genuine accumulated debt that now constrains the system. The same archaic API is both "load-bearing fossil" and "thing that should die." The failure mode is mis-signing legacy: deleting a feature that silently still functions (breaking a working system) or preserving cruft that serves no current function (paying debt forever). Diagnostic: identify which working ancestor introduced the feature and whether the function it served still exists.

T5 — Required Intermediates versus Designed Foresight (scalar). Gall's Law generalizes from systems that evolved, but engineering can sometimes simulate intermediates — prototypes, staging environments, formal verification — collapsing the chain in design-space without shipping each waypoint to production. The boundary is where deliberate design partially substitutes for lived evolution. The failure mode is over-reading the law as forbidding all up-front architecture, refusing to design ahead even where a prototype safely stands in for a shipped intermediate. Diagnostic: distinguish "must this waypoint operate under real load?" from "can a faithful simulation of it suffice?" — the law binds the former, not always the latter.

T6 — Single Evolving System versus Parallel-Run Bridge (coupling). When the viable subgraph is disconnected, the law's own remedy is to run old and new systems in parallel until the new one is independently viable — but parallel operation couples two systems that must stay consistent, introducing a synchronization burden the single-path framing omits. The competing concern is the cost and risk of dual-running. The failure mode is treating the bridge as free, underestimating the coupling cost of keeping two live systems coherent, or conversely abandoning the parallel-run too early at the disconnection point. Diagnostic: budget the consistency-maintenance cost of the bridge configuration as a first-class part of the migration, not an afterthought.

Structural–Framed Character

Gall's Law sits at the midpoint of the structural–framed spectrum — a hybrid with an aggregate of 0.5 and all five diagnostics at 0.5. There is a genuinely substrate-neutral constructibility claim underneath (only all-viable chains through design space are traversable), but the prime is an eponymous law born in systems-design and carries a design-prescription flavor when it travels, so the framed and structural pulls come out even.

Reading the diagnostics one by one bears this out. Vocabulary travels (0.5): the load-bearing content — a viability predicate on every waypoint, connectivity of the viable region under a step relation — is a content-neutral graph-theoretic object, recast in the formal example as reachability within the viability-induced subgraph, yet the prime as stated speaks the language of "systems," "designs," "working intermediates," and "from-scratch rewrites," which needs translation before it reads naturally in evolutionary biology or constitutional history. Evaluative weight (0.5): "works" versus "fails to work" carries a mild prescriptive charge (the law is often deployed as advice — don't plan a non-viable intermediate), but viability is assessed against each waypoint's own environment rather than against a value judgment, which softens it. Institutional origin (0.5): its home is design-and-engineering practice, but the dual claim — that observed complex systems are fossilized records of viable-intermediate chains — is a description of biology, language, and law as much as of software. Human-practice-bound (0.5): the software, MVP, and constitutional cases need designers, but the biological-evolvability case (a connected chain of functional proto-organs, formalized as fitness-landscape connectivity) runs in a substrate with no designer at all, which is exactly what keeps the prime from being fully framed. Import-versus-recognize (0.5): invoking the law imports some design-prescription perspective, but its core move is to recognize a connectivity constraint already present in any design space with a viability predicate.

The honest assessment is that the structural skeleton genuinely transfers — software designers cite evolution, biologists cite engineering, urbanists cite both, and the substrate-independence grade reaches a 4 with strong transfer evidence — while the eponymous, prescriptive, design-flavored packaging keeps it from sliding to the structural pole. The 0.5 aggregate captures that even split faithfully, and the prose should not inflate the constructibility core past the design frame that travels with it.

Substrate Independence

Gall's Law is a broadly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. The pattern it names — a complex working system reached only through a connected chain of simpler systems that each worked — is genuinely relational, and the strong, documented transfer history is what carries the composite to a 4, with only the eponymous-law's design-prescription flavor keeping it short of a 5. On domain breadth (4) the viable-intermediates-chain recurs across distinctly different substrates: software engineering (failed from-scratch rewrites versus grown working minimums), biological evolution and evolvability theory (a complex organ implies a chain of functional intermediate organs, formalized as connectivity of the viable region of genotype-space), constitutional and institutional design (working constitutions grow from earlier working ones), urban planning (cities that work grew by layering working sub-systems), venture methodology (the MVP doctrine), standards and protocol design, and personal habit formation. On structural abstraction (4) the signature — viability of each intermediate, connectivity of the chain, the impossibility of jumping straight to the complex whole — is medium-neutral, though its viability predicate must be re-specified per substrate ("confers a survival edge," "carries legitimacy," "operates under load"), which adds a thin domain-tuning step. On transfer evidence (5) the cross-domain carry is concrete and substantive: evolvability research and systems-design folklore make the same structural claim, the MVP doctrine is Gall's Law explicitly operationalized for the venture substrate, and high-modernist urban-planning failures and collapsed from-scratch constitutions are documented instances of the same chain-broken pathology — transfer here is recognized across fields, not merely analogized. What holds the composite at a 4 is that the prime is born in systems-design and carries a design-prescriptive ("grow it incrementally") flavor when it travels, a mild frame on an otherwise substrate-portable structure.

  • Composite substrate independence — 4 / 5
  • Domain breadth — 4 / 5
  • Structural abstraction — 4 / 5
  • Transfer evidence — 5 / 5

Relationships to Other Primes

One-hop neighborhood: parents above, mutual partners to the right, children below.Gall's Lawsubsumption: Minimum Viable Product (MVP)Minimum ViableProduct (MVP)

Foundational — no parent edges in the catalog.

Children (1) — more specific cases that build on this

  • Minimum Viable Product (MVP) is a kind of Gall's Law

    The file: MVP is 'Gall's Law operationalized for the venture substrate' — the prime is strictly more general (its viability predicate is 'works in its own environment', not 'customers pay'). galls_law is the parent; mvp keeps its satisficing/iteration parents.

Neighborhood in Abstraction Space

Gall's Law sits in a sparse region of abstraction space (70th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.

Family — Formal Methods & Idealized Models (31 primes)

Nearest neighbors

Computed from structural-signature embeddings · 2026-06-14

Not to Be Confused With

The most consequential confusion is with the minimum_viable_product_mvp doctrine, because the MVP is so often presented as Gall's Law that the two collapse in practice. The relation is genuine — MVP is Gall's Law operationalized for the venture substrate — but the prime is strictly more general, and conflating them imports MVP's incidental commitments where they do not belong. MVP carries product-market baggage: a "viable" product is one that customers will pay for or use, viability is judged against market fitness, and the chain of releases is a commercial learning loop. Gall's Law makes no such commitment. Its viability predicate is "works on its own terms in its own environment," which for a proto-eye means "confers a survival edge," for a constitution means "carries legitimacy through the transition," and for a tax system means "operates correctly under real load." A reasoner who knows only MVP will look for customers at every waypoint and miss that the law governs biological evolvability, institutional design, and urban growth where there is no market at all. The distinction matters because it tells the practitioner what "viable" must be measured against in their substrate, rather than defaulting to the commercial yardstick the MVP framing smuggles in.

A second genuine confusion is with iteration. Iteration is the bare repetition of a step or cycle; it says nothing about whether the state between cycles is itself a working system. Gall's Law is precisely the constraint on what the intermediate states must be: not merely that you repeat, but that every waypoint independently works, so that the next increment can be debugged against a running base, can recruit the resources to fund itself, and produces failures diagnostic of the target. One can iterate through a chain of broken intermediates — endlessly modifying a non-working design — and that is exactly the from-scratch fallacy the law warns against, dressed up as process. The practitioner consequence is sharp: "we're iterating" is not compliance with Gall's Law unless each iteration's output is a system that works. The law binds the viability of the waypoints, iteration binds only their recurrence.

A third confusion worth pre-empting is with path_dependence, which shares the intuition that history shapes outcomes. But the two make different kinds of claim. Path dependence is descriptive and constraining: it explains why the present set of options is conditioned by the particular sequence of past states, why early contingent choices lock in later structure. Gall's Law is constructive and prescriptive: it claims that only paths whose every waypoint is viable can be built at all, and prescribes searching for such a path. Path dependence tells you that where you can go depends on where you have been; Gall's Law tells you that you can only have gotten anywhere working by a connected chain of working states, and that a from-scratch teleport lands in a disconnected, unreachable component. The vestigial features path dependence treats as the imprint of history, Gall's Law treats as positive evidence of the viable chain — the same fossils read for a different purpose.

For a practitioner these distinctions change the intervention. Mistaking Gall's Law for MVP misdirects the viability test toward market fitness in substrates that have no market. Mistaking it for iteration licenses endless modification of a broken base as if mere repetition satisfied the law. And mistaking it for path dependence reduces a constructive design discipline to a passive observation about history. The prime earns its place as the constructibility claim — only all-viable chains are traversable — that none of its neighbors supplies on its own.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.