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>
40 KiB
40 KiB
JV delivery index
Generated: 2026-05-20T02:31:41.391Z
This index is the map of every handoff, blocker, validation, source-request, intelligence, staging, and migration artifact needed to move from dashboard preview to Lewis/Euan staging import.
Files present: 179/179
Groups
- Dashboard handoff CSV: 3/3 present
- Dashboard blockers: 3/3 present
- External source requests: 4/4 present
- Source acquisition: 83/83 present
- Validation: 24/24 present
- Intelligence: 3/3 present
- Handoff orchestration: 54/54 present
- Migration CSV: 4/4 present
- Migration validation: 1/1 present
Files
- [present] Dashboard handoff CSV /
products_content_matrixify.csv- Dashboard-side product Matrixify preview. Owner: Dashboard. Readiness use: Import only after all blockers are zero. - [present] Dashboard handoff CSV /
metaobjects_matrixify.csv- Dashboard-side metaobject Matrixify preview. Owner: Dashboard. Readiness use: Import only after source-backed claims/assets are ready. - [present] Dashboard handoff CSV /
smart_collections_matrixify.csv- Dashboard-side smart collection promo-card mapping preview. Owner: Dashboard. Readiness use: Import after promo cards are approved. - [present] Dashboard blockers /
export_blockers.csv- Full product/metaobject blocker list. Owner: Dashboard. Readiness use: Must be empty before Lewis/Euan handoff. - [present] Dashboard blockers /
handoff_manifest.json- Machine-readable handoff readiness manifest. Owner: Dashboard. Readiness use: readyForLewis must be true. - [present] Dashboard blockers /
handoff_summary.md- Human handoff summary. Owner: Dashboard. Readiness use: Use for status only, not as proof of readiness. - [present] External source requests /
source_request_pack.md- Human-readable source request packet. Owner: Research / compliance / image. Readiness use: Send to source owners while blocked. - [present] External source requests /
source_request_items.csv- Raw evidence/source drop request rows. Owner: Research. Readiness use: Use to collect Amazon/Trustpilot/Reddit drops. - [present] External source requests /
clinical_claims_request.csv- Clinical/regulatory evidence request rows. Owner: Compliance. Readiness use: Use to populate claims-library.json. - [present] External source requests /
image_production_brief.csv- PDP image production queue. Owner: Design. Readiness use: Use to produce/upload asset filenames. - [present] Source acquisition /
source_acquisition_plan.md- Staged provider recommendation and spend guardrails. Owner: Research. Readiness use: Use before any paid DataForSEO or Apify run. - [present] Source acquisition /
source_acquisition_targets.csv- Provider target queue by SKU/brand. Owner: Research. Readiness use: Use to batch source collection without credit burn. - [present] Source acquisition /
source_acquisition_spend_gate.md- Provider spend gate status. Owner: Research / project owner. Readiness use: Must explicitly allow provider spend before DataForSEO or Apify is run. - [present] Source acquisition /
source_acquisition_spend_gate.csv- Provider spend gate check rows. Owner: Research / project owner. Readiness use: Use to see exactly which prerequisites block provider spend. - [present] Source acquisition /
source_acquisition_spend_gate.json- Machine-readable provider spend gate status. Owner: Research / project owner. Readiness use: Export Console/API read this before paid provider usage. - [present] Source acquisition /
source_acquisition_budget_gate.md- Provider budget cap gate status. Owner: Research / project owner. Readiness use: Must explicitly cap max spend/tasks before approval or provider subscription. - [present] Source acquisition /
source_acquisition_budget_gate.csv- Provider budget cap check rows. Owner: Research / project owner. Readiness use: Use to see which budget caps still block paid usage. - [present] Source acquisition /
source_acquisition_budget_gate.json- Machine-readable provider budget cap status. Owner: Research / project owner. Readiness use: Export Console/API read this before paid provider usage. - [present] Source acquisition /
source_acquisition_cost_plan.md- Provider cost-estimate plan for staged paid runs. Owner: Research / project owner. Readiness use: Must record current pricing and keep estimates within max spend before approval. - [present] Source acquisition /
source_acquisition_cost_plan.csv- Provider cost-plan check rows. Owner: Research / project owner. Readiness use: Use to see which pricing/estimate fields still block paid usage. - [present] Source acquisition /
source_acquisition_cost_plan.json- Machine-readable provider cost-plan status. Owner: Research / project owner. Readiness use: Export Console/API read this before paid provider usage. - [present] Source acquisition /
source_acquisition_approval_gate.md- Provider approval file validation status. Owner: Research / project owner. Readiness use: Must validate local approval files before any paid provider usage. - [present] Source acquisition /
source_acquisition_approval_gate.csv- Provider approval check rows. Owner: Research / project owner. Readiness use: Use to see which approval fields still block paid usage. - [present] Source acquisition /
source_acquisition_approval_gate.json- Machine-readable provider approval gate status. Owner: Research / project owner. Readiness use: Export Console/API read this before paid provider usage. - [present] Source acquisition /
source_acquisition_control_run.md- One-command source acquisition packet refresh status. Owner: Research / project owner. Readiness use: Use to regenerate all staged provider packet artifacts without spending credits. - [present] Source acquisition /
source_acquisition_control_run.csv- Source acquisition packet refresh step rows. Owner: Research / project owner. Readiness use: Use to identify packet-generation failures. - [present] Source acquisition /
source_acquisition_control_run.json- Machine-readable source acquisition packet refresh status. Owner: Research / project owner. Readiness use: Export Console/API read this for packet freshness. - [present] Source acquisition /
source_acquisition_next_actions.md- Sequenced DataForSEO-first / Apify-selective execution checklist. Owner: Research / project owner. Readiness use: Use as the immediate operating list before any provider subscription or credit spend. - [present] Source acquisition /
source_acquisition_next_actions.csv- Source acquisition next-action rows with owners, stop rules, and spend status. Owner: Research / project owner. Readiness use: Use to assign the next no-spend and approval tasks. - [present] Source acquisition /
source_acquisition_next_actions.json- Machine-readable source acquisition next-action status. Owner: Research / project owner. Readiness use: Export Console/API read this to show the current provider-spend instruction. - [present] Source acquisition /
source_subscription_decision.md- Plain-English provider subscription decision packet. Owner: Research / project owner. Readiness use: Use to decide whether to subscribe now without accidentally enabling spend. - [present] Source acquisition /
source_subscription_decision.csv- Subscription decision rows by provider. Owner: Research / project owner. Readiness use: Use to see why DataForSEO is wait/not-yet and Apify is held. - [present] Source acquisition /
source_subscription_decision.json- Machine-readable subscription decision status. Owner: Research / project owner. Readiness use: Export Console/API read this for the current subscribe/spend recommendation. - [present] Source acquisition /
source_acquisition_pricing_references.md- Official pricing-reference summary for staged provider decisions. Owner: Research / project owner. Readiness use: Use to fill the local cost plan from sourced pricing, not guesses. - [present] Source acquisition /
source_acquisition_pricing_references.csv- Provider pricing reference rows. Owner: Research / project owner. Readiness use: Use to copy source URLs, checked timestamps, and caveats into cost planning. - [present] Source acquisition /
source_acquisition_pricing_references.json- Machine-readable provider pricing references. Owner: Research / project owner. Readiness use: Export Console/API read this before budget/cost approval. - [present] Source acquisition /
source_acquisition_cost_scenarios.md- No-spend capped pilot cost scenarios. Owner: Research / project owner. Readiness use: Use to choose a tiny staged cap without enabling spend. - [present] Source acquisition /
source_acquisition_cost_scenarios.csv- Cost scenario rows by provider/stage. Owner: Research / project owner. Readiness use: Use to compare standard DataForSEO, priority DataForSEO, and held Apify scenarios. - [present] Source acquisition /
source_acquisition_cost_scenarios.json- Machine-readable capped cost scenarios. Owner: Research / project owner. Readiness use: Export Console/API read this before budget/cost approval. - [present] Source acquisition /
apify_gapfill_runbook.md- Stage 2 Apify selective gap-fill runbook. Owner: Research. Readiness use: Use only after DataForSEO pilot review shows a named gap. - [present] Source acquisition /
apify_gapfill_targets.csv- Apify run/hold target queue and spend caps. Owner: Research. Readiness use: Run only first-batch targets before dataset inspection. - [present] Source acquisition /
apify_gapfill_manifest.json- Machine-readable Apify gap-fill packet status. Owner: Research. Readiness use: Export Console/API read this before any Apify spend. - [present] Source acquisition /
apify_competitor_pdp_input_template.json- No-spend Apify actor input template for first batch. Owner: Research. Readiness use: Paste into chosen actor only after approval to run Stage 2. - [present] Source acquisition /
apify_task_preflight.md- Final local guard before paid Apify actor execution. Owner: Research / project owner. Readiness use: Must be ready before any Apify actor run. - [present] Source acquisition /
apify_task_preflight.csv- Apify paid actor preflight check rows. Owner: Research / project owner. Readiness use: Use to see which final paid-run checks are still blocked. - [present] Source acquisition /
apify_task_preflight.json- Machine-readable Apify paid actor preflight. Owner: Research / project owner. Readiness use: Export Console/API read this before any paid Apify usage. - [present] Source acquisition /
dataforseo_pilot_plan.md- Stage 1 DataForSEO pilot instructions. Owner: Research. Readiness use: Run only after ASINs are filled and reviewed. - [present] Source acquisition /
dataforseo_pilot_manifest.json- Machine-readable DataForSEO pilot status. Owner: Research. Readiness use: Ready task count must be reviewed before any paid call. - [present] Source acquisition /
dataforseo_pilot_targets.csv- Stage 1 DataForSEO ASIN intake queue. Owner: Research. Readiness use: Fill ASINs before creating task payload. - [present] Source acquisition /
dataforseo_asin_lookup_queue.md- No-spend manual ASIN lookup workflow. Owner: Research. Readiness use: Use to fill the Stage 1 ASIN map before paid task creation. - [present] Source acquisition /
dataforseo_asin_lookup_queue.csv- No-spend ASIN lookup URLs and actions. Owner: Research. Readiness use: Use to confirm exact Amazon product matches without API credit spend. - [present] Source acquisition /
dataforseo_asin_lookup_queue.json- Machine-readable ASIN lookup queue status. Owner: Research. Readiness use: Export Console/API read this before paid task creation. - [present] Source acquisition /
dataforseo_asin_candidate_report.md- No-spend ASIN candidate evidence report. Owner: Research. Readiness use: Use as lookup aid only; candidates still require Amazon confirmation before paid tasks. - [present] Source acquisition /
dataforseo_asin_candidate_report.csv- ASIN candidate evidence rows. Owner: Research. Readiness use: Use to see candidate confidence, source URL, and promotion blockers. - [present] Source acquisition /
dataforseo_asin_candidate_report.json- Machine-readable ASIN candidate status. Owner: Research. Readiness use: Export Console/API can read this without treating candidates as paid-task ready. - [present] Source acquisition /
dataforseo_asin_web_evidence.md- No-spend public web evidence report for ASIN lookup. Owner: Research. Readiness use: Use to separate third-party ASIN hints and rejected leads from Amazon-confirmed matches. - [present] Source acquisition /
dataforseo_asin_web_evidence.csv- ASIN public web evidence rows. Owner: Research. Readiness use: Use to avoid rechecking weak leads while keeping third-party evidence out of paid payloads. - [present] Source acquisition /
dataforseo_asin_web_evidence.json- Machine-readable ASIN public web evidence status. Owner: Research. Readiness use: Export Console/API read this before treating public evidence as promotion-safe. - [present] Source acquisition /
dataforseo_unresolved_asin_evidence.md- No-spend negative evidence report for unresolved ASINs from live DataForSEO product results. Owner: Research. Readiness use: Use to prove unresolved SKUs stay out of the paid Reviews payload instead of guessing. - [present] Source acquisition /
dataforseo_unresolved_asin_evidence.csv- Unresolved ASIN candidate/rejection rows. Owner: Research. Readiness use: Use to inspect top candidates and exact-match counts for missing ASINs. - [present] Source acquisition /
dataforseo_unresolved_asin_evidence.json- Machine-readable unresolved ASIN evidence status. Owner: Research. Readiness use: Export Console/API read this to show anti-guessing evidence for missing ASINs. - [present] Source acquisition /
dataforseo_asin_confirmation_report.md- Manual Amazon-page ASIN confirmation report. Owner: Research. Readiness use: Use to prove candidate ASINs were checked against visible Amazon title/brand/product/pack evidence. - [present] Source acquisition /
dataforseo_asin_confirmation_report.csv- ASIN confirmation validation rows. Owner: Research. Readiness use: Use to see which confirmations are ready for promotion and why others are blocked. - [present] Source acquisition /
dataforseo_asin_confirmation_report.json- Machine-readable ASIN confirmation status. Owner: Research. Readiness use: Promotion and Export Console read this before copying any candidate into the ASIN map. - [present] Source acquisition /
dataforseo_asin_promotion_report.md- Safe ASIN promotion report. Owner: Research. Readiness use: Copies only Amazon-confirmed/high-confidence candidates into asin-map; blocked rows explain why no payload was created. - [present] Source acquisition /
dataforseo_asin_promotion_report.csv- ASIN promotion check rows. Owner: Research. Readiness use: Use to review which candidates were promoted or blocked. - [present] Source acquisition /
dataforseo_asin_promotion_report.json- Machine-readable ASIN promotion status. Owner: Research. Readiness use: Export Console/API read this before DataForSEO payload generation. - [present] Source acquisition /
dataforseo_amazon_reviews_task_payload.json- DataForSEO task payload generated from ASIN map. Owner: Research. Readiness use: Keep empty until ASINs are supplied; cap first run. - [present] Source acquisition /
dataforseo_amazon_reviews_curl_template.sh- Credential-safe curl template for task creation. Owner: Research. Readiness use: Use shell env credentials only; do not commit secrets. - [present] Source acquisition /
dataforseo_task_preflight.md- Final local guard before paid DataForSEO task creation. Owner: Research / project owner. Readiness use: Must be ready before manually running the curl template. - [present] Source acquisition /
dataforseo_task_preflight.csv- DataForSEO paid task preflight check rows. Owner: Research / project owner. Readiness use: Use to see which final paid-run checks are still blocked. - [present] Source acquisition /
dataforseo_task_preflight.json- Machine-readable DataForSEO paid task preflight. Owner: Research / project owner. Readiness use: Export Console/API read this before any paid DataForSEO usage. - [present] Source acquisition /
dataforseo_support_response_gate.md- DataForSEO support response validation gate. Owner: Research / project owner. Readiness use: Use after support replies to prove endpoint availability or replacement path before any capped retry. - [present] Source acquisition /
dataforseo_support_response_gate.csv- Support response gate check rows. Owner: Research / project owner. Readiness use: Use to see which provider-response fields still block retry. - [present] Source acquisition /
dataforseo_support_response_gate.json- Machine-readable support response gate status. Owner: Research / project owner. Readiness use: Export Console/API read this before treating provider endpoint availability as resolved. - [present] Source acquisition /
dataforseo_reviews_docs_status.md- Official DataForSEO Amazon Reviews documentation status. Owner: Research / project owner. Readiness use: Use to prove whether the provider currently documents the Reviews endpoint as unavailable before any retry. - [present] Source acquisition /
dataforseo_reviews_docs_status.csv- Official docs status check rows. Owner: Research / project owner. Readiness use: Use to see fetched-docs reachability, endpoint mention, and temporary-unavailable detection. - [present] Source acquisition /
dataforseo_reviews_docs_status.json- Machine-readable official docs status. Owner: Research / project owner. Readiness use: Export Console/API read this to keep provider outage evidence current without credentials or paid calls. - [present] Source acquisition /
dataforseo_stage1_approval_request.md- Project-owner approval request packet for the capped DataForSEO Stage 1 pilot. Owner: Research / project owner. Readiness use: Use only after provider endpoint availability is confirmed; this is not approval by itself. - [present] Source acquisition /
dataforseo_stage1_approval_request.csv- Approval request readiness rows. Owner: Research / project owner. Readiness use: Use to see whether payload, budget, cost, endpoint, and approval are ready. - [present] Source acquisition /
dataforseo_stage1_approval_request.json- Machine-readable approval request packet. Owner: Research / project owner. Readiness use: Export Console/API read this to show the exact approval values without storing secrets. - [present] Source acquisition /
manual_amazon_review_capture.md- No-spend manual Amazon review capture fallback queue. Owner: Research. Readiness use: Use if DataForSEO Reviews remains blocked; save completed JSON source drops into data/sources/amazon/. - [present] Source acquisition /
manual_amazon_review_capture.csv- Manual Amazon capture rows by ASIN. Owner: Research. Readiness use: Use to assign capture targets and source-drop save paths. - [present] Source acquisition /
manual_amazon_review_capture.json- Machine-readable manual Amazon capture queue. Owner: Research. Readiness use: Export Console/API read this to show no-spend fallback targets. - [present] Source acquisition /
manual_amazon_review_capture_validation.md- Manual Amazon capture completion gate. Owner: Research. Readiness use: Use to prove listed manual source drops exist and contain valid review evidence before treating fallback as complete. - [present] Source acquisition /
manual_amazon_review_capture_validation.csv- Manual Amazon capture validation rows by ASIN. Owner: Research. Readiness use: Use to see missing/invalid fallback source drops and per-file review counts. - [present] Source acquisition /
manual_amazon_review_capture_validation.json- Machine-readable manual Amazon capture completion status. Owner: Research. Readiness use: Export Console/API read this to distinguish queued fallback work from completed source evidence. - [present] Source acquisition /
dataforseo_ingest_validation.md- DataForSEO raw result ingest validation. Owner: Research. Readiness use: Use after the paid pilot to prove raw results were normalized into Amazon source drops. - [present] Source acquisition /
dataforseo_ingest_validation.csv- DataForSEO ingest output rows. Owner: Research. Readiness use: Shows converted Amazon source files and review counts. - [present] Source acquisition /
dataforseo_ingest_validation.json- Machine-readable DataForSEO ingest status. Owner: Research. Readiness use: Export Console/API read this before source validation. - [present] Source acquisition /
dataforseo_pilot_review.md- DataForSEO pilot output review gate. Owner: Research / project owner. Readiness use: Must be complete before scaling DataForSEO or enabling Apify gap-fill. - [present] Source acquisition /
dataforseo_pilot_review.csv- DataForSEO pilot review check rows. Owner: Research / project owner. Readiness use: Use to see why scale-up or Apify remains blocked. - [present] Source acquisition /
dataforseo_pilot_review.json- Machine-readable DataForSEO pilot review decision. Owner: Research / project owner. Readiness use: Export Console/API read this before scale-up decisions. - [present] Validation /
asset_manifest_validation.csv- Required/missing asset validation. Owner: Dashboard / design. Readiness use: Must have zero missing uploads/references. - [present] Validation /
draft_pdp_asset_generation.csv- Generated draft PDP PNG asset ledger. Owner: Dashboard / design. Readiness use: Use to verify the 570 product PDP image filenames exist as review-marked draft assets; image approval is still required. - [present] Validation /
draft_pdp_asset_generation.json- Machine-readable generated draft PDP PNG asset ledger. Owner: Dashboard / design. Readiness use: Export/review evidence for generated draft product imagery without claiming final creative approval. - [present] Validation /
metaobject_svg_asset_generation.csv- Generated metaobject SVG asset ledger. Owner: Dashboard / design. Readiness use: Use to verify metaobject icon/image files were produced in the asset root; product PDP images are still separate. - [present] Validation /
metaobject_svg_asset_generation.json- Machine-readable generated metaobject SVG asset ledger. Owner: Dashboard / design. Readiness use: Export/review evidence for the 16 SVG files produced locally without treating missing PDP images as complete. - [present] Validation /
template_schema_validation.csv- Template header match evidence. Owner: Dashboard. Readiness use: Must pass before import. - [present] Validation /
source_drop_validation.csv- Source drop validation status. Owner: Research. Readiness use: Must pass before full intelligence generation. - [present] Validation /
claims_library_validation.csv- Claims-library validation status. Owner: Compliance. Readiness use: Must pass before clinical claims content. - [present] Validation /
clinical_claim_mapping_report.csv- SKU-level clinically_shown_to mapping report. Owner: Compliance / dashboard. Readiness use: Use to verify only source-backed claims were mapped and unmatched SKUs stayed blank instead of receiving fake claims. - [present] Validation /
clinical_claim_mapping_report.json- Machine-readable clinically_shown_to mapping report. Owner: Compliance / dashboard. Readiness use: Export Console/reviewer evidence for mapped vs unmapped claim coverage. - [present] Validation /
unmatched_claims_review_packet.md- Human-readable queue for SKUs with blank clinically_shown_to fields. Owner: Compliance. Readiness use: Use for compliance review; do not auto-fill generic claims. - [present] Validation /
unmatched_claims_review_packet.csv- SKU-level unmatched clinical-claim review rows. Owner: Compliance. Readiness use: Use to assign the remaining compliance decisions. - [present] Validation /
unmatched_claims_review_packet.json- Machine-readable unmatched clinical-claim review queue. Owner: Compliance. Readiness use: Export Console/reviewer evidence for unresolved compliance decisions. - [present] Validation /
clinical_blank_decision_template.md- Human-readable approval template for intentionally blank clinical-claim fields. Owner: Compliance. Readiness use: Use only when compliance approves omitting clinically_shown_to for a SKU. - [present] Validation /
clinical_blank_decision_template.csv- Clinical blank-decision validation rows. Owner: Compliance. Readiness use: Use to see pending/valid approved_blank decisions. - [present] Validation /
clinical_blank_decision_template.json- Machine-readable clinical blank-decision gate. Owner: Compliance. Readiness use: Dashboard and migration exporters read valid approvals before clearing missing-claim blockers. - [present] Validation /
product_approval_review_packet.md- Human-readable product approval queue summary. Owner: Umar / JV reviewer. Readiness use: Use to route human review without self-approving products. - [present] Validation /
product_approval_review_packet.csv- Product-level approval blocker rows. Owner: Umar / JV reviewer. Readiness use: Use to approve content/compliance/image/export lanes by SKU. - [present] Validation /
product_approval_review_packet.json- Machine-readable product approval review queue. Owner: Umar / JV reviewer. Readiness use: Export Console/reviewer evidence for unresolved approval decisions. - [present] Validation /
product_approval_decision_gate.md- Human-readable product approval decision gate. Owner: Umar / JV reviewer. Readiness use: Use after human review to apply explicit approval decisions from the editable JSON file. - [present] Validation /
product_approval_decision_gate.csv- Product approval decision validation rows. Owner: Umar / JV reviewer. Readiness use: Use to see which approval decisions are valid/applicable. - [present] Validation /
product_approval_decision_gate.json- Machine-readable product approval decision gate. Owner: Umar / JV reviewer. Readiness use: Export Console/API read this before approvals can clear handoff blockers. - [present] Validation /
content_population_readiness.md- Consolidated readiness audit. Owner: Dashboard. Readiness use: Must report ready YES. - [present] Validation /
handoff_verification_run.md- Master verification run. Owner: Dashboard. Readiness use: Must report ready YES and all checks pass. - [present] Intelligence /
intelligence_generation_workqueue.csv- Per-SKU missing intelligence task queue. Owner: Dashboard intelligence lane. Readiness use: Must be empty/pass before full catalogue approval. - [present] Intelligence /
intelligence_generation_by_sku.csv- SKU-prioritized intelligence queue. Owner: Dashboard intelligence lane. Readiness use: Use to batch full-catalogue generation. - [present] Intelligence /
intelligence_generation_summary.csv- Per-view intelligence coverage summary. Owner: Dashboard intelligence lane. Readiness use: Every view must be 190/190. - [present] Handoff orchestration /
handoff_action_plan.md- Owner-facing action list. Owner: Project owner. Readiness use: All actions must be closed before handoff. - [present] Handoff orchestration /
handoff_packet_refresh.md- One-command no-spend handoff packet refresh report. Owner: Project owner. Readiness use: Use to prove all packet artifacts can be regenerated while still surfacing expected blockers. - [present] Handoff orchestration /
handoff_packet_refresh.json- Machine-readable one-command handoff packet refresh report. Owner: Project owner. Readiness use: Export Console/API can read this for packet freshness and blocked-vs-failed status. - [present] Handoff orchestration /
handoff_packet_refresh.csv- Handoff packet refresh step rows. Owner: Project owner. Readiness use: Use to inspect which packet steps passed, are expected blockers, or failed to refresh. - [present] Handoff orchestration /
handoff_artifact_freshness.md- Artifact freshness report for refresh-scoped handoff files. Owner: Project owner. Readiness use: Use to distinguish packet completeness from current-run freshness. - [present] Handoff orchestration /
handoff_artifact_freshness.json- Machine-readable artifact freshness report. Owner: Project owner. Readiness use: Export Console/API read this to catch stale refresh-scoped artifacts. - [present] Handoff orchestration /
handoff_artifact_freshness.csv- Artifact freshness rows by delivery file. Owner: Project owner. Readiness use: Use to inspect stale, missing, fresh, and static-allowed packet files. - [present] Handoff orchestration /
executive_decision_brief.md- Executive decision brief for Umar/Lewis/Euan. Owner: Project owner. Readiness use: Use to close named decisions and owner blockers before staging handoff. - [present] Handoff orchestration /
executive_decision_brief.json- Machine-readable executive decision brief. Owner: Project owner. Readiness use: Export Console/API read this for current decision status. - [present] Handoff orchestration /
executive_decision_brief_decisions.csv- Decision rows with owners/evidence files. Owner: Project owner. Readiness use: Use to assign required approvals and compliance decisions. - [present] Handoff orchestration /
executive_decision_brief_readiness.csv- Readiness snapshot metrics for decision brief. Owner: Project owner. Readiness use: Use as meeting snapshot alongside the decision brief. - [present] Handoff orchestration /
blocker_burndown.md- Evidence-based blocker burn-down summary. Owner: Project owner. Readiness use: Use to track exactly what remains before handoff readiness can pass. - [present] Handoff orchestration /
blocker_burndown.json- Machine-readable blocker burn-down. Owner: Project owner. Readiness use: Export Console/API read this for remaining evidence counts. - [present] Handoff orchestration /
blocker_burndown.csv- Blocker burn-down rows by lane. Owner: Project owner. Readiness use: Use to track remaining compliance, approval, and staging evidence counts. - [present] Handoff orchestration /
blocker_burndown_next_actions.csv- Ordered next actions from blocker burn-down. Owner: Project owner. Readiness use: Use to assign the next evidence-producing tasks. - [present] Handoff orchestration /
handoff_evidence_dossier.md- Strict requirement-to-evidence completion dossier. Owner: Project owner. Readiness use: Use to prove which master-plan requirements are satisfied vs blocked before claiming completion. - [present] Handoff orchestration /
handoff_evidence_dossier.json- Machine-readable requirement-to-evidence completion dossier. Owner: Project owner. Readiness use: Export Console/API read this for completion-audit evidence. - [present] Handoff orchestration /
handoff_evidence_dossier.csv- Requirement evidence rows with proof and remaining work. Owner: Project owner. Readiness use: Use to audit every requirement area before handoff. - [present] Handoff orchestration /
reviewer_decision_workbook.md- Owner-facing workbook for remaining compliance, approval, provider, and staging decisions. Owner: Project owner. Readiness use: Use to hand reviewers exact editable files, required fields, commands, and guardrails. - [present] Handoff orchestration /
reviewer_decision_workbook.json- Machine-readable reviewer decision workbook. Owner: Project owner. Readiness use: Export Console/API read this for owner-lane status. - [present] Handoff orchestration /
reviewer_decision_workbook.csv- Reviewer decision workbook rows by owner lane. Owner: Project owner. Readiness use: Use to assign remaining human/provider/staging decisions. - [present] Handoff orchestration /
reviewer_completion_commands.csv- Exact regeneration command sequence after reviewer files are filled. Owner: Project owner. Readiness use: Use to rerun gates after human/provider/staging evidence lands. - [present] Handoff orchestration /
reviewer_input_preflight.md- Preflight report for reviewer-owned editable input files. Owner: Project owner. Readiness use: Use before rerunning heavier gates to catch incomplete compliance, approval, provider, and staging inputs. - [present] Handoff orchestration /
reviewer_input_preflight.json- Machine-readable reviewer input preflight. Owner: Project owner. Readiness use: Export Console/API read this to show which editable input files are still missing or incomplete. - [present] Handoff orchestration /
reviewer_input_preflight.csv- Reviewer input preflight rows by input file. Owner: Project owner. Readiness use: Use to route exact missing fields back to reviewers before gate reruns. - [present] Handoff orchestration /
owner_handoff_messages.md- Copy-paste owner handoff messages for remaining evidence blockers. Owner: Project owner. Readiness use: Use to send compliance, approval, staging, and provider-spend owners exact asks without inventing approvals. - [present] Handoff orchestration /
owner_handoff_messages.json- Machine-readable owner handoff message packet. Owner: Project owner. Readiness use: Export Console/API read this for owner-specific message status and guardrails. - [present] Handoff orchestration /
owner_handoff_messages.csv- Owner handoff message rows. Owner: Project owner. Readiness use: Use to copy exact owner asks, editable files, preflight evidence, and rerun commands. - [present] Handoff orchestration /
owner_response_intake.md- Owner reply/evidence intake tracker validation. Owner: Project owner. Readiness use: Use after sending owner messages to record replies and evidence updates before rerunning gates. - [present] Handoff orchestration /
owner_response_intake.json- Machine-readable owner response intake status. Owner: Project owner. Readiness use: Export Console/API read this to show whether owner replies/evidence updates have been recorded. - [present] Handoff orchestration /
owner_response_intake.csv- Owner response intake rows by lane. Owner: Project owner. Readiness use: Use to inspect sent/response/evidence/command status per owner lane. - [present] Handoff orchestration /
handoff_gate_dependency_map.md- Master verifier gate-to-owner dependency map. Owner: Project owner. Readiness use: Use to route blocked verifier gates to exact owner inputs instead of rerunning blindly. - [present] Handoff orchestration /
handoff_gate_dependency_map.json- Machine-readable handoff gate dependency map. Owner: Project owner. Readiness use: Export Console/API read this to show blocked gates, owners, and unblocking inputs. - [present] Handoff orchestration /
handoff_gate_dependency_map.csv- Gate dependency rows by verifier check. Owner: Project owner. Readiness use: Use to inspect command, owner, blockers, and rerun command per gate. - [present] Handoff orchestration /
handoff_gate_dependency_by_owner.csv- Blocked verifier gates grouped by owner. Owner: Project owner. Readiness use: Use to brief owners on which verifier gates their evidence unblocks. - [present] Handoff orchestration /
post_owner_response_rerun_plan.md- Safe rerun plan after owner responses/evidence updates. Owner: Project owner. Readiness use: Use only after owner response intake marks a lane ready for gate rerun. - [present] Handoff orchestration /
post_owner_response_rerun_plan.json- Machine-readable post-owner response rerun plan. Owner: Project owner. Readiness use: Export Console/API read this to show which lane command sequences are safe to rerun. - [present] Handoff orchestration /
post_owner_response_rerun_plan.csv- Post-owner response rerun rows by lane. Owner: Project owner. Readiness use: Use to inspect held/runnable lane command sequences and guardrails. - [present] Handoff orchestration /
owner_evidence_acceptance_guide.md- Acceptance guide for owner-editable evidence files. Owner: Project owner. Readiness use: Use to show reviewers exactly what counts as valid evidence without approving anything. - [present] Handoff orchestration /
owner_evidence_acceptance_guide.json- Machine-readable owner evidence acceptance guide. Owner: Project owner. Readiness use: Export Console/API read this to show valid/invalid evidence criteria per blocker lane. - [present] Handoff orchestration /
owner_evidence_acceptance_guide.csv- Owner evidence acceptance rows by lane. Owner: Project owner. Readiness use: Use to inspect required fields, valid examples, invalid examples, and validators. - [present] Handoff orchestration /
daily_status_2026-05-20.md- Current daily handoff status snapshot. Owner: Project owner. Readiness use: Use as the dated operating snapshot; not proof of final readiness. - [present] Handoff orchestration /
daily_status_2026-05-20.json- Machine-readable current daily handoff status snapshot. Owner: Project owner. Readiness use: Export Console/API can read this for dated blocker and DataForSEO status. - [present] Handoff orchestration /
daily_status_2026-05-20.csv- Daily status rows by area. Owner: Project owner. Readiness use: Use to brief owners on current blockers and next actions. - [present] Handoff orchestration /
staging_handoff_packet.md- Lewis/Euan staging handoff packet. Owner: Project owner + Lewis/Euan. Readiness use: Use to send exact import files, sequence, current blockers, and PDP spot-check queue. - [present] Handoff orchestration /
staging_handoff_packet.json- Machine-readable staging handoff packet. Owner: Project owner + Lewis/Euan. Readiness use: Export Console/API read this for staging handoff status. - [present] Handoff orchestration /
staging_handoff_import_files.csv- Staging import file manifest. Owner: Lewis/Euan. Readiness use: Use to confirm exact Matrixify file paths and import order. - [present] Handoff orchestration /
staging_pdp_spot_check_queue.csv- Queued PDP spot-check sample. Owner: Project owner + Lewis/Euan. Readiness use: Use to assign real staging URL checks; queue is not completed evidence. - [present] Handoff orchestration /
staging_handoff_actions.csv- Staging handoff action rows. Owner: Project owner + Lewis/Euan. Readiness use: Use to assign remaining blocker and staging evidence work. - [present] Handoff orchestration /
staging_import_checklist.md- Preflight/import/PDP/cutover checklist. Owner: Project owner + Lewis/Euan. Readiness use: All blocking rows must be resolved. - [present] Handoff orchestration /
staging_evidence_validation.md- Staging evidence validator output. Owner: Project owner + Lewis/Euan. Readiness use: Must pass with clean import logs, 5+ PDP checks, cutover approval. - [present] Handoff orchestration /
staging_evidence_intake.md- Staging evidence intake initializer report. Owner: Project owner + Lewis/Euan. Readiness use: Use to confirm editable staging evidence intake paths exist without fake import/PDP evidence. - [present] Handoff orchestration /
staging_evidence_intake.json- Machine-readable staging evidence intake initializer status. Owner: Project owner + Lewis/Euan. Readiness use: Export Console/API read this to show pending staging evidence intake paths. - [present] Handoff orchestration /
staging_evidence_intake.csv- Staging evidence intake rows. Owner: Project owner + Lewis/Euan. Readiness use: Use to see which intake files/folders were initialized and what still requires real staging activity. - [present] Migration CSV /
products_content_v5.csv- Lewis/Euan product/variant Matrixify import candidate. Owner: Migration emitter. Readiness use: Import after dashboard handoff is ready. - [present] Migration CSV /
products_content_v5_blockers.csv- Migration product blocker list. Owner: Migration emitter. Readiness use: Must be empty before import. - [present] Migration CSV /
metaobjects_all.csv- Migration metaobject import candidate. Owner: Migration emitter. Readiness use: Import before products after readiness passes. - [present] Migration CSV /
smart_collections_promo_cards.csv- Migration smart collection promo-card import candidate. Owner: Migration emitter. Readiness use: Import after promo cards exist. - [present] Migration validation /
asset_manifest_validation.csv- Migration-side asset validation. Owner: Migration emitter. Readiness use: Must have zero missing uploads/references.
Final readiness rule
delivery_index only proves the packet exists. Final readiness still requires bun run verify:handoff to pass and Lewis/Euan staging evidence to be recorded.