Files
Omair Saleh 056c47581f feat: editorial review dashboard + elite-grade pilot batch (5 SKUs)
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>
2026-06-02 18:50:09 +08:00

2.6 KiB

Reviewer decision workbook

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

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

This workbook is the handoff map for the people who must clear the remaining blockers. It does not approve content, alter decision files, or bypass provider/staging gates.

Open lanes: 4/4 Tracked remaining items: 383 Evidence dossier: 5/10 requirement areas proven

Owner lanes

Owner Lane Remaining Editable file Regenerate command Guardrail
Compliance owner / Umar Compliance blank/source-backed claim decisions 184 data/content/compliance/clinical-blank-decisions.csv 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.
Umar / JV reviewer Product approval decisions 190 data/content/approvals/product-approval-decisions.csv bun run approval:decisions && bun run approval:review-packet && bun run export:content Do not self-approve; reviewer evidence must be human-entered.
Lewis/Euan + dashboard owner Lewis/Euan staging import evidence 5 data/staging/import-logs/, data/staging/pdp-checks/, data/staging/cutover-approval.json bun run staging:evidence && bun run staging:checklist && bun run verify:handoff Queued PDP checks are not evidence; real staging URLs/results are required.
Research / project owner DataForSEO Reviews endpoint/support/spend clearance 4 data/sources/provider-responses/dataforseo-reviews-endpoint-response.json; data/sources/approvals/dataforseo-stage1-approval.json 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.

Exact sequence after reviewers fill files

  1. bun run compliance:blank-decisions && bun run claims:sync-content && bun run export:content
  2. bun run approval:decisions && bun run approval:review-packet && bun run export:content
  3. bun run dataforseo:support-response && bun run dataforseo:task-preflight && bun run source:spend-gate
  4. bun run staging:evidence && bun run staging:checklist
  5. bun run verify:handoff && bun run handoff:evidence-dossier && bun run delivery:index && bun run handoff:daily-status

Guardrail

If any command above remains blocked, keep the goal active and report the exact failing gate. Do not infer approvals, clinical claims, staging evidence, provider availability, or paid-spend clearance.