From 58dbfc8313a52aa630e9f9d250f4bced44c9a557 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Padez?= Date: Tue, 25 Aug 2026 04:38:38 +0000 Subject: [PATCH] todo: transcripts land in the central inbox, not the commander's own directory Co-Authored-By: Claude Fable 5 --- .../watch-a-directory-and-attach-actions-to-what.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/todo/file-watchers/watch-a-directory-and-attach-actions-to-what.md b/todo/file-watchers/watch-a-directory-and-attach-actions-to-what.md index e24bcf94..c97485ea 100644 --- a/todo/file-watchers/watch-a-directory-and-attach-actions-to-what.md +++ b/todo/file-watchers/watch-a-directory-and-attach-actions-to-what.md @@ -52,3 +52,10 @@ language detection, and got the owner's yes to transcribe each new memo as it la audio-arrival half of this item is live in another agent's hands — check what that session built before writing anything here. Stage 2 — an agent reading the transcripts and filing what they say — is still unbuilt, and is the dispatcher item under `mobile-apps/`. + +**Correction the owner made before arming, 2026-08-25:** the transcripts go to a CENTRAL place, not +into the transcribing commander's own directory. The first draft wrote them to `commanders//transcripts/`, +which is text only that commander can find — and stage 2 reads the shared inbox, not another agent's +private state. The watcher's own good ideas stand: a file counts as arrived when unchanged between two +looks (never grab a half-synced file), and done-tracking is keyed on content so a renamed memo is not +transcribed twice.