CORE / 02
OPEN SOURCE
Alex Tavern
- Problem
- Distinctive decision
- Evidence
AGENTIC SYSTEMS / VISUAL AI / CONTROL PLANES
I build systems where AI judgment meets deterministic control.
Complex ideas become usable when every decision has an owner, every boundary can be inspected, and the interface makes the system legible.
Explore the systems- Current work
- GenAI, MLOps, cloud & automation
- Operating mode
- Evidence before confidence
SELECTED SYSTEMS / ONE CONNECTED PRACTICE
Follow the architecture, not a list of logos.
Select a node to inspect the problem it owns, the decision that shapes it, and the evidence behind the claim.
Selected system
Shared design concern
Swipe to inspect
REPEATED DECISIONS / ENGINEERING POSITION
The work keeps returning to three boundaries.
Judgment lives in models. Invariants live in code.
Let models interpret and propose. Let typed contracts, state machines, and deterministic guards decide what becomes real.
Evidence before confidence.
Repeated runs, negative controls, replayable logs, and explicit limitations turn an interesting result into an engineering claim.
Complexity needs an interface.
A difficult workflow becomes useful when people can inspect, edit, recover, and understand the state they are changing.
PAPERS / CASE STUDIES / VALIDATION REPORTS
Research is part of the build.
Architecture claims are published with their measurements, negative controls, failure cases, and limits. These are engineering field notes, not peer-reviewed papers unless explicitly labeled as such.
Token economics as an architectural enabler
A cache-aware cost study with explicit attribution limits and normalized provider counterfactuals.
A structural audience model for speech
Witnessed actions, whispers, two-level recall assertions, and blind continuity review.
Making secret handling structural
A deterministic retry-then-redact guard tested against informational-payload leaks.
Multi-character memory under shifting focus
A reproduction attempt that rejected the reported failure and exposed a different architectural gap.
FINAL DOCUMENT / CURRICULUM VITAE
The résumé comes after the evidence.
The résumé comes last because the work is its context. Every role, project, and figure below traces back to verified work — where a client is confidential, the details are withheld, never the engineering.
CV RENDERER / A4 OUTPUT
Uses your browser's print dialog to save a PDF.