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

I1119

The budgets are measured, and a regression fails rather than being noticed

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
7
Waiting on
I1113
Holds back
I1123
Behind it in all
1
Evidence
0 of 2
In the waySubjectDetail
issueI1113I1113 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 I1119

majordomus plan verify I1119

majordomus plan done I1119

What it is

Objective
Measure what this architecture costs — discovery, reconciliation, the environment entry, the generated artifacts — and hold each to a budget derived from its measured baseline.
Why
A spine every consumer reads is a cost every consumer pays. Measured once and then never again, it grows until somebody works around the tool instead of using it.
Now
The benchmark infrastructure records distributions per command against a committed baseline. The new paths are not among its targets.
Wanted
Each new path is a benchmark target with a recorded baseline and a threshold that catches a material regression while tolerating ordinary growth.
Done when
unknown: the record declares no `completion`
Risk
Wall-clock thresholds are noisy across machines. The structural counters gate strictly and the timings conservatively, as the existing performance doctrine already decided.

Acceptance

  • Discovery, reconciliation, the dry run and the environment entry are benchmark targets with recorded baselines
  • The thresholds are policy data, and the check names the target, both values and the threshold when it fails
  • The environment it was measured on is recorded with each baseline
  • A material regression fails; a byte does not
Validation
majordomus bench --check
Evidence required
budgets_measuredregression_refused
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
.ai/repo/benchmarks.ai/repo/policy.yaml
Not
A second benchmark systemA threshold so tight that ordinary content growth fails the build
Depends on
I1113
Priority
p2
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.