Skip to content

I1024 — The interface has a weight, and it is measured

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.

BLOCKED wave 5 · p2 · implementation profile · parallel safe

Part of capability-graph — One capability graph, two projections, and no second inventory of what this repository can do.

Blocked. This issue cannot start until I1014 is done. The status is derived from that, not declared.

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.

Current state

The benchmark infrastructure records distributions per command against a committed baseline. Nothing measures a page or an asset.

Desired state

The interface's weight and initialisation are baselines like the commands', with thresholds that catch a real regression and ignore a byte.

Scope

  • .ai/repo/benchmarks

Out of scope

  • A new benchmark system beside the one that exists
  • A threshold so tight that ordinary content growth fails the build

Dependencies

What waits on this

Acceptance criteria

  • 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_measured
  • budgets_declared

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Risk

Asset budgets provoke arguments about kilobytes. The threshold is set where it detects a category change, not a content edit.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I1024.yaml. Read it back with majordomus plan show I1024.