A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
execution-telemetry
Execution telemetry, only from providers that expose it honestly
5issuesdevtask.milestone
0readydevtask.milestone
4blockeddevtask.milestone
0activedevtask.milestone
0completedevtask.milestone
The milestone
devtask.milestone- Title
- Execution telemetry, only from providers that expose it honestly
- Outcome
- Execution telemetry is recorded for providers that report it truthfully, and absence is recorded as absence rather than estimated.
- Status
- BLOCKED
- Rank
2- Depends on
- Waiting on
- Holds back
- Record
.ai/repo/project/milestones/execution-telemetry.yaml- Its issues
- Every issue of this milestone
Where the work is
- Ready
- —
- Blocked
- Waiting
- Active
- —
- In review
- —
- Completion blocked
- —
- Complete
- —
- Cancelled
- —
What holds the most back
What may run at the same time
Nothing here can be started now.
Every issue
| Readiness | Status | Issue | Title | Wave | Priority | Waiting on | Holds back |
|---|---|---|---|---|---|---|---|
| waiting | BLOCKED | I0301 | Define the execution record, including what an absence looks like | 0 | p2 | 4 | |
| blocked | BLOCKED | I0302 | Record telemetry a provider reports, and refuse anything it did not | 1 | p2 | 3 | |
| blocked | BLOCKED | I0303 | Prove a silent provider produces an explicit absence, never a guess | 2 | p2 | 2 | |
| blocked | BLOCKED | I0304 | Read the measurements back through the history surface, under a bound | 3 | p2 | 1 | |
| blocked | BLOCKED | I0305 | Publish the telemetry claim and record what remains unmeasured | 4 | p3 | 0 |
Findings
Nothing is wrong with these records.