Prune docs to what code can't say

2026-10-20 22:25:27 -07:00
parent 2bfa62449d
commit 9c07c83d7e
8 changed files with 118 additions and 651 deletions
@@ -5,7 +5,7 @@ These are requirements, not preferences. Changing one needs the owner's agreemen
 ## Workflow

 - Never deploy unless the owner asks for it in the current turn. A finished change is reported undeployed; the owner deploys it, or asks you to. Never run `mac/deploy.sh` or restart the service on your own initiative, not even to check that a change works.
- `docs/operations.md` describes the layout, data, service and APIs; keep it current with every change.
+- Update `docs/` only when a change affects what they hold: rules and process, external facts (where binaries come from, how to regenerate things, vendor quirks), behavior observed live (expected errors, agent refusals), or design intent the code can't show (why a rule exists, cases deliberately ruled out). Never narrate what the code does.
 - Never add tests. byre has no test suite; check a change with `go vet ./...`; when `mac/` or `api/openapi.yaml` changed, `mac/bundle.sh` (release only; debug builds are refused); and when `hands/` changed, `swift build --package-path hands --configuration release`.

 ## Deploying