# RFC-001 Pilot — Implementation Checklist

## 1) Activation
- [x] Mark RFC-001 as **Accepted (Pilot)**.
- [x] Set watchdog mode = **Advisory**.
- [ ] Record pilot start timestamp in maintainer log.
- [ ] Schedule 2-week review checkpoint.

## 2) Canonical Lane Registry
- [x] Create explicit canonical lane map in ops-maintainer docs/state.
- [x] Add drift detector checks:
  - [x] multiple active canonical candidates per role
  - [x] non-canonical control-plane writes (detectable key-pattern anomalies)
  - [x] cron targeting unauthorized lane

## 3) Threshold Monitor (Hybrid)
- [ ] Implement absolute thresholds by lane.
- [ ] Implement percentage thresholds (35/50/65/75%).
- [ ] Trigger on earliest breached threshold.
- [ ] Add per-lane cooldown (30–60 min) to prevent thrash.

## 4) Summarization + Rollover Hooks (Advisory)
- [ ] Emit summarize recommendation when summarize threshold crossed.
- [ ] Emit rollover recommendation at rollover-recommended threshold.
- [ ] Emit action-required alert at rollover-required threshold.
- [ ] Include required summary schema in every advisory payload:
  - objective
  - completed work
  - unresolved issues
  - decisions
  - constraints
  - next actions

## 5) Pruning Hygiene (Low-Risk Only)
- [ ] Cron stale-session prune policy (7–14 day retention target).
- [ ] Worker stale-session recommendation (14–30 day target).
- [ ] Maintainer stale-session rotation recommendation (30 day target).
- [ ] Main/Telegram archive-first policy (no aggressive auto-prune).

## 6) Lifecycle Audit Log Format
- [x] Schema + JSONL writer utility implemented (`scripts/rfc001/lifecycle_audit.py`).
For every lifecycle action/recommendation, log:
- timestamp
- lane + session key
- action type (advisory/rollover/prune/cleanup)
- trigger reason
- old/new session key (if applicable)
- summary reference path
- actor (watchdog/manual)

## 7) Alert Routing
- [x] Route all advisory alerts to `agent:ops-maintainer:main` (via ops-maintainer advisory artifacts).
- [ ] Route warning/action-required alerts to Braden when persistent.
- [x] Ensure no duplicate alert storms (dedupe window).

## 8) Pilot Review (Day 14)
Review and decide:
- [ ] keep advisory mode
- [ ] enable low-risk enforcement actions
- [ ] revise thresholds per lane
- [ ] approve full RFC ratification

## 9) Exit Criteria for Pilot
- [ ] No reliability regressions.
- [ ] Canonical lane drift reduced.
- [ ] Session growth controlled in cron/worker lanes.
- [ ] Actionable findings documented for RFC v1.0 final.