Skip to content

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

Execution telemetry is recorded for providers that report it truthfully, and absence is recorded as absence rather than estimated.

BLOCKED 0 of 5 issues done

ready
0
blocked
5
active
0
verify
0
done
0
cancelled
0

Problem

Nothing here measures what a session actually consumed. Every economic statement about AI-assisted work in this repository is currently an argument rather than a measurement.

Outcome

Execution telemetry is recorded for providers that report it truthfully, and absence is recorded as absence rather than estimated.

Current state

Not started. docs/ECONOMICS.md states what it would take and deliberately claims nothing.

Desired state

A completed task carries measured execution facts, or an explicit record that the provider did not supply them.

Scope

  • bin
  • lib
  • share
  • test/cases
  • docs
  • site/data/generated

Out of scope

  • Estimating a number a provider does not report

Acceptance criteria

  • Telemetry is recorded only where the provider reports it
  • A provider that reports nothing produces an explicit absence, never a guess
  • The record is durable and readable back through the existing history surface

Validation

  • bash test/run.sh

Evidence required

  • suite

Risks

  • A provider's self-reported usage may itself be unreliable; the record must say who reported it.

Issues

Each one is an execution contract with its own acceptance criteria, validation command and required evidence. The wave column is the layer of the dependency graph it sits in.

issuestatuswavedepends ontitle
I0301 BLOCKED 0 — Define the execution record, including what an absence looks like
I0302 BLOCKED 1 I0301 Record telemetry a provider reports, and refuse anything it did not
I0303 BLOCKED 2 I0302 Prove a silent provider produces an explicit absence, never a guess
I0304 BLOCKED 3 I0303 Read the measurements back through the history surface, under a bound
I0305 BLOCKED 4 I0304 Publish the telemetry claim and record what remains unmeasured

The graph

execution-telemetry dependency graphfrom .ai/repo/project
flowchart LR
    I0301["I0301<br/>Define the execution record, including what an absence looks like"]:::blocked
    I0302["I0302<br/>Record telemetry a provider reports, and refuse anything it did not"]:::blocked
    I0303["I0303<br/>Prove a silent provider produces an explicit absence, never a guess"]:::blocked
    I0304["I0304<br/>Read the measurements back through the history surface, under a bound"]:::blocked
    I0305["I0305<br/>Publish the telemetry claim and record what remains unmeasured"]:::blocked
    I0301 --> I0302
    I0302 --> I0303
    I0303 --> I0304
    I0304 --> I0305
    classDef done stroke:#16a34a,fill:#052e16,stroke-width:2px
    classDef active stroke:#2563eb,fill:#eff6ff,stroke-width:2px
    classDef verify stroke:#7c3aed,fill:#f5f3ff,stroke-width:2px
    classDef ready stroke:#0891b2,fill:#ecfeff,stroke-width:2px
    classDef blocked stroke:#b45309,fill:#fffbeb,stroke-width:2px
    classDef cancelled stroke:#6b7280,fill:#f9fafb,stroke-width:2px

Canonical record: .ai/repo/project/milestones/execution-telemetry.yaml. Read it back with majordomus plan show execution-telemetry.