Skip to content

The record, field by field.

R-01 shows a fictional campaign send. Follow each field into the reference file.

01R-01

Interrupted campaign send.

Example: a campaign send to 184,200 subscribers, recorded in ten fields.

Recovering sends after a platform timeout

Marketing operations agent · Spring launch, 184,200 subscribers

L8
E-01

Send call returned no confirmation

Observation · timeout

L13–15
E-02

Agent proposed sending the campaign again

Observation · No send log check was recorded first

L18–20
H-01

Stopped the resend and checked the send log

Campaign manager

L25–27
O-01

One send, no duplicate

Send log shows the original send completed

L32–34
Prompt revision
6L39
Tools
Send campaign · Read send logL40–42
Candidate change
Query the send log; branch on completed, failed or unavailable.L44
Comparison
Not runL45

Completed with human intervention

Independent completion · Not demonstrated by this case

L54–55
  • Send the campaign at most onceHeld, with help · H-01 O-01
    L60
  • Check the send log before any resendNot demonstrated · E-02 H-01
    L68
  • Send only campaigns the campaign manager has approvedNot assessed
    L76
  • Escalate when the send state is unknownNot exercised
    L81

No change to scope until the comparison runs. The owner decides.

Self · recommends Review

L87–88

Compare against

  1. Timeout after a completed send
  2. Confirmed failure before any send went out
  3. Send state cannot be established
L89–93

Hold at Review

Head of lifecycle marketing · decides

L96–97

Review

Send platform approval step · enforces

SELF · RECOMMENDS REVIEWLIFECYCLE HEAD · HOLDSSEND PLATFORM · ENFORCES
L100–101
02The file

Every citation lands on a line.

This reference explains the record. It does not define an API contract or production schema.
r-01-campaign-send.jsonDownload103 lines
{
"format": "self-work-record",
"record_type": "illustrative-reference",
"notice": "Self wrote this file to show the record format. No customer data, test result, endpoint, SDK or production schema stands behind it.",
"case_id": "R-01",
"title": "Interrupted campaign send",
"campaign": "Spring launch, 184,200 subscribers",
"class_of_work": "Recovering sends after a platform timeout",
"agent": "Marketing operations agent",
"evidence": {
"agent_behavior": [
{
"id": "E-01",
"event": "Send call returned no confirmation",
"observation": "timeout"
},
{
"id": "E-02",
"event": "Agent proposed sending the campaign again",
"observation": "No send log check was recorded first"
}
],
"human_judgment": [
{
"id": "H-01",
"role": "Campaign manager",
"event": "Stopped the resend and checked the send log"
}
],
"business_outcomes": [
{
"id": "O-01",
"event": "Send log shows the original send completed",
"state": "One send, no duplicate"
}
]
},
"configuration": {
"prompt_revision": 6,
"tools": [
"Send campaign",
"Read send log"
],
"candidate_change": "Query the send log; branch on completed, failed or unavailable.",
"comparison_status": "Not run"
},
"requirements": [
"Send the campaign at most once",
"Check the send log before any resend",
"Send only campaigns the campaign manager has approved",
"Escalate when the send state is unknown"
],
"reading": {
"outcome": "Completed with human intervention",
"independent_completion": "Not demonstrated by this case",
"retained_requirement": "Check the send log before any resend.",
"statuses": [
{
"requirement": "Send the campaign at most once",
"status": "Held, with help",
"source_ids": [
"H-01",
"O-01"
]
},
{
"requirement": "Check the send log before any resend",
"status": "Not demonstrated",
"source_ids": [
"E-02",
"H-01"
]
},
{
"requirement": "Send only campaigns the campaign manager has approved",
"status": "Not assessed",
"source_ids": []
},
{
"requirement": "Escalate when the send state is unknown",
"status": "Not exercised",
"source_ids": []
}
]
},
"recommendation": {
"handling": "Review",
"change": "No change to scope until the comparison runs. The owner decides.",
"compare_against": [
"Timeout after a completed send",
"Confirmed failure before any send went out",
"Send state cannot be established"
]
},
"policy": {
"owner": "Head of lifecycle marketing",
"decision": "Hold at Review"
},
"effective_authority": {
"handling": "Review",
"enforced_by": "Send platform approval step"
}
}

Bring one record you need to defend.

Talk to us

Bring one queue your team reviews.

Tell us where it runs, and we’ll reply by email to find a time.

We use your details to reply to this request. Privacy

Docs: the record, field by field | Self