⚡ Evolution Velocity

Milestones & turning points per week · cumulative acceleration · era boundaries · 2026-W09 to W22
source: thread-evolution-structure.json · 5 eras E4–E8 · 68 milestones · 25 turning points · all grounded in real msg IDs
HubEra TimelineTree / BranchesFlowchartEmergenceMetricsVelocityCapabilities
68milestones
25turning points
14weeks
4.9ms / week avg
W12peak week
E4 Memory Pipeline · W09–W10 E5 Builtin Hybrid · W11 E6 KERNEL.md · W11–W16 E7 Wiki-Native · W17–W20 E8 Self-Improving · W21–W22
8
Peak Week (W12)
Densest build sprint: all Memory phases complete, Plan-First Protocol, ACK watchdog
26
E6 Milestones
38% of all milestones in one era (6 weeks). System's heaviest build period.
4
Peak TPs (W19)
SessionStart bug found, QMD crash fixed, Adoption Radar, identity restored
100%
Recall at W22
From 96.7% baseline in W16 → 100% perfect score by W21

Milestones per Week + Turning Points

Bars = milestones shipped · dots above bar = turning points · shaded bands = era boundaries
Milestones shipped (bar height)
Turning points (dot = 1 TP)
Era band (background tint)

Cumulative Milestones — Running Total

Slope = pace of evolution · steeper = faster build · era transitions visible as inflection points
Cumulative milestones (total = 68)
Weekly data point

Memory Recall Trajectory

Alongside velocity — how recall quality evolved as capabilities were built. 5 data points from real eval runs.
Recall % (eval corpus)
Data source: thread-evolution-structure.json — 5836 Discord messages · 14 weekly chunks W09–W22 · every milestone & turning point grounded in real msg IDs · no fabricated counts.

W15 = 0 turning points (real — a consolidation/bugfix week). W17, W20 = 0 TPs (real — build-heavy but no architectural pivots).