Install control. Do not wait for motivation.

The 30-Day Control Sprint is now part of the public EXIT core. No payment and no account are required. Start from one active constraint and install the loop under real conditions.

One useful day is evidence. Thirty days can become a system.

This is not thirty lessons, a streak challenge or another to-do app. You work one active constraint through a small persistent control loop.

Daily

State → priority → one action.

Match the load to actual capacity. Record evidence. Stop when the bounded move is complete.

Weekly

Review what reality changed.

Remove friction, update the active priority and keep what still works on lower-capacity days.

Day 30

Leave with My Control System.

Stability rules, priority, Not Now, failure protocol, decision rule, daily/weekly loop, warning signals and next direction.

The system compresses before it demands more force.

RED days prioritize the protected base and one small action. Missed days do not create catch-up debt. There are no streaks, points or punishment mechanics.

LOW CAPACITY

Reduce scope.

Fewer visible demands. Smaller action. Continuity over optimization.

MISSED DAY

Return to reality now.

No backlog of lessons. No manufactured failure. Continue from the current state.

DATA

Local first.

Sprint state is stored in the current browser first. Optional Account + Sync can carry it across devices.

Run the full 30-Day Control Sprint.

The complete implementation loop is public: Daily Control Loop, four Weekly Control Reviews and the Day 30 My Control System artifact.

AccessOpenDuration30 daysDataLocal firstAccountOptional

EXIT Core

Public by design.

Start directly. Sign in only if cross-device sync is useful.

Start the 30-Day Control Sprint →

Public product. Separate research initiative.

Human Autonomy Study remains structurally separate. Using Exit Framework never creates research participation or eligibility.

Research participation is not sold.

Product use and research recruitment remain separate systems.