Evidaxis

verl

repo
Post-training & Alignment · n = 16 · verl-project/verl
1 of 3 axes measurable · conf low
convergence gate
Convergence gate: Gate: not computable — 1 of 3 axes measurable Development velocity: measured × Citation momentum: not measurable ∅ Direct-dependents momentum (deps.dev): not measurable ∅
gate
0 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 20 within cohort p25 p50 p75 p0 p100
percentile
p20
momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
velocity z
velocity z gaugevelocity z-1.49 within cohort, log-slope -0.014/wk.0-1.49
velocity z
-1.49 σ
slope
-0.014/wk
log-slope -0.014/wk
citation z Citation source: not measured.
direct-dependents z Direct-dependents axis: minimum of 14 usable points of the new quantity and 5 latest dependents not met.
cohort
16
systems measured
weekly commits
25.2
Development velocity axis: measured.
total citations
n/a
Citation source: not measured.
momentum
31.4
percentile p20
commit heatmap, last 26 weeks25.2/wk
weekly commits, 26 weeks26 weeks of commits, peak 42 in a week, 26 active weeks, 727 total.week 1: 42 commitsweek 2: 32 commitsweek 3: 36 commitsweek 4: 35 commitsweek 5: 31 commitsweek 6: 24 commitsweek 7: 22 commitsweek 8: 26 commitsweek 9: 38 commitsweek 10: 28 commitsweek 11: 24 commitsweek 12: 26 commitsweek 13: 27 commitsweek 14: 34 commitsweek 15: 26 commitsweek 16: 27 commitsweek 17: 31 commitsweek 18: 18 commitsweek 19: 29 commitsweek 20: 21 commitsweek 21: 18 commitsweek 22: 31 commitsweek 23: 25 commitsweek 24: 28 commitsweek 25: 21 commitsweek 26: 27 commits
weeks
26
peak/wk
42
active
26
total
727
citations by yearCitation source: not measured.
Daily dependents count (unscored) 0 dependents 0 direct · pypi/verl · deps.dev · the scored m5 axis uses weekly partitions

verl holds an Evidaxis momentum score of 31.4 of 100 on methodology m5, snapshot 2026-11-07, 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 +1.74, regime accelerating. prior slope -0.007, recent slope -0.012 per week. -0.007prior 39w-0.012recent 13w+1.74×
swing
+1.74×
regime
accelerating
windows
13w vs 39w
snapshot 1 of 1 · · m5
commit-axis Sharpe log-linear slope over residual std, value -0.033 with 95% CI -0.051 to -0.015, 50 degrees of freedom. CI spans zero.0-0.03395% CI -0.051, -0.015-0.051-0.015
sharpe
-0.033
95% ci
-0.051, -0.015
dof
50
snapshot 1 of 1 · · m5
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 · · m5
code-leads-citation lag reserved

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

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

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

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

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

Reconstructed history

verl reconstructed weekly commits52 points, range 4 to 47 commits/wk.
min
4 commits/wk
max
47 commits/wk
latest
4 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.

Daily dependents count (unscored)

verl dependents over time19 points, range 0 to 1 dependents.
min
0 dependents
max
1 dependents
latest
0 dependents
points
19

Downstream packages depending on pypi/verl (deps.dev), captured point-in-time each snapshot. This daily series is unscored. The scored axis in m5 uses weekly partitions.

Measurement states

verl is under weekly measurement. History: 19 weekly observations; minimum 4. Development velocity axis: measured. Citation source: not measured. Direct-dependents axis: minimum of 14 usable points of the new quantity and 5 latest dependents not met. Gate: not computable — 1 of 3 axes measurable

Sources

verl-project/verl development-velocity axis

Direct-dependents momentum (deps.dev)

Direct-dependents axis: minimum of 14 usable points of the new quantity and 5 latest dependents not met.

Coverage state
below_floor
Cohort z
no axis
OLS slope
n/a
Theil-Sen slope
n/a
Latest direct dependents
n/a
Confirmed-clean points
0
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_607VJ9XWYRJ methodology m5 snapshot 868e3c39d9c7 period 2026-w45 record JSON ↓ source snapshot

Score derived from public data on Evidaxis methodology m5, never edited by hand. Cite as: “Evidaxis, verl, entity e_607VJ9XWYRJ, snapshot 2026-w45.”

Durable reference (format-independent): urn:evidaxis:claim:e_607VJ9XWYRJ:m5:2026-11-07