torbenandClaude Code
cceb9a7bfe
Files changed: - .gitignore - CHANGES.md - VERSION - docs/explanation/architecture.md - docs/explanation/pipeline-rationale.md - docs/how-to/README.md - docs/how-to/back-up-to-a-synced-folder.md - docs/how-to/collect-from-a-synced-folder.md - docs/how-to/ingest-a-source.md - docs/how-to/set-up-the-mcp-server.md - docs/reference/commands/README.md - docs/reference/commands/git.md - docs/reference/commands/instance-health.md - docs/reference/commands/raw-material-and-uploads.md - docs/reference/configuration.md - instructions/gates.md - instructions/ingest-queue.md - instructions/mcp-read-server.md - instructions/migrations/10.0.0-settings-tiers.md - instructions/wiki-ingest/SKILL.md - raw/CONTRACT.md - tools/CONTRACT.md - tools/README.md - tools/chemenu/cli_contract.py - tools/chemenu/collect.py - tools/chemenu/commands/backup_cmd.py - tools/chemenu/commands/docs_verify.py - tools/chemenu/commands/doctor.py - tools/chemenu/commands/raw/pending.py - tools/chemenu/commands/upload_cmd.py - tools/chemenu/config.py - tools/chemenu/config_shapes.py - tools/chemenu/legacy_settings.py - tools/chemenu/mcp/server.py - tools/chemenu/reference_doc.py - tools/chemenu/tests/test_backup.py - tools/chemenu/tests/test_collect.py - tools/chemenu/tests/test_config_shapes.py - tools/chemenu/tests/test_doctor.py - tools/chemenu/tests/test_legacy_settings.py - tools/chemenu/tests/test_mcp_server.py - tools/chemenu/tests/test_upload.py - tools/chemenu/tests/test_upload_cmd.py - tools/chemenu/upload.py Co-Authored-By: Claude Code <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
Explanation
Why the stack is built the way it is. These pages are background for humans and agents alike:
read by link or on request, never as instruction, and they carry no normative sentence - a rule
lives in AGENTS.md or a CONTRACT.md, and a page here only gives its reasons.
- architecture.md - what the stack is made of, and how its parts divide the work
- telemetry-and-evaluation.md - how the stack observes what an agent did, and how that record turns into a score
- pipeline-rationale.md - why the pipeline has four stages
- ownership-and-templates.md - why a
.templatesplit exists, and why an instance comes only from a release - language-boundaries.md - why the control plane is English everywhere and the KB language is a value
- why-gates-are-code.md - why the gates are code rather than instruction
- version-model.md - why a version number answers a compatibility question and a migration question separately
- knowledge-and-commitment.md - why commitments live in a task
tracker rather than in
kb/ - configuration-tiers.md - why settings sit in three tiers, and what keeping secrets out of the tree does not protect against
- model-and-effort-selection.md - which model and effort suit which kind of session, for the harness that has to choose