rules: pre-check gate (1.9) + finished-project no-re-ask (2.10-c)

rules/autonomy.md

@@ -114,6 +114,15 @@ 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.
+- 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: <name>" 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.

rules/skill-process.md

@@ -154,3 +154,13 @@ 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.
+- 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)