The measurement leaves one machine: several tools, several people, over time.
Context and Value
The first two milestones prove the chain on one tool and attach it to the work. Everything that follows requires crossing a boundary the design has so far avoided: another vendor, another repository, another person, and a retention longer than a working week.
The mechanics are already known, and were measured rather than assumed. Each remaining tool exports tokens and a session identifier; what differs is which signal carries them and how the export is switched on. Two of them export no amount at all, so a price table becomes unavoidable. And the flag that makes per-step attribution readable also logs what was typed, so redaction has to happen before anything is stored or sent.
Boundaries
- Includes: Codex, Copilot, Cursor and OpenCode, added one at a time, each with its own gate to lift.
- Includes: a price table, for the two tools that export tokens without a cost.
- Includes: redaction of sensitive attributes before storage or upload.
- Includes: the commit trailer, which attaches cost at commit precision rather than session precision.
- Includes: the upload, and reporting per person, per team and per epic.
- Excludes: replacing any tool's own measurement. The framework configures exports, it does not compute tokens.
- Excludes: anything that would mirror a backlog across supports.
Success Evidence
A team lead reads a week of work broken down by person, tool, model and step, on tools other than Claude Code, from a repository they did not have to open.
The decision that gates this milestone
Anonymised identifiers and per-person statistics were both promised, and they are incompatible. The run journal enters git history: on a company repository it records who worked on what, when, and for how long, permanently. This milestone cannot start before that is settled, and the decision is not the engineering team's alone.
Design: aidd_docs/specs/2026_08/2026_08_13-work-tracking-linkage.md
The measurement leaves one machine: several tools, several people, over time.
Context and Value
The first two milestones prove the chain on one tool and attach it to the work. Everything that follows requires crossing a boundary the design has so far avoided: another vendor, another repository, another person, and a retention longer than a working week.
The mechanics are already known, and were measured rather than assumed. Each remaining tool exports tokens and a session identifier; what differs is which signal carries them and how the export is switched on. Two of them export no amount at all, so a price table becomes unavoidable. And the flag that makes per-step attribution readable also logs what was typed, so redaction has to happen before anything is stored or sent.
Boundaries
Success Evidence
A team lead reads a week of work broken down by person, tool, model and step, on tools other than Claude Code, from a repository they did not have to open.
The decision that gates this milestone
Anonymised identifiers and per-person statistics were both promised, and they are incompatible. The run journal enters git history: on a company repository it records who worked on what, when, and for how long, permanently. This milestone cannot start before that is settled, and the decision is not the engineering team's alone.
Design: aidd_docs/specs/2026_08/2026_08_13-work-tracking-linkage.md