Skip to content

I0305 — Publish the telemetry claim and record what remains unmeasured

Move the telemetry claim to guaranteed for the providers that report honestly, name the implementation and the case, and state in the economics document which providers report nothing and what that costs the analysis.

BLOCKED wave 4 · p3 · implementation profile · runs alone

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

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

Objective

Move the telemetry claim to guaranteed for the providers that report honestly, name the implementation and the case, and state in the economics document which providers report nothing and what that costs the analysis.

Why

The value of this milestone is as much in what it refuses to claim as in what it measures. A reader has to be able to see which sessions are measured and which are not before believing any number built on top.

Current state

The claim is planned and the economics document claims nothing on purpose.

Desired state

The claim is guaranteed with its narrow scope stated, and the economics document says which providers are measured, which are not, and what follows from that.

Scope

  • docs
  • site/data/generated

Out of scope

  • Any figure derived from the measurements

Dependencies

Acceptance criteria

  • The claim cites an implementation path and a test path that both exist
  • The economics document names the measured and unmeasured cases
  • The generated site data regenerates with no stale file

Validation

  • scripts/generate-site-data --check
  • bash test/run.sh

Evidence required

  • docs_build

Evidence

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

Risk

Publishing measurement invites treating partial coverage as full coverage; the coverage statement has to sit next to the claim, not in a footnote.

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