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
I0842
Before and after evidence for every optimisation
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Record, for each hot spot removed, the phase time before and after and the counter before and after, in the benchmark history and in the commit message, and summarise them in docs/PERFORMANCE.md by pointing at the baseline file.
- Why
- A speed-up without numbers is a claim.
- Now
- 77f5d79 records the first ranking in its message.
- Wanted
- Every optimisation commit carries its measured delta; the baseline file carries the accepted state.
- Done when
- unknown: the record declares no `completion`
- Risk
- project.no-counts-in-prose keeps measured values out of the documents; the baseline file is the one place they live.
Acceptance
- Each optimisation commit names its phase and both values
- The baseline reflects the state after the last optimisation
- Validation
git log --grep perf- Evidence required
doctor_under_budget- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
docs/PERFORMANCE.md.ai/repo/benchmarks/baseline.json- Not
Numbers in prose outside the baseline and the history- 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.