AI Workflow Architecture

I design AI-ready workflows for messy, high-context work:
source-of-truth systems, decision memory, review loops, and reusable operating context.

I’m focused on the layer between AI output and actual work: context routing, evidence handling, ownership, review, and the source-of-truth updates that make workflows durable.

20 years in brand, motion, creative direction, and visual systems. Selected Work ↗

Four workflow systems for the same problem: AI breaks when context, evidence, decisions, and review logic are scattered. The diagnostic starts with one workflow and repairs the source-of-truth layer behind it.

A working LifeOS system for keeping AI-assisted work grounded in source-of-truth architecture, context routing, durable memory, raw evidence, review loops, and system repair.

Why it matters: AI becomes more useful when it can reason against maintained operating context instead of scattered chats, notes, screenshots, and stale memory.

The same pattern applies to teams, founders, creative systems, support knowledge, decision memory, and recurring workflows where context has to survive beyond one chat.

Not a productivity template. A context architecture lab.

A source-backed workflow for turning meetings, calls, and working sessions into decision memory: decisions, rationale, owners, risks, open questions, review status, and source references.

Why it matters: Most meeting tools summarize conversation. The deeper workflow problem is preserving decisions and evidence so teams and AI systems can reason from the same source of truth.

An AI-ready creative workflow for turning brand assets, guidelines, tone, visual examples, taste, and approval logic into reusable AI context.

The work: structure do and don't patterns, review loops, source examples, and decision logic so creative AI output can be evaluated against maintained brand context instead of loose preference.

A support knowledge architecture for source-of-truth answers, policy boundaries, edge cases, escalation paths, human review, and feedback loops before support automation.

The work: define canonical answers and route failures back into the knowledge base so AI-assisted support has clear source material, review states, and escalation logic.