From this morning's brief (2026-10-31)

Open the whole brief

← all clients

PIO

Pioneer Carry parked ppc launch-velocity rebuilt Sat, Oct 31, 1:20 PM

Shared growth plan — 2026-09-28 through 2026-10-27. reported revenue $29,634.05; reported net $11,745.82.

PROVISIONAL — reported net is not a verified contribution margin; reconcile itemized costs and refunds.

Pioneer Carry: 0 execution result(s) recorded in the last 7 days; 4 overdue action(s). Financial or evidence gaps remain. See Growth plan for current actions and evidence. The separate Numbers tab is an earlier planning snapshot; it does not establish that today's profit target is met or authorize increased spending.

The machineall 4 of the things we run for them are up to date
Changes madenothing has been changed on their account in this run
Work delivered5 things produced in the last 30 days
Results measurednothing of theirs is on the clock to be scored in money
Waiting on you4 things cannot move until you decide or hand something over

Growth plan

Grow organic sell-through and contribution from the active catalog while preserving the parked advertising constraint.

30-day, 60-day and quarterly scorecard

Plan as of 2026-09-13. Baseline: August · COULD-NOT-VERIFY — baseline source missing or changed.

Reported revenue 9161.78; reported net 1766.86. Reported net is not certified contribution. Source window, fees, cost coverage and client-specific adjustments must reconcile before financial scoring. This snapshot does not refresh the underlying data. Evidence review 2026-09-13: August US reported revenue $8764, net $1547.5. Revenue scope bridge resolved: August US $8,764 / 27 units plus Mexico $397.78 / 1 unit equals all-marketplace $9,161.78 / 28 units. Current all-marketplace net $1,766.54 versus old $1,766.86 is a $0.32 restatement, not the $397.78 sales gap. Original client New COGS June/July supports Savant black $82.2741, forest $81.9814, navy $82.80681 landed. Molecule Robusta cost and conflicting Navy Panda rows remain unresolved. PPC remains parked with $0 launch burn and September 19 inventory hold. Evidence: Sync/client-growth/scorecards/financial-evidence-20260913/PIO-observation.json. August settlement review starts September 15; original baseline values remain unchanged. Continuation 2026-09-13: August US cost gap is 3 Safari Sling Black units, SKU PIO-SAF-BLA / ASIN B0F2H27QH1, out of 27 units; live Sellerboard cost is zero. The client COGS 2025 workbook lists Safari Sling Black landed $18.27, a recovered historical candidate requiring confirmation for August 2026 before entry. Molecule Robusta is not the sold-SKU cause of this August gap. Marketplace revenue bridge remains resolved: US $8764 plus Mexico $397.78 equals all-market $9161.78. Cost applicability, effective dates and settled fees still block target certification.

Baseline source and limits

mode7-analysis/mode6k-actuals/PIO_actuals.json

["RECON (money, not adopted): the P&L reports revenue 9,161.78 but Amazon's own order-date figure for 2026-08-01..2026-08-31 is 8,764.00 (-4.3%) — the incumbent still wins, but the window or the source disagrees and it should be reconciled.","SESSIONS CORRECTED: the P&L reported 976 sessions for 2026-08-01..2026-08-31; Amazon's own Business Report says 911 (-6.7%). Amazon's figure is used. Any CVR quoted from the old number was wrong by the inverse of this."]

Horizon / deadlineMeasurable targetOwner / existing actionsResults / evidence
30 days
2026-09-09 → 2026-10-08
Review: 2026-10-09		After September 15 settlement, reconcile August revenue sources and the 2.73% COGS gap; establish the first post-relaunch milestone while keeping PPC parked.

Delivery target: 1 source-backed delivery (validated_baseline_and_selected_intervention_package)

mode6k + client-growth
PIO-ECONOMICS, PIO-RISK, PIO-DIAGNOSIS, PIO-EXPERIMENT		OVERDUE — outcome not assessed

UNMEASURED — experiment measurement is separate from milestone delivery

PIO-ECONOMICS: needs_input · Preparation / research

Fresh authenticated Finance read confirms the Mexico settlement remains Open at MXN 15,366.70 without Amazon-applied USD conversion. August economics remain uncertified; no account changes made.

No usable completion evidence

PIO-RISK: completed · Preparation / research

