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
I0401
Define an accepted outcome, and join it to its measurements without storing the join
Where it stands
devtask.issue- Readiness
- waiting every dependency is satisfied; the milestone cost-per-accepted-outcome 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
3- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| milestone | cost-per-accepted-outcome | the milestone cost-per-accepted-outcome waits on an outcome of its own |
Moves
plan.transitionWhat it is
- 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.
- Now
- 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.
- Wanted
- 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.
- Done when
- unknown: the record declares no `completion`
- 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.
Acceptance
- 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 present
- unknown: the record carries no `evidence` entries
Scope
- Touches
libdocs- Not
Any stored aggregateCounting a completed finish that the contract did not accept- 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.