From 9fa2f59497ee2d14aecbb5ebff467616097417b4 Mon Sep 17 00:00:00 2001 From: treylom Date: Wed, 9 Sep 2026 12:45:08 +0900 Subject: [PATCH 1/4] =?UTF-8?q?rules:=20pre-check=20before=20starting=20as?= =?UTF-8?q?signed=20ledger=20rows=20(1.9)=20+=20no=20re-asking=20about=20f?= =?UTF-8?q?inished=20projects=20(2.10-c)=20=E2=80=94=20mirror=20of=20vault?= =?UTF-8?q?=20docs/rules-full=202026-09-09?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Fable 5.1 --- rules/autonomy.md | 5 +++++ rules/skill-process.md | 4 ++++ 2 files changed, 9 insertions(+) diff --git a/rules/autonomy.md b/rules/autonomy.md index f614b74..5792bed 100644 --- a/rules/autonomy.md +++ b/rules/autonomy.md @@ -114,6 +114,11 @@ reached partial / blocked / awaiting-permission state. separate table. - Case-based; re-judge per situation; the maintainer's call wins. + +## 2.10-c No re-asking the operator about finished projects (2026-09-09) +If a deferred ledger row's release condition is "wait for the operator to confirm," and that confirmation is tied to a project or delivery that has already finished, do not raise it to the operator again. Close the row as not applicable instead. Check this once, based on the project's actual closing record (its outcome note or its calendar end date) rather than memory or a guess. The bot that defers the row writes the note "finished project: " directly on that row. Exception: if the same finished project still has an open follow-up contract, re-engagement, or maintenance window, it is not closed — the release condition should instead point to that open window. +(vault docs/rules-full/autonomy.md, 2026-09-09) + ## 3. No busywork - If all remaining work is blocked on a user decision, don't invent fake follow-ups. Report the state, then stop. Don't poll the user. diff --git a/rules/skill-process.md b/rules/skill-process.md index d2b1543..3a0c8d0 100644 --- a/rules/skill-process.md +++ b/rules/skill-process.md @@ -42,6 +42,10 @@ an automated experiment loop; delegating to a sub-agent. the failure mode is invisible. See the periodic-review rule for the standing check and for why nested collisions behave differently. +## 1.9 Pre-check before starting a provisionally assigned ledger row (2026-09-09) +Before starting a ledger row that was provisionally assigned or handed over, run the pre-check script once for that owner. For any row it flags as a possible match, open the diff of the matching commit and judge whether the work was actually reflected in code, rules, skills, or config files, or merely quoted in a meeting note, log, or mirror copy. If it was reflected, close the row with a one-line receipt pointing to the exact file and line (or commit hash). If it was only quoted, leave the row's status unchanged and add a note explaining it was a false match. Only rows the script does not flag should be started as new work. The bot starting the row is responsible for writing the receipt or note directly on that row; the script's own exclusion list for quoted sources is the reference to follow, not a copy kept in this document. +(vault docs/rules-full/skill-process.md, 2026-09-09) + ## 2. Design-before-implement (hard gate) - "Let's build X" = present a design and get alignment **before** scaffolding or implementation. Exception: if the user explicitly said "proceed" under a From e909322a2673b2f708f04b7bf717aad273902821 Mon Sep 17 00:00:00 2001 From: treylom Date: Wed, 9 Sep 2026 12:52:43 +0900 Subject: [PATCH 2/4] rules: restyle 2026-09-09 mirror to this file's section convention (review round 2) Co-Authored-By: Claude Fable 5.1 --- rules/autonomy.md | 2 +- rules/skill-process.md | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/rules/autonomy.md b/rules/autonomy.md index 5792bed..c98bded 100644 --- a/rules/autonomy.md +++ b/rules/autonomy.md @@ -115,7 +115,7 @@ reached partial / blocked / awaiting-permission state. - Case-based; re-judge per situation; the maintainer's call wins. -## 2.10-c No re-asking the operator about finished projects (2026-09-09) +## 2.11 No re-asking the operator about finished projects (2026-09-09) If a deferred ledger row's release condition is "wait for the operator to confirm," and that confirmation is tied to a project or delivery that has already finished, do not raise it to the operator again. Close the row as not applicable instead. Check this once, based on the project's actual closing record (its outcome note or its calendar end date) rather than memory or a guess. The bot that defers the row writes the note "finished project: " directly on that row. Exception: if the same finished project still has an open follow-up contract, re-engagement, or maintenance window, it is not closed — the release condition should instead point to that open window. (vault docs/rules-full/autonomy.md, 2026-09-09) diff --git a/rules/skill-process.md b/rules/skill-process.md index 3a0c8d0..831a9f4 100644 --- a/rules/skill-process.md +++ b/rules/skill-process.md @@ -42,10 +42,6 @@ an automated experiment loop; delegating to a sub-agent. the failure mode is invisible. See the periodic-review rule for the standing check and for why nested collisions behave differently. -## 1.9 Pre-check before starting a provisionally assigned ledger row (2026-09-09) -Before starting a ledger row that was provisionally assigned or handed over, run the pre-check script once for that owner. For any row it flags as a possible match, open the diff of the matching commit and judge whether the work was actually reflected in code, rules, skills, or config files, or merely quoted in a meeting note, log, or mirror copy. If it was reflected, close the row with a one-line receipt pointing to the exact file and line (or commit hash). If it was only quoted, leave the row's status unchanged and add a note explaining it was a false match. Only rows the script does not flag should be started as new work. The bot starting the row is responsible for writing the receipt or note directly on that row; the script's own exclusion list for quoted sources is the reference to follow, not a copy kept in this document. -(vault docs/rules-full/skill-process.md, 2026-09-09) - ## 2. Design-before-implement (hard gate) - "Let's build X" = present a design and get alignment **before** scaffolding or implementation. Exception: if the user explicitly said "proceed" under a @@ -158,3 +154,7 @@ tool(s) and where the diversity check is recorded. sibling gates (other surfaces of the same defect) first; and never share a waiver key across surfaces whose recoverability differs — the agent who coined that principle violated it themselves three days later. + +## 10. Pre-check before starting a provisionally assigned ledger row (2026-09-09) +Before starting a ledger row that was provisionally assigned or handed over, run the pre-check script once for that owner. For any row it flags as a possible match, open the diff of the matching commit and judge whether the work was actually reflected in code, rules, skills, or config files, or merely quoted in a meeting note, log, or mirror copy. If it was reflected, close the row with a one-line receipt pointing to the exact file and line (or commit hash). If it was only quoted, leave the row's status unchanged and add a note explaining it was a false match. Only rows the script does not flag should be started as new work. The bot starting the row is responsible for writing the receipt or note directly on that row; the script's own exclusion list for quoted sources is the reference to follow, not a copy kept in this document. +(vault docs/rules-full/skill-process.md, 2026-09-09) From f49867fd65c02238966519bce6e42a2e039ea230 Mon Sep 17 00:00:00 2001 From: treylom Date: Wed, 9 Sep 2026 12:58:42 +0900 Subject: [PATCH 3/4] rules: restyle 2026-09-09 mirror to this file's section convention (review round 2) Co-Authored-By: Claude Fable 5.1 --- rules/autonomy.md | 7 ++++++- rules/skill-process.md | 8 +++++++- 2 files changed, 13 insertions(+), 2 deletions(-) diff --git a/rules/autonomy.md b/rules/autonomy.md index c98bded..3a406b0 100644 --- a/rules/autonomy.md +++ b/rules/autonomy.md @@ -116,7 +116,12 @@ reached partial / blocked / awaiting-permission state. ## 2.11 No re-asking the operator about finished projects (2026-09-09) -If a deferred ledger row's release condition is "wait for the operator to confirm," and that confirmation is tied to a project or delivery that has already finished, do not raise it to the operator again. Close the row as not applicable instead. Check this once, based on the project's actual closing record (its outcome note or its calendar end date) rather than memory or a guess. The bot that defers the row writes the note "finished project: " directly on that row. Exception: if the same finished project still has an open follow-up contract, re-engagement, or maintenance window, it is not closed — the release condition should instead point to that open window. + +- If a deferred ledger row's release condition is "wait for the operator to confirm," and that confirmation is tied to a project or delivery that has already finished, do not raise it to the operator again. Close the row as not applicable instead. +- Check this once, based on the project's actual closing record (its outcome note or its calendar end date) rather than memory or a guess. +- Owner: the bot that defers the row writes the note "finished project: " directly on that row. +- Exception: if the same finished project still has an open follow-up contract, re-engagement, or maintenance window, it is not closed — the release condition should instead point to that open window. + (vault docs/rules-full/autonomy.md, 2026-09-09) ## 3. No busywork diff --git a/rules/skill-process.md b/rules/skill-process.md index 831a9f4..de29e08 100644 --- a/rules/skill-process.md +++ b/rules/skill-process.md @@ -156,5 +156,11 @@ tool(s) and where the diversity check is recorded. that principle violated it themselves three days later. ## 10. Pre-check before starting a provisionally assigned ledger row (2026-09-09) -Before starting a ledger row that was provisionally assigned or handed over, run the pre-check script once for that owner. For any row it flags as a possible match, open the diff of the matching commit and judge whether the work was actually reflected in code, rules, skills, or config files, or merely quoted in a meeting note, log, or mirror copy. If it was reflected, close the row with a one-line receipt pointing to the exact file and line (or commit hash). If it was only quoted, leave the row's status unchanged and add a note explaining it was a false match. Only rows the script does not flag should be started as new work. The bot starting the row is responsible for writing the receipt or note directly on that row; the script's own exclusion list for quoted sources is the reference to follow, not a copy kept in this document. + +- Before starting a ledger row that was provisionally assigned or handed over, run the pre-check script once for that owner. +- For any row it flags as a possible match, open the diff of the matching commit and judge whether the work was actually reflected in code, rules, skills, or config files, or merely quoted in a meeting note, log, or mirror copy. +- If it was reflected, close the row with a one-line receipt pointing to the exact file and line (or commit hash). If it was only quoted, leave the row's status unchanged and add a note explaining it was a false match. +- Only rows the script does not flag should be started as new work. +- Owner of this entry: the bot starting the row is responsible for writing the receipt or note directly on that row; the script's own exclusion list for quoted sources is the reference to follow, not a copy kept in this document. + (vault docs/rules-full/skill-process.md, 2026-09-09) From 8a91d1eaefb25674bfb6b73092faeabb12a62ac5 Mon Sep 17 00:00:00 2001 From: treylom Date: Wed, 9 Sep 2026 13:03:42 +0900 Subject: [PATCH 4/4] rules: single blank line before 2.11 (review round 3 nit) Co-Authored-By: Claude Fable 5.1 --- rules/autonomy.md | 1 - 1 file changed, 1 deletion(-) diff --git a/rules/autonomy.md b/rules/autonomy.md index 3a406b0..d60f98d 100644 --- a/rules/autonomy.md +++ b/rules/autonomy.md @@ -114,7 +114,6 @@ reached partial / blocked / awaiting-permission state. separate table. - Case-based; re-judge per situation; the maintainer's call wins. - ## 2.11 No re-asking the operator about finished projects (2026-09-09) - If a deferred ledger row's release condition is "wait for the operator to confirm," and that confirmation is tied to a project or delivery that has already finished, do not raise it to the operator again. Close the row as not applicable instead.