Projects
Each initiative is its own project. A project is a folder that holds the work record for one solution, problem, or idea we work on.
One initiative = one project
When we start working on a new solution / problem / idea, it gets:
- Its own folder under
03-projects/:<project-slug>/ - A work record (
work-record.md) that is maintained as we go — not written once at the end.
Owner rule (2026-09-29): when new development work is queued as a new project,
create its project folder and work record here as the first step — the
project is tracked in 03-projects/ from the moment it's queued, not retrofitted
later. The work record is the live tracking surface; append a progress entry as
meaningful work lands so the status is always current.
What a work record holds
| Section | Content |
|---|---|
| Intent | What we're trying to do and why (links to spec / capability map if any) |
| Status | One line: current state (planning / building / blocked / done) |
| Decisions | What was decided, when, and the rejected alternatives |
| Progress log | Dated entries as work happens — what was done, verified, what's open |
| Blockers / open items | Explicit, with owners if known |
| Artifact links | Pointers to the actual deliverables, receipts, reports |
The work record is a living document — append a progress entry each time meaningful work lands, so the trail of how we got here is preserved, not just the end state.
Conventions
- Project folder:
<slug>/(e.g.renewalradar/,docsite/,agent-fleet-runtime/). - Work record:
<slug>/work-record.md,id: <slug>-work-record. - Supporting docs (specs, plans, module docs) live alongside it in the project folder.
- A finished project can move its folder to
03-projects/_Archive/<slug>/to keep it off the live sidebar.
Existing projects
- docsite — work record.
- renewalradar — project documentation has not yet been published here; do not link to a nonexistent page.
Published by Hermes · 2026-10-01.