Open to opportunities
Principal AI Architect · Forward Deployed
Governed agent stack you can fork — 5-spine review with Demo vs Strict labeled, not a 17-product catalog.
Panel receipt
Demo vs Strict labeled. Free cold starts are not warm SLOs — probe these artifacts before you book a loop.
Decision
Hit live /health before the call so cold-start latency is labeled, not surprise.
Signal
Portfolio probes the D1 spine APIs server-side and surfaces warm vs cold honestly.
Limitation
Render Free idle spin-down is real — first hit after idle can take 15–40s.
Decision
Panel default is Strict-local packs — not the public Free demo as an always-on SLO.
Signal
AegisAI and Enterprise RAG ship STRICT_PANEL_PACK docs for local / JWT panel paths.
Limitation
Public Free demos stay honesty-labeled; Strict may require local or GCP setup.
Decision
Replay ask→RAG→govern→meter without a guided tour when you want a stranger-checkable receipt.
Signal
GOLDEN_PATH.md + latest JSON artifact in the architecture portfolio.
Limitation
Full ask→answer needs API keys; ACF live publish still requires Clerk.
Decision
Every portfolio-wide claim should resolve to Verified, Demonstrated, or Contextual.
Signal
/proof marks soft career metrics as Contextual with explicit limitations.
Limitation
Contextual does not mean false — it means primary records are confidential or external.
Start here
Recruiters & Hiring Leaders
Dual-fit cards, LinkedIn recommendations, live spine, and a one-page brief you can forward — before you burn a loop.
Open hiring pageFDE / Applied AI panels
Discovery → scored wedge → HITL → handoff. How architecture depth shows up when someone has to ship under their constraints.
Open FDE methodTechnical Reviewers
Diagrams, 17 catalog products, repos, and case studies on one page — start with the spine, not a scavenger hunt.
View portfolio5-spine review path
Start with AegisAI (governance), then orchestration, access-aware RAG, and a governed publish path. Labs and curriculum patterns stay in the full catalog — not the panel path.
Monitor → Govern → Remediate — a runtime control plane for tool authorization, policy violations, HITL approvals, signed audit, and agent registry lifecycle.
Reviewer evidence
Control plane over agent builder — enterprises need governance across fleets, not another chat UI.
Website deploy tools forced through approval_required policy on live platform.
Registry defaults to in-memory on free tier; Postgres path documented for production.
Supporting · Multi-agent OS
LangGraph stateful graphs over linear chains — enterprise workflows need checkpoints and HITL.
Case studySupporting · Knowledge layer
Authorization before ranking — vector DB is implementation; access control is architecture.
Case studySupporting · Content automation
AegisAI gateway blocks publish until policy allows — side effects never bypass governance.
Case studySpine and AgentOps consumers wire critical suites as merge gates: RAG answer + adversarial (Enterprise RAG), harness QA + repo fix (LoopForge), mission gate + collaboration scorecard (AegisLoop), graph HITL (Content Factory), brief gate (Sentinel), triage preference (DomainForge), and router_invariant across VAP, AegisAI, and FinOps. Builds fail on regression — not just fixture validation.
Get in touch
Read the hiring overview, browse the full portfolio, or subscribe for weekly architecture essays.