From 067ed55b6bf6276f9e5203cc521a2785716d0ece Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Mon, 20 Jul 2026 00:21:41 -0500 Subject: chore(sentry): inbox zero — file 3 sentry design considerations from live trial MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit .emacs.d routed three sentry-workflow design ideas from its own hand-run trial (codebase-gated bug/enhancement logging, a system-health pass, a sibling-machine freshness pass). Filed as a [#C] backlog task rather than applied — they're design input for the sentry Living Document refinements and two of them hinge on an unresolved cross-driver coordination question. Replied to the sender. --- ...-0009-from-.emacs.d-three-sentry-design-considerations.org | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 inbox/PROCESSED-2026-07-20-0009-from-.emacs.d-three-sentry-design-considerations.org (limited to 'inbox') 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. -- cgit v1.2.3