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)
CI / verify (push) Successful in 7m59s
CI / pwsh (push) Successful in 2m45s

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
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-15 21:46:40 +02:00
1 parent eae4a427d2
commit 4f5913a9c8
1 file changed
+3 -3
+3 -3
View File
@@ -103,9 +103,9 @@ tracker item, never a page; a source that also carries knowledge gets that knowl
through the ordinary page-creation commands, as a separate step. The two are never one
transaction the way `new project`'s tracker-then-page order is within a single command - they are
two independent writes a skill sequences, tracker first, so a failure creating the item leaves no
page and no promoted source material behind it. That holds for an ordinary source; a source large
or broad enough to run through the large-tree procedure instead promotes ahead of its own
per-unit commitment decision, because that procedure hands its units through a workshop directory
page and no promoted source material behind it. That holds for an ordinary source; a source large,
broad or long enough to run through the large-tree procedure instead promotes ahead of its own
commitment decision, because that procedure hands its units through a workshop directory
that needs them already promoted to address them at all - the same raw-file-without-page state
the ordinary case avoids becomes, there, the expected condition for as long as the run takes. And
a failure on the knowledge side afterwards is exactly the ordinary "a source without a page" state