Anthropic APIs to S3 archive, Athena, Bedrock AI layer, and the 19-page React dashboard
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Beyond the 90-Day Window
• A Node 20 Lambda snapshots Analytics and Compliance daily into S3 NDJSON partitions
• Raw record sidecars under raw/ keep unmapped API fields recoverable
• Glue partition projection exposes six tables per org to Athena
S3-First Serving
• Range queries hit the archive first; only missing dates go to the live API
• Responses carry s3_hits / live_calls hints for freshness diagnosis
• splitCostWindow() merges 31-day chunks into windows up to 186 days
AI Guardrails
• Bedrock Claude Sonnet 4.6 answers via ConverseStream with five chat tools
• User and LLM SQL pass the same SELECT-only, allowlist sanitizer
• Emails are masked in UI and LLM output as a data contract
Data-flow diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export