torben/chemenu

1 Fork 0

Files

T

History

torbenandClaude Opus 5.5 4f5913a9c8

CI / verify (push) Successful in 7m59s

Details

CI / pwsh (push) Successful in 2m45s

Details

docs/explanation: knowledge-and-commitment nennt auch die lange Quelle als Weg in den Großbaum-Ingest; die Commitment-Frage fällt dort nicht immer je Unit (#226 )

Files changed:
- docs/explanation/knowledge-and-commitment.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

2026-10-15 21:46:40 +02:00

architecture.md

docs: publish-cycle says what a WARN or ERROR from the page export after publish means, architecture names the page export as the way out for a reader that cannot ask (#214 close); 10.0.0-beta.14

2026-10-13 06:39:19 +02:00

configuration-tiers.md

backup: an instance backs up into a synced folder - backup init makes a bare repository under <target>/git its origin, backup run and publish mirror the machine data into <target>/<machine>/, doctor warns about .git in a synced folder (#186 ); 10.0.0-beta.10

2026-10-12 19:39:49 +02:00

knowledge-and-commitment.md

docs/explanation: knowledge-and-commitment nennt auch die lange Quelle als Weg in den Großbaum-Ingest; die Commitment-Frage fällt dort nicht immer je Unit (#226 )

2026-10-15 21:46:40 +02:00

language-boundaries.md

instructions: the agent speaks the KB language in chat - AGENTS.md § Conversation language, and instructions sync compiles the language tag into every published SKILL.md (#116 ); 10.0.0-beta.9

2026-10-12 06:57:51 +02:00

model-and-effort-selection.md

feat!: docs/ sorted into tutorials, how-to, reference, explanation plus unshipped docs/dev/; explanation pages and developer guide moved, human docs English (#187 )

2026-10-06 20:45:09 +02:00

ownership-and-templates.md

docs: troubleshoot names doctor's telemetry WARN; ownership-and-templates says the configuration shapes are rendered from tools/ too (#193 )

2026-10-07 09:05:32 +02:00

pipeline-rationale.md

intake: several configured intake channels (mcp, folder, command) all end in quarantine/ (was mcp-upload/), and upload collect pulls the synced-folder and command channels into it (#213 ); 10.0.0-beta.11

2026-10-12 22:04:18 +02:00

README.md

settings: three tiers - wikitool.json (instance), .wikitool-local.json (checkout), secrets by reference incl. 1Password CLI; new command config set (#207 )

2026-10-10 15:34:28 +02:00

telemetry-and-evaluation.md

settings: the four per-feature files .wikitool-remotes/-telemetry/-upload/-tasks.json move into the three tiers and disappear; new command config migrate; 10.0.0-beta.1 (#208 )

2026-10-11 06:54:35 +02:00

version-model.md

feat!: docs/ sorted into tutorials, how-to, reference, explanation plus unshipped docs/dev/; explanation pages and developer guide moved, human docs English (#187 )

2026-10-06 20:45:09 +02:00

why-gates-are-code.md

settings: the four per-feature files .wikitool-remotes/-telemetry/-upload/-tasks.json move into the three tiers and disappear; new command config migrate; 10.0.0-beta.1 (#208 )

2026-10-11 06:54:35 +02:00

README.md

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