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
I1024
The interface has a weight, and it is measured
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
5- Waiting on
- Holds back
- Behind it in all
1- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I1014 | I1014 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Measure the generated data, the served HTML, the initial scripts and styles and the graph's initialisation, and hold them to budgets through the benchmark infrastructure the repository already has.
- Why
- A derived interface grows with the repository by construction. Without a measured budget it becomes slow gradually, which is the way that never gets noticed.
- Now
- The benchmark infrastructure records distributions per command against a committed baseline. Nothing measures a page or an asset.
- Wanted
- The interface's weight and initialisation are baselines like the commands', with thresholds that catch a real regression and ignore a byte.
- Done when
- unknown: the record declares no `completion`
- Risk
- Asset budgets provoke arguments about kilobytes. The threshold is set where it detects a category change, not a content edit.
Acceptance
- The generated data size, the served HTML size, the initial script and style weight and the graph initialisation are all measured
- The baselines live where the benchmark infrastructure already keeps them, with the environment recorded
- Thresholds catch a material regression and tolerate ordinary growth, and the policy states which is which
- Heavy libraries are absent from pages that do not use them, proved by measurement rather than by intent
- Validation
majordomus bench --check- Evidence required
interface_measuredbudgets_declared- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
.ai/repo/benchmarks- Not
A new benchmark system beside the one that existsA threshold so tight that ordinary content growth fails the build- Depends on
- Priority
- p2
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-06
- Updated
- 2026-09-06
- 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.