Browser-based reference implementation

Architecture illustration: qualify, draft, approve, and execute.

Use case

An outreach workflow needs to track qualification, drafts, review decisions, delivery outcomes, and recipient suppression.

How it works

A stateful pipeline with deterministic qualification, AI-provider and delivery adapters, operator approval, separate execution controls, and an event history.

Inspect the implementation

The repository documents the operator walkthrough and behavioral tests for approval, duplicate protection, suppression, delivery outcomes, and quotas.

Scope

The reference uses fictional leads, deterministic mock providers, and browser-local state.

State and execution controls

Approval moves a lead to Approved without calling the delivery adapter. A separate execution action checks recipient suppression, duplicate-send state, and the successful-send quota. Only a successful provider result advances the lead to Sent. Bounce and unsubscribe events suppress the recipient.

A reviewer can reset the demo, approve a fictional lead, confirm send_count remains zero, execute it, and inspect the resulting event history.

Review procedure

npm test

Content reviewed against repository documentation on November 5, 2026.