Skip to content

I0404 — Publish the cost-per-outcome claim with its unit defined beside it

Move the cost-per-outcome claim to guaranteed, define the unit and the denominator where a reader meets the figure, and state what the number cannot be used to compare.

BLOCKED wave 3 · p3 · implementation profile · runs alone

Part of cost-per-accepted-outcome — Cost per accepted outcome, only on measured data.

Blocked. This issue cannot start until I0403, milestone:cost-per-accepted-outcome are done. The status is derived from that, not declared.

Objective

Move the cost-per-outcome claim to guaranteed, define the unit and the denominator where a reader meets the figure, and state what the number cannot be used to compare.

Why

Cost per accepted outcome is the one figure this project argues is the right unit. Publishing it without saying what it excludes would repeat the mistake the economics document was written to avoid.

Current state

The claim is planned. The economics document argues for the unit and reports nothing.

Desired state

The claim is guaranteed, the unit and denominator are defined next to the reported figure, and the limits of comparison are stated.

Scope

  • docs
  • site/data/generated

Out of scope

  • Any comparison against another tool or another team

Dependencies

Acceptance criteria

  • The claim cites an implementation path and a test path that both exist
  • The unit and denominator are defined where the figure is presented
  • The document states what the figure cannot be used to compare
  • The generated site data regenerates with no stale file

Validation

  • scripts/generate-site-data --check
  • bash test/run.sh

Evidence required

  • docs_build

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Risk

A published cost figure is the most quotable thing this repository will produce and the most easily stripped of its qualifiers.

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/I0404.yaml. Read it back with majordomus plan show I0404.