docs(todo): file the silent-until-signal proposal and a location-MCP research task

Two .emacs.d handoffs. The silent-until-signal monitor pattern (Craig-approved) files as a [#B] spec candidate — it's a cross-workflow shared-asset change across triage-intake, inbox, and sentry, and the sentry live trial just demonstrated the noise problem it solves. The device-location MCP question files as a [#D] research task.

1 files changed, 12 insertions, 0 deletions

diff --git a/todo.org b/todo.org
index 5d1d7a9..4459dbf 100644
--- a/todo.org
+++ b/todo.org
@@ -183,6 +183,18 @@ From the sentry live trial (2026-07-20): triage-intake self-activates in every p
 
 Awaiting Craig's deep read of the spec (DRAFT → READY gate). Two decisions still open in the spec (declaration format details, whether interactive adopts the same gate). On READY, spec-response decomposes the 5 phases into build tasks. Supersedes Fire 1's triage-probe approval-queue item, which was the narrower probe-only framing.
 
+** TODO [#B] Silent-until-signal for in-session monitor loops :feature:spec:
+Craig-approved proposal from .emacs.d (2026-07-20). In-session cron/loop monitors surface a visible LLM turn on every fire even when nothing changed, filling a long session with "quiet fire" / "no new items" noise. The rulesets sentry live trial demonstrated it directly — fires 3-8 were walls of no-op lines.
+
+Pattern: split silent shell-level detection from LLM judgment. A watcher (systemd user timer, backgrounded loop, or the Monitor tool) diffs the source against a seen-list every N minutes with zero output on an empty check; only a genuinely new item surfaces (drops a handoff into inbox/, the inbox-boundary stop-hook surfaces it at the next boundary). The watcher-owned seen-list replaces the in-anchor Dispositioned list.
+
+Apply to: auto inbox-zero (roam-inbox monitor — the originating case), auto triage-intake (same shape), and sentry (a quiet fire collapses to a one-line heartbeat — "sentry checked HH:MM, nothing" — instead of a full per-pass digest; only a fire that did or queued something writes a full digest — Craig's explicit ask).
+
+Cross-workflow shared-asset change (triage-intake.org, inbox.org, sentry.org all in rulesets), warrants a spec like the triage-source-activation one. Open questions: watcher mechanism (systemd timer vs in-session background vs Monitor tool), where the seen-list lives, passive inbox-drop vs paging. Overlaps the sentry cluster ([[file:todo.org::*Sentry vNext passes][Sentry vNext passes]], [[file:todo.org::*Triage source activation][Triage source activation]]).
+
+** TODO [#D] Research: MCP for device locations shared with you :feature:
+From .emacs.d (2026-07-20, rulesets-owned research). Is there a Google Maps MCP (or similar) that reports the locations of devices sharing their location with you? If none exists, research how hard it would be to build one. (Google's location-sharing has no official public API; likely needs investigation of unofficial routes or a different provider.)
+
 ** TODO [#C] Sentry vNext passes — from live-trial design input :feature:spec:
 Three considerations captured by .emacs.d's own hand-run sentry trial (routed via the shared roam inbox, 2026-07-20), for folding into the sentry workflow. Design input, needs deliberation — not applied to the shared workflow unattended.