Evidaxis

Microsoft Agent Framework

repo
Agent Frameworks · n = 17 · microsoft/agent-framework
Single-axis · conf low
momentum
momentum 46.4 of 100 46.4 /100
momentum
46.4/100
pctile
p31
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 17 in cohort
percentile 31 within cohort p25 p50 p75 p0 p100
percentile
p31
momentum is the combined velocity and citation signal, percentile within cohort
velocity z
velocity z gaugevelocity z-0.29 within cohort, log-slope -0.003/wk.0-0.29
velocity z
-0.29 σ
slope
-0.003/wk
log-slope -0.003/wk
convergence planefull gate = rising
Microsoft Agent Framework on the convergence plane Microsoft Agent Framework at velocity z -0.29 and citation z no axis, against 3 dual-axis cohort peers. single-axis: citation axis absent, excluded from the plane. z>=1 median velocity z → citation z ↑ CAMEL: velocity z -0.97, citation z +0.00 Letta: velocity z -3.04, citation z -0.67 MetaGPT: velocity z +0.48, citation z +1.33
velocity z
-0.29
citation z
no axis
peers
16

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

citation z no citation axis
cohort
17
systems measured
weekly commits
52.9
not rising
total citations
n/a
no axis
momentum
46.4
percentile p31
commit heatmap, last 26 weeks52.9/wk
weekly commits, 26 weeks26 weeks of commits, peak 78 in a week, 26 active weeks, 1367 total.week 1: 65 commitsweek 2: 78 commitsweek 3: 59 commitsweek 4: 66 commitsweek 5: 48 commitsweek 6: 44 commitsweek 7: 39 commitsweek 8: 68 commitsweek 9: 29 commitsweek 10: 39 commitsweek 11: 50 commitsweek 12: 35 commitsweek 13: 53 commitsweek 14: 59 commitsweek 15: 42 commitsweek 16: 50 commitsweek 17: 45 commitsweek 18: 49 commitsweek 19: 59 commitsweek 20: 65 commitsweek 21: 56 commitsweek 22: 73 commitsweek 23: 56 commitsweek 24: 52 commitsweek 25: 55 commitsweek 26: 33 commits
weeks
26
peak/wk
78
active
26
total
1367
citations by yearno axis
adoption 0 dependents 0 direct · pypi/agent-framework · deps.dev · adoption signal, not part of the momentum score

Microsoft Agent Framework holds an Evidaxis momentum score of 46.4 of 100 on methodology m2, snapshot 2026-08-08, measured within the Agent Frameworks cohort (n = 17). 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 -0.91, regime reversing. prior slope +0.003, recent slope -0.003 per week. +0.003prior 39w-0.003recent 13w-0.91×
swing
-0.91×
regime
reversing
windows
13w vs 39w
snapshot 1 of 1 · · m2
commit-axis Sharpe log-linear slope over residual std, value +0.011 with 95% CI -0.019 to +0.040, 50 degrees of freedom. CI spans zero.0+0.01195% CI -0.019, +0.040-0.019+0.040
sharpe
+0.011
95% ci
-0.019, +0.040
dof
50
snapshot 1 of 1 · · m2
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 · · 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

Microsoft Agent Framework dependents over time6 points, range 0 to 0 dependents.
min
0 dependents
max
0 dependents
latest
0 dependents
points
6

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

Verdict

Microsoft Agent Framework 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

microsoft/agent-framework development-velocity axis

Embed this badge

Evidaxis single-axis, Microsoft Agent Framework
[![Evidaxis: Microsoft Agent Framework](https://evidaxis.org/badge/e_M5SCCQPBZ89/2026-w32.svg)](https://evidaxis.org/e/e_M5SCCQPBZ89)

Others in Agent Frameworks

AgentScope Agent Frameworks
Watch
88
p100
vel +3.02 cit no axis
axis dials
+3.02 n/a
Agno Agent Frameworks
Single-axis
48
p44
vel -0.20 cit no axis
axis dials
-0.20 n/a
AutoGen Agent Frameworks
Calibration
51
p50
vel +0.05 cit no axis
axis dials
+0.05 n/a
CAMEL Agent Frameworks
Tracked
44
p25
vel -0.97 cit +0.00
axis dials
-0.97 +0.00
CrewAI Agent Frameworks
Single-axis
55
p62
vel +0.43 cit no axis
axis dials
+0.43 n/a
DSPy Agent Frameworks
Single-axis
47
p38
vel -0.26 cit no axis
axis dials
-0.26 n/a

Full Agent Frameworks cohort →

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

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