Every product on CommsLink is designed and shipped to production by an AI — live, most days. This is the raw record, generated straight from the commit history. No hand-picking, no polish: 2,359 ships and counting.
Atlas: underground = shared electric PIPES not train tracks — dedup segments (one pipe per grid segment, no overlap), 3x deeper, solid glowing lines, centerline routes (v0.0.21)
Atlas: subway rides the GRID — client links route on the road grid (off-grid page spurs onto it) + render as tracks underground following the routed path, sharing segments (v0.0.20)
Atlas: client links as a SUBWAY — page->endpoint connections become rails-with-ties ramping under the city, glowing up through the ground (replaces the pink lines) (v0.0.19)
Atlas: click a line to see what it connects + clients as houses (pyramid roofs) + client HTTP roads in a distinct pink color (v0.0.18)
Atlas: FIX handlers/actions buried inside 2x-taller buildings (lift roof members to new roof) + scatter unconnected clouds along the border instead of a vertical stack (v0.0.17)
Atlas: fix camera orbit (fallback to a changed node when no explicit focus) + diff inspector panel on click (transparent, X to close) + bundled architecture guide for teaching AI (v0.0.16)
Atlas: edge routing v3 — exit to NEAREST road (short on-ramp, more corners), lanes within road width (overlap ok), enter buildings from closest road point; verified 0 off-road interior vertices on real data (v0.0.15)
Atlas: FIX edge routing — route per-grid on each grid's real roads, cross between grids only on a shared avenue (the two grids have different scales; merging their coords put lines on non-existent roads) (v0.0.14)
Atlas: full Manhattan edge routing — turn at street corners (node → vertical street → avenue → target street), per-street lanes (v0.0.13)
Atlas: wire street-routed edges — reads/writes/calls run orthogonally along avenues in parallel lanes, shown at rest (v0.0.12)
Atlas: bloom glow (UnrealBloomPass) + street curbs glow with dashed center + 2x module/datastore height; routeEdges module + tests (not yet wired) (v0.0.11)
Atlas: neon Tron streets (glowing centerlines) + scale modules & datastores by line count (v0.0.10)
Atlas: Tron pass — neon additive edge outlines per element (fill stays semantic) + deeper background for contrast (v0.0.9)
Atlas: milestone celebrations — fireworks + chime + banner on commit (green) / push (blue), with a mute toggle (v0.0.8)
Atlas: changed nodes signal via GOLD borders + gold titles (fill color untouched); distinctive isometric icon + colored status bar/tab (v0.0.7)
Atlas extension: always-visible launchers — Activity Bar icon + Status Bar button (no file needed) (v0.0.6)
Atlas activity: district-level glow + clickable cycle pill + Changes list panel (navigate the diff through the map, v0.0.5)
Atlas extension: live git-activity layer — glow uncommitted-change nodes amber + orbit the file being edited (v0.0.4)
Medusa (Shopify) + Medplum (healthcare/FHIR) importers — file-based + Express parsers, pinned meta.domain grouping
Add Cal.com (Calendly) tRPC gallery example + tRPC router-grouping fix (skip generic procedures/handlers dirs)
TRPC importer — procedures→endpoints (query=read, mutation=write) + Prisma access; extract Documenso (267 procedures) as a real tRPC gallery example (7 tests)
Model picker in chat — <AtlasViewer models> dropdown; extension enumerates vscode.lm models (Copilot exposes Claude/GPT) + user key, routes ask() to the chosen model
Chat fallback — editor model (Copilot) → user's own OpenAI-compatible API key → graceful msg, so 'Ask your architecture' works for anyone (incl. Cursor/no-Copilot); map always works with no LLM
Atlas ext: add map-icon button to the editor toolbar; README leads with the user flow (install → click map icon → see your open project)
VS Code/Cursor extension scaffold (packages/atlas-vscode) — thin host+webview shell reusing the extractor + <AtlasViewer>; builds both bundles, F5-launchable
Extract shared <AtlasViewer> (canvas+sidebar+chat) from page.tsx — page now injects graph+ask; the single-codebase seam for the VS Code/Cursor extension
Detect S3 asset buckets referenced in next.config.js → the commslink-assets bucket now shows on the CommsLink map (web reads from S3)
Atlas vision: guiding light — local MVP, 'watch the agent build' live diff+camera, live telemetry (cars on roads) seam, terminal-context awareness
Atlas roadmap: extension strategy (big-3 editors, no fork), ladder business model, thin-shells-over-shared-core
Webhook endpoints badged distinctly (WEBHOOK) in module contents + detail, so they're identifiable when clicking a domain
Clickable domain buildings (module → lists its endpoints/handlers/actions) + reconcile Cursor outline-toggle onto EC2
Next.js API-route importer + monorepo Prisma discovery → extract dub (bit.ly) as first REAL company: 194 pages, 175 API routes, 116 tables, full-stack
Fix invisible page-phantoms bloating api container (exclude client nodes from backend zone); AWS account always shown as foundation border; pages served-by web module (removed nonsensical Users->page); reverted off-grid compaction
Users node + page-load 'requests' edges (the basic HTTP GET-page requests, distinct from API calls) + compact off-grid block (api container 382→224 deep)
Atlas docs: full-stack front-end city (Next.js client extraction)
Full-stack — front-end extractor (Next.js routes + client API calls) renders the CLIENT as its own city outside the gates, wired to the backend endpoints
AWS account is a dashed BORDER (not a plane) — servers stay their own cities, databases on their own separate plane
Lambdas off the EC2 — serverless base = AWS account (not EC2), no container box for managed resources, each Lambda/compute gets its own raised plane
De-clutter grants (drop bold roads → quiet lines + guarded-vault checkpoint) + MMO/AI-training/AI-RAG gallery examples
Atlas docs: grant-roads + checkpoints, EC2/ECS/Fargate compute, containment model
Grant roads + police checkpoints (DUI barricade + flashing cruiser to vaults) + EC2/ECS/Fargate compute
Atlas docs: record CDK importer, AWS city vocabulary, telemetry opt-in-overlay decision
CDK-as-TypeScript importer — Lambdas as tents, IAM grants as roads (AWS-native extraction + city vocabulary)
Docs: bring README lab-suite update from PR #3 onto main (Atlas CITY-1g preserved)
Atlas CITY-1g: externals as clouds (outbound, over consumers); webhooks as helicopters; clouds pickable
Atlas CITY-1f: helipads (air network) — buildings that call out get a fenced pad; helicopters on islands
Atlas CITY-1e: remove fake harbor; external islands sized by dependency count, routes on focus
Atlas CITY-1d: table road grid + orphan-table sorting (unused tables off to the side)
Atlas CITY-1c: buildings = modules (endpoints=doors, handlers=machines, actions=people); off-grid inside container; uniform roads
Atlas CITY-1b: street grid between blocks + off-grid module sorting (stateless districts detached)
Atlas CITY-1a: quiet edges + data avenue + coastline (mainland + offshore island externals)
Atlas CITY-0: generic model + example-architecture gallery (serverless/3-tier/event-driven)
Atlas CITY-0: generic city-role model + doc plan
Atlas UI: scale fog + clip planes to scene so buildings stay visible when zoomed out
Atlas UI: infra nesting (EC2 host + containers, tables grouped in mysql)
Infrastructure layer — EC2 host + containers from docker-compose
Docs: Atlas Phase 4 (talk to your architecture) shipped — end goal met
Atlas Phase 4: talk to your architecture (GraphRAG /api/v1/atlas/ask + chat panel)
Atlas Phase 3: self-updating architecture doc at /atlas/architecture
Atlas Phase 3: living architecture doc generator (graph → Markdown)
Docs: Atlas Phase 2b (handler nodes + LLM tier) shipped
Atlas Phase 2b: handler nodes + LLM-inferred edges on the 3D map
Atlas Phase 2b: handler nodes + Tier-2 LLM edge extraction (grounded, provenance-tagged)
Docs: Atlas Phase 2 external-services slice shipped
Atlas Phase 2: external services on the 3D map (arteries out of the system)
Atlas Phase 2: external-service extraction from adapters (Stripe/Polly/Grok/Anthropic/AWS/…)
Docs: mark Atlas Phase 1 (3D map at /atlas) done
Atlas Phase 1: 3D architecture map at /atlas (nested districts, data-flow highlight)
Nested-district layout unit test
Atlas Phase 0: deterministic graph substrate (endpoints/actions/datastores + provenance)
Add Atlas app card + about page to landing
Generated 2026-07-16 from git across all CommsLink repos · page 3/3, showing 201–271 of 271 Atlas ships · complete record: /changelog.txt · /changelog.json.