Local first cycle
Five Days Forward
A private browser prototype for the first five days forward. The production version still needs accounts, durable storage, and access controls.
Before Day One
Look Back
Capture the current map before changing it. This makes the shift visible later.
Needs more signal
Day One
What Matters
Choose a direction that can hold attention after the mood changes.
Needs more signal
Day Two
What Is Possible
Name one obstacle, then decide whether it is real, assumed, reducible, or ready to test.
Needs more signal
Day Three
Direct Intelligence
Turn a vague request into an assignment with context, constraints, and review.
Needs more signal
Day Four
Multiply Action
Coordinate help without turning the work into noise.
Needs more signal
Day Five
Make It Real
A proof is something controllable, inspectable, and honest enough to teach you what to do next.
- MISSING_FIELDProof title needs a specific answer.
- MISSING_FIELDConnected direction needs a specific answer.
- MISSING_FIELDArtifact needs a specific answer.
- MISSING_FIELDEvidence needs a specific answer.
- MISSING_FIELDParticipant control needs a specific answer.
- MISSING_FIELDFeedback plan needs a specific answer.
After Day Five
The reveal appears when the first cycle has a valid proof and retained assets.
The next cycle begins with what this one left behind.
Add retained assets in Make It Real to carry them forward.