Evidaxis

ms-swift

repo
Post-training & Alignment · n = 14 · modelscope/ms-swift
Single-axis · conf low
momentum
momentum 49.8 of 100 49.8 /100
momentum
49.8/100
pctile
p54
convergence gate
Convergence gate: velocity only, citation axis absent ×
gate
0 of 2 axes

velocity only, citation axis absent.

gate shut
position in cohort distribution one of 14 in cohort
percentile 54 within cohort p25 p50 p75 p0 p100
percentile
p54
momentum is the combined velocity and citation signal, percentile within cohort
velocity z
velocity z gaugevelocity z-0.02 within cohort, log-slope -0.006/wk.0-0.02
velocity z
-0.02 σ
slope
-0.006/wk
log-slope -0.006/wk
convergence planefull gate = rising
ms-swift on the convergence plane ms-swift at velocity z -0.02 and citation z no axis, against 0 dual-axis cohort peers. single-axis: citation axis absent, excluded from the plane. z>=1 median velocity z → citation z ↑
velocity z
-0.02
citation z
no axis
peers
13

single-axis: citation axis absent, excluded from the plane.

citation z no citation axis
cohort
14
systems measured
weekly commits
20.4
not rising
total citations
n/a
no axis
momentum
49.8
percentile p54
commit heatmap, last 26 weeks20.4/wk
weekly commits, 26 weeks26 weeks of commits, peak 43 in a week, 26 active weeks, 584 total.week 1: 12 commitsweek 2: 13 commitsweek 3: 28 commitsweek 4: 31 commitsweek 5: 43 commitsweek 6: 10 commitsweek 7: 23 commitsweek 8: 23 commitsweek 9: 27 commitsweek 10: 26 commitsweek 11: 32 commitsweek 12: 21 commitsweek 13: 22 commitsweek 14: 28 commitsweek 15: 21 commitsweek 16: 15 commitsweek 17: 34 commitsweek 18: 27 commitsweek 19: 25 commitsweek 20: 18 commitsweek 21: 12 commitsweek 22: 25 commitsweek 23: 13 commitsweek 24: 16 commitsweek 25: 18 commitsweek 26: 21 commits
weeks
26
peak/wk
43
active
26
total
584
citations by yearno axis
adoption 0 dependents 0 direct · pypi/ms-swift · deps.dev · adoption signal, not part of the momentum score

ms-swift holds an Evidaxis momentum score of 49.8 of 100 on methodology m2, snapshot 2026-08-08, measured within the Post-training & Alignment cohort (n = 14). No axis is currently rising within the cohort, and no second (citation) axis is available, so it sits below the two-axis gate.

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 +3.99, regime accelerating. prior slope -0.008, recent slope -0.032 per week. -0.008prior 39w-0.032recent 13w+3.99×
swing
+3.99×
regime
accelerating
windows
13w vs 39w
snapshot 1 of 1 · · m2
commit-axis Sharpe log-linear slope over residual std, value -0.024 with 95% CI -0.048 to +0.000, 50 degrees of freedom. CI spans zero.0-0.02495% CI -0.048, +0.000-0.048+0.000
sharpe
-0.024
95% ci
-0.048, +0.000
dof
50
snapshot 1 of 1 · · m2
commit changepoint52 weekly commit points. Changepoint at week 5 (2025-09-13), slope change +3.016 commits per week.2025-09-13
date
week
5 of 52
Δslope
+3.016/wk
snapshot 1 of 1 · · m2
code-leads-citation lag reserved

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

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

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

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

reserved: needs snapshot history (1 snapshot exists)

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

Adoption trend

ms-swift dependents over time5 points, range 0 to 4 dependents.
min
0 dependents
max
4 dependents
latest
0 dependents
points
5

Downstream packages depending on pypi/ms-swift (deps.dev), captured point-in-time each snapshot. An adoption signal, not part of the momentum score.

Verdict

ms-swift is tracked. No axis is currently rising relative to its cohort, and it has no second (citation) axis available.

Path to Rising: needs development velocity to turn positive within its cohort; a second measurable axis to exist (no academic paper is currently tracked).

Sources

modelscope/ms-swift development-velocity axis

Embed this badge

Evidaxis single-axis, ms-swift
[![Evidaxis: ms-swift](https://evidaxis.org/badge/e_FJPV9XH9GPR/2026-w32.svg)](https://evidaxis.org/e/e_FJPV9XH9GPR)
entity_id e_FJPV9XH9GPR methodology m2 snapshot 035a72a81e59 period 2026-w32 record JSON ↓ source snapshot

Score derived from public data on Evidaxis methodology m2, never edited by hand. Cite as: “Evidaxis, ms-swift, entity e_FJPV9XH9GPR, snapshot 2026-w32.”

Durable reference (format-independent): urn:evidaxis:claim:e_FJPV9XH9GPR:m2:2026-08-08