Engineering / 02

AI infrastructure & MLOps

Production machine learning is more than a model. It is the data, deployment, inference, evaluation, and operational discipline around it. I build the infrastructure that brings those pieces together.

System map / Architecture

Evidence before eloquence

A client support question crosses identity and retrieval boundaries before producing a cited draft. Evaluation and human approval remain distinct; an unsafe or unsupported answer returns to manual work.

Discuss this kind of system
Custom Codex artwork; live diagrams explain the system. A short sequence plays automatically, showing the flows through the deployed system.
  1. GroundAuthorization happens before retrieval
  2. ApproveA cited draft is not a sent answer
  3. EvaluateImprove quality without training on assumptions

Inside the system

Boundaries, not black boxes.

Select a node in the diagram to read its responsibilities, interfaces and failure behavior.

01 / Component

Agent

An authenticated support agent submits a customer question within an explicitly selected tenant and case.

Inputs
Question · Tenant session
Outputs
Scoped assistance request
Failure & recovery
An expired session returns to sign-in; the system never silently broadens tenant scope.

02 / Component

Tenant ACL

The authorization service resolves permitted document sets and rechecks access when evidence is read.

Inputs
Identity · Document permissions
Outputs
Authorized evidence filter
Failure & recovery
Missing or stale permissions fail closed and send the agent to ordinary support tools.

03 / Component

Retrieve

Hybrid retrieval searches only authorized, versioned chunks and keeps source identifiers with every passage.

Inputs
Scoped query · Authorized index
Outputs
Ranked evidence · Source versions
Failure & recovery
Empty or stale evidence produces abstention; cross-tenant cache reuse is forbidden.

04 / Component

Draft

A bounded model request treats retrieved text as untrusted data and emits a draft with explicit source references.

Inputs
Question · Ranked passages
Outputs
Cited draft · Token usage
Failure & recovery
Timeouts, injected instructions or unsupported claims trigger the manual fallback instead of repeated expensive generation.

05 / Component

Checks

A versioned evaluation policy checks citation support, sensitive-data handling and required escalation categories.

Inputs
Draft · Evidence versions · Evaluation policy
Outputs
Reviewable draft · Failure reason
Failure & recovery
A policy failure withholds the draft; passing checks is not equivalent to factual certainty.

06 / Component

Human

The support agent compares cited evidence with the case, edits the response and explicitly approves any customer communication.

Inputs
Reviewable draft · Customer context
Outputs
Approved response · Correction feedback
Failure & recovery
No approval means no send; high-risk account actions remain outside the assistant.

07 / Component

Manual

Existing search and escalation remain available when assistance is unavailable, unauthorized or unhelpful.

Inputs
Abstention · Escalation reason
Outputs
Human-led resolution
Failure & recovery
Fallback load is visible to staffing planners; it is not counted as an assisted time saving.

08 / Component

Evaluate

Deidentified reviewer feedback and a held-out task set test candidate retrieval and prompt versions before promotion.

Inputs
Reviewed corrections · Held-out tasks
Outputs
Release evidence · Rollback recommendation
Failure & recovery
A failing privacy or critical-quality check blocks promotion even when average latency improves.

Recognize the situation?

Move from an interesting model to a system people can depend on.

What we can work on

Architecture through implementation.

Data systems for ML

Develop dependable ingestion and processing workflows across Postgres, Snowflake, streaming systems, and cloud-native services.

Secure AI delivery

Design IAM boundaries, observable pipelines, and deployment controls for sensitive data and healthcare workflows.

Engineering notes

A closer look at the engineering.

Real client engagements and the engineering behind them.

A practical starting point

Start with the constraint.

Understand the constraint. Build the smallest durable solution. Measure what changed. Leave the team with a system they can own.

Share what is running today, where it is getting in the way, and what needs to change.

Discuss ai infrastructure Explore engagement options

A useful next conversation

What needs to work better?

A system, a delivery bottleneck, or an engineering opportunity. Tell me what you are building and where you want to go.

Let’s talk

Technical glossary: definitions, connected ideas and further reading.

Optional analytics off. Contact works either way.

How measurement works