Understand the shape of the work.
- Added, deleted, rewritten, and net footprint
- Test and documentation tokens added
- Complexity, duplication, and refactor-pressure movement
- Exact-patch coverage and disclosed estimates
Accepted delivery evidenceSee what changed.
See what changed.
Including what disappeared.
Shipped Tokens tracks authored source tokens added, deleted, and rewritten after work reaches the default branch. It then shows whether deterministic refactor pressure rose or fell.
Actual Assessment output
PostHog · current reportSee accepted token flow in context.
Two views, one evidence base
Useful at the keyboard and in the boardroom.
Separate delivery from code growth.
- Organization and repository timelines
- Conserved credit across shared authors
- Pressure improvements alongside net footprint
- Frozen evidence in permissioned reports
No test runner, incident system, or AI opinion required.
The repository scan and accepted patch are enough to produce the measurement. The limitations stay visible with the result.
Complete patches use lexical token counts. Incomplete patches retain a clearly labeled line-estimate fallback.
A versioned score combines duplication, branch density, oversized-file share, and dependency density. Negative movement means pressure fell.
Generated, vendored, lock, binary, and build output are excluded. Source files and raw diffs are not stored.
Added = net-new + rewrittenDeleted = removed + rewrittenNet footprint = net-new − removedPressure Δ = after − before
Questions
How to read token movement correctly.
Token flow explains the shape of accepted change. It should never be read as a volume contest.
What is a shipped token?
It is a lexical source token observed in an accepted repository change after generated, vendored, lock, binary, and build output are excluded. Complete patches use token counts; incomplete patches use a clearly labeled line-estimate fallback.
Do deleted tokens reduce delivered value?
Not automatically. The system separates removed code from rewritten code and reads token movement beside accepted value and structural change. Useful deletion can retire complexity or burden, while removal of needed capability can reduce retained value.
How is refactor pressure measured?
A versioned deterministic score combines duplication, branch density, oversized-file share, and dependency density. The report shows the before-and-after movement, with negative movement indicating that measured pressure fell.
Does the measurement require test results or incident tools?
No. Shipped Tokens uses repository scans and accepted patches. Tests and documentation can be measured as visible codebase surfaces, but the result does not claim that tests passed, incidents declined, or runtime behavior improved.
Are raw diffs or source files stored?
No. Source and raw diffs are evaluated from authorized GitHub access and are not stored. Derived token measurements, evidence references, coverage, and valuation history are retained for the workspace record.
Track the flow behind the value
Start free trial Code can get smaller and still deliver more.
See token movement, structural pressure, Contributor Value, RepoWorth, and report evidence in one signed workspace.