How It Works
Nothing on this site is hardcoded. Every page, journey, and recommendation is generated live from four layers working together — content is authored in the CMS, reasoned over by Alex OS, retrieved through a vector database, and rendered as a dynamic experience on the frontend you're using right now.
The four layers
CMS — Content Registry
The single source of truth for every content type, page, and setting. The owner edits it directly — nothing is baked into the code.
Alex OS — Reasoning Layer
Reads the content registry, reasons over relationships and intent, and decides what to surface, summarize, or recommend to each visitor.
PGVector — Vector Database
Semantic memory for the system. Embeddings power retrieval, similarity, and the connections Alex OS reasons about.
Frontend — Dynamic Experience
The public site itself. Journeys, the orbit, and every section render live from what the CMS and Alex OS produce.
How a page actually gets built
- Content is authored or updated in the CMS — a page, a project, a note, a piece of proof.
- It's embedded and indexed into PGVector, so it becomes something the system can reason about semantically, not just keyword-match.
- Alex OS reasons over the content graph — relationships, journeys, and what's relevant right now — and decides what to surface.
- The frontend renders it live: the journey spheres, the orbit, and every section you see are generated from that output, not hand-built pages.
Why it's built this way
Most personal sites are static — a fixed set of pages the owner has to manually keep in sync. Alex OS is built so the site can reorganize itself around what actually matters: new work gets connected automatically, journeys stay current, and the assistant can answer questions grounded in real content instead of a canned script.
See it in action
Head back and pick a journey — Proof, Build, or Thinking.