# Owner handoff messages

Generated: 2026-05-20T02:31:35.016Z

Handoff remains blocked: 383 evidence items remaining; verification 8/17 passing; delivery packet 179/179 present.

Messages: 4
Tracked remaining items: 383
Verifier: 8/17 passing
Delivery packet: 179/179 present
DataForSEO account status: 20000; credentialPrinted=false

These are copy-paste prompts for the owners who must produce the remaining evidence. They do not approve content, close gates, or unlock provider spend.

## Guardrails
- Do not self-approve compliance blanks or product approvals.
- Do not treat queued staging checks as completed evidence.
- Do not run paid DataForSEO Reviews while the endpoint/support/spend gates are blocked.
- Use the real pi-fresh-foundation .env credentials only through shell environment; never print or paste secrets.

## Messages
### 1. Compliance review handoff

**To:** Compliance owner / Umar
**Subject:** [JV handoff] Compliance blank/source-backed claim decisions - 184 remaining

```text
Hi Compliance owner / Umar,

Current JV dashboard handoff status: Handoff remains blocked: 383 evidence items remaining; verification 8/17 passing; delivery packet 179/179 present.

Your lane: Compliance blank/source-backed claim decisions
Remaining: 184
Ask: Please either approve the SKU to ship with the clinical claim field blank, or provide source-backed claim evidence and refs. Do not add generic health claims.

Editable file(s): data/content/compliance/clinical-blank-decisions.csv
Review packet: content_population_exports/clinical_blank_decision_template.md
Required fields/evidence: decision, approvedBy, approvedAt, rationale, constraintsAcknowledged

Current preflight evidence: Compliance clinical blanks: 0/184 valid approved_blank rows; 184 still pending/invalid.

After updating the file/evidence, rerun: bun run compliance:blank-decisions && bun run claims:sync-content && bun run export:content

Guardrail: Do not invent clinical claims. Blank clinical module needs explicit compliance approval.

Please do not approve, infer, or backfill anything unless the evidence is actually reviewed and recorded in the editable file above.
```

### 2. Product approval handoff

**To:** Umar / JV reviewer
**Subject:** [JV handoff] Product approval decisions - 190 remaining

```text
Hi Umar / JV reviewer,

Current JV dashboard handoff status: Handoff remains blocked: 383 evidence items remaining; verification 8/17 passing; delivery packet 179/179 present.

Your lane: Product approval decisions
Remaining: 190
Ask: Please review content, compliance, images, export readiness, and supporting evidence for each SKU before setting approve_all.

Editable file(s): data/content/approvals/product-approval-decisions.csv
Review packet: content_population_exports/product_approval_review_packet.md
Required fields/evidence: decision, approvedBy, approvedAt, reviewEvidence, contentReviewed, complianceReviewed, imagesReviewed, exportReviewed, noFakeEvidenceAcknowledged

Current preflight evidence: Product approval decisions: 0/190 valid approve_all rows; 190 still pending/invalid.

After updating the file/evidence, rerun: bun run approval:decisions && bun run approval:review-packet && bun run export:content

Guardrail: Do not self-approve; reviewer evidence must be human-entered.

Please do not approve, infer, or backfill anything unless the evidence is actually reviewed and recorded in the editable file above.
```

### 3. Staging import handoff

**To:** Lewis/Euan + dashboard owner
**Subject:** [JV handoff] Lewis/Euan staging import evidence - 5 remaining

```text
Hi Lewis/Euan + dashboard owner,

Current JV dashboard handoff status: Handoff remains blocked: 383 evidence items remaining; verification 8/17 passing; delivery packet 179/179 present.

Your lane: Lewis/Euan staging import evidence
Remaining: 5
Ask: Please run/record the staging import evidence: clean import logs, real PDP spot checks, and signed cutover approval after checks pass.

Editable file(s): data/staging/import-logs/, data/staging/pdp-checks/, data/staging/cutover-approval.json
Review packet: content_population_exports/staging_handoff_packet.md
Required fields/evidence: clean import logs, at least 5 PDP checks, signed cutover approval

Current preflight evidence: Staging import evidence: 0 import log file(s) found. | Staging PDP spot checks: 0/5 PDP check file(s) found. | Staging cutover approval: approved=false; approver=blank; approvedAt=blank

After updating the file/evidence, rerun: bun run staging:evidence && bun run staging:checklist && bun run verify:handoff

Guardrail: Queued PDP checks are not evidence; real staging URLs/results are required.

Please do not approve, infer, or backfill anything unless the evidence is actually reviewed and recorded in the editable file above.
```

### 4. Provider clearance handoff

**To:** Research / project owner
**Subject:** [JV handoff] DataForSEO Reviews endpoint/support/spend clearance - 4 remaining

```text
Hi Research / project owner,

Current JV dashboard handoff status: Handoff remains blocked: 383 evidence items remaining; verification 8/17 passing; delivery packet 179/179 present.

Your lane: DataForSEO Reviews endpoint/support/spend clearance
Remaining: 4
Ask: Please wait for DataForSEO Reviews endpoint clearance, record support response, then explicitly approve the capped Stage 1 spend only if the endpoint is retry-safe.

Editable file(s): data/sources/provider-responses/dataforseo-reviews-endpoint-response.json; data/sources/approvals/dataforseo-stage1-approval.json
Review packet: content_population_exports/dataforseo_support_escalation.md; content_population_exports/dataforseo_stage1_approval_request.md
Required fields/evidence: provider response, endpoint/replacement path, retry-safe confirmation, valid spend approval

Current preflight evidence: DataForSEO provider response: responseReceived=false; endpointAvailable=false; replacementEndpoint=blank; retrySafe=false; credentialIncluded=false | DataForSEO spend approval: approved=false; maxSpendApproved=0; targetCap=0/10; runLimit=0/1; depth=0/10; hardStop=false; noCredentialStorage=false

After updating the file/evidence, rerun: bun run dataforseo:support-response && bun run dataforseo:task-preflight && bun run source:spend-gate

Guardrail: Use pi-fresh-foundation .env credentials only; do not print secrets or retry while docs/support block.

Please do not approve, infer, or backfill anything unless the evidence is actually reviewed and recorded in the editable file above.
```

