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>
1.3 KiB
1.3 KiB
Source acquisition budget gate
Generated: 2026-05-20T16:49:00.672Z
DataForSEO Stage 1 budget allowed: YES Apify Stage 2 budget allowed: YES
This gate prevents provider subscriptions or paid calls from starting without an explicit local budget cap. It does not store credentials or pricing assumptions.
Budget file: data/sources/budgets/source-acquisition-budget.json
Checks
- [pass] DataForSEO Stage 1: Budget lane enabled — enabled=true
- [pass] DataForSEO Stage 1: Max spend recorded — GBP 5
- [pass] DataForSEO Stage 1: Task cap covers pilot only — 10 max tasks for 10 pilot targets
- [pass] DataForSEO Stage 1: Review depth capped — 100 reviews per ASIN (target range 100-1000)
- [pass] DataForSEO Stage 1: Hard stop after first run — hardStopAfterFirstRun=true
- [pass] Apify Stage 2: Budget lane enabled — enabled=true
- [pass] Apify Stage 2: Max spend recorded — GBP 5
- [pass] Apify Stage 2: Actor and target caps preserve selective gap-fill — 1 actor runs, 3 targets, 100 requests/brand for 3 first-batch targets (target range 100-1000)
- [pass] Apify Stage 2: Hard stop after first dataset — hardStopAfterFirstDataset=true
Rule
A human approval file is not enough by itself. The matching budget lane must also be enabled with a max spend and hard-stop caps before source:spend-gate can allow paid provider usage.