stage-1listed

# stage-1 — the four files, then stop Read STATE first, work, update STATE last. That habit is the user's. These four files are yours to create. Nothing else. 1. Confirm the current directory is a git repository and you were started inside it. If not, stop and say so — one repository is the workspace. 2. For each file below: if it already exists, **do not overwrite it**; show its first lines and ask. Otherwise write it exactly as given. 3. Run `ls -la CLAUDE.md NON-GOALS.md STATE.md LESSONS.md` and paste the output. Then stop. Do not build a gate, a hook, a skill, or a subagent workflow. Do not commit. ## CLAUDE.md Replace the placeholder line with one paragraph about this project. Keep the rest verbatim. ```markdown # CLAUDE.md ## What this is <one paragraph: what the project is for — not how it works> ## Non-goals See NON-GOALS.md. That file wins. If a task touches one of them: stop and ask. Never change it quietly. ## Prime directives 1. No unverifiable claims. Every statement about state must be derivable from the filesystem, git, or the database. 2. Nothing is "done" until verification has run and its output is quoted — not summarised. The check must exercise the claim. 3. Report before any bulk delete, move or rename. ## Rhythm Read STATE.md first. Update it last. Four lines are enough. Lessons go in LESSONS.md, never here. Status never goes here. ``` ## NON-GOALS.md The first two lines hold for every project. Ask the user for up to three of their own; if t