# Marketing automation brief

## Current workflow

- Task and decision it supports:
- Trigger and frequency:
- Current process and evidence date:
- Outcome owner:
- Authoritative system for each object:
- Hands-on time measured or estimated:
- Waiting time measured or estimated:
- Current errors and their evidence:

## Proposed data contract

- Trigger and stable source ID:
- Input version and event time:
- Required and optional fields:
- Supplied facts versus unknowns:
- Field mappings and types:
- Intended destination and account:
- Permitted read/write actions:
- Secrets handled by supported account storage:
- Data retention and private logging limits:
- Deterministic rules:
- Supervised AI step, if useful:
- Actions that remain with a person:
- Explicitly authorized external actions:
- Exclusions:

## Failure and recovery

- Duplicate/replay behavior:
- Missing-field behavior:
- Ambiguous identity behavior:
- Permission-denied behavior:
- Temporary-provider failure and bounded retry:
- Partial write and destination readback:
- Notification owner and actual recovery action:
- Stop switch:
- Manual fallback:
- Resume procedure without duplicate action:
- Maintenance owner and review trigger:

## Test design prompt

```text
Create test cases for this bounded workflow.
Current process and proposed rules: [PASTE]
Permitted inputs and actions: [PASTE]

Cover normal success, duplicate input, missing required field, ambiguous identity, denied permission, temporary failure, partial completion, and resume after pause.
For each, state artificial input, expected stored result, forbidden side effect, evidence to inspect, and recovery owner. Mark unresolved policy questions instead of deciding them.
Do not access accounts, send messages, publish, or infer missing facts.
```

## Constructed handoff example

A confirmed inquiry is added to an existing pipeline record. This is a teaching specification, not a working account integration.

Source ID: a stable inquiry ID supplied by the source system.
Input: confirmed email, supplied name, capture time, and stated need.
Unknowns: company and role when not supplied.
Match: source ID first, then an exact verified email under an agreed identity rule.
Success: add one source-linked note to the positively matched person.
Duplicate: same ID and version makes no second note.
Ambiguous match: hold the write for review.
Permission failure: preserve confirmed source, report unresolved downstream work.
Consent: inquiry capture does not subscribe the person to a newsletter.
Acceptance: destination readback confirms the right record and exact permitted fields.

## Supervised weekly report prompt

```text
Prepare a short report from the approved metric log.
Metric definitions and sources: [PASTE]
Current and comparison periods: [PASTE]
Documented changes: [PASTE]

State coverage first. Preserve values, definitions, and missing data. Describe comparable movement only when the periods and definitions match. Separate observation from possible explanation. List anomalies to inspect and at most two proposed actions.
Do not infer revenue, qualified demand, or causality from attention metrics. Do not fill unavailable values with zero. A quiet week may need no action.
Return a draft for inspection. Do not send or publish it.
```

## Accept and hand over

Import workflow-map.csv. Link step and test rows with workflow_id. Record observed evidence for each case, not just the expected outcome. Accept only after the agreed success and failure cases are verified in the intended permitted environment. Keep unresolved items named. Test the pause, manual fallback, and safe resume. Documentation should let the owner inspect, recover, and maintain the workflow.