01 / Stabilize
Protect the base
Reduce avoidable volatility before adding load.
EXIT Core / Open protocol
EXIT is a public operating protocol for preserving and rebuilding usable choice under load. It is designed to keep working when motivation, attention or capacity are imperfect.
Operating loop
Move from state to evidence without asking motivation to carry the system.
01 / Stabilize
Reduce avoidable volatility before adding load.
02 / Observe
Describe the system before explaining it.
03 / Separate
Distinguish facts, interpretation and uncertainty.
04 / Choose
Find the bottleneck that matters now.
05 / Execute
Make the next action small enough to finish.
06 / Measure
Record what changed.
07 / Document
Preserve useful evidence.
08 / Adjust
Keep what worked and change what did not.
Public tools
Three public tools cover the core sequence. Account + Sync stays optional.
Observe
Six short questions identify the strongest pressure and one useful next move.
Run the Chaos Audit →Stabilize
Turn actual capacity into a smaller 24-hour operating plan that protects the base.
Build an MVD →Execute
Choose one bounded action, define done, cap the block and stop when the mission is complete.
Build a Daily Mission →Open core
The protocol and core tools are public. Founder 100 is a separate, finite founding layer.
Founder 100
The protocol is public. Founder status is scarce.Founder 100 marks the first one hundred people in EXIT's founding record. It does not unlock the core method.
Human Autonomy Study is separate from EXIT. Buying or using EXIT never creates research eligibility or consent.
Visit Human Autonomy Study →Recruitment and consent remain independent from EXIT.
Next move
Start with one public tool. Re-enter from reality whenever the loop breaks.