Evidaxis

mem0

repo
Unassigned (AI-v1 census) · n = 77 · mem0ai/mem0
1 of 3 axes measurable · conf low
convergence gate
Convergence gate: Gate: not computable — history 3 of 4 weekly observations Development velocity: measured × Citation momentum: not measurable Direct-dependents momentum (deps.dev): not measurable
gate
0 of 3 axes

Gate: not computable — history 3 of 4 weekly observations

Gate: not computable — history 3 of 4 weekly observations
position in cohort distribution one of 77 in cohort
percentile 14 within cohort p25 p50 p75 p0 p100
percentile
p14
momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
velocity z
velocity z gaugevelocity z-0.75 within cohort, log-slope -0.035/wk.0-0.75
velocity z
-0.75 σ
slope
-0.035/wk
log-slope -0.035/wk
citation z Citation source: not measured.
direct-dependents z Direct-dependents axis: outside the frozen panel; not measured.
cohort
77
systems measured
weekly commits
19.2
Development velocity axis: measured.
total citations
n/a
Citation source: not measured.
momentum
40.6
percentile p14
commit heatmap, last 26 weeks19.2/wk
weekly commits, 26 weeks26 weeks of commits, peak 62 in a week, 26 active weeks, 650 total.week 1: 55 commitsweek 2: 48 commitsweek 3: 19 commitsweek 4: 33 commitsweek 5: 23 commitsweek 6: 8 commitsweek 7: 10 commitsweek 8: 11 commitsweek 9: 15 commitsweek 10: 19 commitsweek 11: 15 commitsweek 12: 45 commitsweek 13: 56 commitsweek 14: 62 commitsweek 15: 24 commitsweek 16: 47 commitsweek 17: 9 commitsweek 18: 32 commitsweek 19: 20 commitsweek 20: 30 commitsweek 21: 24 commitsweek 22: 12 commitsweek 23: 10 commitsweek 24: 5 commitsweek 25: 4 commitsweek 26: 14 commits
weeks
26
peak/wk
62
active
26
total
650
citations by yearCitation source: not measured.

mem0 holds an Evidaxis momentum score of 40.6 of 100 on methodology m3, snapshot 2026-09-19, measured within the Unassigned (AI-v1 census) cohort (n = 77). Axis coverage: 1 of 3 axes measurable. Gate: not computable — history 3 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.

recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio -2.94, regime recent slope sign differs from prior window. prior slope +0.049, recent slope -0.145 per week. +0.049prior 39w-0.145recent 13w-2.94×
swing
-2.94×
regime
recent slope sign differs from prior window
windows
13w vs 39w
snapshot 1 of 1 · · m3
commit-axis Sharpe log-linear slope over residual std, value +0.036 with 95% CI -0.004 to +0.075, 50 degrees of freedom. CI spans zero.0+0.03695% CI -0.004, +0.075-0.004+0.075
sharpe
+0.036
95% ci
-0.004, +0.075
dof
50
snapshot 1 of 1 · · m3
commit changepoint52 weekly commit points. Changepoint at week 39 (2026-06-20), slope change -4.189 commits per week.2026-06-20
date
week
39 of 52
Δslope
-4.189/wk
snapshot 1 of 1 · · m3
code-leads-citation lag reserved

reserved: citation series too short / axis absent for cross-correlation

status
reserved
value
insufficient data
snapshot 1 of 1 · · m3
axis alpha vs cohort reserved

reserved: cohort N too small for regression (power ~0)

status
reserved
value
insufficient data
snapshot 1 of 1 · · m3
gate ETA reserved

reserved: needs snapshot history (1 snapshot exists)

status
reserved
value
insufficient history
snapshot 1 of 1 · · m3
methodology gate snapshot 1 of 1 · · m3
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 · · m3

Reconstructed history

mem0 reconstructed weekly commits47 points, range 1 to 62 commits/wk.
min
1 commits/wk
max
62 commits/wk
latest
14 commits/wk
points
47

Weekly commits over the past year, reconstructed from git history (GitHub commit_activity). This is reconstructed, not a point-in-time capture. Evidaxis captures the Type-2 signals (watchers, issues, dependents) live and never backfills them; those are the moat.

Measurement states

mem0 is under weekly measurement. History: 3 of 4 weekly observations. Development velocity axis: measured. Citation source: not measured. Direct-dependents axis: outside the frozen panel; not measured. Gate: not computable — history 3 of 4 weekly observations

Sources

mem0ai/mem0 development-velocity axis

Direct-dependents momentum (deps.dev)

Direct-dependents axis: outside the frozen panel; not measured.

Coverage state
out_of_panel
Cohort z
no axis
OLS slope
n/a
Theil-Sen slope
n/a
Latest direct dependents
n/a
Confirmed-clean points
n/a
Reconstructed history points
n/a
As-of partition
n/a
Fragility veto
n/a
Rising vote
no

Source: deps.dev (Google), CC-BY 4.0. Modified: aggregated to system-level counts and momentum scores.

Axis definition · Snapshot axis correlations

entity_id e_TEVNVWBZ8HJ methodology m3 snapshot fcfd3a7ccdcb period 2026-w38 record JSON ↓ source snapshot

Score derived from public data on Evidaxis methodology m3, never edited by hand. Cite as: “Evidaxis, mem0, entity e_TEVNVWBZ8HJ, snapshot 2026-w38.”

Durable reference (format-independent): urn:evidaxis:claim:e_TEVNVWBZ8HJ:m3:2026-09-19