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

I0825

An explicit committed baseline

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
M004
Milestone status
ACTIVE
Wave
3
Waiting on
none
Holds back
I0826
Behind it in all
6
Evidence
1 of 1

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 I0825

majordomus plan verify I0825

majordomus plan done I0825

What it is

Objective
Add bench --write-baseline, which refuses a dirty tree unless forced, prints old, new and delta per target, and writes .ai/repo/benchmarks/baseline.json with schema majordomus/benchmark-baseline/v1.
Why
A baseline that updates itself is not a baseline.
Now
No baseline exists.
Wanted
A reviewable file under .ai/repo/, updated only by the command, carrying the commit, the profile and the summary statistics per target and mode.
Done when
unknown: the record declares no `completion`
Risk
Two machines give two baselines; the file records the platform and the check reports not comparable across a different profile or schema.

Acceptance

  • Writing on a dirty tree is refused without --force
  • The written file round-trips through bench --check with zero regressions
Validation
bash test/run.sh 81_bench_baseline
Evidence required
baseline_explicit
Evidence present
baseline_explicit

Scope

Touches
lib/bench.sh.ai/repo/benchmarks/baseline.jsonshare/skeleton/ai/repo/benchmarksdocs/SCHEMAS.mdtest/cases/81_bench_baseline.sh
Not
Raw samples in the baseline
Depends on
I0824
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
2026-09-05T03:47:33Z
Verified
2026-09-05T03:47:33Z
Completed
2026-09-05T03:47:33Z

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.