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

I0822

Every canonical file is flattened at most once per command

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
M004
Milestone status
ACTIVE
Wave
3
Waiting on
I0820
Holds back
I0831I0835
Behind it in all
3
Evidence
0 of 1
In the waySubjectDetail
issueI0820I0820 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 I0822

majordomus plan verify I0822

majordomus plan done I0822

What it is

Objective
Add a case that runs doctor, watch, context and plan validate under MJ_TIMING and asserts the yaml_flatten count never exceeds the number of distinct canonical files a command reads.
Why
This is the shell tool's form of the no-rebuild-per-request invariant: repeated work is structural, and a counter catches it where a clock cannot.
Now
doctor flattens 181 times for a repository with fewer canonical files than that.
Wanted
The counter equals the distinct-file count per command and the case fails when a validator regresses to re-flattening.
Done when
unknown: the record declares no `completion`
Risk
Some validators legitimately flatten a file twice in different shapes; the case names the allowed exceptions explicitly rather than tolerating a margin.

Acceptance

  • Case 78 passes on this repository and fails on a mutation that re-flattens inside a loop
Validation
bash test/run.sh 78_flatten_once
Evidence required
batch_reads
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
test/caseslib/common.sh
Not
none
Depends on
I0818I0819I0820
Priority
p0
Profile
implementation
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-05
Updated
2026-09-05
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.