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

M004

Performance is executable evidence, and the hot path does no canonical work twice

38issuesdevtask.milestone
10readydevtask.milestone
10blockeddevtask.milestone
1activedevtask.milestone
16completedevtask.milestone

The milestone

devtask.milestone
Title
Performance is executable evidence, and the hot path does no canonical work twice
Outcome
Every public command can be benchmarked from the command registry with cold and warm distributions, the phases and work counters of any run can be printed, the caches and batch reads that remove repeated work preserve every observable result, an accepted baseline lives in the repository and a check refuses a regression by policy, and the pre-commit hook is fast enough that nobody routes around it.
Status
ACTIVE
Rank
0
Depends on
unknown: the record declares no `depends_on`
Waiting on
none
Holds back
none
Record
.ai/repo/project/milestones/M004.yaml
Its issues
Every issue of this milestone

Where the work is

Ready
Blocked
Waiting
—
Active
In review
Completion blocked
—
Complete
Cancelled
—

What holds the most back

What may run at the same time

WaveTogetherSerialised by scope
0—
0

I2660 before I2661: both touch .github/workflows/pages.yml

0

I2660 before I2662: both touch .github/workflows/pages.yml

I2661 before I2662: both touch .github/workflows/pages.yml

1—
1—
2—
2—
3—
5—

Every issue

ReadinessStatusIssueTitleWavePriorityWaiting onHolds back
completeDONEI0817Phase timing and work counters behind MJ_TIMING0p0—25
completeDONEI0818The command registry is read in one pass1p0—10
completeDONEI0819The project model is loaded with one flatten per file and no per-file lookups1p0—12
readyREADYI0820Catalogue, DAG, context and command-surface validators read their inputs once2p0—9
readyREADYI0821Flattened YAML is cached under .ai/local/cache by content hash1p0—3
blockedBLOCKEDI0822Every canonical file is flattened at most once per command3p03
completeDONEI0823majordomus bench: targets derived from the command registry1p0—12
completeDONEI0824Bench persists local runs and keeps a latest projection2p0—7
completeDONEI0825An explicit committed baseline3p0—6
completeDONEI0826bench --check refuses a regression by policy4p0—5
completeDONEI0827The benchmark policy block2p0—3
blockedBLOCKEDI0828doctor under a declared budget, and the hook inherits it3p02
completeDONEI0829Performance doctrine as project rules0p0—2
completeDONEI0830docs/PERFORMANCE.md, README, CONTRIBUTING and CLI reference5p0—1
blockedBLOCKEDI0831Performance claims at their proven status5p01
readyREADYI0832generate-site-data instrumented and its hot spots removed2p0—2
completeDONEI0833knowledge nodes and edges read each source once1p0—2
blockedBLOCKEDI0834The test runner reports per-case time and the suite budget4p00
blockedBLOCKEDI0835CI runs the structural performance checks5p01
completeDONEI0836A synthetic repository generator for scaling cases2p0—0
completeDONEI0837Timing report as JSON1p0—0
readyREADYI0838bench compare and the top regressions report5p0—0
blockedBLOCKEDI0839watch inherits every doctor fix and its own budget4p00
blockedBLOCKEDI0840context and its subcommands under a second3p00
blockedBLOCKEDI0841Cache equivalence proved by property-shaped cases2p01
blockedBLOCKEDI0842Before and after evidence for every optimisation3p01
blockedBLOCKEDI0843The performance workflow is discoverable and complete6p00
reviewVERIFYI2068A verdict that depends on the runner says so, and one cold sample is not a regression0p2—0
readyREADYI2660The site is published as an artifact by the job that built it, so a ready site waits for no second workflow0p1—0
readyREADYI2661A publication that did not arrive is a finding the next reader meets, never a green step0p1—0
readyREADYI2662Validation leaves the deployment a runner: a branch's checks never hold the pool a publication or a release record needs0p1—0
readyREADYI2663The published UI is not read from nothing on every deployment3p1—0
completeDONEI2664A run that has already failed is cancelled by itself, and a red on the trunk is fixed before anything else is prepared0p1—1
readyREADYI2709A red on the trunk has one named carrier, and nobody else may land until it is paid1p1—0
completeDONEI2710A release run never waits behind pull-request validates for a job slot0p0—0
completeDONEI2711The pages job judges production only after the deployment of its own commit has arrived0p0—0
in_progressACTIVEI2716A case derives its budgets and lists from what it tests, never pins them0p2—0
readyREADYI2717A release record pull request gets a verdict that can pass0p0—0

Findings

LevelCodeMessageReproduce
WARNscope_conflictI0820: shares test/cases/28_catalogue.sh with I2487; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0820: shares test/cases/28_catalogue.sh with I2488; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares docs/SCHEMAS.md with I1302; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares test/cases with I1951; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares test/cases with I1965; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares test/cases with I1985; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares share/skeleton/policy.yaml with I1988; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares share/allow/policy.txt with I2401; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares test/cases with I2403; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares test/cases with I2484; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares test/cases with I2700; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares .ai/repo/policy.yaml with I2701; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares test/cases with I2706; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares test/cases with I2708; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0821: shares test/cases with I2709; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0832: shares test/cases/10_site_data.sh with I2487; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI0832: shares test/cases/10_site_data.sh with I2488; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2660: shares .github/workflows/pages.yml with I2661; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2660: shares .github/workflows/pages.yml with I2662; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2660: shares .github/workflows/pages.yml with I2786; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2661: shares .github/workflows/pages.yml with I2662; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2661: shares .github/workflows/pages.yml with I2786; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2662: shares .ai/repo/ci/gates.yaml with I2716; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2662: shares .github/workflows/validate.yml with I2717; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2662: shares .github/workflows/pages.yml with I2786; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2717; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2718; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2720; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2723; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2731; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2734; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2740; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2742; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2747; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2760; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2716: shares test/cases with I2786; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2718; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2720; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2723; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2731; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2734; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2740; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2742; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2747; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2760; they may not run concurrentlymajordomus plan validate
WARNscope_conflictI2717: shares test/cases with I2786; they may not run concurrentlymajordomus plan validate