Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0001

Audit what actually plans work in this repository

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
M000
Milestone status
DONE
Wave
0
Waiting on
none
Holds back
I0002
Behind it in all
14
Evidence
1 of 1

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0001

majordomus plan verify I0001

majordomus plan done I0001

What it is

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.
Now
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.
Wanted
The current-state map exists, backed by commands anyone can rerun, and the schema work that follows cites it.
Done when
unknown: the record declares no `completion`
Risk
Low. Read-only.

Acceptance

  • 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 allgh api repos/korczis/prismatic-majordomus/milestones
Evidence required
inventory
Evidence present
inventory

Scope

Touches
docs
Not
Any change to behaviour
Depends on
none
Priority
p0
Profile
deep-work
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-04
Updated
2026-09-04T02:54:02Z
Started
2026-09-04T02:54:00Z
Verified
2026-09-04T02:54:01Z
Completed
2026-09-04T02:54:02Z

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.