I design agentic systems around a simple engineering principle:
A model generates intelligence. The system determines whether that intelligence can be trusted.
My work connects AI engineering, full-stack systems, cloud-native infrastructure, and real business operations. I focus on the parts that make agents useful beyond a demo: deterministic routing, governed tool access, typed state, evaluation, fallbacks, observability, and human approval boundaries.
I also lead Texcot Embroidery Sourcing House, which gives me direct experience with production, inventory, orders, customers, deadlines, and the realities software must survive outside the codebase.
Every claim below links to inspectable source code or a live system.
| Discipline | Evidence | Inspect |
|---|---|---|
| Deterministic orchestration | 39 tests · 0 API keys | OrchestratorX tests |
| MCP × A2A interoperability | 61 tests · protocol-level transport | ProtoBridge protocols |
| Deterministic guardrails | 17 tests · 3 compliance domains | GuardrailAI controls |
| Portfolio agent runtime | Typed routes · tools · fallbacks | Source · Live |
Test counts describe the linked repositories at the time of verification. The portfolio states limitations and distinguishes representative traces from captured production telemetry.
|
Deterministic multi-agent orchestration A supervisor-pattern framework that keeps routing in typed state and plain Python. Required specialists, termination, failure handling, and audit traces are enforced as testable invariants.
|
MCP × A2A interoperability A governed protocol layer implementing real JSON-RPC over MCP stdio and A2A HTTP while preserving identity, sensitivity, and correlation context across boundaries.
|
Deterministic agent governance Pre-flight controls, bounded execution, post-flight enforcement, circuit breakers, and SHA-256 hash-chained audit records around probabilistic agents.
|
Read the full architecture case studies →
| Layer | Engineering question | What I implement |
|---|---|---|
| Harness | What can the agent see and do? | Scoped tools, memory, permissions, typed state, protocol boundaries |
| Loop | How does the system know the work is correct? | Evidence, trace assertions, evaluations, retries, verification |
| Graph | Who acts next, and what happens on failure? | Deterministic routing, approvals, termination, fallback paths |
Model → Harness → Loop → Graph → Tools & Protocols → Guardrails → Evaluation → Observability
One governed request path—from intent to verified, auditable execution.
flowchart TD
A["Request"] --> B["Input guardrails"]
B --> C["Supervisor"]
C --> D["Specialist agents"]
D --> E["Governed tools"]
E --> F["Observation"]
F --> G{"Verified?"}
G -->|Retry or fallback| C
G -->|Pass| H["Audited result"]
C -. typed route .-> I["Shared state"]
D -. evidence .-> I
E -. tool calls .-> I
I --> H
| Control | Engineering guarantee |
|---|---|
| Supervisor routing | One deterministic decision point controls every handoff |
| Guardrails | Policy checks run before and after probabilistic execution |
| Verification loop | Evidence—not confidence—decides whether work passes |
| Typed shared state | Routes, observations, tool calls, and failures remain inspectable |
| Audit result | The final response can be traced back to the execution path |
| System | Outcome | Evidence |
|---|---|---|
| Agentic OS Portfolio | A portfolio that exposes its architecture, agent runtime, trace model, and source evidence | Repository |
| Textile ERP Platform | Multi-tenant fabric inventory SaaS with PostgreSQL row-level security | Repository |
| Hackathon Completion Engine | Event-driven AI platform using FastAPI, Kafka, Dapr, Kubernetes, and safety middleware | Repository |
| Agentic Reference Platforms | Open-source domain implementations with agent architectures, gateways, and test suites | Explore GitHub |
Completion badges from Claude Academy, Anthropic's learning platform. Each course title links to its public verification page.
- AI Fluency: Framework and foundations
- Introduction to Claude Cowork
- Claude Code 101
- AI Fluency for builders
- AI capabilities and limitations
- Claude 101
- Claude Code in action
- Introduction to Model Context Protocol
AI systems Agent orchestration · MCP · A2A · RAG · evaluation · guardrails
Backend Python · FastAPI · Pydantic · async services
Frontend TypeScript · Next.js · React · Tailwind CSS · shadcn/ui
Data PostgreSQL · Redis · vector databases
Infrastructure Docker · Kubernetes · Dapr · Kafka · GitHub Actions
Observability OpenTelemetry · Prometheus · Grafana
Method Specification-first · evidence-driven · human-governed
I am building toward AI operating systems that turn AI into business capacity: supervised agents with durable context, governed tools, deterministic progression, auditable decisions, and clear human approval gates.
The goal is not more isolated prompts. It is reliable systems that help small teams research, prepare, execute, verify, and report work at greater scale.


