---
type: atlas-artifact-library
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, templates]
---

# Atlas Artifact Templates

Canonical templates for durable Atlas outputs. Use these when chat, Kanban, or session work should become durable project state instead of staying only in a transcript.

## Templates

- [[implementation-plan]] — implementation and migration plans.
- [[decision-log]] — architecture or operations decisions.
- [[runbook]] — repeatable operational procedures.
- [[diagram]] — Mermaid/Excalidraw/SVG/source-backed diagrams.
- [[test-report]] — test, benchmark, evaluation, and smoke-check reports.
- [[status-report]] — weekly/monthly/milestone status updates.
- [[postmortem]] — incident/failure writeups.
- [[agent-audit-event]] — short audit notes for agent actions: model, provider, tools/MCP, data touched, outcome, cost, and latency.
- [[reviewer-checklist]] — common review checklist for all artifacts.

## Destination policy

- 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/`

## Naming conventions

Use lowercase kebab-case filenames with a date prefix where chronology matters.

- Plans: `YYYY-MM-DD-<feature>-implementation-plan.md`
- Decisions: `YYYY-MM-DD-<decision-topic>.md`
- Runbooks: `<system>-<operation>-runbook.md`
- Diagrams: `<system>-<view>-diagram.md`
- Test reports: `YYYY-MM-DD-<scope>-test-report.md`
- Status reports: `YYYY-MM-DD-status-report.md`
- Postmortems: `YYYY-MM-DD-<incident-name>-postmortem.md`
- Agent audit events: `YYYY-MM-DD-<agent-or-system>-<event-topic>-audit.md`

## Promotion workflow

1. Decide whether a chat/session/Kanban result has durable value.
2. Pick the closest template from this folder.
3. Draft in the worker workspace if useful; save the final artifact in the project-local destination folder.
4. Link the artifact from the parent project note and from any relevant runbook/decision/status report.
5. Mention the artifact path in Kanban `metadata.created_artifacts` or in a review-required comment.
6. Run [[reviewer-checklist]] before marking the artifact accepted.

## Required links in every artifact

- Parent project note.
- Source Kanban task, session, PR, issue, or incident.
- Superseded artifact when replacing something.
- Owner and next action.
