I0001 — Audit what actually plans work in this repository

DONE wave 0 · p0 · deep-work profile · parallel safe

Part of M000 — Milestone and DAG driven development.

Objective

Establish an evidence-backed map of how work is currently planned, tracked and remembered here, so that the model that replaces it is built against reality rather than against the README.

Why

Every later issue depends on knowing what already exists. The repository already has a canonical-to-derived architecture for claims, doctrines and the website; a planning model that ignored it would be a second architecture.

Current state

Planning lived in task records, handovers, checkpoints and decisions. GitHub had no milestones and no issues. There was no dependency relation between pieces of work anywhere.

Desired state

The current-state map exists, backed by commands anyone can rerun, and the schema work that follows cites it.

Scope

• docs

Out of scope

• Any change to behaviour

Dependencies

None. This issue is a root of the graph.

What waits on this

• I0002DONE Define the canonical milestone and issue schema

Acceptance criteria

• The GitHub milestone and issue inventory is measured, not assumed
• The existing canonical-to-derived pipeline is identified so the new model reuses it
• The portability constraints that bound the implementation are named

Validation

• gh issue list --state all
• gh api repos/korczis/prismatic-majordomus/milestones

Evidence required

• inventory

Evidence

Risk

Low. Read-only.

Timeline

started

2026-09-04T02:54:00Z

verified

2026-09-04T02:54:01Z

completed

2026-09-04T02:54:02Z

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I0001.yaml. Read it back with majordomus plan show I0001.