The Law of Mission
Foundational postulate
In 30 seconds
Every system pursues a purpose. Rules exist to maximize that mission.
Civilization · Country · Enterprise
Mechanism
VC funds maximize returns. States maximize sovereignty and social cohesion. Family capital maximizes continuity. Apparent irrationality is often mission optimization you have not named. Import a US VC playbook into a French state-and-labor mission and you will diagnose incompetence where there is only a different objective function.
French labor law as feature-not-bug is a mission read, not a glitch in an American labor-market game. Compatibility (Law 14) follows: systems accelerate players who reinforce mission and friction those who contradict it. Games (Law 2) inherit their scoreboards from mission. Name the mission before you criticize the rules.
Signals
- Policy or strategy coherence when read through the mission lens.
- Apparent inefficiencies that persist because they serve a higher mission constraint.
- Capital allocation patterns stable across leadership changes when mission is institutional.
- Stakeholder conflicts resolving toward a detectable primary objective.
- Imported playbooks failing until rewritten to local mission (state, family capital, VC).
Falsifiers
- Systems with no detectable mission optimization over decades of decisions.
- Rules systematically undermining stated and revealed mission without correction or dual-mission explanation.
- Random rule changes producing no change in mission-relevant outcomes.
Decision implications
- 01 Infer mission from revealed preferences before criticizing rules.
- 02 Design enterprise strategy to fit the missions of capital and state you operate under.
- 03 In cross-border expansion, remap mission before remapping tactics.
- 04 Treat labor and tax regimes as mission artifacts, not temporary bugs.
- 05 When missions conflict (growth vs cohesion), name the hierarchy explicitly.
Edge cases
- Dual missions (sovereign fund + return target) create oscillating rules — still mission-driven, not random.
- Capture by a subsystem can hijack mission — diagnose as mission conflict, not absence of mission.