Verified PIO saleable stock, offers and catalog risks against live Amazon data pulled in this run (no reuse of stale copies). Live FBA supply read 2026-09-15T10:36:44Z via inventory-replenish/scripts/read_supply.mjs: 54 fulfillable, 146 reserved in FC transfer, 42 inbound receiving, 4 customer-reserved, 2 FC-processing, 1 unfulfillable, 1 researching; 249 total across 81 physical pools; inventory_complete=true, shipments_complete=true, 7 open inbound shipments, zero errors. Live GET_MERCHANT_LISTINGS_ALL_DATA: 89 rows, 13 Active / 59 Inactive / 17 Incomplete. Every active catalogue segment covered: backpacks (9 Active, all thin on sellable stock behind large FC-transfer blocks; CL-HMLY-J0OG Active with 0 sellable), slings (only PIO-SAF-BLA Active; 5 dark), pouches (all 3 Co-Pilot dark), wallets (confirmed dormant, consistent with the secondary directive, no correction proposed), parents (12 expected-Incomplete on DEFAULT, 6 real Incomplete defects on AMAZON_NA). Exceptions found: 9 of 18 launch-floor SKUs Inactive with zero units in every bucket four days before the 2026-09-19 hold expiry; an ASIN identity conflict where the Inventory API puts G9-WBOB-SN6D on B0H37W4ZDK/X0054Y2BVT while the listings report puts it on B0H9G3JMMR (contradicting the hold file's 2026-08-19 amendment), with the same shape on Panda Black (YR-3BYD-37YB on B0F8JHPD5J); 8 unlisted Stickered.MSKU rows. Duplicate-action exclusions applied from onboarding/PIO/sources.json (mode6-pio-inventory-availabili-pio-saf-bla OPEN and replenish-PIO-pio-pan-bla already own those shortfalls; DROPPED mktwatch and mode6 conversion levers not revived). Account Health / Performance Notifications and Buy-Box eligibility were NOT read and are recorded as UNMEASURED, not clear. No prior PIO-RISK attempt exists on disk; all earlier runs are PIO-CONTEXT preparations, so nothing partial needed reconciling. PPC left PARKED, launch hold and its expiry preserved unchanged, no price/fee/repricer field read or written, no account mutation.

No usable completion evidence

PIO-DIAGNOSIS: open · Preparation / research

No result recorded

No usable completion evidence

PIO-EXPERIMENT: in_progress · Preparation / research

record

No usable completion evidence

Evidence requiredOne client-specific package: dated cost/fee/traffic bridge with unknowns; verified stock/offer constraints; one Mode6K-selected lever, own-unit success measure, owner and due date. Record the actual implementation evidence separately. A blocked prerequisite is a miss/hold, not a successful intervention.
60 days
2026-09-09 → 2026-11-07
Review: 2026-11-09		Evaluate one non-advertising bags/pouches catalog or offer intervention against the validated post-relaunch baseline.

Delivery target: 1 source-backed delivery (matched_window_intervention_assessment)

Financial working target: null USD contribution per month. PPC PARKED AT $0; CONTRIBUTION TARGET PENDING RECONCILIATION. The $0 launch-burn decision is already explicit. Size contribution only after the remaining cost and settled-fee gates clear; preserve September 19 inventory hold.

mode6k + client-growth
PIO-ECONOMICS, PIO-DIAGNOSIS, PIO-EXPERIMENT, PIO-WEEKLY		OPEN — outcome not assessed

UNMEASURED — experiment measurement is separate from milestone delivery

PIO-ECONOMICS: needs_input · Preparation / research

Fresh authenticated Finance read confirms the Mexico settlement remains Open at MXN 15,366.70 without Amazon-applied USD conversion. August economics remain uncertified; no account changes made.

No usable completion evidence

PIO-DIAGNOSIS: open · Preparation / research

No result recorded

No usable completion evidence

PIO-EXPERIMENT: in_progress · Preparation / research

record

No usable completion evidence

PIO-WEEKLY: open · Preparation / research

No result recorded

No usable completion evidence

Evidence requiredOne assessment links the chosen lever to baseline and follow-up windows, live implementation proof and the appropriate client profit/royalty measure. Record achieved, missed or inconclusive with source evidence. A planning document or low sample is not proof of lift.
Quarterly
2026-10-01 → 2026-12-31
Review: 2027-01-15		Build profitable organic demand for bags/pouches with documented inventory cover; retain the PPC hold and keep wallets secondary.

Delivery target: 1 source-backed delivery (settled_quarter_outcome_and_next_quarter_plan)

Financial working target: null USD contribution per month. PPC PARKED AT $0; CONTRIBUTION TARGET PENDING RECONCILIATION. The $0 launch-burn decision is already explicit. Size contribution only after the remaining cost and settled-fee gates clear; preserve September 19 inventory hold.

mode6k + horizon-review
PIO-WEEKLY, PIO-EXPERIMENT		OPEN — outcome not assessed

UNMEASURED — experiment measurement is separate from milestone delivery

PIO-WEEKLY: open · Preparation / research

No result recorded

No usable completion evidence

PIO-EXPERIMENT: in_progress · Preparation / research

record

No usable completion evidence

Evidence requiredOne Q4 assessment after settlement compares October–December actuals to the validated goal, separates recurring contribution from recoveries, records held/missed milestones, and assigns Q1 actions and inventory needs. Monthly reference targets are not multiplied into an invented quarter forecast.

Inputs and delivery deadlines

External due dates are agency follow-up/review deadlines, not promises made by the client.

PIO-INPUT-20260913 · overdue · due 2026-09-16

Continuation 2026-09-13: August US cost gap is 3 Safari Sling Black units, SKU PIO-SAF-BLA / ASIN B0F2H27QH1, out of 27 units; live Sellerboard cost is zero. The client COGS 2025 workbook lists Safari Sling Black landed $18.27, a recovered historical candidate requiring confirmation for August 2026 before entry. Molecule Robusta is not the sold-SKU cause of this August gap. Marketplace revenue bridge remains resolved: US $8764 plus Mexico $397.78 equals all-market $9161.78. Cost applicability, effective dates and settled fees still block target certification.

Owner: mom-report + catalog-econ + mode6k. Agency coordinator: client-growth. Action: PIO-ECONOMICS.

Use Sync/client-growth/scorecards/financial-continuation-20260913/PIO-review.json and the source-verified evidence already recovered; resolve the remaining cost/royalty or settlement gates on PIO-ECONOMICS by 2026-09-16. Do not request sources already found or treat configured costs as supplier-invoice verification.

Close only when: The named owner supplies dated own-client evidence, explains remaining discrepancies and updates the existing canonical source or explicitly retains the unresolved gate.

mode6-pio-panda-spec-clarification-20260916:readout:2026-09-30:input · overdue · due 2026-09-30

The post-change report window has not matured; readout is unmeasured.

Owner: amazon-experiments. Agency coordinator: client-growth. Action: mode6-pio-panda-spec-clarification-20260916:readout:2026-09-30.

Read-only sequential observational follow-up of the September16 PIONEER CARRY Panda Pack B0DCZXB76F, SKU pio-pan-bla bullet/description correction. Original action mode6-pio-returns-driven-listing-problem-b0dczxb76f; final corrective action mode6-pio-panda-spec-clarification-20260916. These are one change sequence, not separate experiments. Owner amazon-experiments with mode4 feedback. Baseline August17–September15:393sessions,13units (3.31% unit session rate). Two size comments September12/14 are qualitative reasons, NOT a return-rate denominator. Recover order-linked returns and dates; do not divide returns received in one period by orders in a different cohort. Return-rate baseline is presently unverified. No dated cost collection (operator skipped it), no dollars or causal lift. Verify shopper-visible corrected copy first; API acceptance alone does not establish shopper exposure. If exposure cannot be dated, report confounding and use a newly verified start for the observational window. Keep ads parked and all prices/listing fields unchanged. Interim checkpoint only: pull September17–29 sessions/orders/units and current return comments, compare daily rates with baseline, disclose incomplete return lag and small samples. Never call a win or stop monitoring on this interim read. Preserve October16 final checkpoint. Save substantive source reports and a dated local readout linked to this same source action. Resolve only this readout input with evidence, refresh client progress, and retain any further maturity follow-up. No external messages or account writes. Same-day final highlight correction mode6-pio-panda-highlight-clarification-20260916 was verified at 2026-09-16T17:02:33.865Z, submission fde1b2b210bc4a92b70e801a28ca9b6c: only title_differentiation changed. Include this in the existing single change sequence; do not attribute effects separately to the highlight versus bullets/description. Final API-verified change time is 2026-09-16T17:02:33.865Z; shopper exposure remains unverified. Original baseline and September30/October16 dates stay unchanged. No emails. Propagation checkpoint 2026-09-18: seller contribution (2026-09-18T22:49:25.123Z), Amazon catalog via SP-API Catalog Items (2026-09-18T22:49:26.544Z) and the public amazon.com product page (2026-09-18T22:51:04.329Z) all carry the corrected highlight, all five bullets and the description exactly as in final-after.json; the old "6 compartments" highlight is absent from the page HTML. Shopper exposure is verified as of 2026-09-18T22:51:04.329Z. Evidence: C:\Users\miraf\Sync\client-growth\runs\PIO\2026-09-18T22-48-37.981Z-304ff34f\claude-work\propagation-comparison.json. Outcome still unmeasured; dates unchanged.

Close only when: Dated source-backed readout reports metric numerator/denominator, exact comparable windows, attribution/return lag, exposure and confounders; outcome is supported improvement, no improvement or explicit inconclusive. A verified configuration or date alone never completes this action. If insufficient, preserve a named next read date.

mode6-pio-panda-spec-clarification-20260916:readout:2026-10-16:input · resolved · due 2026-10-16

The post-change report window has not matured; readout is unmeasured.

Owner: amazon-experiments. Agency coordinator: client-growth. Action: mode6-pio-panda-spec-clarification-20260916:readout:2026-10-16.

Read-only sequential observational follow-up of the September16 PIONEER CARRY Panda Pack B0DCZXB76F, SKU pio-pan-bla bullet/description correction. Original action mode6-pio-returns-driven-listing-problem-b0dczxb76f; final corrective action mode6-pio-panda-spec-clarification-20260916. These are one change sequence, not separate experiments. Owner amazon-experiments with mode4 feedback. Baseline August17–September15:393sessions,13units (3.31% unit session rate). Two size comments September12/14 are qualitative reasons, NOT a return-rate denominator. Recover order-linked returns and dates; do not divide returns received in one period by orders in a different cohort. Return-rate baseline is presently unverified. No dated cost collection (operator skipped it), no dollars or causal lift. Verify shopper-visible corrected copy first; API acceptance alone does not establish shopper exposure. If exposure cannot be dated, report confounding and use a newly verified start for the observational window. Keep ads parked and all prices/listing fields unchanged. Thirty-day checkpoint: pull September17–October15 sessions/orders/units and order-linked return cohorts. Compare pre/post with equal follow-up age; recent orders are right-censored. If matching 30-day return maturity, traffic or exposure proof is absent, explicitly inconclusive and set a further dated maturity read (e.g. November15 for orders through October15); do not label October16 a final causal verdict. Investigate new size confusion without automatically reverting verified factual copy. Save substantive source reports and a dated local readout linked to this same source action. Resolve only this readout input with evidence, refresh client progress, and retain any further maturity follow-up. No external messages or account writes. Same-day final highlight correction mode6-pio-panda-highlight-clarification-20260916 was verified at 2026-09-16T17:02:33.865Z, submission fde1b2b210bc4a92b70e801a28ca9b6c: only title_differentiation changed. Include this in the existing single change sequence; do not attribute effects separately to the highlight versus bullets/description. Final API-verified change time is 2026-09-16T17:02:33.865Z; shopper exposure remains unverified. Original baseline and September30/October16 dates stay unchanged. No emails. Propagation checkpoint 2026-09-18: seller contribution (2026-09-18T22:49:25.123Z), Amazon catalog via SP-API Catalog Items (2026-09-18T22:49:26.544Z) and the public amazon.com product page (2026-09-18T22:51:04.329Z) all carry the corrected highlight, all five bullets and the description exactly as in final-after.json; the old "6 compartments" highlight is absent from the page HTML. Shopper exposure is verified as of 2026-09-18T22:51:04.329Z. Evidence: C:\Users\miraf\Sync\client-growth\runs\PIO\2026-09-18T22-48-37.981Z-304ff34f\claude-work\propagation-comparison.json. Outcome still unmeasured; dates unchanged.

Close only when: Dated source-backed readout reports metric numerator/denominator, exact comparable windows, attribution/return lag, exposure and confounders; outcome is supported improvement, no improvement or explicit inconclusive. A verified configuration or date alone never completes this action. If insufficient, preserve a named next read date.

mode6-pio-panda-highlight-clarification-20260916:propagation:2026-09-17:input · overdue · due 2026-09-17

Independent catalog still showed the prior highlight immediately after API verification.

Owner: mode4. Agency coordinator: client-growth. Action: mode6-pio-panda-highlight-clarification-20260916:propagation:2026-09-17.

Read-only propagation checkpoint for PIONEER CARRY Panda Pack Black B0DCZXB76F / pio-pan-bla. Do not start before September17 17:15UTC (12:15Lima), roughly24hours after the final correction. Source action mode6-pio-panda-highlight-clarification-20260916 is part of the existing September16 bullet/description/highlight correction sequence. Seller Listings API verified only title_differentiation changed at2026-09-16T17:02:33.865Z; the Helium10 real-time catalog snapshot at17:03:42.589Z still returned the old highlight. Read the latest seller contribution and independent catalog/shopper surface for this exact ASIN, marketplaceUS, then compare title_differentiation/highlight, all five bullet values and product_description with final-after.json in C:\Users\miraf\projects\claude-mode-skills\artifacts\mode6-approved-2026-09-16\resume\PIO-highlight. Save exact fresh responses and observation times. Compare normalized rendered text if catalog removes HTML; do not equate a missing field with a match. Distinguish seller contribution from catalog/shopper propagation. If catalog or shopper surface is unavailable/stale, state exactly which surface is unverified; retain the previous observed old value and assign a concrete later read. DO NOT resubmit, revert, patch, change prices, touch ads or inventory, send emails or create a new experiment. No profit claim. Preserve September30/October16 observational readouts and original baseline. Record propagation confirmation time or measured remaining gap in the existing PIO observation, then resolve this dated input only with source-backed evidence.

Close only when: A dated local comparison covers expected versus observed highlight, five bullets and description for the exact US ASIN, names the source surface and latest available timestamps, and concludes propagated or specifically not yet verified. No account writes; incomplete propagation remains an explicit dated follow-up.

Latest cycle (2026-10-30T20:11:41.922Z): interrupted — Timeout: reconcile process and artifacts before any retry

Financial targets are existing contract references pending the stated validation; these dates do not change spending authority. Quarterly actuals are assessed after settlement.

Weekly progress

COULD-NOT-MEASURE · As of 2026-10-30T20:11:35.017Z

Pioneer Carry: 0 execution result(s) recorded in the last 7 days; 4 overdue action(s). Financial or evidence gaps remain.

Reporting window: from: 2026-09-28; through: 2026-10-27

MetricReported value
revenue29634.05
orders139
units139
ad Spend0
reported Net11745.82
tacos Pct0
reconciliation Difference0

PROVISIONAL — reported net is not a verified contribution margin; reconcile itemized costs and refunds.

No period comparison is available.

What changed

No changes have been recorded.

Open issues

  • Financial input gate [mode6k/kpi_contracts.json clients.PIO]: N/A-PRELAUNCH - not a gap. Full-catalog relaunch fired 2026-08-01, so there is no post-relaunch month to derive from, and the pre-relaunch months were restated (June $977 -> $582 when an order was removed) and stockout-distorted (2 orders on 458 sessions). Deriving a rung off that data would target a number the account never really posted. Next input: the PIO_Sellerboard_COGS_FILLED_2026-08-03.xlsx upload lands (operator action - see cogs_note) AND one clean post-relaunch month closes. Both are dated events, not open questions.
  • Executor interrupted: Timeout: reconcile process and artifacts before any retry
  • Codex audit COULD-NOT-MEASURE: The historical preparation remains needs_input and correctly claims no mutation or financial lift, but its required factual checks are supported only by narrative. Supplied material cannot independently verify completion criteria or current PIO state; no prior audit is resolved.
  • 41 Codex audit(s) have unresolved findings; inspect audit evidence before dependent work.

Next actions

  • Verify current financial bridge and SKU economics — in_progress — 2026-09-13 — Read existing dependency/run evidence at Sync/client-growth/runs/PIO/index.json and this action result before retry. The aggregate marketplace bridge is explained: $8,764 US + $397.78 Mexico = $9,161.78 all-market sales. Order/refund and fee populations still need reconciliation. August configured-cost coverage is 24/27 units (88.89%, below 90%). Live Safari Sling SKU PIO-SAF-BLA / ASIN B0F2H27QH1 has zero cost and accounts for the 3 uncovered August units; recover its exact supplier cost and effective date. Savant black $82.27 and Panda black $93.22 are configured Forever, which does not certify supplier historical validity. Retain Molecule Robusta and duplicate Navy Panda as broader catalog follow-ups. PPC remains parked at $0; September 19 inventory hold remains. The diagnostic $1,766.54 target is unapplied and unvalidated. Preserve all price/spend/stock constraints. Review settlement from September 15; complete input follow-up by 2026-09-16. Record source bodies, hashes, exact window and posted-net bridge. Derive any missing target only after economics gates pass. No completed intervention or measured profit is implied.
  • Select one evidence-backed growth or loss-recovery driver — open — 2026-09-16 — Read existing dependency and execution evidence from Sync/client-growth/runs/PIO/index.json before starting; preserve completed/partial effects. Client PIO only. Read the canonical registry, KPI contract and current client requests/stock holds. PIONEER CARRY ads are PARKED_PPC; selling/catalog work is still active. Keep PPC parked. Bags/pouches take priority; wallets remain secondary. Preserve the dated inventory launch file and its expiry; verify clean post-relaunch economics. Use ECONOMICS and RISK evidence plus own search-query/conversion/ads history. Rank opportunities by verified contribution potential, stock feasibility, effort and confidence; select one driver. For ads-only work use royalty efficiency. Keep discovery findings attached to existing actions; do not create duplicate campaigns/listings or change prices.
  • Prepare a measurable, bounded intervention for the chosen driver — in_progress — 2026-09-19 — Read existing dependency and execution evidence from Sync/client-growth/runs/PIO/index.json before starting; preserve completed/partial effects. Client PIO only. Read the canonical registry, KPI contract and current client requests/stock holds. PIONEER CARRY ads are PARKED_PPC; selling/catalog work is still active. Keep PPC parked. Bags/pouches take priority; wallets remain secondary. Preserve the dated inventory launch file and its expiry; verify clean post-relaunch economics. Design the selected intervention at unchanged prices. Record a fresh immutable baseline window, own-unit forecast, spend/resource cap supported by verified economics, stop rule, rollback, matched post-intervention readout and confounders. Research and staging only. List exact gate evidence required before any account change; preserve parked/launch restrictions.
  • Publish client progress, unresolved inputs and next actions — open — 2026-09-11 — Read existing dependency and execution evidence from Sync/client-growth/runs/PIO/index.json before starting; preserve completed/partial effects. Client PIO only. Read the canonical registry, KPI contract and current client requests/stock holds. PIONEER CARRY ads are PARKED_PPC; selling/catalog work is still active. Keep PPC parked. Bags/pouches take priority; wallets remain secondary. Preserve the dated inventory launch file and its expiry; verify clean post-relaunch economics. Review plan execution and audit outcomes. Prepare actual-versus-target reference with matching periods, evidence-backed completed work, unknowns and next priority; distinguish descriptive financial movement from causal lift and report operator interventions/time where measured.
  • Daily client decisions, execution and outcome review — implemented — Review the deterministic Mode6K intake for this client and reuse its canonical goals, selected levers, existing owners and measured results. This review cannot choose or apply independent account changes. The dispatcher routes a selected actionable lever to its owner under shared action ownership; Mode7 owns advertising. Report only a due review, changed input or unresolved decision, reusing specialist evidence and preserving the price lock.

Latest execution: claude — interrupted — mode6-pio-inventory-availabili-pio-saf-bla-.

  • claude — interrupted
Weekly evidence and sources
facts
source: C:\Users\miraf\projects\mode6-catalog-gap-audit\inputs_PIO\PIO_ProfitAndLoss_2026-09-28_2026-10-27.csv; period: from: 2026-09-28; through: 2026-10-27; modified At: 2026-10-28T07:17:23.625Z
evidence
Not recorded
execution Evidence
source Path
Not recorded

Codex audit

COULD-NOT-MEASURE — The historical preparation remains needs_input and correctly claims no mutation or financial lift, but its required factual checks are supported only by narrative. Supplied material cannot independently verify completion criteria or current PIO state; no prior audit is resolved.

Pending: 64. Coverage is limited to registered work and supplied evidence.

Actions and next steps

ActionOwnerStatusDueNext action
Reconcile current client priorities, prior work and constraintsclient-growth + mode6k + ppc-recapcompleted2026-09-11Read existing dependency and execution evidence from Sync/client-growth/runs/PIO/index.json before starting; preserve completed/partial effects. Client PIO only. Read the canonical registry, KPI contract and current client requests/stock holds. PIONEER CARRY ads are PARKED_PPC; selling/catalog work is still active. Keep PPC parked. Bags/pouches take priority; wallets remain secondary. Preserve the dated inventory launch file and its expiry; verify clean post-relaunch economics. Read current client documents, action/lever history and unresolved tasks; deduplicate completed work and identify existing owners. Produce a client-specific priority and constraint map with explicit unresolved requests. Do not send messages or change accounts.
Verify current financial bridge and SKU economicsmom-report + catalog-econ + mode6kin_progress2026-09-13Read existing dependency/run evidence at Sync/client-growth/runs/PIO/index.json and this action result before retry. The aggregate marketplace bridge is explained: $8,764 US + $397.78 Mexico = $9,161.78 all-market sales. Order/refund and fee populations still need reconciliation. August configured-cost coverage is 24/27 units (88.89%, below 90%). Live Safari Sling SKU PIO-SAF-BLA / ASIN B0F2H27QH1 has zero cost and accounts for the 3 uncovered August units; recover its exact supplier cost and effective date. Savant black $82.27 and Panda black $93.22 are configured Forever, which does not certify supplier historical validity. Retain Molecule Robusta and duplicate Navy Panda as broader catalog follow-ups. PPC remains parked at $0; September 19 inventory hold remains. The diagnostic $1,766.54 target is unapplied and unvalidated. Preserve all price/spend/stock constraints. Review settlement from September 15; complete input follow-up by 2026-09-16. Record source bodies, hashes, exact window and posted-net bridge. Derive any missing target only after economics gates pass. No completed intervention or measured profit is implied.
Verify saleable stock, offers and account risksinventory-replenish + amazon-featured-offer + mode10-daily-checkcompleted2026-09-13Read existing dependency and execution evidence from Sync/client-growth/runs/PIO/index.json before starting; preserve completed/partial effects. Client PIO only. Read the canonical registry, KPI contract and current client requests/stock holds. PIONEER CARRY ads are PARKED_PPC; selling/catalog work is still active. Keep PPC parked. Bags/pouches take priority; wallets remain secondary. Preserve the dated inventory launch file and its expiry; verify clean post-relaunch economics. Read current saleable/reserved/inbound stock, velocity and stock-hold instructions; inspect offer/account/catalog risks and prior repairs. Check existing claims before proposing another. Save dated current evidence and separate protective work from optional growth; no account mutations.
Select one evidence-backed growth or loss-recovery drivermode6 + mode6k + mode7-strategyopen2026-09-16Read existing dependency and execution evidence from Sync/client-growth/runs/PIO/index.json before starting; preserve completed/partial effects. Client PIO only. Read the canonical registry, KPI contract and current client requests/stock holds. PIONEER CARRY ads are PARKED_PPC; selling/catalog work is still active. Keep PPC parked. Bags/pouches take priority; wallets remain secondary. Preserve the dated inventory launch file and its expiry; verify clean post-relaunch economics. Use ECONOMICS and RISK evidence plus own search-query/conversion/ads history. Rank opportunities by verified contribution potential, stock feasibility, effort and confidence; select one driver. For ads-only work use royalty efficiency. Keep discovery findings attached to existing actions; do not create duplicate campaigns/listings or change prices.
Prepare a measurable, bounded intervention for the chosen drivermode6k + client-growth + self-checkin_progress2026-09-19Read existing dependency and execution evidence from Sync/client-growth/runs/PIO/index.json before starting; preserve completed/partial effects. Client PIO only. Read the canonical registry, KPI contract and current client requests/stock holds. PIONEER CARRY ads are PARKED_PPC; selling/catalog work is still active. Keep PPC parked. Bags/pouches take priority; wallets remain secondary. Preserve the dated inventory launch file and its expiry; verify clean post-relaunch economics. Design the selected intervention at unchanged prices. Record a fresh immutable baseline window, own-unit forecast, spend/resource cap supported by verified economics, stop rule, rollback, matched post-intervention readout and confounders. Research and staging only. List exact gate evidence required before any account change; preserve parked/launch restrictions.
Publish client progress, unresolved inputs and next actionsclient-growth + mode6kopen2026-09-11Read existing dependency and execution evidence from Sync/client-growth/runs/PIO/index.json before starting; preserve completed/partial effects. Client PIO only. Read the canonical registry, KPI contract and current client requests/stock holds. PIONEER CARRY ads are PARKED_PPC; selling/catalog work is still active. Keep PPC parked. Bags/pouches take priority; wallets remain secondary. Preserve the dated inventory launch file and its expiry; verify clean post-relaunch economics. Review plan execution and audit outcomes. Prepare actual-versus-target reference with matching periods, evidence-backed completed work, unknowns and next priority; distinguish descriptive financial movement from causal lift and report operator interventions/time where measured.
Daily client decisions, execution and outcome reviewclient-growthimplementedNot recordedReview the deterministic Mode6K intake for this client and reuse its canonical goals, selected levers, existing owners and measured results. This review cannot choose or apply independent account changes. The dispatcher routes a selected actionable lever to its owner under shared action ownership; Mode7 owns advertising. Report only a due review, changed input or unresolved decision, reusing specialist evidence and preserving the price lock.
PIO 2026-09-30 observational readout of approved September16 changeamazon-experimentscompleted2026-09-30Read-only sequential observational follow-up of the September16 PIONEER CARRY Panda Pack B0DCZXB76F, SKU pio-pan-bla bullet/description correction. Original action mode6-pio-returns-driven-listing-problem-b0dczxb76f; final corrective action mode6-pio-panda-spec-clarification-20260916. These are one change sequence, not separate experiments. Owner amazon-experiments with mode4 feedback. Baseline August17–September15:393sessions,13units (3.31% unit session rate). Two size comments September12/14 are qualitative reasons, NOT a return-rate denominator. Recover order-linked returns and dates; do not divide returns received in one period by orders in a different cohort. Return-rate baseline is presently unverified. No dated cost collection (operator skipped it), no dollars or causal lift. Verify shopper-visible corrected copy first; API acceptance alone does not establish shopper exposure. If exposure cannot be dated, report confounding and use a newly verified start for the observational window. Keep ads parked and all prices/listing fields unchanged. Interim checkpoint only: pull September17–29 sessions/orders/units and current return comments, compare daily rates with baseline, disclose incomplete return lag and small samples. Never call a win or stop monitoring on this interim read. Preserve October16 final checkpoint. Save substantive source reports and a dated local readout linked to this same source action. Resolve only this readout input with evidence, refresh client progress, and retain any further maturity follow-up. No external messages or account writes. Same-day final highlight correction mode6-pio-panda-highlight-clarification-20260916 was verified at 2026-09-16T17:02:33.865Z, submission fde1b2b210bc4a92b70e801a28ca9b6c: only title_differentiation changed. Include this in the existing single change sequence; do not attribute effects separately to the highlight versus bullets/description. Final API-verified change time is 2026-09-16T17:02:33.865Z; shopper exposure remains unverified. Original baseline and September30/October16 dates stay unchanged. No emails. Propagation checkpoint 2026-09-18: seller contribution (2026-09-18T22:49:25.123Z), Amazon catalog via SP-API Catalog Items (2026-09-18T22:49:26.544Z) and the public amazon.com product page (2026-09-18T22:51:04.329Z) all carry the corrected highlight, all five bullets and the description exactly as in final-after.json; the old "6 compartments" highlight is absent from the page HTML. Shopper exposure is verified as of 2026-09-18T22:51:04.329Z. Evidence: C:\Users\miraf\Sync\client-growth\runs\PIO\2026-09-18T22-48-37.981Z-304ff34f\claude-work\propagation-comparison.json. Outcome still unmeasured; dates unchanged.
PIO 2026-10-16 observational readout of approved September16 changeamazon-experimentscompleted2026-10-16Read-only sequential observational follow-up of the September16 PIONEER CARRY Panda Pack B0DCZXB76F, SKU pio-pan-bla bullet/description correction. Original action mode6-pio-returns-driven-listing-problem-b0dczxb76f; final corrective action mode6-pio-panda-spec-clarification-20260916. These are one change sequence, not separate experiments. Owner amazon-experiments with mode4 feedback. Baseline August17–September15:393sessions,13units (3.31% unit session rate). Two size comments September12/14 are qualitative reasons, NOT a return-rate denominator. Recover order-linked returns and dates; do not divide returns received in one period by orders in a different cohort. Return-rate baseline is presently unverified. No dated cost collection (operator skipped it), no dollars or causal lift. Verify shopper-visible corrected copy first; API acceptance alone does not establish shopper exposure. If exposure cannot be dated, report confounding and use a newly verified start for the observational window. Keep ads parked and all prices/listing fields unchanged. Thirty-day checkpoint: pull September17–October15 sessions/orders/units and order-linked return cohorts. Compare pre/post with equal follow-up age; recent orders are right-censored. If matching 30-day return maturity, traffic or exposure proof is absent, explicitly inconclusive and set a further dated maturity read (e.g. November15 for orders through October15); do not label October16 a final causal verdict. Investigate new size confusion without automatically reverting verified factual copy. Save substantive source reports and a dated local readout linked to this same source action. Resolve only this readout input with evidence, refresh client progress, and retain any further maturity follow-up. No external messages or account writes. Same-day final highlight correction mode6-pio-panda-highlight-clarification-20260916 was verified at 2026-09-16T17:02:33.865Z, submission fde1b2b210bc4a92b70e801a28ca9b6c: only title_differentiation changed. Include this in the existing single change sequence; do not attribute effects separately to the highlight versus bullets/description. Final API-verified change time is 2026-09-16T17:02:33.865Z; shopper exposure remains unverified. Original baseline and September30/October16 dates stay unchanged. No emails. Propagation checkpoint 2026-09-18: seller contribution (2026-09-18T22:49:25.123Z), Amazon catalog via SP-API Catalog Items (2026-09-18T22:49:26.544Z) and the public amazon.com product page (2026-09-18T22:51:04.329Z) all carry the corrected highlight, all five bullets and the description exactly as in final-after.json; the old "6 compartments" highlight is absent from the page HTML. Shopper exposure is verified as of 2026-09-18T22:51:04.329Z. Evidence: C:\Users\miraf\Sync\client-growth\runs\PIO\2026-09-18T22-48-37.981Z-304ff34f\claude-work\propagation-comparison.json. Outcome still unmeasured; dates unchanged.
PIO September17 catalog propagation check for September16 copy sequencemode4completed2026-09-17Read-only propagation checkpoint for PIONEER CARRY Panda Pack Black B0DCZXB76F / pio-pan-bla. Do not start before September17 17:15UTC (12:15Lima), roughly24hours after the final correction. Source action mode6-pio-panda-highlight-clarification-20260916 is part of the existing September16 bullet/description/highlight correction sequence. Seller Listings API verified only title_differentiation changed at2026-09-16T17:02:33.865Z; the Helium10 real-time catalog snapshot at17:03:42.589Z still returned the old highlight. Read the latest seller contribution and independent catalog/shopper surface for this exact ASIN, marketplaceUS, then compare title_differentiation/highlight, all five bullet values and product_description with final-after.json in C:\Users\miraf\projects\claude-mode-skills\artifacts\mode6-approved-2026-09-16\resume\PIO-highlight. Save exact fresh responses and observation times. Compare normalized rendered text if catalog removes HTML; do not equate a missing field with a match. Distinguish seller contribution from catalog/shopper propagation. If catalog or shopper surface is unavailable/stale, state exactly which surface is unverified; retain the previous observed old value and assign a concrete later read. DO NOT resubmit, revert, patch, change prices, touch ads or inventory, send emails or create a new experiment. No profit claim. Preserve September30/October16 observational readouts and original baseline. Record propagation confirmation time or measured remaining gap in the existing PIO observation, then resolve this dated input only with source-backed evidence.

30-day plan and quarterly roadmap

First 30 days
label: First 30 days; from: 2026-09-09; through: 2026-10-08; priority: Establish current client economics and constraints, resolve input blockers, and stage one measurable driver.

Starting figures and what we still cannot measure

status
NOT-VERIFIED-FOR-ROLLOUT
source
C:\Users\miraf\Sync\client-growth\onboarding\PIO\sources.json
note
Archived actuals are evidence references, not a current financial baseline; ECONOMICS validates its own window and quality.

Targets

status
UNSIZED-INPUT-OR-SCOPE-GATE
financial Authority
mode6k/kpi_contracts.json clients.PIO
contract
status: PROVISIONAL-JULY - ladder derivation next solve cycle (July verified data on disk); posture: launch-velocity; targets: ; provenance: Not recorded; no target reason: N/A-PRELAUNCH - not a gap. Full-catalog relaunch fired 2026-08-01, so there is no post-relaunch month to derive from, and the pre-relaunch months were restated (June $977 -> $582 when an order was removed) and stockout-distorted (2 orders on 458 sessions). Deriving a rung off that data would target a number the account never really posted.; unblocks when: the PIO_Sellerboard_COGS_FILLED_2026-08-03.xlsx upload lands (operator action - see cogs_note) AND one clean post-relaunch month closes. Both are dated events, not open questions.
goal Id
PIO-CONTRIBUTION
new Growth Target
Not recorded
reason
N/A-PRELAUNCH - not a gap. Full-catalog relaunch fired 2026-08-01, so there is no post-relaunch month to derive from, and the pre-relaunch months were restated (June $977 -> $582 when an order was removed) and stockout-distorted (2 orders on 458 sessions). Deriving a rung off that data would target a number the account never really posted.
next Input
the PIO_Sellerboard_COGS_FILLED_2026-08-03.xlsx upload lands (operator action - see cogs_note) AND one clean post-relaunch month closes. Both are dated events, not open questions.

Rules for spending and scaling

1
No price, discount, coupon, shipping-charge or repricer changes. No messages, purchases or client-account mutations from these research actions.
2
Preserve existing client instructions and inventory/advertising holds; absence of a copied constraint is not authorization to ignore its source.
3
PIONEER CARRY ads are PARKED_PPC; selling/catalog work is still active. Keep PPC parked. Bags/pouches take priority; wallets remain secondary. Preserve the dated inventory launch file and its expiry; verify clean post-relaunch economics.
4
Never infer causal lift or time saved from completed tasks; use the experiment ledger and independent evidence review.

Who does the work and checks it

cadence
daily: Shared all-client daily fleet schedule, America/Lima
engine
claude
fallback
codex
live Execution
true
automatic Actions
10
total Actions
10

Plan source: C:\Users\Brian\Sync\client-growth\plans\PIO.json. Completed work and business results require dated evidence; planned actions do not prove results.

What I am working on — 9

  1. $3,048 a month raised 3 days ago

    ME — the hidden search terms are not the wording customers read, so they are mine

    Index + ad-cover 'travel backpack' (relevant, you sell this).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is worth $3,048 a month.

    the evidence behind it
    [KPI no active rung | posture launch-velocity] MODE 6 engine, source report SQP: 'travel backpack' (vol 82794): 930 purchases per week, brand share 0.00% -> $3,048/mo at stake (CONFIRMED). Action: Index + ad-cover 'travel backpack' (relevant, you sell this)

    Tracked: on the task board at https://app.clickup.com/t/86eywphwh · finding mode6-pio-non-branded-capture-term-travel-backpack.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  2. $442 a month raised 38 days ago

    ME — the hidden search terms are not the wording customers read, so they are mine

    Index + ad-cover 'travel backpack for women' (relevant, you sell this).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is worth $442 a month.

    the evidence behind it
    MODE 6 engine, source report SQP: 'travel backpack for women' (vol 36981): 441 purchases per week, brand share 0.00% -> $442/mo at stake (CONFIRMED). Action: Index + ad-cover 'travel backpack for women' (relevant, you sell this)

    Tracked: on the task board at https://app.clickup.com/t/86eyxp57e · finding mode6-pio-non-branded-capture-term-travel-backpack-for-women.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack-for-women --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack-for-women --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack-for-women --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  3. $268 a month raised 3 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    Review the storage footprint of the slowest-turning SKUs -- storage is running above 2%% of the catalog's monthly margin.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. It is usually spend that produced nothing, a fee charged wrongly, or stock Amazon owes for. This one is worth $268 a month.

    the evidence behind it
    [KPI no active rung | posture launch-velocity] MODE 6 engine, source report Inventory Planning (C4): Next month's FBA storage is estimated at $267.77 against $3962 of monthly contribution margin -> $268/mo at stake (MEASURED). Action: Review the storage footprint of the slowest-turning SKUs -- stora

    Tracked: on the task board at https://app.clickup.com/t/z8y71x3udm · finding mode6-pio-fba-fee-dimensional-account-of-margin.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-fba-fee-dimensional-account-of-margin --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-fba-fee-dimensional-account-of-margin --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-fba-fee-dimensional-account-of-margin --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  4. $116 a month raised 2 days ago

    ME — restocking and sending stock to Amazon is mine; the inventory email goes out only after every number in it is checked

    Ship 23 units of pio-div-ony-2 (B0CFZMQYS8) into FBA for Pioneer. 23 is the quantity Amazon's own Restock Report of 2026-10-29 recommends, against 0 available and 8d of total cover. Re-derive the ship plan before ordering: python ~/.claude/skills/inventory-replenish/scripts/analyze.py --client Pioneer --csv ~/inventory-pipeline/2026-10-29/Pioneer_Restock.csv --date 2026-10-29 --posture launch-velocity.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. It is usually spend that produced nothing, a fee charged wrongly, or stock Amazon owes for. This one is worth $116 a month.

    the evidence behind it
    [KPI M1 hold best-posted CM$ $5,890.04 | cm_dollars_monthly>=5890.04 | posture launch-velocity] tacos_ceiling 0.4031, cm target 5890.04/mo. Pioneer/pio-div-ony-2 (B0CFZMQYS8): 8d total cover incl. inbound (Restock Report DoS column), 4u/$392 in last 30d, 0 available, Amazon recq 23. Projected dark 2

    Tracked: NOT on the task board — nothing is chasing it but this row · finding replenish-PIO-pio-div-ony-2.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id replenish-PIO-pio-div-ony-2 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id replenish-PIO-pio-div-ony-2 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id replenish-PIO-pio-div-ony-2 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  5. $45 a month raised 38 days ago

    ME — the hidden search terms are not the wording customers read, so they are mine

    Index + ad-cover 'mens travel backpack' (relevant, you sell this).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is worth $45 a month.

    the evidence behind it
    MODE 6 engine, source report SQP: 'mens travel backpack' (vol 3092): 45 purchases per week, brand share 0.00% -> $45/mo at stake (CONFIRMED). Action: Index + ad-cover 'mens travel backpack' (relevant, you sell this)

    Tracked: NOT on the task board — nothing is chasing it but this row · finding mode6-pio-non-branded-capture-term-mens-travel-backpack.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-mens-travel-backpack --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-mens-travel-backpack --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-mens-travel-backpack --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  6. $1 a month raised 3 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    Create a removal or liquidation order for the aged units of PIO-SAF-BLA (B0F2H27QH1) -- the surcharge is a cost to STOP, not money Amazon owes back.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. It is usually spend that produced nothing, a fee charged wrongly, or stock Amazon owes for. This one is worth $1 a month.

    the evidence behind it
    [KPI no active rung | posture launch-velocity] MODE 6 engine, source report Inventory Planning (C4): PIO-SAF-BLA (B0F2H27QH1) is accruing an aged-inventory surcharge of $0.54 -> $1/mo at stake (CONFIRMED). Action: Create a removal or liquidation order for the aged units of PIO-SAF-BLA (B0F2H27QH1) -

    Tracked: NOT on the task board — nothing is chasing it but this row · finding mode6-pio-inventory-availabili-pio-saf-bla-.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-inventory-availabili-pio-saf-bla- --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-inventory-availabili-pio-saf-bla- --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-inventory-availabili-pio-saf-bla- --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  7. not sized raised 59 days ago

    ME — changing bids, budgets and campaigns is already signed off — I fire one, re-read it live, then do the rest

    run the competitor-identification pass on "passport wallet," name who took/ceded the impression share, and attach it to this finding before the monthly strategy review decides the bid -- impr_share reversed upward 2026-06:0.87% to 2026-07:0.7% to 2026-08:0.89% (RECOVERY, DEFEND to conquest ladder candidate).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Action: run the competitor-identification pass on "passport wallet," name who took/ceded the impression share, and attach it to this finding before the monthly strategy review decides the bid -- impr_share reversed upward 2026-06:0.87% to 2026-07:0.7% to 2026-08:0.89% (RECOVERY, DEFEND to conquest l

    Tracked: on the task board at https://app.clickup.com/t/86eytr3zb · finding pio-impr-share-passport-wallet-recovery-2026-09.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-impr-share-passport-wallet-recovery-2026-09 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-impr-share-passport-wallet-recovery-2026-09 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-impr-share-passport-wallet-recovery-2026-09 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  8. 80 visits a month raised 15 days ago

    ME — catalog details, images and settings are mine — the four things customers read are not

    Re-run auto_fix_chain.py --clients PIO on a box with Excel to build the target-rows xlsm, then mode8 Phase 5 canary upload.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 80 visits a month — that is not dollars.

    the evidence behind it
    PIO 93 SKUs avg 41.7%, 65 below 50%; auto_fix_chain stage=partial: Excel unavailable on this box

    Tracked: on the task board at https://app.clickup.com/t/z8y71x12gv · finding rufus-attribute-sweep-pio-structured-attrs.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id rufus-attribute-sweep-pio-structured-attrs --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id rufus-attribute-sweep-pio-structured-attrs --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id rufus-attribute-sweep-pio-structured-attrs --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  9. not sized raised 28 days ago

    ME — listing wording on a Miraflores client is mine; it ships through the copy lane and the claims check, never as a raw write

    run pio-inbound-check.mjs until PIO-PANXL-BLA and pio-pan-bla show fulfillable > 0, confirm each ASIN is buyable, then re-read unit session % for Oct 1-15 against Sept 2.74 and resolve MEASURED.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Sept vs Aug MoM (out/PIO_verified.json, gates PASS): unit session % fell 2.87 -> 2.74 while sessions rose 976 -> 1607; PIO-PANXL-BLA 0 fulfillable (15 inbound shipped), pio-pan-bla 11 fulfillable (4 receiving); 309-unit restock (2 plans, UPS ~09-28) landing now

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyydd · finding mom-PIO-cvr-restock-recovery-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mom-PIO-cvr-restock-recovery-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mom-PIO-cvr-restock-recovery-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mom-PIO-cvr-restock-recovery-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

Booked, queued or already started

  • booked to run on 16 Nov 2026 - Claude Rufus Attribute Sweep. Booked is not done.
  • in the queue - [KPI no active rung | posture launch-velocity] MODE 6 engine, source report Inventory Planning (C4): Next month's FBA storage is estimated at $267.77 against $3962 of monthly contribution margin -> $2
  • in the queue - [KPI M1 hold best-posted CM$ $5,890.04 | cm_dollars_monthly>=5890.04 | posture launch-velocity] tacos_ceiling 0.4031, cm target 5890.04/mo. Pioneer/pio-div-ony-2 (B0CFZMQYS8): 8d total cover incl. inb
  • in the queue - [KPI no active rung | posture launch-velocity] MODE 6 engine, source report Inventory Planning (C4): PIO-SAF-BLA (B0F2H27QH1) is accruing an aged-inventory surcharge of $0.54 -> $1/mo at stake (CONFIR
  • in the queue - [KPI no active rung | posture launch-velocity] MODE 6 engine, source report SQP: 'travel backpack' (vol 82794): 930 purchases per week, brand share 0.00% -> $3,048/mo at stake (CONFIRMED). Action: Ind
  • in the queue - [KPI no active rung | posture launch-velocity] MODE 6 engine, source report BusinessReport: B0HDVVD5ML Unit Session % = 0.00% -> $144/mo at stake (CONFIRMED). Action: Find out why B0HDVVD5ML converts
  • in the queue - MODE 6 engine, source report SQP: 'travel backpack for women' (vol 36981): 441 purchases per week, brand share 0.00% -> $442/mo at stake (CONFIRMED). Action: Index + ad-cover 'travel backpack for wome
  • in the queue - [KPI no active rung | posture launch-velocity] MODE 6 engine, source report BusinessReport: B0DBWK75MK Unit Session % = 1.92% -> $127/mo at stake (CONFIRMED). Action: Find out why B0DBWK75MK converts
  • in the queue - B0DCZXBHMW Savant Pack 18L Backpack: Margin -263.12/unit at 0.06 units/day (1.8/mo), a 329 dollar item with correct-looking price and COGS. Driven almost entirely by Refunds -445.90 pooled across a ti
  • in the queue - MODE 6 engine, source report SQP: 'mens travel backpack' (vol 3092): 45 purchases per week, brand share 0.00% -> $45/mo at stake (CONFIRMED). Action: Index + ad-cover 'mens travel backpack' (relevant,
  • in the queue - Action: run the competitor-identification pass on "passport wallet," name who took/ceded the impression share, and attach it to this finding before the monthly strategy review decides the bid -- impr_

What we run for them

What we do for themStateLast doneHow often
catalog + economics solveup to date31 Oct 2026, todayevery 10 days
monthly reportup to date12 Oct 2026, 19 days agoevery 35 days
replenishment planup to date26 Oct 2026, 5 days agoevery 35 days
compliance / claims sweepup to date10 Oct 2026, 20 days agoevery 35 days

Goals

Sales goal

PeriodTargetSo farHow we are doingWho is working on itOpen item
This month 2026-10 $11,000 $21,193 as of Oct 25 Ahead (367% of pace) - none open
This quarter 2026-Q4 $39,379 $21,193 as of Oct 25 Ahead (387% of pace) - none open
This year 2026 $95,969 $85,815 as of Oct 25 Ahead (123% of pace) - none open

Next year (2027): $144,268 - proposed, not graded.

Last change made for this goal: 5 days ago.

The numbers

$5,890Kept after everything (at most)at most - no ad cost is on file, and anything spent comes off this
nothingShort of the goalthe goal is being met
$14,612Soldin the last 30 days
withheldAd cost per sales dollarno ad spend on file to work it out from
$4,538Open work wortha month, if we work it
What we measureWhere it is nowWhere it needs to beWhat that means
Sales$14,612in the last 30 dayseverything customers paid, before any costs come out
People who looked1,607no target sethow many visits the products got
How many of them bought2.7%no target setabout 1 in 36 of the people who look at it buys
Average order$332no target setwhat a customer spends when they do buy
Units sold44no target sethow many items went out of the door
Ad spendwithheldcannot be worked outno ad-spend figure reached the profit report for this month - either nothing was spent or the ad figures never arrived, and the two look identical here, so neither is claimed
Ad cost per sales dollarwithheldcannot be worked outthis needs the ad spend, which is being held back above
Kept per sales dollar40.3%no target setwhat is left of each dollar after Amazon, the product itself and the ads
Kept in total (at most)$5,890goal $5,890 a monththe number every piece of work below is trying to move - shown before ad cost, because no ad cost is on file for this month

Measured as at 29 Oct 2026 (yesterday). Costs are known for 92% of the products, so what is kept is an upper bound, not a final figure. How the goal was set: DERIVED September from mom-engine (gate-verified): tacos_ceiling = cm_before_ads 5,890.04 / sales 14,611.65 = 0.4031 (BE-ACoS). cm_dollars_monthly = 5,890.04 = best posted net across August, September. Latest net +5,890.04, ad spend 0.00, TACoS 0.0% vs ceiling 40.3%. MARGIN BASIS (as configured 2026-10-28T16:33Z; sellerboard serves no historical settings, so this is NOT verified for the derived window September) measured off the account's own sellerboard settings: margin denominator = GROSS sales; VAT not deducted; multi-channel orders EXCLUDED; FBA shipping chargeback/giftwrap excluded from sales; pending returns assumed unsellable; storage fees booked in the month charged.

This board shows whether the numbers moved. It does not say we moved them - what our own work is measured to have earned is the separate figure further down.

The goal we are working to

Right now: spend to get it moving - it needs traffic before it can be judged - the account is still getting started.

Keep $5,890 a month, with ads staying under 40.3% of sales.

  1. M0 true landed break-evendefinitional — CM$ >= 0 post-ads already reached
  2. M1 hold best-posted CM$ $5,890.04highest net across the months on disk (August, September): September posted +5,890.04 — a level this account has ACTUALLY achieved, not an assumed lift this is the one we are working to

AT/ABOVE M0. Best posted CM$ is September (+5,890.04); latest September is +5,890.04. Rung is a HOLD — the rung above stays NEEDS-SIZING until a block measures a real lift.

Done this week

Since Oct 24: 0 things delivered, 0 findings acted on, 14 tickets closed, 0 automated runs.

Delivered to Downloads

No file reached Downloads for them since Oct 24.

Findings acted on

No finding moved from open to fired, verified or measured since Oct 24.

Tickets closed 14

Automated runs

No scheduled job left a receipt for them since Oct 24.

What we have produced lately

  • 16 Oct 2026PIO - COGS 2025 (Henry 2026-02-18).xlsx
  • 8 Oct 2026PIO_passport_wallet_strategy_2026-10-08.html
  • 8 Oct 2026PIO_passport_wallet_strategy_2026-10-08.pdf
  • 6 Oct 2026PIO-click-share-reconciliation-2026-10-05.pdf
  • 6 Oct 2026PIO-click-share-reconciliation-2026-10-05.html

5 things produced for them in the last 30 days.

Did it work

Nothing of theirs has been scored yet, and none of the changes we have made for them is currently on the clock to be scored in money.

4 went out without anyone writing down the before-figure, so they can never be scored - not late, unmeasurable.

What needs you — 4

  1. $474 a month raised 41 days ago

    YOU — the selling price is one of the four things I never change without you

    Ask the client to pull the return reason codes on this ASIN before any repricing action; a single-return sample this small can look like a systemic loss when it is a one-off quality or fit complaint.

    This product is selling for less than it should be, given what it now costs to make and what Amazon takes. Every sale earns less than it used to. This one is worth $474 a month.

    the evidence behind it
    B0DCZXBHMW Savant Pack 18L Backpack: Margin -263.12/unit at 0.06 units/day (1.8/mo), a 329 dollar item with correct-looking price and COGS. Driven almost entirely by Refunds -445.90 pooled across a tiny unit count, one or two return events, not a pricing or COGS problem.

    Tracked: on the task board at https://app.clickup.com/t/86eyxa0uk · finding pio-b0dczxbhmw-refund-spike.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-b0dczxbhmw-refund-spike --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-b0dczxbhmw-refund-spike --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-b0dczxbhmw-refund-spike --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  2. $144 a month raised 3 days ago

    YOU — this goes to someone outside the agency, and it cannot be taken back

    Find out why B0HDVVD5ML converts at 0.0% vs the catalog's 3.2%: check it is buyable and in stock, its images, rating and reviews, and its price against sibling products. If the listing is the cause, prepare a MODE4/MODE5 draft for approval (no live edit); otherwise drop the finding with the evidence.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. This one is worth $144 a month.

    the evidence behind it
    [KPI no active rung | posture launch-velocity] MODE 6 engine, source report BusinessReport: B0HDVVD5ML Unit Session % = 0.00% -> $144/mo at stake (CONFIRMED). Action: Find out why B0HDVVD5ML converts at 0.0% vs the catalog's 3.2%: check it is buyable and in stock, its images, rating and reviews, and

    Tracked: NOT on the task board — nothing is chasing it but this row · finding mode6-pio-conversion-b0hdvvd5ml.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-conversion-b0hdvvd5ml --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-conversion-b0hdvvd5ml --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-conversion-b0hdvvd5ml --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  3. not sized raised 4 days ago

    YOU — the unit cost (ex-shipping) for PIO B085SYL385, B0CFZCTSY3, B0CFZFQ6TG, B0CFZJVG4N, B0CFZMQYS8, B0CFZNCWJX, B0CFZRF5M5, B0CFZRJFC6, B0CFZRLMPC, B0CFZSFH43, B0DBWK75MK, B0DJGBGV4R, B0DJGBYGG6, B0F2H27QH1, B0FPRHNF3J, B0FPRNRTWM, B0GQP1GLL7, B0HF8V615L, B0HJDFHXR4, B0HJDNMZ9L

    I need you to give me the unit cost (ex-shipping) for PIO B085SYL385, B0CFZCTSY3, B0CFZFQ6TG, B0CFZJVG4N, B0CFZMQYS8, B0CFZNCWJX, B0CFZRF5M5, B0CFZRJFC6, B0CFZRLMPC, B0CFZSFH43, B0DBWK75MK, B0DJGBGV4R, B0DJGBYGG6, B0F2H27QH1, B0FPRHNF3J, B0FPRNRTWM, B0GQP1GLL7, B0HF8V615L, B0HJDFHXR4, B0HJDNMZ9L. I cannot get this anywhere else — re-running /goal-cascade PIO would only raise the same finding again, so nothing moves until you send it. Once you have, I run /goal-cascade PIO and work it to a decision.

    This one is stuck waiting on the unit cost (ex-shipping) for PIO B085SYL385, B0CFZCTSY3, B0CFZFQ6TG, B0CFZJVG4N, B0CFZMQYS8, B0CFZNCWJX, B0CFZRF5M5, B0CFZRJFC6, B0CFZRLMPC, B0CFZSFH43, B0DBWK75MK, B0DJGBGV4R, B0DJGBYGG6, B0F2H27QH1, B0FPRHNF3J, B0FPRNRTWM, B0GQP1GLL7, B0HF8V615L, B0HJDFHXR4, B0HJDNMZ9L — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    PIO readiness cogs: 16 selling ASIN(s) with a $0 cost: B085SYL385, B0CFZCTSY3, B0CFZFQ6TG, B0CFZJVG4N, B0CFZMQYS8, B0CFZNCWJX, B0CFZRF5M5, B0CFZRJFC6, B0CFZRLMPC, B0CFZSFH43, B0DBWK75MK, B0DJGBGV4R, B0DJGBYGG6, B0F2H27QH1, B0FPRHNF3J, B0FPRNRTWM; 4 selling ASIN(s) with no cost row at all: B0GQP1GLL7

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyx7m · finding goal-pio-readiness-cogs.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id goal-pio-readiness-cogs --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id goal-pio-readiness-cogs --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id goal-pio-readiness-cogs --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

the other 1 waiting on you, in the same order
  1. not sized raised 32 days ago

    YOU — PIO has zero live/scheduled promo activity on any surface — confirm whether to greenlight a first coupon/BTP

    I need you to give me PIO has zero live/scheduled promo activity on any surface — confirm whether to greenlight a first coupon/BTP. I cannot get this anywhere else — re-running /amazon-promotions PIO would only raise the same finding again, so nothing moves until you send it. Once you have, I run /amazon-promotions PIO and work it to a decision.

    This one is stuck waiting on PIO has zero live/scheduled promo activity on any surface — confirm whether to greenlight a first coupon/BTP — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    PIO promo surfaces all read empty this sweep. Action: operator call on greenlighting a first promo for PIO.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wy3n7 · finding pio-zero-promo-activity-2026-09-29.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-zero-promo-activity-2026-09-29 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-zero-promo-activity-2026-09-29 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-zero-promo-activity-2026-09-29 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

Their task board — 8 of them past due

Ranked by what each one is worth to the account per month, highest first. 4 of the 18 carry a dollar figure, $4,232 a month between them. 8 are tickets with no finding behind them at all, so they appear on no other tab on this page.

  1. $3,048 a month

    Index + ad-cover 'travel backpack' (relevant, you sell this).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is worth $3,048 a month.

    Tracked: on the task board at https://app.clickup.com/t/86eywphwh · finding mode6-pio-non-branded-capture-term-travel-backpack.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  2. $474 a month

    Ask the client to pull the return reason codes on this ASIN before any repricing action; a single-return sample this small can look like a systemic loss when it is a one-off quality or fit complaint.

    This product is selling for less than it should be, given what it now costs to make and what Amazon takes. Every sale earns less than it used to. This one is worth $474 a month.

    Tracked: on the task board at https://app.clickup.com/t/86eyxa0uk · finding pio-b0dczxbhmw-refund-spike.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-b0dczxbhmw-refund-spike --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-b0dczxbhmw-refund-spike --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-b0dczxbhmw-refund-spike --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  3. $442 a month

    Index + ad-cover 'travel backpack for women' (relevant, you sell this).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is worth $442 a month.

    Tracked: on the task board at https://app.clickup.com/t/86eyxp57e · finding mode6-pio-non-branded-capture-term-travel-backpack-for-women.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack-for-women --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack-for-women --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-non-branded-capture-term-travel-backpack-for-women --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  4. $268 a month

    Review the storage footprint of the slowest-turning SKUs -- storage is running above 2%% of the catalog's monthly margin.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. It is usually spend that produced nothing, a fee charged wrongly, or stock Amazon owes for. This one is worth $268 a month.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x3udm · finding mode6-pio-fba-fee-dimensional-account-of-margin.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-fba-fee-dimensional-account-of-margin --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-fba-fee-dimensional-account-of-margin --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mode6-pio-fba-fee-dimensional-account-of-margin --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  5. not sized

    run the competitor-identification pass on "passport wallet," name who took/ceded the impression share, and attach it to this finding before the monthly strategy review decides the bid -- impr_share reversed upward 2026-06:0.87% to 2026-07:0.7% to 2026-08:0.89% (RECOVERY, DEFEND to conquest ladder candidate).

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/86eytr3zb · finding pio-impr-share-passport-wallet-recovery-2026-09.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-impr-share-passport-wallet-recovery-2026-09 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-impr-share-passport-wallet-recovery-2026-09 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-impr-share-passport-wallet-recovery-2026-09 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  6. 80 visits a month

    Re-run auto_fix_chain.py --clients PIO on a box with Excel to build the target-rows xlsm, then mode8 Phase 5 canary upload.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. This one is sized at 80 visits a month — that is not dollars.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x12gv · finding rufus-attribute-sweep-pio-structured-attrs.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id rufus-attribute-sweep-pio-structured-attrs --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id rufus-attribute-sweep-pio-structured-attrs --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id rufus-attribute-sweep-pio-structured-attrs --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  7. not sized

    I need you to give me PIO has zero live/scheduled promo activity on any surface — confirm whether to greenlight a first coupon/BTP. I cannot get this anywhere else — re-running /amazon-promotions PIO would only raise the same finding again, so nothing moves until you send it. Once you have, I run /amazon-promotions PIO and work it to a decision.

    This one is stuck waiting on PIO has zero live/scheduled promo activity on any surface — confirm whether to greenlight a first coupon/BTP — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wy3n7 · finding pio-zero-promo-activity-2026-09-29.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-zero-promo-activity-2026-09-29 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-zero-promo-activity-2026-09-29 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id pio-zero-promo-activity-2026-09-29 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  8. not sized

    run pio-inbound-check.mjs until PIO-PANXL-BLA and pio-pan-bla show fulfillable > 0, confirm each ASIN is buyable, then re-read unit session % for Oct 1-15 against Sept 2.74 and resolve MEASURED.

    People are finding this product but not buying it. The traffic is already paid for, so every visitor who leaves without buying is money spent for nothing. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyydd · finding mom-PIO-cvr-restock-recovery-2026-10.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mom-PIO-cvr-restock-recovery-2026-10 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mom-PIO-cvr-restock-recovery-2026-10 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id mom-PIO-cvr-restock-recovery-2026-10 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  9. not sized

    I need you to give me the unit cost (ex-shipping) for PIO B085SYL385, B0CFZCTSY3, B0CFZFQ6TG, B0CFZJVG4N, B0CFZMQYS8, B0CFZNCWJX, B0CFZRF5M5, B0CFZRJFC6, B0CFZRLMPC, B0CFZSFH43, B0DBWK75MK, B0DJGBGV4R, B0DJGBYGG6, B0F2H27QH1, B0FPRHNF3J, B0FPRNRTWM, B0GQP1GLL7, B0HF8V615L, B0HJDFHXR4, B0HJDNMZ9L. I cannot get this anywhere else — re-running /goal-cascade PIO would only raise the same finding again, so nothing moves until you send it. Once you have, I run /goal-cascade PIO and work it to a decision.

    This one is stuck waiting on the unit cost (ex-shipping) for PIO B085SYL385, B0CFZCTSY3, B0CFZFQ6TG, B0CFZJVG4N, B0CFZMQYS8, B0CFZNCWJX, B0CFZRF5M5, B0CFZRJFC6, B0CFZRLMPC, B0CFZSFH43, B0DBWK75MK, B0DJGBGV4R, B0DJGBYGG6, B0F2H27QH1, B0FPRHNF3J, B0FPRNRTWM, B0GQP1GLL7, B0HF8V615L, B0HJDFHXR4, B0HJDNMZ9L — a number that exists only where you can get it, so no run of any job here will fill it in. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wyx7m · finding goal-pio-readiness-cogs.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id goal-pio-readiness-cogs --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id goal-pio-readiness-cogs --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id goal-pio-readiness-cogs --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  10. not sized

    Investigate why "pioneer carry molecule cardholder" lost 25.9 points of brand impression share this week (organic rank slip, PPC coverage gap, or a competitor's new listing/coupon) and restore visibility.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x3v39 · finding sqp-weekly-pio-sessions-pioneer-carry-molecule-cardholder-2026-10-24.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id sqp-weekly-pio-sessions-pioneer-carry-molecule-cardholder-2026-10-24 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id sqp-weekly-pio-sessions-pioneer-carry-molecule-cardholder-2026-10-24 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id sqp-weekly-pio-sessions-pioneer-carry-molecule-cardholder-2026-10-24 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

  11. nobody has sized this yet 36 days past due

    PIO: Pioneer Carry PPC launch deferred — revisit after baseline weeks TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/86eyw8q8p · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  12. nobody has sized this yet 34 days past due

    PIO Panda Black B0DCZXB76F - 3 decisions after the light set went live: drop slots 7-8? Premium A+ p06-p07? brand attribute case? TO DO · Pioneer Carry/OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/86eyxa50c · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  13. nobody has sized this yet 17 days past due

    Replies owed: BPS Bruna (flavor+who ships), PIO Henry (acct health), HGS Zoom times TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x0k25 · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  14. nobody has sized this yet 15 days past due

    [PIO] Account Health header reads At Risk (rating 200): INFORM Consumers Act priority action is due Oct 16 2026 and Regulatory Compliance sh TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x0bnk · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  15. nobody has sized this yet 9 days past due

    🟡 [PIO] Ed replied on unit costs - load sheet, exclude out-of-stock SKUs from COGS gate TO DO · Pioneer Carry/OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x1rrt · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  16. nobody has sized this yet 5 days past due

    MODE7 strategy: Monday skufix emit INCOMPLETE 13/14 clients; AFL/PIO audit >25m; competitor rung quota-skipped TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/z8y71wzuyh · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  17. nobody has sized this yet 4 days past due

    ADS AUDIT [NEEDS OPERATOR]: Brand Referral Bonus earning $0 — AFL 9 Attribution tags paused, FCS+PIO have none TO DO · SOP & Prompts/CLAUDE OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/86eyjghqu · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

  18. nobody has sized this yet 2 days past due

    PIO — follow up with Henry on Invoice #6 ($650, August) Thu 10-29 TO DO · Pioneer Carry/OPS

    This ticket records no action to take. Open it and write one, or close it — as it stands nothing on any machine here can act on it.

    No finding is attached to this ticket, so there is no record of what it is worth or why it was raised. That is a gap in whatever filed it, not a decision waiting on you.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x3dfg · no finding id is attached to it.

    When it is done: this ticket never said what would count as finished, so no command closes it — which is exactly why it has stayed open.

Nobody has said who owns this one

Nobody has said who owns this one, so it is on neither list above. That is a gap in the job that raised it, not a decision waiting on you.

  1. not sized raised 3 days ago

    NOBODY YET — nobody has decided whether "sqp-weekly" findings of this kind are mine to act on or yours to approve, so it is not on either list yet

    Investigate why "pioneer carry molecule cardholder" lost 25.9 points of brand impression share this week (organic rank slip, PPC coverage gap, or a competitor's new listing/coupon) and restore visibility.

    Customers are searching for what this product is, and it is not showing up. The demand is there and it is going to someone else. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it
    Query "pioneer carry molecule cardholder": impression share fell 25.9 points week on week (was 45.5%, now 19.5%); found by the SQP weekly decode (week 2026-10-24).

    Tracked: on the task board at https://app.clickup.com/t/z8y71x3v39 · finding sqp-weekly-pio-sessions-pioneer-carry-molecule-cardholder-2026-10-24.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id sqp-weekly-pio-sessions-pioneer-carry-molecule-cardholder-2026-10-24 --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id sqp-weekly-pio-sessions-pioneer-carry-molecule-cardholder-2026-10-24 --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PIO --id sqp-weekly-pio-sessions-pioneer-carry-molecule-cardholder-2026-10-24 --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

Issues to check

Where this is tracked

19 tasks open on their board, 8 of them past due. The most valuable, worth first:

12 more are in the “On the board” tab above, in the same order.