Operating rules: the nine things a fresh session must not have to rediscover
Project folder convention, how a task is judged finished, content-bound approvals, untrusted text as data, secret handling, ocr review and serialised merge, one project per machine, cost limits, and the four commands that already work. Referenced from AGENTS.md.
This commit is contained in:
@@ -12,7 +12,8 @@ If you are the person: read these in order:
|
||||
3. `docs/PAPERCLIP-API-NOTES.md` — what we measured against your running Paperclip, with the endpoint and the response.
|
||||
4. `CHECKLIST.md` — the exact steps for the next session, in order, with boxes to tick.
|
||||
5. `docs/TUIOS-RUNBOOK.md` — TUIOS, not tmux: the three machines, starting a session, driving panes.
|
||||
6. `docs/DOCMAP.md` — which document is authoritative for what. One home per document.
|
||||
6. `docs/OPERATING-RULES.md` — the nine rules, including how a task is judged finished.
|
||||
7. `docs/DOCMAP.md` — which document is authoritative for what. One home per document.
|
||||
6. `docs/ENVIRONMENT-FACTS.md` — the ids, the installed tools, and the one step that is
|
||||
still unproven.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user