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

I0816

Prove the loop on a real issue, without a transcript

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
M003
Milestone status
ACTIVE
Wave
8
Waiting on
I0815
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI0815I0815 is not DONE

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 I0816

majordomus plan verify I0816

majordomus plan done I0816

What it is

Objective
Execute the whole lifecycle against a real issue of this repository — session start, plan next, plan show, context, knowledge retrieval, work, checkpoint and decision, evidence, plan done, session close, knowledge sync, watch — and record as evidence what a following session could determine from the records alone.
Why
The milestone is not finished when a command returns something. It is finished when a worker with no conversation history can say what happened, why, what was decided, which evidence supports it, where the canonical source lives and what to do next. That is a demonstration, not an assertion, and it is the only acceptance criterion that tests the parts against each other.
Now
The pieces are individually tested in disposable repositories. Nothing has run the assembled loop on this repository's own canonical model.
Wanted
The loop has been run, its measurements recorded — discovery, cold sync, no-op sync, search, context assembly — and the questions a following worker can answer from records alone are listed with the command that answers each.
Done when
unknown: the record declares no `completion`
Risk
A dogfood run that is narrated rather than measured proves nothing. Every claim in the evidence has to name a command that produced it.

Acceptance

  • The loop ran on a real issue and the evidence names the commands and what each showed
  • Each of the six questions a following worker must answer is listed with the command that answers it
  • The measurements are recorded, and no number appears in README or claims that they do not support
  • A read-only pass over the whole surface leaves git status byte-identical
Validation
bash test/run.shbin/majordomus doctorbin/majordomus watchbin/majordomus plan validate
Evidence required
dogfood_loop
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docs/DOGFOODING.md.majordomus/project
Not
Any new capabilityAny performance guarantee in README or claims that the measurement does not support
Depends on
I0815
Priority
p1
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-04
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

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.