Evidaxis

NeMo-RL

repo
Post-training & Alignment · n = 16 · NVIDIA-NeMo/RL
1 of 3 axes measurable · conf low
convergence gate
Convergence gate: Gate: not computable — 1 of 3 axes measurable Development velocity: rising vote Citation momentum: not measurable ∅ Direct-dependents momentum (deps.dev): not measurable ∅
gate
1 of 3 axes

Gate: not computable — 1 of 3 axes measurable

Gate: not computable — 1 of 3 axes measurable
position in cohort distribution one of 16 in cohort
percentile 87 within cohort p25 p50 p75 p0 p100
percentile
p87
momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
velocity z
velocity z gaugevelocity z+1.29 within cohort, log-slope +0.025/wk.0+1.29
velocity z
+1.29 σ
slope
+0.025/wk
log-slope +0.025/wk
citation z Citation source: not measured.
direct-dependents z Direct-dependents axis: no admitted own package; not measured.
cohort
16
systems measured
weekly commits
31.3
Development velocity axis: measured.
total citations
n/a
Citation source: not measured.
momentum
66.2
percentile p87
commit heatmap, last 26 weeks31.3/wk
weekly commits, 26 weeks26 weeks of commits, peak 54 in a week, 26 active weeks, 745 total.week 1: 11 commitsweek 2: 11 commitsweek 3: 9 commitsweek 4: 16 commitsweek 5: 17 commitsweek 6: 34 commitsweek 7: 23 commitsweek 8: 42 commitsweek 9: 23 commitsweek 10: 47 commitsweek 11: 36 commitsweek 12: 39 commitsweek 13: 36 commitsweek 14: 25 commitsweek 15: 26 commitsweek 16: 29 commitsweek 17: 28 commitsweek 18: 33 commitsweek 19: 44 commitsweek 20: 30 commitsweek 21: 36 commitsweek 22: 34 commitsweek 23: 25 commitsweek 24: 28 commitsweek 25: 54 commitsweek 26: 9 commits
weeks
26
peak/wk
54
active
26
total
745
citations by yearCitation source: not measured.

NeMo-RL holds an Evidaxis momentum score of 66.2 of 100 on methodology m4, snapshot 2026-10-10, measured within the Post-training & Alignment cohort (n = 16). Axis coverage: 1 of 3 axes measurable. Gate: not computable — 1 of 3 axes measurable

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 -0.42, regime recent slope sign differs from prior window. prior slope +0.036, recent slope -0.015 per week. +0.036prior 39w-0.015recent 13w-0.42×
swing
-0.42×
regime
recent slope sign differs from prior window
windows
13w vs 39w
snapshot 1 of 1 · · m4
commit-axis Sharpe log-linear slope over residual std, value +0.064 with 95% CI +0.046 to +0.083, 50 degrees of freedom. CI excludes zero.0+0.06495% CI +0.046, +0.083+0.046+0.083
sharpe
+0.064
95% ci
+0.046, +0.083
dof
50
snapshot 1 of 1 · · m4
commit changepoint52 weekly commit points. No significant changepoint detected (|delta slope| within the noise floor).no significant changepoint
changepoint
none detected
snapshot 1 of 1 · · m4
code-leads-citation lag reserved

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

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

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

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

reserved: needs snapshot history (1 snapshot exists)

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

Reconstructed history

NeMo-RL reconstructed weekly commits52 points, range 1 to 47 commits/wk.
min
1 commits/wk
max
47 commits/wk
latest
1 commits/wk
points
52

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

NeMo-RL is under weekly measurement. History: 15 weekly observations; minimum 4. Development velocity axis: measured. Citation source: not measured. Direct-dependents axis: no admitted own package; not measured. Gate: not computable — 1 of 3 axes measurable

Sources

NVIDIA-NeMo/RL development-velocity axis

Direct-dependents momentum (deps.dev)

Direct-dependents axis: no admitted own package; 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_QHYA574DXDQ methodology m4 snapshot ad5e404d4f82 period 2026-w41 record JSON ↓ source snapshot

Score derived from public data on Evidaxis methodology m4, never edited by hand. Cite as: “Evidaxis, NeMo-RL, entity e_QHYA574DXDQ, snapshot 2026-w41.”

Durable reference (format-independent): urn:evidaxis:claim:e_QHYA574DXDQ:m4:2026-10-10