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.
20+
Projects shipped
7
Enterprise builds
4+
Years across the stack
Care Platform
A regulated patient platform — four role-based portals, one GraphQL edge, encrypted-per-request data, and AI agents on a leash. Compliance is designed in, not bolted on.
Layer 00
Interface wireframes
Patient Portal — Clinical Data
Clinical Data
Journey
Story
Network
Care Circle — Permissions
Care Circle
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
Client Surfaces
API Edge
Compute
Data + Compliance
External
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
- Portal → APIA GraphQL call leaves the portal with a signed token.
- API → IdentityThe JWT is verified at the edge — bad tokens never reach code.
- API → LambdaThe resolver is invoked with a trusted identity attached.
- Lambda → DataSQL runs in a sealed transaction carrying the caller’s encryption key.
- Lambda → AIAgentic turns route out to Bedrock; sessions persist on our side.
- API → PortalA typed payload returns — the audit trail writes itself.
Shipped work and working theory — this is how I structure everything I touch.
View résumé →