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:
@@ -9,6 +9,7 @@ it is a pointer and should be deleted or replaced.
|
||||
| `AGENTS.md` | project root | instructions for the agent: what to build, which key, the first test |
|
||||
| `HANDOVER.md` | project root | what we tried before, what worked, what failed, the pitfalls |
|
||||
| `CHECKLIST.md` | project root | the next session, step by step, with tick boxes |
|
||||
| `docs/OPERATING-RULES.md` | this project | the nine rules: project folder, how work is judged, approvals, untrusted text, secrets, review and merge, one project per machine, cost, existing commands |
|
||||
| `docs/TUIOS-RUNBOOK.md` | this project | how TUIOS works, the three machines, how to start a session, how to drive panes |
|
||||
| `docs/PLAN.md` | this project | the plan: four screens, five milestones, who owns what |
|
||||
| `docs/ENVIRONMENT-FACTS.md` | this project | ids, installed tools, the unproven heartbeat step |
|
||||
|
||||
Reference in New Issue
Block a user