Framework Laws
The Large People Model laws explain why the layers behave as a system. They show how structure, decisions, incentives, information, governance, AI, leadership, autonomy, and oversight reinforce or weaken each other.
Where laws fit
Use a layer to locate an operating condition. Use a law when you need to explain a repeating pattern, dependency, or failure that crosses layers.
Seven Layers
A diagnostic map of ownership, decisions, communication, information, platforms, governance, and AI.
Nine Laws
Explanations for why operating patterns repeat, interact, and cascade through that map.
Nine Laws
Each law strengthens or constrains the others. When one law is ignored, failure usually cascades across multiple layers.
Law 01
People scale to the structure they are given. Performance problems are usually architecture problems.
Foundation law. Every other law depends on whether the operating structure is explicit.
Familiar violation
A transformation team adds a new workflow tool, but approvals still follow the old reporting hierarchy and work slows down.
Use this law when
a recurring behavior persists despite new tools, policies, or leadership messages.
Law 02
Organizations move through decisions. Every delay is a decision-architecture failure.
Depends on Law 1 because decision behavior follows the structure that defines it.
Familiar violation
A product launch is revisited in three meetings because contributors were named but one decider was not.
Use this law when
decisions stall, reverse, or escalate because authority is unclear.
Law 03
Declared values never beat lived incentives. Behavior follows what is rewarded.
Depends on Law 1 because incentives are part of the operating structure.
Familiar violation
Leaders ask teams to share customer data while bonuses still reward isolated departmental performance.
Use this law when
stated priorities and rewarded behavior point in different directions.
Law 04
Signal clarity determines decision quality, human or AI. AI on ungoverned information amplifies disorder.
Depends on Laws 1 and 2 because information quality follows ownership and decision discipline.
Familiar violation
An AI assistant gives different answers because policy copies across three systems have different owners and dates.
Use this law when
people or AI cannot identify which information is current and authoritative.
Law 05
Real governance creates operational clarity. Compliance theater creates the appearance of control.
Depends on Laws 1 through 4 because governance must govern real behavior, decisions, incentives, and information.
Familiar violation
A review board approves AI use annually, but no control fires when confidence drops or exceptions spike.
Use this law when
governance exists in documents but not inside the path of work.
Law 06
AI amplifies the operating system beneath it. Structure before velocity.
Depends on Laws 1 through 5 because AI requires structure, decisions, incentives, information, and governance.
Familiar violation
An agent accelerates refund recommendations while unclear ownership and conflicting policy sources create faster mistakes.
Use this law when
AI activity is increasing faster than operating-model readiness.
Law 07
The operating model mirrors leadership behavior. No exception.
Sustains Laws 1 through 6 because leaders make the architecture credible in practice.
Familiar violation
Executives bypass the published decision path for urgent work, teaching everyone that the architecture is optional.
Use this law when
leadership exceptions are weakening an otherwise sound operating design.
Law 08
No agent or decision type advances in autonomy by default. Advancement requires clearing a measurable confidence threshold owned by the business, not engineering.
Depends on Laws 5 and 6 because governance and architecture must exist before autonomy can be safely extended.
Familiar violation
A successful pilot is granted broad autonomy without measured thresholds, exception history, or rollback evidence.
Use this law when
a team wants to expand AI authority based on confidence or enthusiasm alone.
Law 09
Every governed agent consumes a named human supervisor's finite control capacity. Exceeding Supervisory Control Capacity is an operational failure, not a warning.
Depends on Laws 1 and 8 because supervision is structure and earned autonomy keeps supervisory load survivable.
Familiar violation
One manager nominally supervises dozens of agents but cannot review exceptions, overrides, and performance drift.
Use this law when
agent scale is increasing without an explicit model of human oversight capacity.
Dependency Chain
The laws explain why LPM starts with structure and ownership before moving to decisions, information, governance, and AI.
Structure defines the behavior the organization will actually repeat.
Decision architecture makes commitments observable and accountable.
Incentives determine whether people protect the system or route around it.
Information quality determines whether humans and AI can reason from reality.
Governance keeps the system coherent as speed, scale, and risk increase.
AI amplifies whatever operating architecture exists beneath it.
Leadership behavior determines whether the architecture survives pressure.
Autonomy is earned through measurable confidence thresholds.
Oversight is finite and must be designed before agents scale.
Operating Tensions
Use risk tiering. Governance wins for irreversible, high-stakes decisions; velocity wins for low-risk, reversible decisions.
Fix the incentive architecture. Leaders cannot out-message rewards that point in the wrong direction.
Constrain AI to governed sources. Speed should expand only inside trusted information corridors.
Invite broad input, but keep one accountable owner for commitment and outcome.
Governance should be embedded into workflows, platforms, and decision paths before AI scales.
Leaders model the architecture; they do not replace it.
Failure Cascades
Structure is vague -> decisions are shared by everyone -> incentives reward avoidance -> information has no owner.
Execution feels collaborative but no one carries the outcome.
Controls sit outside work -> decisions route around approval -> information is copied into side channels.
The organization appears governed while the real operating model remains unmanaged.
AI is added before ownership, decisions, information, platforms, and governance are clear.
AI increases throughput while also increasing rework, risk, and uncertainty.
Leadership asks for enterprise coordination while rewarding local speed, budget protection, or volume.
The operating model fragments exactly where it needs integration.
Communication creates context, but nothing becomes durable, versioned, owned, or trusted.
People debate facts, platforms preserve conflicting truth, and AI retrieves noise.
