diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/design/2026-06-15-auto-triage-intake-spec.org | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/design/2026-06-15-auto-triage-intake-spec.org b/docs/design/2026-06-15-auto-triage-intake-spec.org index 1c7cd94..b41c99c 100644 --- a/docs/design/2026-06-15-auto-triage-intake-spec.org +++ b/docs/design/2026-06-15-auto-triage-intake-spec.org @@ -41,3 +41,7 @@ The standard engine is one-shot and mutating, which is right for an at-the-desk - The interval loop is the delivery mechanism (CronCreate session-only, or a durable schedule); the mode is the behavior. They compose. - "Responses awaiting acknowledgment" tracking needs a small piece of state. In a session it can live in the session-context log; if the engine wants it durable across sessions, a tiny =.ai/triage-unacked.org= (or similar) is the natural home — flagged as a design choice for the rulesets side to decide. - Deltas-only reporting (the 2026-06-11 ruling) and loud scan-failure surfacing both still apply inside each sweep. + +* Addendum (work, 2026-06-15 17:16) + +Add a third end-of-sweep output line: the current date/time/timezone, on its own final line, via =date "+%A %Y-%m-%d %H:%M:%S %Z (%z)"=. Reason: on an away day with frequent unattended sweeps, the per-sweep stamp shows how fresh each summary is at a glance. Sweep output sections become: (a) Deltas, (b) Responses awaiting acknowledgment, (c) the timestamp. Implemented 2026-06-15; the stamp prints on quiet sweeps too, as proof the loop ran. |