# Operator Onboarding Checklist

Owner: PM
Status: not started
Date: YYYY-MM-DD

## 1. Project Framing

- project name:
- objective:
- key constraints:
- environments in scope:

## 2. Roles and Boundaries

- PM assigned: pending Operator confirmation
- AM assigned: pending Operator confirmation
- CM assigned: pending Operator confirmation
- SM assigned: pending Operator confirmation
- OM-Test assigned: pending Operator confirmation
- OM assigned: pending Operator confirmation
- PM handoff mode: `commit-only` / `commit-and-push`
- AM handoff mode: `commit-only` / `commit-and-push`
- CM handoff mode: `commit-only` / `commit-and-push`
- SM handoff mode: `commit-only` / `commit-and-push`
- OM-Test handoff mode: `commit-only` / `commit-and-push`
- OM handoff mode: `commit-only` / `commit-and-push`
- any role exceptions approved by Operator: none currently

## 3. Required Artifacts

- `MEMORY.md` reviewed and accepted by Operator
- `CHANGELOG.md` initialized and owner set
- `ROADMAP.md` initialized and owner set
- `TODO.md` initialized and owner set
- mailbox coordination workflow reviewed (`docs/project/mailbox-collaboration-model.md`, `minions/mail/README.md`)
- vendored template snapshot initialized (recommended `.minions-template/`; exclude `.git/` and `do-not-export` files)
- initial downstream export completed using `docs/downstream-onboarding-playbook.md`
- downstream template-upgrade owner confirmed (default `PM`)
- `minion-version.md` reviewed and downstream version format confirmed

## 4. Escalation Policy (Operator Optional)

Enabled by Operator: yes/no

If enabled:

- production blocker response expectation:
- non-critical blocker response expectation:
- incident communication expectation:

## 5. Guardrail Confirmation

- base guardrails accepted
- project-specific guardrails added:
- secret and personal-data handling confirmed
- machine-specific metadata hygiene confirmed (example: .DS_Store stays untracked)
- rollback posture expectation confirmed

## 6. Sign-Off

Operator decision: pending

Notes: