geo-score holds an Evidaxis momentum score of 89.5 of 100 on methodology m5, snapshot 2026-10-17, measured within the Unassigned (AI-v1 census) cohort (n = 6153). Axis coverage: 1 of 3 axes measurable. Gate: not computable — history 2 of 4 weekly observations
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
n/a
regime
accelerating from a flat base
windows
13w vs 39w
snapshot 1 of 1 ·· m5
commit Sharpereserved: <26 non-zero commit weeks
changepoint
none detected
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
2
reserved
4
shipped
recency-swing
commit-changepoint
reserved
commit-sharpe
code-leads-citation-lag
axis-alpha
gate-eta
snapshot 1 of 1 ·· m5
Measurement states
geo-score is under weekly measurement. History: 2 of 4 weekly observations. Development velocity axis: measured. Citation source: not measured. Direct-dependents axis: no admitted own package; not measured. Gate: not computable — history 2 of 4 weekly observations
Score derived from public data on Evidaxis methodology m5, never edited by hand. Cite as:
“Evidaxis, geo-score, entity e_92WY2183XK3, snapshot 2026-w42.”