Evidaxis

Microsoft Agent Framework

repo
Agent Frameworks · n = 16 · microsoft/agent-framework
2 of 3 axes measurable · conf medium
convergence gate
Convergence gate: Gate: computed weekly across the cohort; no convergence event this week Development velocity: measured × Citation momentum: not measurable ∅ Direct-dependents momentum (deps.dev): rising vote
gate
1 of 3 axes

Gate: computed weekly across the cohort; no convergence event this week

Gate: computed weekly across the cohort; no convergence event this week
position in cohort distribution one of 16 in cohort
percentile 93 within cohort p25 p50 p75 p0 p100
percentile
p93
momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
velocity z
velocity z gaugevelocity z+0.60 within cohort, log-slope +0.018/wk.0+0.60
velocity z
+0.60 σ
slope
+0.018/wk
log-slope +0.018/wk
citation z Citation source: not measured.
direct-dependents z
direct-dependents z gaugedirect-dependents z+2.34 within cohort, log-slope +0.078/point.0+2.34
direct-dependents z
+2.34 σ
slope
+0.078/point
Direct-dependents axis: measured.
cohort
16
systems measured
weekly commits
71.7
Development velocity axis: measured.
total citations
n/a
Citation source: not measured.
momentum
68.4
percentile p93
commit heatmap, last 26 weeks71.7/wk
weekly commits, 26 weeks26 weeks of commits, peak 132 in a week, 26 active weeks, 1604 total.week 1: 50 commitsweek 2: 35 commitsweek 3: 53 commitsweek 4: 59 commitsweek 5: 42 commitsweek 6: 50 commitsweek 7: 45 commitsweek 8: 49 commitsweek 9: 59 commitsweek 10: 65 commitsweek 11: 56 commitsweek 12: 73 commitsweek 13: 56 commitsweek 14: 52 commitsweek 15: 55 commitsweek 16: 33 commitsweek 17: 32 commitsweek 18: 70 commitsweek 19: 37 commitsweek 20: 74 commitsweek 21: 121 commitsweek 22: 132 commitsweek 23: 86 commitsweek 24: 116 commitsweek 25: 82 commitsweek 26: 22 commits
weeks
26
peak/wk
132
active
26
total
1604
citations by yearCitation source: not measured.
Daily dependents count (unscored) 26 dependents 26 direct · pypi/agent-framework · deps.dev · the scored m4 axis uses weekly partitions

Microsoft Agent Framework holds an Evidaxis momentum score of 68.4 of 100 on methodology m4, snapshot 2026-10-10, measured within the Agent Frameworks cohort (n = 16). Axis coverage: 2 of 3 axes measurable. Gate: computed weekly across the cohort; no convergence event this week

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.21, regime accelerating. prior slope +0.012, recent slope +0.040 per week. +0.012prior 39w+0.040recent 13w+3.21×
swing
+3.21×
regime
accelerating
windows
13w vs 39w
snapshot 1 of 1 · · m4
commit-axis Sharpe log-linear slope over residual std, value +0.021 with 95% CI -0.007 to +0.049, 50 degrees of freedom. CI spans zero.0+0.02195% CI -0.007, +0.049-0.007+0.049
sharpe
+0.021
95% ci
-0.007, +0.049
dof
50
snapshot 1 of 1 · · m4
commit changepoint52 weekly commit points. Changepoint at week 50 (2026-09-26), slope change -47.611 commits per week.2026-09-26
date
week
50 of 52
Δslope
-47.611/wk
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

Microsoft Agent Framework reconstructed weekly commits51 points, range 1 to 134 commits/wk.
min
1 commits/wk
max
134 commits/wk
latest
132 commits/wk
points
51

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)

Microsoft Agent Framework dependents over time15 points, range 0 to 26 dependents.
min
0 dependents
max
26 dependents
latest
26 dependents
points
15

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

Measurement states

Microsoft Agent Framework is under weekly measurement. History: 15 weekly observations; minimum 4. Development velocity axis: measured. Citation source: not measured. Direct-dependents axis: measured. Gate: computed weekly across the cohort; no convergence event this week

Sources

microsoft/agent-framework development-velocity axis

Direct-dependents momentum (deps.dev)

Direct-dependents axis: measured.

Coverage state
scored
Cohort z
+2.34
OLS slope
+0.078
Theil-Sen slope
+0.077
Latest direct dependents
26
Confirmed-clean points
26
Reconstructed history points
15
As-of partition
2026-09-28
Fragility veto
inactive
Rising vote
yes

This axis measures the trajectory of a system's own packages: declared in its own tree, published under that name, and not attributed by deps.dev to another repository. A package with no repository link is unverified and stays. The self-name exclusion list is fixed at the v2h.1 panel. Systems with no admitted package are not measured on this axis. Points that cannot be derived exactly are withheld, and the series restarts after a withheld point.

The earliest weekly points of each series were read from deps.dev's BigQuery history on 2026-07-21; later points are weekly captures. m4 does not replay those partitions: each point is the stored system total, one package's unique_direct, or a complete sketch union, and a point that is not exact is withheld. Each record reports how many of its points are reconstructed history.

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_M5SCCQPBZ89 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, Microsoft Agent Framework, entity e_M5SCCQPBZ89, snapshot 2026-w41.”

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