← the map
the system

Your system starts as one file.

You do not build an operating system up front. You start with a couple of files, and they grow into one as your projects teach you what to keep.

day one
CLAUDE.mdDECISIONSsession-current

enough to not lose your thread.

when something hurts
CLAUDE.mdDECISIONSsession-currentopen-questionsLEARNINGS

a new file appears when a real pain calls for one.

over time
CONSTITUTIONWORKFLOWSTYLEjourney/INDEXMENTAL-MODELSBUILD-METHODStemplates/VISIONPROJECTS

your own system, grown not designed.

the new file each time is highlighted. The faint ones are where it can grow, not a checklist for today.

It grows when something hurts

You never add a file because a guide said so. A new home shows up the moment a real pain makes you want one.

buildhit frictiongive it a homeapply it nextand again

Three habits make it work

01

Write it down when you decide

Not later. By then the reason is gone.

02

One home per thing

Each fact in one place, so you always know where to look.

03

Fix the file, not the prompt

When the AI is off, fix what it reads, not your wording.