Skip to main content

Project

A bounded initiative with a stakeholder, a scope, and deliverables: the container the rest of the work concepts hang from. A project is opened deliberately — its record is the first step when it is queued — and it closes when its outcomes are delivered, not when its chat goes quiet.

Estate surface​

Each project carries a living work record under docs/03-projects/<slug>/work-record.md in the docsite, a charter, a repository, and (for development work) an in-repo board. Six projects stand on record: agent-fleet-runtime, workbench, inbox-triage, docsite, cmsmakers, and the SEO agent.

Relations​

  • A project is documented by its work record — the living narrative of its intent, status, and decisions.
  • A project is governed by its charter — the scope, constraints, and acceptance it is judged against.
  • A project has board board — the queue surface its work is claimed and tracked on.
  • A project is stored in a repository — its code, board, and artifacts live under version control.

Notes​

Phase 1 records the concept and its relations, not the roster of projects: the named projects are instance data, held by their work records.