LLM workflow design
Turn a multi-step task into reviewable work with explicit context, outputs and decision boundaries.
Selected public work · Evidence and limitations
Applied LLMs · Agent systems · Governed delivery
Multi-step AI work needs more than fluent output: reliable context, reviewable execution and decisions people can own. This portfolio shows how I connect those concerns in a working prototype.
I configured and combined existing LLM assistants, coding agents and local inference tools with a Git-backed context layer, evidence classification and a human-reviewed delivery workflow. The contribution is the operating design, integration and evaluation around those tools. This work does not claim authorship of the foundation models or agent products.
Documented prototype work includes curated AI-readable context, a locally smoke-tested read-only MCP interface, and recovery testing. These demonstrate bounded engineering work; they do not establish enterprise adoption, general autonomy or production-scale performance.
Turn a multi-step task into reviewable work with explicit context, outputs and decision boundaries.
Coordinate capabilities and handoffs while preserving human authority over material decisions.
Distinguish fluent output from a supported result. Keep validation, source limitations and uncertainty visible.
Test durable workflow state and recovery under bounded interruptions, keeping mechanical results separate from business value.
Frame the problem and context
Coordinate bounded execution
Evaluate outputs and evidence
Review results and decide
Review adds time and limits autonomy, but preserves accountability when a plausible answer is not sufficient evidence to act.
A curated read-only interface reduces what the system can access or change. Its narrower scope trades convenience for a more inspectable trust boundary.
Bounded interruption tests demonstrated recovery of workflow state across crashes and sessions. This supports the tested mechanism; continuous production reliability and human productivity gains remain unproven.
Local discovery checks passed in 5 of 5 accepted repositories. Two stale or conflicting control scenarios failed closed. These are control-plane test results, not evidence of general agent autonomy.