Project telemetry
What we’re building, fixing, and learning.
A report drawn from the prompt log, repository history, ingest runs, and the current KIDO dataset.
Primary work type
What the work was for
Each prompt appears once. Release work comes first, then data support, feature development, product quality, and workflow maintenance.
Code purpose
What code changes supported
Only prompts tagged Code Fix appear here. Code used by scrapers, normalization, or data repair counts as data support.
Tag glossary
What the raw tracking tags mean
These tags overlap because they describe changed artifacts or workflow steps. They are diagnostic labels, not competing work categories.
Delivery
Change and data activity
Commits come from the local repository. Deployments come from explicitly logged deploy operations.
Work ledger
Recent features, fixes, and follow-through
Each entry keeps the requested change beside its affected area, verification, and outcome.
Measurement map
What a standard development dashboard can see
This separates recorded facts from signals that still need GitHub, CI, deployment, or incident integrations.
| Signal | Coverage | Current source | What it means |
|---|
The report does not infer lead time, failure rate, or recovery time from prompt wording. Those measures need linked lifecycle events.