# Lifecycle onboarding sequence

Original prompt workbook by Jon Bishop. CC BY 4.0. Model execution has not been tested.

## Intended output

A trigger-and-message plan with draft emails

## Input worksheet

Verified activation event, product paths, consent and suppression rules, eligibility, tone and approved product claims

Fill in:
- Decision and owner:
- Source ID, URL/file, date and exact supporting observation:
- Relevant population, version or edition:
- Approved constraints and sensitive fields to remove:
- Missing evidence:

Use sanitized inputs. Follow your approved model provider and data handling rules. No external action is part of these prompts.

## Prompt 1

```text
Inspect the supplied inputs for lifecycle onboarding sequence. Identify supported facts with their source IDs, contradictions and missing information. Do not infer missing product capabilities, numbers or customer evidence. Return an evidence ledger and blocking questions.

SUPPLIED INPUTS / PREVIOUS ARTIFACT:
[paste sanitized material here]
```

## Prompt 2

```text
Using only the evidence ledger and the original inputs, prepare a trigger-and-message plan with draft emails. Label assumptions and unknowns. Keep dates, versions, cohort and edition boundaries attached to claims. Do not execute external actions.

SUPPLIED INPUTS / PREVIOUS ARTIFACT:
[paste sanitized material here]
```

## Prompt 3

```text
Review the draft against this criterion: Triggers are observable, destinations work, opt-out ownership is explicit and no email is sent by this workflow. List failed checks, unsupported claims and corrections. Return a corrected draft plus unresolved questions; do not claim checks were performed when the inputs do not contain their results.

SUPPLIED INPUTS / PREVIOUS ARTIFACT:
[paste sanitized material here]
```

## Worked example — fictional, manually authored

Input: Fictional: an account created a project but has not sent its first test event.

Expected bounded output: Draft one reminder linking the verified test-event guide; suppress it after the first valid event.

This illustrates the review standard; it is not a recorded model run.

## Human review

Triggers are observable, destinations work, opt-out ownership is explicit and no email is sent by this workflow.

Verify factual claims against the original evidence, check calculations or commands independently and record unresolved issues. Save the inputs, prompt version, model version and corrections if you run this workbook. Publication, sending, account changes and spending are separate decisions.