documenting

# Documenting a repository **A package's document is its own `README.md`.** It sits next to the code it describes, so the diff that invalidates it and the diff that fixes it are the same diff. Only the repository-level map lives apart: ``` _deploy/graph/ ├── README.md the package's page — the one authored document (authored) ├── package.json └── src/ docs/architecture/ ├── repo.json the map: components, glossary, reading order (authored) ├── repo.md the repository's own page, plain language + figures (authored) └── index.json one-liners, anchors, facts, staleness — GENERATED by `intentic-docs check`. Never write this by hand. ``` There is no per-package JSON sidecar. Everything the app needs to *read* rather than render — the one-liner, the anchors, the size and neighbour facts, whether the page is stale — is derived from the README and from git. `intentic-docs` is on your PATH: ```sh intentic-docs facts --repo intentic # packages, dependency edges, sizes, revisions intentic-docs validate --repo intentic --from published # every package has a README, every anchor resolves intentic-docs check --repo intentic --from published --write # rewrite index.json (staleness, orphans, facts) ``` **`--repo` names a repository under the workspace root, not the directory you are standing in.** It is resolved against `--root` (`/work`), so `cd`-ing into a repository changes nothing a...