Skip to content

I0304 — Read the measurements back through the history surface, under a bound

Make recorded execution facts readable through the surface that already answers questions about past tasks, with the same retention bound the other durable stores carry.

BLOCKED wave 3 · p2 · implementation profile · runs alone

Part of execution-telemetry — Execution telemetry, only from providers that expose it honestly.

Blocked. This issue cannot start until I0303, milestone:execution-telemetry are done. The status is derived from that, not declared.

Objective

Make recorded execution facts readable through the surface that already answers questions about past tasks, with the same retention bound the other durable stores carry.

Why

A measurement that can only be read by opening a file is a measurement nobody reads. It also has to be bounded, because an unbounded append-only store is exactly what this repository refuses everywhere else.

Current state

Facts are recorded against tasks and can be read only from the record itself.

Desired state

History reports the measured facts alongside the task they belong to, says not_reported where that is what happened, and the store is capped like the ledger.

Scope

  • lib
  • docs

Out of scope

  • Aggregation, averages or any figure derived across tasks; that is the next milestone

Dependencies

What waits on this

Acceptance criteria

  • History shows measured facts and explicit absences for past tasks
  • The store has a declared retention bound and the bound is enforced by a case
  • No aggregate figure appears at this layer

Validation

  • bash test/run.sh

Evidence required

  • suite

Evidence

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

Risk

Showing per-task numbers invites reading a trend into them; the surface has to present facts without implying a series.

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/I0304.yaml. Read it back with majordomus plan show I0304.