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
I0301
Define the execution record, including what an absence looks like
Where it stands
devtask.issue- Readiness
- waiting every dependency is satisfied; the milestone execution-telemetry waits on an outcome of its own
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
0- Waiting on
- Holds back
- Behind it in all
4- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| milestone | execution-telemetry | the milestone execution-telemetry waits on an outcome of its own |
Moves
plan.transitionWhat it is
- 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.
- Now
- Nothing measures a session. The economics document states what measurement would take and deliberately claims nothing, and no schema exists to be filled.
- Wanted
- 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.
- Done when
- unknown: the record declares no `completion`
- 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.
Acceptance
- 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 present
- unknown: the record carries no `evidence` entries
Scope
- Touches
sharelibdocs- Not
Collecting anything; this issue defines what would be storedAny field the tool would have to estimate to populate- Depends on
- none
- Priority
- p2
- Profile
- deep-work
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-04
- Updated
- 2026-09-04
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.