Measure Delivery Throughput

Objective

Measure accepted delivery flow from the same assessment snapshot independently of variable assessment and ticket mutation.

Procedure

1. Use the iteration ID, repository revision, and source cursors from RUN.md.
2. Read the authoritative delivery records declared in the Huginn contract (for example accepted scenario issues, merged changes, releases, and acceptance checks).
3. Count completed accepted items in the declared cadence/window. Also record cycle time and work-in-progress when the source supports them.
4. Story points are optional and must not replace item throughput unless the Charter explicitly defines their source and use.
5. Exclude reopened, rejected, duplicate, or unaccepted work and record the exclusion reason.
6. Write THROUGHPUT.json with window, sources/queries, counts, item IDs, exclusions, cycle-time summary, WIP, freshness, and errors.

Completion evidence

The result is reproducible from named records, uses the run snapshot and cadence window, distinguishes accepted work from activity volume, and expresses missing/stale data as Unknown rather than zero.