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

I0921

Size is measured first and budgeted second

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
fly-deployment
Milestone status
ACTIVE
Wave
5
Waiting on
I0910I0911
Holds back
I0928
Behind it in all
2
Evidence
0 of 3
In the waySubjectDetail
issueI0910I0910 is not DONE
issueI0911I0911 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 I0921

majordomus plan verify I0921

majordomus plan done I0921

What it is

Objective
Measure the binary, the assets, the image and the build context, declare budgets with headroom over the measured baseline, and gate unexplained growth.
Why
A budget invented before a measurement is a number somebody will disable. A budget derived from a measured baseline with stated headroom is a regression detector.
Now
Nothing is measured because nothing is built.
Wanted
The baselines live where the benchmark infrastructure already keeps such things, the budgets are policy data, the gate fails on unexplained growth, and the documentation and UI can show both numbers without either being retyped.
Done when
unknown: the record declares no `completion`
Risk
A budget with no headroom fails on an unrelated dependency bump and trains everybody to raise it without looking.

Acceptance

  • Binary bytes, generated asset bytes, image size, compressed size where obtainable and the layer breakdown are all measured and recorded
  • The budgets are declared with stated headroom over the measured baseline and live as policy data
  • CI fails on growth beyond the budget and names what grew
  • The documentation and the UI read the baseline and the budget from the recorded data rather than from prose
Validation
majordomus bench --checkbash test/run.sh
Evidence required
sizes_measuredbudget_declaredci_gate
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
.ai/repo/benchmarks/rust.ai/repo/policy.yaml
Not
An arbitrary size target chosen before the first buildA second place where a size number is written by hand
Depends on
I0910I0911
Priority
p1
Profile
implementation
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-06
Updated
2026-09-06
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.