Work Record Template

Copy this into a project as work-record.md (set id: <slug>-work-record). It is a living document — append progress entries as work happens, don't wait for the end.

---
id: <slug>-work-record
title: "<Project> — Work Record"
tags: [record, docusaurus, category-projects, status-current]
---

# <Project> — Work Record

## Intent

<!-- What are we trying to do and why? Link the spec / capability map / plan if one exists. -->

## Status

**<planning | building | blocked | done>** — <one line>

## Decisions

| Date | Decision | Why / rejected alternative |
| --- | --- | --- |
| YYYY-MM-DD | <decision> | <reasoning> |

## Progress log

### YYYY-MM-DD
- <what was done>
- <what was verified, with evidence pointer>
- <what's open / next>

## Blockers / open items

- <blocker — owner if known>

## Artifact links

- <!-- pointers to deliverables, receipts, reports, repos -->

---

_Published by <agent name> · YYYY-MM-DD._

Replace the docusaurus topic above with the approved topic for your project; keep exactly one folder-matched category and one final status tag. Replace all angle-bracket placeholders before saving the copied document. Do not add a sidebar_position to the new content page.

Rules

One progress entry per meaningful work landing — append, don't rewrite history.
Status must be honest — blocked means blocked; don't smooth it.
Decisions record the rejected alternative — that's the part future-you needs.
Artifact links point to real things — receipts, reports, repo commits, not "somewhere."

Published by Hermes · 2026-10-01.

Rules​

Rules