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
I0828
doctor under a declared budget, and the hook inherits it
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Report doctor's own wall time against benchmark.budget.doctor_ms as a finding, advisory, and record the measured value on this repository as the budget's rationale in docs/PERFORMANCE.md.
- Why
- The pre-commit hook is the one place a slow doctor is paid on every commit.
- Now
- 10 s on this repository before this milestone.
- Wanted
- Under 1.5 s on this repository, with the budget declared and the hook unchanged.
- Done when
- unknown: the record declares no `completion`
- Risk
- WARN never changes the exit code, by doctrine.
Acceptance
- doctor prints its total and the budget; over budget is WARN, never the exit code
- Case 83 proves the finding appears with a tiny budget
- Validation
MJ_TIMING=1 bin/majordomus doctorbash test/run.sh 83_doctor_budget- Evidence required
doctor_under_budget- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
lib/doctor.shdocs/PERFORMANCE.md.ai/repo/policy.yamltest/cases/83_doctor_budget.sh- Not
A blocking budget- Depends on
- 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
- 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.