CODE, HISTORY, DOCUMENTATION, AND ARCHITECTURE — ONE MAP SOURCE-BACKED ENGINEERING INTELLIGENCE

From synchronized sources to verifiable impact

See your whole system.
Understand every change.

Connect GitHub and Notion. Map architecture, trace dependencies, and verify change impact with source-backed evidence.

Run an impact analysis See how it works
INGEST GitHub code and history + selected Notion knowledgeMODEL Architecture, symbols, APIs, and cross-repository pathsANALYZE Planned changes and pull requests with cited evidence
impact-analysis.atlas
Illustrative proposed changeReplace persistent session tokens with rotating refresh tokens.
Tracing code, GitHub history, and Notion decisions96%
7 affected components
4 relevant pull requests
2 cross-repo paths
01 / SyncGitHub intelligenceCode, PR authors, review outcomes, mergers, and bounded history
02 / ContextNotion knowledgeSelected specifications, ADRs, runbooks, pages, and data sources
03 / MapLiving system graphPackages, files, symbols, APIs, dependencies, and architecture
04 / AnalyzeVerifiable change impactRisk, affected paths, evidence, unknowns, and verification steps

01 — WHY ATLAS

Your system is more than source code.
Its history and decisions matter too.

Codewhat existsHistoryhow it evolvedContextwhy it existsImpactwhat changes next
AtlasSystem
understanding

Atlas connects code, change history, and engineering decisions in one explorable map—so teams can understand what exists, why it exists, and what a change will affect.

02 — CONNECTED SOURCES

Synchronize the sources
that explain your system.

Index approved GitHub repositories and Notion pages, then connect code relationships to the decisions that explain them.

  • GitHub code, revisions, commits, pull requests, authors, and reviews
  • Selected Notion specifications, ADRs, runbooks, pages, and data sources
  • Incremental, retryable synchronization with source revision and citation metadata
Explore connected sources
GitHub + Notion context graph Sources synchronized

03 — CHANGE INTELLIGENCE

Explore the system.
Then analyze the change.

Explore architecture and search indexed sources. Analyze a plan or pull request to reveal risk, downstream paths, evidence, and verification steps.

ChangeDirect impactDownstreamEvidence

What happens if we change the refresh-token response?

identity-service · main
HIGH
RISK
Executive summary

This contract crosses three repository boundaries.

The gateway validator and storefront edge middleware require coordinated updates. One external mobile consumer cannot be verified.

SessionController.refresh()

Response contract changes at lines 84–112

observed
storefront-web / edge middleware

Reads the existing sessionToken field

observed
Mobile authentication clients

Mentioned in ADR-024; repository unavailable

inferred

04 — TRUST BY DESIGN

Evidence stays attached.
Uncertainty stays visible.

Trace every finding to code, history, or selected Notion context. Atlas labels evidence, inference, and unknowns clearly.

CODE · OBSERVEDSessionController.refresh

identity-service/src/session/session.controller.ts

return this.sessions.rotate(refreshTokenId);
GITHUB · HISTORICALPR #401 — Rotate compromised sessions

8 files · reviewed by Maya Chen

NOTION · DECISIONADR-024 — Token rotation

Edited by Maya Chen · 6 weeks ago · editor observed at sync

atlas

Build a living map
your team can act on.

Connect your sources, explore the system, and verify the next change before it ships.

Open the workspace