---
type: atlas-artifact-template
artifact_type: reviewer-checklist
project: "Atlas Capability Upgrade Program"
status: accepted
owner: "writer profile / Atlas docs owner"
created: 2026-05-14
updated: 2026-05-14
source: "kanban:t_6f875045"
reviewer: "reviewer profile"
tags: [atlas, artifact, checklist]
---

# Atlas Artifact Reviewer Checklist

Use this checklist before accepting any Atlas artifact as durable project state.

## Destination and naming

- [ ] The artifact is in the correct project-local folder:
  - Plans: `Projects/<Project Name>/Plans/`
  - Decisions: `Projects/<Project Name>/Decisions/`
  - Runbooks: `Projects/<Project Name>/Runbooks/`
  - Diagrams: `Projects/<Project Name>/Diagrams/`
  - Test reports: `Projects/<Project Name>/Reports/Test Reports/`
  - Status reports: `Projects/<Project Name>/Reports/Status/`
  - Postmortems: `Projects/<Project Name>/Reports/Postmortems/`
- [ ] Filename uses lowercase kebab-case and a date prefix where chronology matters.
- [ ] Template source is one of `Templates/Atlas Artifacts/*.md`.

## Frontmatter and links

- [ ] Frontmatter includes `type`, `artifact_type`, `project`, `status`, `owner`, `created`, `updated`, `source`, `reviewer`, and `tags`.
- [ ] The artifact links to the parent project note.
- [ ] The artifact links to source Kanban task, issue, PR, session, or incident when available.
- [ ] Superseded/replaced artifacts are linked when relevant.

## Content quality

- [ ] Purpose, audience, owner, status, and next action are clear.
- [ ] Claims are backed by command output, source links, or explicitly labeled assumptions.
- [ ] Risks, rollback, recovery, or revisit triggers are documented where relevant.
- [ ] The artifact is concise enough to use but complete enough to orient a new specialist.

## Safety and durability

- [ ] No secrets, tokens, private keys, raw PII, or unredacted credentials are included.
- [ ] Runtime churn/log dumps are summarized or linked safely rather than pasted wholesale.
- [ ] Any unsafe or destructive action is labeled with approval requirements.
- [ ] The Kanban handoff or project note includes the artifact path if this came from a worker task.

## Artifact-specific checks

- Plans: tasks are bite-sized, exact paths/commands are included, tests and rollback are clear.
- Decisions: options/tradeoffs are represented, decision is explicit, revisit trigger exists.
- Runbooks: prerequisites, safety tier, verification, rollback/recovery, and last-tested date exist.
- Diagrams: source format/path, legend, assumptions, and omitted details exist.
- Test reports: scope, environment, commands, results, evidence, and follow-ups exist.
- Status reports: color/status is justified; blockers, risks, decisions, and next actions have owners.
- Postmortems: timeline, root cause, corrective actions, follow-up verification, and blamelessness note exist.
