Skip to content

I0816 — Prove the loop on a real issue, without a transcript

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.

BLOCKED wave 9 · p1 · deep-work profile · runs alone

Part of M003 — A session is a durable envelope, and knowledge is compiled from what is already canonical.

Blocked. This issue cannot start until I0815 is done. The status is derived from that, not declared.

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.

Current state

The pieces are individually tested in disposable repositories. Nothing has run the assembled loop on this repository's own canonical model.

Desired state

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.

Scope

  • docs/DOGFOODING.md
  • .majordomus/project

Out of scope

  • Any new capability
  • Any performance guarantee in README or claims that the measurement does not support

Dependencies

Acceptance criteria

  • 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.sh
  • bin/majordomus doctor
  • bin/majordomus watch
  • bin/majordomus plan validate

Evidence required

  • dogfood_loop

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

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.

Timeline

started
—
verified
—
completed
—

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/I0816.yaml. Read it back with majordomus plan show I0816.