Ridge Admin, ridged, SQL execution, durable storage, and trust boundaries
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
Primary flow
• The browser never connects directly to Ridge or SSH
• Ridge Admin owns sessions, transactions, cancellation, and cleanup
• ridged maps pgwire sessions to the same Ridge SQL and storage contracts
Security limits
• Both HTTP and ridged listeners bind to loopback
• Secrets stay out of profiles and are zeroized from process memory
• Unsupported protocol, SQL, size, and queue shapes fail explicitly
External dependencies
• OpenSSL 3 supplies the native server TLS backend
• The hosted Seed runtime supplies sockets, reactor, signals, entropy, locks, files, and fsync
• Durability is Ridge WAL/B+Tree behavior, not PostgreSQL physical WAL
Architecture 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