gramps
b5e3dbe614
One file (AGENTS.md) that bootstraps the rest: rules, the file map to create, what belongs in each file, the first-session interview order, and the list of anti-patterns that killed the previous map (1,308-line guide, 63 task files, narrative history inline, sessions skimming 56k tokens of context). Separates four kinds of content by read frequency: rules/invariants -> AGENTS.md (every session) subsystem truth -> docs/ai/<topic>.md (only the matching one) lookups -> environment.md (grepped, never read) retired decisions -> decisions.md (only when re-opening one) Caps are enforced, not promised: scripts/verify.sh checks doc budgets before the build, so a commit that pads a capped file fails. Proven both ways — it passes clean and exits 1 on an over-cap file. scripts/scope-check.sh blocks edits outside the declared file list. templates/ holds fill-in skeletons for the seven files a project must create. CC0: copy it, rename it, sell it, no attribution needed.
35 lines
690 B
Markdown
35 lines
690 B
Markdown
# Environment — lookups
|
|
|
|
Facts you grep for, never read start to finish. Add a line the first time one costs a hunt.
|
|
|
|
## Hosts & access
|
|
|
|
| Host | Address | Role |
|
|
|---|---|---|
|
|
| <host> | <ip> | <role> |
|
|
|
|
SSH / credentials: <where they live, never in this repo>.
|
|
|
|
## Build, run, test
|
|
|
|
```bash
|
|
<clean command>
|
|
<build command>
|
|
<run command>
|
|
<test command>
|
|
```
|
|
|
|
<The traps: which toolchain, which host, why not the other one. Notes on warnings, restores, caches.>
|
|
|
|
## Paths
|
|
|
|
- App data / config: `<path>`
|
|
- Logs: `<path>` (rotation: <rule>)
|
|
- Build output / artifacts: `<path>`
|
|
|
|
## Test map
|
|
|
|
| Area | Test file | Notes |
|
|
|---|---|---|
|
|
| <area> | `<file>` | <known flaky? slow? needs env?> |
|