Showcase Archive

Monthly, story-driven case studies. Each showcase ships with a report and a compressed evidence bundle.

July 2026
Featured
Repository Context Strategies After Revision
A second cross-language evaluation cycle: new PViz-guided and bundle-only runs across the same seven repositories, presented alongside a historical raw-source-exploration baseline from the prior cycle.
GoJavaLLM evaluationagent toolingrepository analysis
56 new assessed sessions (PViz + Solo) across the same 28 tasks and seven repositories as the prior cycle; the Raw baseline was reused rather than re-run against unchanged repositories.
Open →
June 2026
Repository Context Strategies for Codebase Analysis Agents
A controlled cross-language evaluation of raw source exploration, PViz-guided source reads, and bundle-only analysis.
GoJavaLLM evaluationagent toolingrepository analysis
84 assessed sessions across 28 tasks, seven repositories, and three repository-context strategies.
Open →
May 2026
VSCode: Turning a 72 MB Bundle into Focused Architecture Views
How PViz slicing extracts fifteen purpose-built analysis artifacts from a single canonical bundle — 10,311 nodes, 92,011 edges, ranging from 2 KB to 3 MB.
microsoft/vscodeTypeScriptJavaScriptslicingdependency-analysisarchitecture
A single 72 MB PViz bundle becomes 15 focused architecture views, each under 5% of the source bundle.
Open →
April 2026
Scrapy: Structural Evolution Across 68 Iterations
How a 66-node dependency cycle was traced, measured, and systematically broken using PViz structural analysis.
scrapy/scrapyPythonSCC analysisdependency cyclesrefactoring
Scrapy's dependency graph began as a single 66-node conceptual SCC spanning orchestration, HTTP, spiders, and settings.
Open →
February 2026
FastAPI Structural Evolution: v0.20 → v0.129
How FastAPI's internal architecture evolved across 7 years and 9 versions — dependency graph analysis tracking God Modules, circular dependencies, and the Pydantic v2 migration.
fastapi/fastapiPythonGod Module patterncircular dependency resolutionPydantic v2 migration impact
Within-file complexity spike during Pydantic v2 migration
Open →