Arc Design
Choosing one arc and implementing it
Commitment + construction + execution
Core Distinction
O3 chooses direction.
Arc Design commits to form.
Orientation answers where to point.
Design answers what to build.
What Arc Design Does
Arc Design is a commitment layer. It takes the directional constraints from O3 and turns them into something real.
It answers:
What form does this arc take?
What is being initiated, concretely?
What do we build, launch, become, or pursue?
Arc Design outputs:
A new role
A new business line
A new product
A new identity arc
A new configuration of resources
Navigation Analogy
Terrain + weather
Compass heading
Vehicle + route
You can know the terrain is hostile, the old road is collapsing, and the new direction should be north.
But until you choose: walk vs sail vs build a bridge, fast vs durable, solo vs institutional…
…you haven't designed anything.
The Hard Boundary
Use this rule:
If you can sketch it, prototype it, or launch it — it's Arc Design.
If you can only describe direction or constraint — it's O3.
Examples:
"The next arc should invert centralization"
"We build a protocol with local ownership"
"The obvious failure is attention extraction"
"We build a tool that compounds quietly without presence"
Arc Design Is Where:
Tradeoffs become explicit
Risk becomes asymmetric
Failure becomes possible again
Design is where you pick a form and accept consequences.
Characteristics
Concrete
Real, tangible, actionable
Irreversible
At least in the short term
Costly
Requires resource allocation
Reality-tested
Validated by execution
Why ARC Needs Both Layers
Without O3:
Arc Design becomes reactive. You rebuild the same arc with cosmetic changes.
Without Arc Design:
O3 becomes philosophical. Insight never crystallizes into reality.
ARC works because:
Forces humble you → Orientation constrains you → Design commits you