Gate: computed weekly across the cohort; no convergence event this week
Gate: computed weekly across the cohort; no convergence event this week
position in cohort distributionone of 20 in cohort
percentile
p79
momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
velocity z
velocity z
-1.46 σ
slope
-0.054/wk
log-slope -0.054/wk
citation z
∅no citation axis
Citation source: not measured.
direct-dependents z
direct-dependents z
+2.71 σ
slope
+0.069/point
Direct-dependents axis: measured.
cohort
20
systems measured
weekly commits
378.1
Development velocity axis: measured.
total citations
n/a
Citation source: not measured.
momentum
57.8
percentile p79
commit heatmap, last 26 weeks378.1/wk
weeks
26
peak/wk
810
active
26
total
13404
citations by yearCitation source: not measured.
∅Citation source: not measured.
Kilo Code holds an Evidaxis momentum score of 57.8 of 100 on methodology m5, snapshot 2026-11-07, measured within the Coding Agents cohort (n = 20). Axis coverage: 2 of 3 axes measurable. Gate: computed weekly across the cohort; no convergence event this week
Derived signals
second-order reads, computed from the published series
Three signals ship when the commit series is statistically sufficient; the rest are held in a reserved state
until the data supports them. A reserved signal shows its reason, never a fabricated number.
How these are computed.
swing
-6.82×
regime
recent slope sign differs from prior window
windows
13w vs 39w
snapshot 1 of 1 ·· m5
sharpe
-0.013
95% ci
-0.056, +0.030
dof
50
snapshot 1 of 1 ·· m5
date
week
6 of 52
Δslope
-88.220/wk
snapshot 1 of 1 ·· m5
code-leads-citation lagreserved
reserved: citation series too short / axis absent for cross-correlation
status
reserved
value
insufficient data
snapshot 1 of 1 ·· m5
axis alpha vs cohortreserved
reserved: cohort N too small for regression (power ~0)
status
reserved
value
insufficient data
snapshot 1 of 1 ·· m5
gate ETAreserved
reserved: needs snapshot history (1 snapshot exists)
status
reserved
value
insufficient history
snapshot 1 of 1 ·· m5
methodology gate
snapshot 1 of 1 ·· m5
commit weeks
52
citation years
0
shipped
3
reserved
3
shipped
recency-swing
commit-sharpe
commit-changepoint
reserved
code-leads-citation-lag
axis-alpha
gate-eta
snapshot 1 of 1 ·· m5
Measurement states
Kilo Code is under weekly measurement. History: 19 weekly observations; minimum 4. Development velocity axis: measured. Citation source: not measured. Direct-dependents axis: measured. Gate: computed weekly across the cohort; no convergence event this week
This axis measures the trajectory of a system's own packages: declared in its own tree, published under that name, and not attributed by deps.dev to another repository. A package with no repository link is unverified and stays. The self-name exclusion list is fixed at the v2h.1 panel. Systems with no admitted package are not measured on this axis. Points that cannot be derived exactly are withheld, and the series restarts after a withheld point.
The earliest weekly points of each series were read from deps.dev's BigQuery history on 2026-07-21; later points are weekly captures. m5 does not replay those partitions: each point is the stored system total, one package's unique_direct, or a complete sketch union, and a point that is not exact is withheld. Each record reports how many of its points are reconstructed history.
Source: deps.dev (Google), CC-BY 4.0. Modified: aggregated to system-level counts and momentum scores.
Score derived from public data on Evidaxis methodology m5, never edited by hand. Cite as:
“Evidaxis, Kilo Code, entity e_JA1TAYFFAHR, snapshot 2026-w45.”