CAPTAIN_ONLINE
CAPTAIN_ONLINE
We map the terrain first — where AI actually moves the needle, where it's theater, and what governance the business needs before a single model touches production.
Declarative systems whose documents ARE the deployment. Durable orchestration, MCP tool rails, and compliance enforced structurally — not in a policy PDF nobody reads.
Working software in your infrastructure, pinned by tests, handed off with the rails to run it. No slideware. No pilot purgatory. Systems that survive contact with the org.
Marketing intent in, governed execution out.
Meijer's marketing automation, rebuilt as a governed platform: a declarative language (MOSL) whose documents ARE the deployments, one durable Temporal runtime that executes them all, and MCP tool rails across Meijer's Digital APIs — 215 operations over 10 Azure APIM APIs, mPerks loyalty, and Emarsys. Consent and frequency caps enforced structurally, in code, pinned by tests.
Marketing intent in, governed execution out.
Meijer's marketing automation, rebuilt as a platform. A marketer authors a journey, campaign, A/B experiment, or cohort as one declarative document — no code, no redeploy. It compiles at PR time, dispatches by event, and executes durably against the live opt-out registry. Consent and frequency caps aren't a policy PDF; they're enforced structurally, in code, pinned by ~1,500 tests.
A declarative language whose documents ARE the deployments. 43 marketing verbs in three dispatch classes, a total partition pinned by tests; compiler and runtime tables parity-tested byte-for-byte. Author a journey once — the same syntax covers campaigns, experiments, and cohorts.
Every integration is a single gateway tool: Meijer's Digital APIs, mPerks loyalty, Emarsys, SAP CDP. The only vendor-specific text in a document is one `via:` line. Identity, idempotency, and audit headers are enforced at the rail, not per-vendor.
One generic Temporal workflow runs every document. Multi-week waits survive restarts, experiments bucket deterministically, and all I/O lives in activities — workflow code stays deterministic behind a swappable abstraction.
Consent fails closed against the live opt-out registry. Frequency caps live in encrypted KeyDB; idempotency keys are required by lint; PII is redacted in logs and analytics egress; every vendor record joins back to its Temporal run by audit header.
Same brief, run through the pipeline. Consent, brand, and hierarchy stop being someone's judgment call and become part of the output.
Global Group Director of Digital Innovation at The Coca-Cola Company — conversational AI in vending infrastructure, deployed across 15,000+ locations.