Omair Saleh
056c47581f
Ships the second dashboard surface — a Pattern Library + Preview Theatre — that presents the 4-section PDP pilot batch back to Umar, compliance, and the board in an editorial format. Adds the full data layer that drives it: 5 source-backed per-SKU drafts at QA 100/100, 15 competitor PDP semantic extracts, PubMed evidence packs, EFSA claims library extension, JV brand voice guide, hand-curated product FAQs, and the Matrixify-ready CSV exports for Lewis. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
8.0 KiB
8.0 KiB
| 1 | Sequence | Audience | Channel | Lane | Subject | RemainingCount | EditableFile | ReviewPacket | RequiredFields | PreflightEvidence | RegenerateCommand | Guardrail | MessageBody |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | 1 | Compliance owner / Umar | Compliance review handoff | Compliance blank/source-backed claim decisions | [JV handoff] Compliance blank/source-backed claim decisions - 184 remaining | 184 | data/content/compliance/clinical-blank-decisions.csv | content_population_exports/clinical_blank_decision_template.md | decision, approvedBy, approvedAt, rationale, constraintsAcknowledged | Compliance clinical blanks: 0/184 valid approved_blank rows; 184 still pending/invalid. | bun run compliance:blank-decisions && bun run claims:sync-content && bun run export:content | Do not invent clinical claims. Blank clinical module needs explicit compliance approval. | 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. |
| 3 | 2 | Umar / JV reviewer | Product approval handoff | Product approval decisions | [JV handoff] Product approval decisions - 190 remaining | 190 | data/content/approvals/product-approval-decisions.csv | content_population_exports/product_approval_review_packet.md | decision, approvedBy, approvedAt, reviewEvidence, contentReviewed, complianceReviewed, imagesReviewed, exportReviewed, noFakeEvidenceAcknowledged | Product approval decisions: 0/190 valid approve_all rows; 190 still pending/invalid. | bun run approval:decisions && bun run approval:review-packet && bun run export:content | Do not self-approve; reviewer evidence must be human-entered. | 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. |
| 4 | 3 | Lewis/Euan + dashboard owner | Staging import handoff | Lewis/Euan staging import evidence | [JV handoff] Lewis/Euan staging import evidence - 5 remaining | 5 | data/staging/import-logs/, data/staging/pdp-checks/, data/staging/cutover-approval.json | content_population_exports/staging_handoff_packet.md | clean import logs, at least 5 PDP checks, signed cutover approval | 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 | bun run staging:evidence && bun run staging:checklist && bun run verify:handoff | Queued PDP checks are not evidence; real staging URLs/results are required. | 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. |
| 5 | 4 | Research / project owner | Provider clearance handoff | DataForSEO Reviews endpoint/support/spend clearance | [JV handoff] DataForSEO Reviews endpoint/support/spend clearance - 4 remaining | 4 | data/sources/provider-responses/dataforseo-reviews-endpoint-response.json; data/sources/approvals/dataforseo-stage1-approval.json | content_population_exports/dataforseo_support_escalation.md; content_population_exports/dataforseo_stage1_approval_request.md | provider response, endpoint/replacement path, retry-safe confirmation, valid spend approval | 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 | bun run dataforseo:support-response && bun run dataforseo:task-preflight && bun run source:spend-gate | Use pi-fresh-foundation .env credentials only; do not print secrets or retry while docs/support block. | 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. |