---
type: atlas-artifact
artifact_type: plan
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, plan]
---

# Artifact Generation System Implementation Plan

Parent project: [[Atlas Capability Upgrade Program]]
Source: kanban:t_6f875045
Supersedes: N/A

## Goal

Create a reusable Obsidian template library so important Atlas outputs become durable, linked, reviewable artifacts.

## Non-goals

- Automating template selection inside Hermes.
- Changing Hermes runtime configuration.
- Moving existing project notes into the new folder layout.

## Current state / context

- Workstream 8 requires templates for plans, decision logs, runbooks, diagrams, test reports, status reports, and postmortems.
- Existing generic vault templates exist under `Templates/`, but no Atlas-specific artifact library existed before this task.
- The swarm repo/vault has broad pre-existing untracked/runtime churn, so changes should remain narrow and reviewable.

## Architecture approach

Create a canonical `Templates/Atlas Artifacts/` folder with one Markdown template per artifact type plus a README and reviewer checklist. Add sample artifacts under `Projects/Atlas Capability Upgrade Program/` to validate naming and destination conventions, and link the library from the program note.

## Files/tools to touch

- Create: `Templates/Atlas Artifacts/*.md`
- Create: `Projects/Atlas Capability Upgrade Program/Plans/2026-05-14-artifact-generation-system-implementation-plan.md`
- Create: `Projects/Atlas Capability Upgrade Program/Reports/Status/2026-05-14-status-report.md`
- Modify: `Projects/Atlas Capability Upgrade Program.md`

## Task breakdown

### Task 1: Create template library folder and README

Objective: make the canonical destination and naming policy discoverable.

Verification:

```bash
find Templates/Atlas\ Artifacts -maxdepth 1 -type f | sort
```

Expected: README plus eight template/checklist files.

### Task 2: Create artifact templates

Objective: provide frontmatter, required sections, and review checklists for all seven artifact types.

Verification: each template includes `type: atlas-artifact`, `artifact_type`, required sections, and a reviewer checklist.

### Task 3: Create sample artifacts

Objective: prove the naming and destination conventions with one plan and one status report.

Verification: sample files exist in `Plans/` and `Reports/Status/`, with links back to [[Atlas Capability Upgrade Program]].

### Task 4: Link from the program note

Objective: make the artifact library discoverable from the workstream source note.

Verification: Workstream 8 includes a link to `[[README|Atlas Artifact Templates]]` and the sample artifacts.

## Tests and verification

- [x] All template files exist under `Templates/Atlas Artifacts/`.
- [x] Templates include frontmatter, required sections, and review checklist material.
- [x] Sample implementation plan and status report were created.
- [x] Program note links to the template library.
- [x] Manual no-secrets check performed on generated Markdown.

## Rollback plan

Remove `Templates/Atlas Artifacts/`, remove `Projects/Atlas Capability Upgrade Program/`, and revert the added Workstream 8 lines in `Projects/Atlas Capability Upgrade Program.md`.

## Risks and mitigations

- Risk: templates become too heavy. Mitigation: sections allow concise content and `N/A` with reason.
- Risk: artifacts are saved but not findable. Mitigation: require project links and Kanban metadata paths.
- Risk: secrets leak into runbooks/test reports. Mitigation: explicit no-secrets checklist in every review.

## Next action

- Owner: reviewer profile.
- Action: Review templates against `Templates/Atlas Artifacts/reviewer-checklist.md` before treating the library as canonical.

## Plan-specific review checklist

- [x] Tasks are ordered and bite-sized.
- [x] File paths and commands are exact.
- [x] Tests/verification prove acceptance criteria.
- [x] Rollback is clear.

## Universal reviewer checklist

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