3

Explanation

Wiki Mirror edited this page 2026-10-16 14:43:37 +00:00

Table of Contents

• Explanation

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Generated from docs/explanation/README.md at v10.1.0 – edit the repository, not this wiki.

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 .template split 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

• Chemenu - Personal IT Knowledge Base
• Install a Chemenu instance
• Tutorials
  • From your first source to your first answer
  • Home lab backups - how they work now
• How-to guides
  • Back up to a synced folder
  • Browse the wiki in Obsidian
  • Capture documentation from a git repository
  • Collect documents from a synced folder
  • Export guidelines to captured repositories
  • Export to a synced folder
  • Fetch pages behind a login
  • Ingest a source
  • Maintain the wiki
  • Query the wiki
  • Run the weekly review
  • Set up the MCP read server
  • Trace and score agent sessions
  • Troubleshoot an instance
  • Update an instance
  • Use 1Password for settings
  • Write a site handler
• Reference
  • Command reference
    • Catalog and log
    • Configuration
    • Content migrations
    • Distribution and versioning
    • Exports
    • Finding and checking
    • Git
    • Instance health
    • Links and citations
    • Pages
    • Provenance
    • Raw material and uploads
    • Telemetry
    • Types, instructions and docs
    • Workshop runs and session budget
  • Configuration
  • Exit codes and gates
  • Page types
  • Skill catalogue
• Explanation
  • Architecture
  • Configuration tiers
  • Why knowledge and commitments are two layers
  • Language Boundaries
  • Choosing a Claude Code model and effort level
  • Ownership and Templates
  • Why the pipeline has four stages
  • Telemetry and evaluation
  • Why the stack version splits compatibility from migration
  • Why gates are code
• Dev
  • Developing this stack