One engineer, one week, a graph that observes Amplifier
The Context Intelligence Server captures Amplifier's own sessions as structured events and persists them as a graph. It watches the thing it was built with.
First, how much of it got built — and by how many people.
Diego Colombo was the sole author across 2026-03-13 to 03-19. The numbers are real, and they landed fast.
But a commit count doesn't tell you what he actually shipped.
Hundreds of commits don't tell you what was actually built or why it's different. Of the ~250, only 169 are first-parent and just one arrived as a merged pull request. Scale is the setup — not the point.
The point starts with a plan written before any code.
2026-03-13 held only two commits: the initial commit and a single design document for a FastAPI + Neo4j telemetry server — written before any code.
That plan defined the machinery: how sessions become a graph.
Live sessions POST in through a fire-and-forget ingest API and land in a Neo4j property graph — one path from event to structure.
Once ingestion worked, the build hardened around it.
POST /events — fire-and-forget, 5s timeout, failures logged as warningsAcross five active days (03-14 to 03-19) the graph grew from plumbing into a system that could replay, route, and stay up under load.
Hardened enough to finally watch a running system: itself.
The platform starts recording its own runtime into the graph — Amplifier watching itself run. Self-observation of runtime, made concrete.
Which reframes what the week was actually about.
From a bundle hook to a standalone graph that lets Amplifier see itself. The ~250 commits and ~19.6k lines were the means; the keeper is a system that observes its own sessions.
Self-observation, not just scale.
Feature status: Active on main
Repository: microsoft/amplifier-context-intelligence (branch main, HEAD 440bc5d, 549 total commits).
Data as of: week-1 window 2026-03-13 to 2026-03-19; snapshot metrics anchored to commit e5d88ce (2026-03-19 23:45).
Commands run:
git remote -v; git branch --show-current; git rev-parse HEAD; git rev-list --count HEADgit log --format='%ad' --date=format:'%Y-%m-%d' | sort | uniq -cgit log --since='2026-03-13' --until='2026-03-20' --format='%an <%ae>' | sort | uniq -c; feat/first-parent counts via grep -cE '^feat' and git log --first-parentgit ls-tree -r --name-only e5d88ce | grep '\.py$' piped through git show, wc -l, and grep -cE 'def test_|async def test_'grep -n '5 node / 8 edge' README.mdgrep -rin 'fire-and-forget' --include='*.md' .git show 0bb9e47 --stat (426 lines confirmed)git grep -l run_tokens e5d88ce; git grep -ln SystemEventHandler e5d88ceGaps & caveats: ~250 is the author-date grouping (235 under --since/--until commit-date semantics); 169 first-parent commits, 1 merged PR. run_tokens and SystemEventHandler were later refactored — anchored to snapshot e5d88ce, not main HEAD.
Primary contributor: Diego Colombo — sole author of the first week (533 repo-total commits).