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

I0827

The benchmark policy block

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
2
Waiting on
none
Holds back
I0828
Behind it in all
3
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 I0827

majordomus plan verify I0827

majordomus plan done I0827

What it is

Objective
Declare benchmark.samples, benchmark.warmup, benchmark.timeout_seconds, benchmark.cache_max_entries, benchmark.regression.p50/p95/p99 and benchmark.budget.doctor_ms in the policy, its allow-list and the skeleton, with no reader-side default.
Why
Repeated constants in code are the thing majordomus.policy-completeness exists to refuse.
Now
The policy has no benchmark keys.
Wanted
One block, documented in docs/SCHEMAS.md, read by bench, the cache and the budget check.
Done when
unknown: the record declares no `completion`
Risk
The peer branch generates allow-lists from schemas; the keys are added in the anchored one-per-line form so the fold is mechanical.

Acceptance

  • doctor's policy-completeness check passes with the new keys
  • An unknown benchmark key is refused
Validation
bin/majordomus doctor
Evidence required
docs_integrated
Evidence present
docs_integrated

Scope

Touches
share/allow/policy.txtshare/skeleton/policy.yaml.ai/repo/policy.yamldocs/SCHEMAS.mdlib/doctor.sh
Not
none
Depends on
I0823
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:33:10Z
Verified
2026-09-05T03:33:10Z
Completed
2026-09-05T03:33:10Z

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.