---
type: atlas-artifact
artifact_type: diagram
project: "{{project}}"
status: draft
owner: "{{owner}}"
created: {{date}}
updated: {{date}}
source: "{{source}}"
reviewer: "{{reviewer|TBD}}"
tags: [atlas, artifact, diagram]
---
# Diagram: {{title}}

Parent project: [[{{project}}]]
Source: {{source}}

## Purpose and audience

What this diagram explains and who it is for.

## Source format

Mermaid | Excalidraw | SVG | other: ...

## Source file path

`path/to/source-diagram`

## Rendered/exported path

`path/to/rendered-output` or N/A.

## Diagram source

```mermaid
flowchart TD
    A[Source] --> B[Process]
    B --> C[Artifact]
```

## Legend

- Shape/color/edge meanings.

## Assumptions / omitted details

- Assumption: ...
- Omitted: ... because ...

## Next action

- Owner: ...
- Action: ...

## Diagram-specific review checklist

- [ ] Source is text/diffable when practical.
- [ ] Audience and purpose are clear.
- [ ] Legend explains non-obvious symbols.
- [ ] Omissions and assumptions are documented.

## Universal reviewer checklist

Before accepting this artifact, verify:

- [ ] Clear owner, status, date, source, and next action.
- [ ] Saved in the correct durable destination and named using the convention.
- [ ] Links back to the relevant project note and source task/issue/PR/session/incident.
- [ ] Claims are backed by evidence links, command output, or labeled assumptions.
- [ ] Risks, rollback, recovery, or revisit triggers are documented where relevant.
- [ ] No secrets, tokens, raw PII, private keys, or unredacted credentials are included.
- [ ] A new specialist can understand the artifact without rereading the whole chat.
