From f058b4c15a67ce3b54e306e8b4778aa3cb540c7c Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Fri, 12 Jun 2026 19:15:22 -0500 Subject: docs(rules): codify propagating synced-file edits back to rulesets A downstream edit to a rulesets-owned synced file (workflows, scripts, rules, protocols.org) is a stopgap the next template sync reverts. cross-project.md now documents the three-step propagation (edit locally, inbox-send the file to rulesets, include an intro note with the why and any companions to reconcile) so agents propagate a synced-file edit without being told. From the .emacs.d handoff 2026-06-12. --- .ai/notes.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '.ai/notes.org') diff --git a/.ai/notes.org b/.ai/notes.org index b9b2ed0..4790af9 100644 --- a/.ai/notes.org +++ b/.ai/notes.org @@ -79,6 +79,6 @@ Format: Markers maintained by workflows to record when they last ran. Read by other workflows that gate their behavior on freshness. :LAST_AUDIT: 2026-05-28 -:LAST_INBOX_PROCESS: 2026-06-12 (overnight batch: memory sweeps x3, lint-org mu4e fix, page-signal VERIFY) +:LAST_INBOX_PROCESS: 2026-06-12 (evening: spec-create decisions-as-TODO convention from .emacs.d, applied + companions reconciled) Format: one =:MARKER: YYYY-MM-DD= line per workflow. Workflows overwrite their own marker on completion. -- cgit v1.2.3