Appearance
Policies
Rules the repository enforces mechanically. Each policy names the script that checks it and the decision in DECISIONS.md that motivates it. A policy that cannot be checked by a script is a convention, and conventions live in AGENTS.md, not here.
| Policy | Checked by | Decision |
|---|---|---|
| Public vocabulary | pnpm check:vocabulary (scripts/check-public-vocabulary.mjs) | D-006 |
| Security posture | packages/*/features/ scenarios, pnpm check:deps, Playwright in pnpm test:e2e | D-001, D-002, D-003 |
| Spec conformance | packages/*/features/ scenarios; review. Running @napplet/conformance in the suite is roadmap work. | AGENTS.md "Spec before code" |
Two further gates apply to everything, including these pages:
- Docs gate.
pnpm docs:checkbuilds TypeDoc and VitePress, then runsscripts/audit-docs.mjs: a page per package with its version row, every page in the sidebar, a TypeDoc module per package,llms.txt,llms-full.txtand a Markdown twin per built page. - Slop gate.
pnpm slopruns aislop over the repository andscripts/assert-slop-score.mjsfails below 100. Functions under 120 lines, files under 600, nesting under 4, at most 5 parameters, no narrative comments.