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

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

## Reporting period

YYYY-MM-DD to YYYY-MM-DD.

## Overall status

Green | Yellow | Red

Reason: one sentence.

## Completed work

- Completed: ... Link: ...

## Current blockers

- Blocker: ... Owner: ... Needed by: ...

## Risks

- Risk: ... Impact: ... Mitigation: ...

## Next actions

- [ ] Owner: ... Action: ... Due: ...

## Decisions needed

- Decision: ... Owner: ... Deadline: ...

## Links to artifacts created this period

- [[artifact-name]] — purpose.

## Status-report-specific review checklist

- [ ] Status color is justified.
- [ ] Blockers, risks, and next actions have owners.
- [ ] Created artifacts are linked.
- [ ] Decisions needed are explicit.

## 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.
