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>
2.4 KiB
2.4 KiB
| 1 | Lane | Owner | RemainingCount | EditableFile | ReviewPacket | RequiredFields | AcceptedCompletion | RegenerateCommand | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| 2 | Compliance blank/source-backed claim decisions | Compliance owner / Umar | 184 | data/content/compliance/clinical-blank-decisions.csv | content_population_exports/clinical_blank_decision_template.md | decision, approvedBy, approvedAt, rationale, constraintsAcknowledged | All blank SKUs have decision=approved_blank with required fields, or source-backed claim refs are provided and synced. | 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. |
| 3 | Product approval decisions | Umar / JV reviewer | 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 | All products have valid decision=approve_all rows with evidence and all acknowledgements. | bun run approval:decisions && bun run approval:review-packet && bun run export:content | Do not self-approve; reviewer evidence must be human-entered. |
| 4 | Lewis/Euan staging import evidence | Lewis/Euan + dashboard owner | 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:evidence passes with failedRows=0, 5 PDP spot checks passing, and cutover approval signed. | bun run staging:evidence && bun run staging:checklist && bun run verify:handoff | Queued PDP checks are not evidence; real staging URLs/results are required. |
| 5 | DataForSEO Reviews endpoint/support/spend clearance | Research / project owner | 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 | support-response, task-preflight, and source spend gate pass before any paid Reviews retry. | 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. |