[EPIC] Proactive day-2 operations: the first end-to-end story #1977
Notifications
Due Date
No due date set.
Depends on
#1989 Hard rules and change-request rules
sam/archie
#1992 Time triggers: schedules and deadlines
sam/archie
#1994 Unmatched events are kept and grouped
sam/archie
#1996 Decision trail per run
sam/archie
#1998 Run Archie off the hosts it manages
sam/archie
#2004 Earning and losing autonomy
sam/archie
Reference: sam/archie#1977
Reference in new issue
Block a user
Archie hears disk-pressure alerts on a lab host, works out why, and earns the right to clean up on its own: it starts by asking, gains autonomy after consistent approvals, loses it on a denial, uses ServiceNow change requests where policy requires them, and proposes a root-cause fix once the problem recurs. It exercises the whole loop (Hears, Understands, Decides, Defines, Does, Delivers) and the platform (Governs, Reports, Assesses, Manages risk, Invokes policy), with no repository involved.
The spec, with the decision trees, the guard verdicts and the full requirement list, is SPEC.md in the private sam/archie-product repository. Requirement numbers (R1 and so on) refer to it.
The story
Done when
Everything not on this story's path is deferred until it passes.
Slice 1 (an alert is investigated) passes its done-when on staging: the 2.3 spike's injection and kill-mid-run checks.
487736222with a reproducing test.Also landed in this slice: credentials sealed with age and secret engines (sops on the sops library); the host connector's read-only lookups with pinned host keys, root helpers behind a narrow sudo rule, and per-host path roots; MCP servers as accepted packages with prometheus-mcp (#2005); the decision trail API, the composer, and the binary's own dashboard entry (#1996 and #1984 in part).
Next: slice 2, starting with the judgement module (see the 2026-11-16 review notes on #1986).
The epic's children were only the day-2 slices, so today's archie was mostly unaccounted for. Five children added for what must move into the one binary rather than disappear when the six services stop:
Not yet filed and not decided: exposing Archie's tools to external agents over MCP (#2012 deletes the old path), dashboard parity for the old pages (workflow editor, captures, alerts, services, logs, summary, setup, config), skills and curators, and the remote runner over HTTPS (spec 2.5). Slice 6 should not land until the children above are done.
Spec continuation, 2026-11-16. ARCHITECTURE.md: 2.1 now says the runner is required for real estates (no inbound connection, credentials on the runner's side) and records that only in-process extensions exist today; 2.9 keeps the canvas as the workflow viewer and editor through drafts and carries a parity table for every old page; 2.10 is new, audit and evidence as a compliance requirement; section 4 gains slice 7, today's archie moving in, so slice 6 does not stop the old services before their capabilities land. SPEC.md gains R39 (runner and task runs), R40 (system health), R41 (chat), R42 (audit log), R43 (identity and access) and states that Archie's own MCP server is a later day-2 stage. The spec-building session is exported to archie-product/transcripts/. New children: #2022 runner, #2023 dashboard parity, #2017-#2021 from earlier. Still to decide: whether alerts has its own page, whether a home page exists before there is more than one binary. Slice 7's issues are #2017-#2023.
Control plane: the maintainer restated it as a day-1 show-stopping requirement, not a re-implementation choice. ARCHITECTURE.md 2.9 gains 'Every setting has a page (R45)' and SPEC.md gains R45 plus principle 9, 'The dashboard is the control plane'. The judge is a control now, along with hard rules, change-request rules, guards, policy text and action classes. #2026 inventories the gap in the new binary (agent model, connectors, guards and their judge, secret engines, MCP servers, credentials, sources, key fields, triggers, events, bootstrap display and admin token rotation) and an agent is implementing it.