Internal operator guidance for this fork. Not canonical public collaboration policy; public-facing authority lives in
README.md,CONTRIBUTING.md,SECURITY.md, andSUPPORT.md.
Root navigation guide.
Use this file to answer three questions quickly:
- where to read next
- what must never be tracked
- which checks are required before claiming a change is safe
- frontend:
apps/web/CLAUDE.md - api:
services/api/CLAUDE.md - core runtime:
packages/core/CLAUDE.md - tests and verification:
tests/CLAUDE.md
Read order is fixed:
- nearest
CLAUDE.md - nearest
AGENTS.md - root
CLAUDE.md - root
AGENTS.md - a targeted file under
docs/
rg -n "<keyword>" AGENTS.md CLAUDE.md README*.md docs config contracts tooling services packages apps tests ops evals mutants
rg --files -g 'AGENTS.md' -g 'CLAUDE.md' -g 'README*.md'Keep at least one evidence token in the changed docs, for example README.md:1.
- Keep docs English-only.
- Keep docs minimal.
- Keep runtime, agent, cache, and log directories untracked.
- Prefer repo-local docs and scripts over stale historical notes.
bash tooling/scripts/runtime/run_uv_managed.sh sync
cd apps/web && npm ci && cd ../..
bash tooling/scripts/ci/check_env_governance.sh
bash tooling/scripts/ci/check_secret_leaks.sh
bash tooling/scripts/runtime/run_uv_managed.sh run python tooling/scripts/ci/check_navigation_docs_pair.py