I0401 — Define an accepted outcome, and join it to its measurements without storing the join
Define precisely which finishes count as accepted outcomes, and derive the join between an accepted outcome and the execution facts of the work that produced it from records that already exist, storing no third record.
BLOCKED wave 0 · p2 · deep-work profile · runs alone
Part of cost-per-accepted-outcome — Cost per accepted outcome, only on measured data.
Blocked. This issue cannot start until milestone:cost-per-accepted-outcome is done. The status is derived from that, not declared.
Objective
Define precisely which finishes count as accepted outcomes, and derive the join between an accepted outcome and the execution facts of the work that produced it from records that already exist, storing no third record.
Why
Cost per outcome is a ratio, and both halves of it are already recorded: the finish contract decides acceptance and telemetry measures consumption. Storing the join would be a third place for them to disagree.
Current state
The finish contract evaluates acceptance and records the outcome. Telemetry records what a session consumed. Nothing connects them, and the word outcome is used loosely across the documents.
Desired state
One written definition of an accepted outcome, matching what the finish contract actually enforces, and a derivation that produces the set of accepted outcomes with their measurements, computed on demand.
Scope
- lib
- docs
Out of scope
- Any stored aggregate
- Counting a completed finish that the contract did not accept
Dependencies
None. This issue is a root of the graph.
What waits on this
Acceptance criteria
- The definition matches what the finish contract enforces, and a case fails if the two drift apart
- The join is derived from existing records, with nothing new persisted
- An outcome whose work reported no telemetry appears in the set with an explicit absence
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
The tempting definition is the one that produces more data points; the correct one is the one the finish contract already enforces, even when that is a smaller set.
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/I0401.yaml. Read it back with majordomus plan show I0401.