I want to change something. Which file is it in?¶
Find the row for what you want to change, then read across to your framework's file. The last column says whether you edit it yourself, or ask for the change through a design session, a build or a question.
The files¶
| You want to change | App-Director | Godot-Director | SaaSAllTheThings | How |
|---|---|---|---|---|
| What the product is | product/brief.md |
design/gdd.md |
product/prd.md |
Through a design session |
| Why a decision was made | product/decisions.md |
design/decisions.md |
product/decisions.md |
Through a design session. The log is append-only: a session adds a line, and no one edits an old one |
| What's undecided | brief › Open Questions | GDD › Open Questions | PRD › Open Questions | Through a design session. /design questions ranks them, and the agent never answers one for you |
| What gets built next, and in what order | TASKS.md |
TASKS.md |
TASKS.md |
Edit the order yourself, or ask the agent for a suggestion (How do I get things built?) |
| The rules the agent follows | AGENTS.md › Project rules |
AGENTS.md › Project rules |
AGENTS.md › Project rules |
Edit it yourself. The agent reads it at the start of every session, and the records check compares it with the rest |
| Which systems exist, and what each owns | AGENTS.md › Architecture |
AGENTS.md › Architecture |
AGENTS.md › Architecture |
Ask the agent in the build that adds or moves a system. The row changes in the same commit |
| What the check enforces | tools/check.cfg |
tools/check.cfg |
tools/check.cfg, and the reference in .satt/reference/layers.md |
Edit check.cfg yourself, since it is yours to change. The reference belongs to the framework, and a project exception needs an accepted ADR (the check) |
| A screen's layout | None: the screen's own code | design/ui/<screen>.md |
None: the client code in clients/ |
Through the UI question |
| Your own assets and notes | director/ |
director/ |
None: there is no director/ folder |
Edit it yourself. The agent reads it for context and never writes there. Drawings go in director/ui/ (UI changes) |
| What the agent may do without asking | .claude/settings.json |
.claude/settings.json |
.claude/settings.json |
Edit it yourself. Put machine-only changes in .claude/settings.local.json, which is gitignored. A new permission loads when a session starts (Something isn't there) |
| The model for each task size | AGENTS.md › Project rules, Model sizing |
AGENTS.md › Project rules, Model sizing |
AGENTS.md › Project rules, Model sizing |
Ask for "Refresh the model sizing", or run /refresh-model-sizing (cost) |
| Where research notes live | product/research/ |
design/research/ |
product/research/ |
Ask a question (I need facts before I decide). The researcher writes the notes, and later sessions reuse or update them |
| Architecture decisions (ADRs) | None | None | adr/ADR-<n>-<slug>.md |
Through /architect. Only you accept an ADR, and a hook asks before it is marked accepted (the ADR rule) |
How to read it¶
Edit a file yourself when the change is small and you can see the result in it. Ask the agent when the change should land with the code it touches, as a build does. Go through a design session when the change is a decision, because the decision and its reason are written down together, and the decision log never changes by hand.
The rows come from each framework's "Each fact lives in one place" table at its latest release: App-Director, Godot-Director and SaaSAllTheThings. Not sure where a fact lives? Ask the agent. It reads the same table at the start of every session.
Related¶
- Records in files, the concept behind these files.
- How do I decide what gets built, or change how something works? and How do I get things built?, the two ways most changes are made.