← Back to portfolio
OB. The Architect Layer
Interactive
Dive In

Every system,
every layer.

Seven systems — shipped platforms and the blueprints I structure everything with — each opened in three layers: the system view, the component map, and the live wire. Every box carries its why.

12+
Projects shipped
4+
Enterprise builds
5+
Years across the stack
01
Care Platform
Serverless GraphQL · AWS
02
Marketplace Platform
FastAPI · React Native · Stripe
03
Home Automation + Security
React Native · Swift · Kotlin · Socket.io
04
Agentic AI Systems
Multi-agent · Bedrock
05
Scalability Blueprint
Reference architecture · the why of every hop
06
Containerised Delivery
Docker · CI/CD · orchestration
07
Knowledge Platform
Docs-as-code · search · shared context

Knowledge Platform

How a team stops re-answering the same question — knowledge captured where the work happens, indexed once, findable by humans and machines. The docs behind this very site are structured this way.

Layer 01
System view
Inspector
Select a component

Click any block in the system view. The highlighted path follows the live wire below.

Layer 02
Component map
Capture
Retrieve
Consume
Why share
Inspector
Select a module

Click any module in the component map to see what it does and why it exists.

Layer 03
The live wire
  1. Sources → IngestDocs live beside code — a merged PR is a published doc.
  2. Decisions → IngestEvery ADR records the why, not just the what.
  3. IndexContent chunks into full-text and vector indexes — words and meaning.
  4. GraphDocs link to the systems they describe — staleness becomes visible.
  5. AskOne search surface serves humans; RAG answers with citations.
  6. ArriveReaders zoom L1 → L3; new joiners follow role-based trails.
Shipped work and working theory — this is how I structure everything I touch.
View résumé →