docs: Nachzug zu #119 - Verpflichtungsschicht in Installation, Setup und docs/ (#119)
CI / verify (push) Successful in 49s
Release / release (push) Successful in 35s

Files changed:
- AGENTS.md
- CHANGES.md
- INSTALL.md
- README.md
- VERSION
- docs/knowledge-and-commitment.md
- instructions/dev/doc-pull-through.md
- instructions/setup-instance.md
- instructions/upgrade-instance.md
- tools/README.md
This commit is contained in:
torben committed 2026-09-20 10:08:45 +02:00
1 parent 44909c9e47
commit 1d695f6536
10 files changed
+296 -24

No files matched your search

+8 -6
View File
@@ -142,19 +142,21 @@ background consulted in passing, not a rule to follow; anything that would bind
type, index, lint or provenance; `dist export` ships it verbatim and no other `tools/wikitool`
command touches it.
Five pages are reached from this file, each by link rather than automatically:
Six pages are reached from this file, each by link rather than automatically:
[docs/pipeline-rationale.md](docs/pipeline-rationale.md) (why the pipeline has four stages),
[docs/ownership-and-templates.md](docs/ownership-and-templates.md) (why a `.template` split
exists, and why silent overwrite is the failure it guards against),
[docs/language-boundaries.md](docs/language-boundaries.md) (why the control plane is English
everywhere and the KB language is a value, and why the axis is the reader rather than the
owner), [docs/why-gates-are-code.md](docs/why-gates-are-code.md) (why the four gates in
[Gates](#gates) are code rather than instruction), and
[Gates](#gates) are code rather than instruction),
[docs/version-model.md](docs/version-model.md) (why a version number answers a compatibility
question and a migration question separately). A sixth,
`docs/model-and-effort-selection.md`, is deliberately not linked here but from `CLAUDE.md`: it
decides something only that harness has to decide, and a link here would load it into the other
three.
question and a migration question separately), and
[docs/knowledge-and-commitment.md](docs/knowledge-and-commitment.md) (why commitments live in a
task tracker rather than in `kb/`, and why the two are joined at read time instead of synced). A
seventh, `docs/model-and-effort-selection.md`, is deliberately not linked here but from
`CLAUDE.md`: it decides something only that harness has to decide, and a link here would load it
into the other three.
## Personalization