diff options
| -rw-r--r-- | inbox/PROCESSED-2026-07-20-0009-from-.emacs.d-three-sentry-design-considerations.org | 11 | ||||
| -rw-r--r-- | todo.org | 9 |
2 files changed, 20 insertions, 0 deletions
diff --git a/inbox/PROCESSED-2026-07-20-0009-from-.emacs.d-three-sentry-design-considerations.org b/inbox/PROCESSED-2026-07-20-0009-from-.emacs.d-three-sentry-design-considerations.org new file mode 100644 index 0000000..9a545f8 --- /dev/null +++ b/inbox/PROCESSED-2026-07-20-0009-from-.emacs.d-three-sentry-design-considerations.org @@ -0,0 +1,11 @@ +#+TITLE: Three sentry-design considerations captured in the shared ro +#+SOURCE: from .emacs.d +#+DATE: 2026-07-20 00:09:58 -0500 + +Three sentry-design considerations captured in the shared roam inbox (rulesets-owned), routed here during a sentry inbox-zero pass from .emacs.d: + +1. Bug/enhancement logging during sentry: only if the project owns a codebase, file bugs by default and enhancements only if asked; review-and-accept/decline them during the morning sentry reconciliation. (Note: .emacs.d ran exactly this by hand tonight — findings logged to its session anchor for reconcile — so this is live-tested design input worth folding into the sentry workflow.) +2. System-health during sentry: decide what parts are safe to check, and how to keep the two daily drivers (ratio/velox) from running it simultaneously (lock/coordination question). +3. Keeping the sibling machine (velox/ratio) up-to-date during sentry. + +These are rulesets backlog items about the sentry workflow itself; process per rulesets inbox conventions. @@ -181,6 +181,15 @@ session needs its own contract (mutation rights, async surfacing, dedup state across runs) — same open questions inbox.org logs for unattended auto inbox zero. Take up only if the interactive shape proves too narrow. +** 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. + +1. Bug/enhancement logging pass. Only where the project owns a codebase: file bugs by default, enhancements only if asked; review-and-accept/decline during the morning reconciliation. Live-tested — .emacs.d ran exactly this by hand and logged findings to its session anchor. Strongest candidate of the three; overlaps the deferred KB lesson-detection pass ([[file:todo.org::*KB lesson-detection heuristic][KB lesson-detection heuristic]]). +2. System-health pass. Decide which checks are safe unattended, and how to keep ratio and velox from running it simultaneously (a cross-driver lock/coordination question — agent-lock is host-local tmpfs, so it doesn't coordinate across machines). +3. Sibling-machine freshness pass. Keep the other daily driver (velox/ratio) up to date during sentry (see daily-drivers.md; same cross-driver coordination question as #2). + +Take up with the sentry Living Document refinements once the trial has quiet nights behind it. Related: the sentry /schedule variant above, and Fire 1's triage-probe finding in the approval queue. + ** TODO [#B] Extend ui-prototyping rule with build-to-prototype :feature: :PROPERTIES: :CREATED: [2026-07-11 Sat] |