Async proof slice proof.
A redacted or synthetic test-build proof that takes one workflow brief and redacted sample events, then produces a status ledger, review queue, error log, and written update. It is built to show whether ongoing collaboration is worth continuing without broad hourly availability, live credentials, or a call-heavy first step.
Status Ledger CSV
Review Queue CSV
Error Log CSV
Status Update
Workflow Briefs CSV
Sample Events CSV
Validation Rules CSV
Runbook
Source Script
Input
One workflow brief, redacted sample rows, destination fields, and explicit blocked-row definitions.
Output
Accepted rows become a status ledger with destination keys and a written status note.
Failure Path
Duplicate ids, missing owners, missing destinations, and low-confidence output go to review. Impossible rows go to the error log.
| Event | Workflow | Destination | Decision | Reason |
|---|---|---|---|---|
| evt-2101 | Lead Routing Sample | HubSpot | Ready for reviewed delivery | Owner, destination key, confidence, and correlation id passed. |
| evt-2104 | Ops Export Cleanup | Google Sheets | Review queue | Duplicate correlation id would create a repeated side effect. |
| evt-2105 | AI Summary Check | Notion | Review queue | Low-confidence or unsupported output stays visible before any write. |
| evt-2107 | Unknown brief | None | Hard error | Rows that cannot map to a registered brief are logged instead of guessed. |