Skip to content

I0301 — Define the execution record, including what an absence looks like

Define the durable shape of a task's execution facts: which fields exist, who reported each one, and how a provider that reported nothing is recorded, so that absence is a value with a reason rather than a missing key or a zero.

BLOCKED wave 0 · p2 · deep-work profile · runs alone

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

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

Objective

Define the durable shape of a task's execution facts: which fields exist, who reported each one, and how a provider that reported nothing is recorded, so that absence is a value with a reason rather than a missing key or a zero.

Why

Every economic statement this repository could make rests on this record. If absence is representable only as a gap, the first report that reads it will treat a gap as a zero and the whole layer becomes an estimate wearing a measurement's clothes.

Current state

Nothing measures a session. The economics document states what measurement would take and deliberately claims nothing, and no schema exists to be filled.

Desired state

One schema, with an allowlist like every other record here, in which each measured field names its reporter, and not_reported is a first-class value carrying why it is absent.

Scope

  • share
  • lib
  • docs

Out of scope

  • Collecting anything; this issue defines what would be stored
  • Any field the tool would have to estimate to populate

Dependencies

None. This issue is a root of the graph.

What waits on this

Acceptance criteria

  • Every field names the reporter it came from, and a record without a reporter is refused
  • not_reported is representable with a reason, and is distinguishable from zero everywhere it is read
  • Unknown keys are refused like every other record in this repository
  • The schema is documented where the other file formats are

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

A schema designed around one provider's numbers becomes that provider's schema; the reporter field is what keeps a second provider from having to lie to fit.

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