diff options
3 files changed, 36 insertions, 0 deletions
diff --git a/inbox/PROCESSED-2026-07-20-1059-from-.emacs.d-proposal-craig-approved-2026-07-20.org b/inbox/PROCESSED-2026-07-20-1059-from-.emacs.d-proposal-craig-approved-2026-07-20.org new file mode 100644 index 0000000..4934cdf --- /dev/null +++ b/inbox/PROCESSED-2026-07-20-1059-from-.emacs.d-proposal-craig-approved-2026-07-20.org @@ -0,0 +1,19 @@ +#+TITLE: PROPOSAL (Craig-approved 2026-07-20): silent-until-signal pa +#+SOURCE: from .emacs.d +#+DATE: 2026-07-20 10:59:59 -0500 + +PROPOSAL (Craig-approved 2026-07-20): silent-until-signal pattern for in-session monitor loops — apply to auto triage-intake, auto inbox-zero, and sentry. + +Problem: in-session cron/loop monitors surface a visible LLM turn on every fire even when nothing changed, so a long session fills with 'no new items' / 'quiet fire' noise. A background subagent does NOT fix it — it notifies on every completion, including the empty ticks. + +Proposed pattern — split silent detection from LLM judgment: +- A shell-level watcher (systemd user timer, or a backgrounded loop) does detection silently: diff the source (roam inbox, or triage sources) against a seen-list every N minutes, producing ZERO output on an empty check. +- Only a genuinely new item surfaces — the watcher drops a handoff into the project inbox/, and the existing inbox-boundary stop-hook surfaces it at the next natural boundary. The LLM then does the implement-vs-file/route judgment, only when there's something. +- The watcher-owned seen-list replaces the in-anchor 'Dispositioned' list. + +Apply to: +- auto inbox-zero (the roam-inbox monitor) — the case this came from (.emacs.d session, 2026-07-20). +- auto triage-intake — same shape (silent scan, surface only real items). +- sentry — quiet fires should collapse to JUST the check-time, a one-line heartbeat ('sentry checked HH:MM, nothing'), not a full per-pass digest. An all-quiet night becomes a short timestamp list instead of a wall of SKIP/no-op lines; only a fire that actually did or queued something writes a full digest. (Craig's explicit ask.) + +Why rulesets: triage-intake.org, inbox.org, and sentry.org all live in rulesets, and the detection/judgment split is generic. Open questions for the rulesets session: watcher mechanism (systemd timer vs in-session background vs the Monitor tool); where the seen-list lives; passive inbox-drop vs paging. diff --git a/inbox/PROCESSED-2026-07-20-1059-from-.emacs.d-research-is-there-a-google-maps-mcp-or.org b/inbox/PROCESSED-2026-07-20-1059-from-.emacs.d-research-is-there-a-google-maps-mcp-or.org new file mode 100644 index 0000000..20aaae1 --- /dev/null +++ b/inbox/PROCESSED-2026-07-20-1059-from-.emacs.d-research-is-there-a-google-maps-mcp-or.org @@ -0,0 +1,5 @@ +#+TITLE: Research: is there a Google Maps MCP (or similar) that can r +#+SOURCE: from .emacs.d +#+DATE: 2026-07-20 10:59:58 -0500 + +Research: is there a Google Maps MCP (or similar) that can report the locations of devices that are sharing their location with you? If none exists, research how hard it would be to build one. (Captured in the shared roam inbox, routed here since it's rulesets-owned research.) @@ -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. |