Nishi DORA — sovereign delivery metrics (F740)

the four keys DERIVED from our own event stream (ws_sync.jrnl + debt plane) — zero git-poll, zero manual entry · measured, never asserted
50
deploys (DONE frames) · ELITE
1h
median lead time · ELITE
42%
change-fail (proxy) · LOW

The four keys — measured from sovereign planes

keyvaluebandkindhow it is derived
Deployment frequency50 over 1d (185/wk)ELITEMEASUREDcount of DONE frames in ws_sync.jrnl (each = a delivered capability)
Lead time for changesmedian 1h (30 matched pairs)ELITEMEASUREDDONE_epoch - most-recent prior KICKOFF of the same workstream
Change failure rate42% (21 incident-class open debts)LOWPROXYdeploy-failure open debts (regression/rollback/revert/outage/brick) / deploys (declared coarse-upper-bound heuristic; broad coordination/stale debts EXCLUDED)
Time to restore (MTTR)PENDINGfiled→eaten span needs the debthist- join (F740b); NOT asserted rather than faked

Why this is beyond SOTA

axisNishiJellyfish / LinearB / Swarmia / DX
instrumentationZERO manual + ZERO git-poll: derived from the native delivery event streampoll git/CI/Jira webhooks; batch ETL
honestyeach key tagged MEASURED / PROXY / PENDING; a key it cannot ground is shown PENDING, never fakedsingle confident numbers
agents as workersautonomous zero-Claude DONE frames counted as first-class deliverieshumans-only

Fetch spec (what to ingest to harden this)

targetwhy
dora.dev 2024 State of DevOpsthe canonical thresholds + the AI-impact findings to re-band against
DX Core 4 (getdx.com)unify DORA+SPACE+DevEx; the 4-dim model to extend these keys with effectiveness/quality
debthist- join (F740b)filed→eaten timestamps to turn MTTR from PENDING into MEASURED