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

I0003

Implement the model loader and the status derivation engine

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
2
Waiting on
none
Holds back
I0004
Behind it in all
12
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 I0003

majordomus plan verify I0003

majordomus plan done I0003

What it is

Objective
Load every canonical file into one normalised model and derive issue and milestone status from recorded facts, in exactly one implementation that every surface calls.
Why
Four surfaces need to know what is READY. Four implementations of READY is four answers. One engine is the whole architecture.
Now
Nothing read the canonical files.
Wanted
lib/project.sh loads the files, lib/project.awk derives the model, and the CLI, the site generator and the GitHub adapter all read that model.
Done when
unknown: the record declares no `completion`
Risk
bash 3.2 has no associative arrays; the graph work is done in awk, which does.

Acceptance

  • Issue status is derived from started_at, verified_at, completed_at, cancelled, evidence coverage and dependency state
  • Milestone status is derived from its issues and its own evidence
  • The active milestone is derived from order and status, not declared
  • A completed issue whose required evidence is missing derives VERIFY, not DONE
Validation
bash test/run.sh 41_project_status
Evidence required
status_test
Evidence present
status_test

Scope

Touches
lib/project.shlib/project.awk
Not
Any status field a human can set directly
Depends on
I0002
Priority
p0
Profile
deep-work
Parallel safe
false
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-04T03:12:47Z
Started
2026-09-04T03:12:45Z
Verified
2026-09-04T03:12:46Z
Completed
2026-09-04T03:12:47Z

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.