PHY

Growth plan

Restore or protect contribution dollars toward this client's own break-even/profit milestone; recover waste and supply first.

Weekly progress

COULD-NOT-MEASURE · As of 2026-10-31T08:41:18.353Z

Physiovolution: 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

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

• Reported net has an unexplained $121.80 difference from the displayed revenue/cost lines.
• Codex audit COULD-NOT-MEASURE: S2 is a useful dated context map, but the cited underlying pulls are not supplied and S1/S3 are truncated. It cannot independently prove required operational gates, current economics, or closure of prior audit findings.
• 31 Codex audit(s) have unresolved findings; inspect audit evidence before dependent work.

Next actions

• Verify current financial bridge and SKU economics — blocked — 2026-09-13 — Read existing dependency and execution evidence from Sync/client-growth/runs/PHY/index.json before starting; preserve completed/partial effects. Client PHY only. Read the canonical registry, KPI contract and current client requests/stock holds. Recover contribution toward its own posted milestone; preserve agency-fee exclusion only where documented. Reconcile the return-mining baseline conflict before attributing gains; audit medical/support claims. Collect same-window P&L, itemized fees/refunds, costed SKU identity and COGS coverage. Reconcile contribution vs posted net and fixed costs. Use the client's own source and enumerate missing input rows; do not replace unknowns with averages. Save the input body/hash/window and reproducible calculation. Keep target references provisional until validated.
• Select one evidence-backed growth or loss-recovery driver — open — 2026-09-16 — Read existing dependency and execution evidence from Sync/client-growth/runs/PHY/index.json before starting; preserve completed/partial effects. Client PHY only. Read the canonical registry, KPI contract and current client requests/stock holds. Recover contribution toward its own posted milestone; preserve agency-fee exclusion only where documented. Reconcile the return-mining baseline conflict before attributing gains; audit medical/support claims. 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 — open — 2026-09-19 — Read existing dependency and execution evidence from Sync/client-growth/runs/PHY/index.json before starting; preserve completed/partial effects. Client PHY only. Read the canonical registry, KPI contract and current client requests/stock holds. Recover contribution toward its own posted milestone; preserve agency-fee exclusion only where documented. Reconcile the return-mining baseline conflict before attributing gains; audit medical/support claims. 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/PHY/index.json before starting; preserve completed/partial effects. Client PHY only. Read the canonical registry, KPI contract and current client requests/stock holds. Recover contribution toward its own posted milestone; preserve agency-fee exclusion only where documented. Reconcile the return-mining baseline conflict before attributing gains; audit medical/support claims. 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 — open — 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: codex — needs_input — PHY-ECONOMICS:prepare:1fa1d30bf7e6561e.

• claude — needs_input
• codex — needs_input

Codex audit

COULD-NOT-MEASURE — S2 is a useful dated context map, but the cited underlying pulls are not supplied and S1/S3 are truncated. It cannot independently prove required operational gates, current economics, or closure of prior audit findings.

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

Actions and next steps

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\PHY\sources.json

note

Archived actuals are evidence references, not a current financial baseline; ECONOMICS validates its own window and quality.

Targets

status

CONTRACT-REFERENCE-REQUIRES-CURRENT-VALIDATION

financial Authority

mode6k/kpi_contracts.json clients.PHY

contract

status: DERIVED (July) - deterministic, derive_contract.py; AGENCY FEE EXCLUDED 2026-08-06; ceiling REFRESHED 2026-08-28 (REV 5, ticket 86eyr538g); posture: efficiency; targets: cm dollars monthly: 556.7; tacos ceiling: 0.4378; provenance: DERIVED July from mom-engine (gate-verified) - REV 3, 2026-08-06; tacos_ceiling REFRESHED REV 5, 2026-08-28 (ticket 86eyr538g). tacos_ceiling = (Sellerboard GROSS PROFIT 269.72 + ad spend 1,292.91) / sales 3,569.15 = 0.4378 (BE-ACoS) - PHY_verified.json's own `sb_grossprofit` field for July, pulled 2026-08-14 (postdates the REV 3 pull of 2026-08-06 that produced 235.23; build_actuals.py's independent net+fixed-addback reconstruction (net -30.28 + $300 retainer addback = 269.72) matches this field exactly, cross-verified 2026-08-28). This form needs no assumption about cost composition: Sellerboard's Gross profit is already net of refund cost, so adding spend back yields contribution-before-ads directly. AGENCY FEE EXCLUDED (operator directive 2026-08-06, 'this is my fee remove it from our analysis'): the $300 hand-entered Sellerboard Expenses line is MIRAFLORES' OWN RETAINER, not a client operating cost, so it belongs in NEITHER the ad ceiling NOR the M0 milestone. VERIFIED LIVE it is RECURRING, not one-off: two entries, $300 each, on 2026-06-24 and 2026-07-24 (per-day Net-minus-Gross across the staged P&Ls; the two windows showing none were pulled before the entries were typed in). PRIOR VALUES ALL WRONG: mode6k's 0.3445 used allin_gp (= NET + spend), i.e. net of the agency fee - a fixed cost loaded into a marginal ad rate, understating the ceiling by 8.41 pts; ppc-engine's 0.617 uses (sales-fees-cogs)/sales and omits the refund cost entirely; the frozen REV-3 0.4286 was itself a stale July snapshot superseded by a later mom-engine data refresh. 0.4378 is the current fee-free, refund-inclusive truth as of the 2026-08-14 pull. CONSEQUENCE: July TACoS 36.22% is BELOW the ceiling - NOT a breach; 7.56 pts of headroom = $269.42/mo of spend room. And with the fee out, July contribution is +$269.72, so M0 (CM$ >= 0) is CLEARED - there is no gap and no coverage shortfall. The plan is upside on an already-profitable account, not a rescue. Note: derive_contract.py's own generic --refresh --force recipe was tested (dry-run only, NOT applied) and rejected as unsafe for this field - its cm_dollars_monthly/milestone-ladder branch uses raw Sellerboard NET (still fee-loaded), which would wrongly flip M0 back to BELOW-BREAKEVEN; only tacos_ceiling was hand-refreshed here, cm_dollars_monthly/milestone_ladder were left on the correct fee-excluded values below.; milestone ladder: name: M0 true landed break-even; metric: cm_dollars_monthly; value: 0; sized from: definitional - CM$ >= 0 post-ads, agency fee excluded; status: CLEARED 2026-08-06 - June +556.70, July +269.72 (July refreshed REV 5 2026-08-28, was +235.23); name: M1 recover the posted best month; metric: cm_dollars_monthly; value: 556.7; sized from: best CM$ the account has actually posted (June 2026, ex-agency-fee) - derive_contract.py recipe; status: ACTIVE - July at +269.72, $286.98 short (July refreshed REV 5 2026-08-28); active milestone: 1

goal Id

PHY-CONTRIBUTION

new Growth Target

Not recorded

reason

No new client revenue promise inferred during onboarding.

next Input

Refresh own same-window economics and verify the active milestone before sizing a new growth target.

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

Recover contribution toward its own posted milestone; preserve agency-fee exclusion only where documented. Reconcile the return-mining baseline conflict before attributing gains; audit medical/support claims.

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

7

total Actions

7

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

What I am working on — 14

1. 0.5 percentage points of conversion raised 19 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

   Add measured size guidance to both PHY listings through mode4 (Too Large is the top return reason) and re-read NCX/returns at the next VoC pull.

   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 sized at 0.5 percentage points of conversion — that is not dollars.

   the evidence behind it

   VoC 10-09 unchanged: both SKUs 3.6 stars, NCX 13.2%/11.5%, returns ~25%/20%, top reason Too Large

   Tracked: on the task board at https://app.clickup.com/t/z8y71x004j · finding amazon-feedback-reviews-PHY-too-large-sizing.

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

2. not sized raised 15 days ago

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

   fix the engine spec so approved PHY actions A008 (hero bid $1.45 over its $1.16 ceiling - set MAX_BID_BY_CLASS.EXACT_HERO or clamp), A014 and A019 (keyword with comma/over 80 chars) ship in the bulk file or are rewritten legal, then rebuild. Tab_07 shows all three NOT IN BULK on week 2026-10-12.

   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: fix the engine spec so approved PHY actions A008 (hero bid $1.45 over its $1.16 ceiling - set MAX_BID_BY_CLASS.EXACT_HERO or clamp), A014 and A019 (keyword with comma/over 80 chars) ship in the bulk file or are rewritten legal, then rebuild. Tab_07 shows all three NOT IN BULK on week 2026-10

   Tracked: on the task board at https://app.clickup.com/t/z8y71x13f7 · finding phy-drift-2026-10-16-unshippable-approved-actions.

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

3. 27 visits a month raised yesterday

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

   mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

   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 27 visits a month — that is not dollars.

   the evidence behind it

   [CLICK] "strassburg sock" wk ending 2026-10-24: impr share 1.7% -> click share 0.8% -> cart 1.9% -> purchase share 1.0% (market 102 purchases/wk, ours 1; 2 ASIN(s) pulled). Failing 3 of the last 3 weeks. Worth ~6.3 clicks/wk at share parity with the stage before. Source: SP-API SQP (sqp_funnel_gap.m

   Tracked: on the task board at https://app.clickup.com/t/z8y71wypam · finding sqp-funnel-phy-strassburg-sock-click.

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

4. not sized raised 15 days ago

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

   set MAX_BID_BY_CLASS.EXACT_HERO or fix the post-clamp stage so the rank-push hold is reconciled with the ceiling; PHY A008 'plantar fasciitis night sock' hold bid $1.45 exceeds ceiling $1.16 and is not shipped, 2026-10-12 build.

   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: set MAX_BID_BY_CLASS.EXACT_HERO or fix the post-clamp stage so the rank-push hold is reconciled with the ceiling; PHY A008 'plantar fasciitis night sock' hold bid $1.45 exceeds ceiling $1.16 and is not shipped, 2026-10-12 build.

   Tracked: on the task board at https://app.clickup.com/t/z8y71x121p · finding phy-hero-bid-over-ceiling-stuck-2026-10.

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

5. not sized raised today

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

   re-check these competitor ASINs on tomorrow's mode-7-comp run and route them to the monthly strategy review once the window close dates are known. Signals (2026-10-31): B002Y2SAF4 (The Strassburg Sock) no buyable New offer: buyable on the previous run (2026-10-29), no buyable New offer now; BASE_PRODUCT not a…

   There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

   the evidence behind it

   Action: re-check these competitor ASINs on tomorrow's mode-7-comp run and route them to the monthly strategy review once the window close dates are known. Signals (2026-10-31): B002Y2SAF4 (The Strassburg Sock) no buyable New offer: buyable on the previous run (2026-10-29), no buyable New offer now; 

   Tracked: on the task board at https://app.clickup.com/t/z8y71x4a2r · finding mktwatch-PHY-B0FP422RWB-comp-oos-B002Y2SAF4.

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

6. not sized raised 20 days ago

   ME — opening or answering a case with Amazon is already signed off, one at a time

   File Help Center 'FBA product weights and dimensions' Lane B (check /cu/case-lobby for the FNSKU first; quote PANEL dims).

   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. Nobody has put a size on this one yet, so measuring it is the first step.

   the evidence behind it

   Sellerboard fbaFeeChanges 2026-10-10 pull; UNSIZED - IDR counter=0 blocks a dollar delta and the true overcharge is unknown; upper bound is the whole fee on flagged orders; deadline is the earliest row only: upper bound 8.18, B0FP422RWB 8/26 x2 (due 11/24); 7/11 order expired 10/09

   Tracked: on the task board at https://app.clickup.com/t/z8y71x05tb · finding amazon-fba-reimbursements-PHY-fee-weight-dims.

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

7. not sized raised 6 days ago

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

   Remove or re-scope the campaign-level negative "plantar fasciitis night splint sock" (NEGATIVE_EXACT) in campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US" (161917741284431) so the positive "plantar fasciitis night splint sock" (EXACT) can serve again.

   There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. Nobody has put a size on this one yet, so measuring it is the first step.

   the evidence behind it

   SELF_CANCEL collision: negative "plantar fasciitis night splint sock" (NEGATIVE_EXACT, CAMPAIGN) blocks positive "plantar fasciitis night splint sock" (EXACT) in ad group 105371249171335, campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US"; found by the T+1 D2 leaf probe.

   Tracked: on the task board at https://app.clickup.com/t/z8y71x30wf · finding ppc-t1-verify-phy-161917741284431-105371249171335-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock.

   When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-105371249171335-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-105371249171335-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-105371249171335-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

8. not sized raised 6 days ago

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

   Remove or re-scope the campaign-level negative "night splint" (NEGATIVE_EXACT) in campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US" (161917741284431) so the positive "night splint" (EXACT) can serve again.

   There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. Nobody has put a size on this one yet, so measuring it is the first step.

   the evidence behind it

   SELF_CANCEL collision: negative "night splint" (NEGATIVE_EXACT, CAMPAIGN) blocks positive "night splint" (EXACT) in ad group 145905234931098, campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US"; found by the T+1 D2 leaf probe.

   Tracked: on the task board at https://app.clickup.com/t/z8y71x30wh · finding ppc-t1-verify-phy-161917741284431-145905234931098-night-splint-night-splint.

   When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-night-splint-night-splint --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-night-splint-night-splint --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-night-splint-night-splint --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

9. not sized raised 6 days ago

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

   Remove or re-scope the campaign-level negative "plantar fasciitis night splint sock" (NEGATIVE_EXACT) in campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US" (161917741284431) so the positive "plantar fasciitis night splint sock" (EXACT) can serve again.

   There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. Nobody has put a size on this one yet, so measuring it is the first step.

   the evidence behind it

   SELF_CANCEL collision: negative "plantar fasciitis night splint sock" (NEGATIVE_EXACT, CAMPAIGN) blocks positive "plantar fasciitis night splint sock" (EXACT) in ad group 145905234931098, campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US"; found by the T+1 D2 leaf probe.

   Tracked: on the task board at https://app.clickup.com/t/z8y71x30wj · finding ppc-t1-verify-phy-161917741284431-145905234931098-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock.

   When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

10. not sized raised 6 days ago

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

    Remove or re-scope the campaign-level negative "night splint" (NEGATIVE_EXACT) in campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US" (161917741284431) so the positive "night splint" (EXACT) can serve again.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it

    SELF_CANCEL collision: negative "night splint" (NEGATIVE_EXACT, CAMPAIGN) blocks positive "night splint" (EXACT) in ad group 205432032468410, campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US"; found by the T+1 D2 leaf probe.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x30wg · finding ppc-t1-verify-phy-161917741284431-205432032468410-night-splint-night-splint.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-205432032468410-night-splint-night-splint --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-205432032468410-night-splint-night-splint --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-205432032468410-night-splint-night-splint --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

11. not sized raised 6 days ago

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

    Remove or re-scope the campaign-level negative "night splint" (NEGATIVE_EXACT) in campaign "PHY | GENERIC | SP | EXACT | B0FP422RWB_US" (520678299589912) so the positive "night splint" (EXACT) can serve again.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it

    SELF_CANCEL collision: negative "night splint" (NEGATIVE_EXACT, CAMPAIGN) blocks positive "night splint" (EXACT) in ad group 329407515494018, campaign "PHY | GENERIC | SP | EXACT | B0FP422RWB_US"; found by the T+1 D2 leaf probe.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x30wd · finding ppc-t1-verify-phy-520678299589912-329407515494018-night-splint-night-splint.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-night-splint-night-splint --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-night-splint-night-splint --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-night-splint-night-splint --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

12. not sized raised 6 days ago

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

    Remove or re-scope the campaign-level negative "plantar fasciitis night splint sock" (NEGATIVE_EXACT) in campaign "PHY | GENERIC | SP | EXACT | B0FP422RWB_US" (520678299589912) so the positive "plantar fasciitis night splint sock" (EXACT) can serve again.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. Nobody has put a size on this one yet, so measuring it is the first step.

    the evidence behind it

    SELF_CANCEL collision: negative "plantar fasciitis night splint sock" (NEGATIVE_EXACT, CAMPAIGN) blocks positive "plantar fasciitis night splint sock" (EXACT) in ad group 329407515494018, campaign "PHY | GENERIC | SP | EXACT | B0FP422RWB_US"; found by the T+1 D2 leaf probe.

    Tracked: on the task board at https://app.clickup.com/t/z8y71x30we · finding ppc-t1-verify-phy-520678299589912-329407515494018-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

13. not sized raised 32 days ago

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

    Size a Sponsored Brands budget increase for PHY on the campaigns that share SP shoppers through mode7-strategy and hand it over for spend sign-off.

    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

    AMC 2026-08-27..2026-09-26: shoppers who saw SP and SB converted at 6.86x the SP-only rate (1487 vs 42862 reach)

    Tracked: on the task board at https://app.clickup.com/t/86eyyj06t · finding amc-sb-overlap-PHY.

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

14. not sized raised 58 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 mode5-update on the main image and check price + rating count for "strassburg sock" — shoppers see us on this query and click a competitor.

    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

    SQP share shape CARD-LOSES-CLICK on "strassburg sock" — we win a smaller slice of the clicks than of the impressions (2026-08: impressions 0.34x reference), held in 2 of 2 months read; source ~/mode7-analysis/market_share_PHY_2026-09.json

    Tracked: on the task board at https://app.clickup.com/t/86eyu6j7c · finding share-shape-PHY-strassburg-sock.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id share-shape-PHY-strassburg-sock --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id share-shape-PHY-strassburg-sock --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id share-shape-PHY-strassburg-sock --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 9 Nov 2026 - Claude Feedback Hygiene Monthly. Booked is not done.
• booked to run on 5 Nov 2026 - Claude SQP Funnel Gap Weekly. Booked is not done.
• booked to run on 1 Nov 2026 - Claude Market Watch Daily. Booked is not done.
• in the queue - Action: fix the engine spec so approved PHY actions A008 (hero bid $1.45 over its $1.16 ceiling - set MAX_BID_BY_CLASS.EXACT_HERO or clamp), A014 and A019 (keyword with comma/over 80 chars) ship in th
• in the queue - Action: set MAX_BID_BY_CLASS.EXACT_HERO or fix the post-clamp stage so the rank-push hold is reconciled with the ceiling; PHY A008 'plantar fasciitis night sock' hold bid $1.45 exceeds ceiling $1.16 a

What we run for them

Goals

The numbers

Measured as at 29 Oct 2026 (yesterday). How the goal was set: DERIVED July from mom-engine (gate-verified) - REV 3, 2026-08-06; tacos_ceiling REFRESHED REV 5, 2026-08-28 (ticket 86eyr538g). tacos_ceiling = (Sellerboard GROSS PROFIT 269.72 + ad spend 1,292.91) / sales 3,569.15 = 0.4378 (BE-ACoS) - PHY_verified.json's own `sb_grossprofit` field for July, pulled 2026-08-14 (postdates the REV 3 pull of 2026-08-06 that produced 235.23; build_actuals.py's independent net+fixed-addback reconstruction (net -30.28 + $300 retainer addback = 269.72) matches this field exactly, cross-verified 2026-08-28). This form needs no assumption about cost composition: Sellerboard's Gross profit is already net of refund cost, so adding spend back yields contribution-before-ads directly. AGENCY FEE EXCLUDED (operator directive 2026-08-06, 'this is my fee remove it from our analysis'): the $300 hand-entered Sellerboard Expenses line is MIRAFLORES' OWN RETAINER, not a client operating cost, so it belongs in NEITHER the ad ceiling NOR the M0 milestone. VERIFIED LIVE it is RECURRING, not one-off: two entries, $300 each, on 2026-06-24 and 2026-07-24 (per-day Net-minus-Gross across the staged P&Ls; the two windows showing none were pulled before the entries were typed in). PRIOR VALUES ALL WRONG: mode6k's 0.3445 used allin_gp (= NET + spend), i.e. net of the agency fee - a fixed cost loaded into a marginal ad rate, understating the ceiling by 8.41 pts; ppc-engine's 0.617 uses (sales-fees-cogs)/sales and omits the refund cost entirely; the frozen REV-3 0.4286 was itself a stale July snapshot superseded by a later mom-engine data refresh. 0.4378 is the current fee-free, refund-inclusive truth as of the 2026-08-14 pull. CONSEQUENCE: July TACoS 36.22% is BELOW the ceiling - NOT a breach; 7.56 pts of headroom = $269.42/mo of spend room. And with the fee out, July contribution is +$269.72, so M0 (CM$ >= 0) is CLEARED - there is no gap and no coverage shortfall. The plan is upside on an already-profitable account, not a rescue. Note: derive_contract.py's own generic --refresh --force recipe was tested (dry-run only, NOT applied) and rejected as unsafe for this field - its cm_dollars_monthly/milestone-ladder branch uses raw Sellerboard NET (still fee-loaded), which would wrongly flip M0 back to BELOW-BREAKEVEN; only tacos_ceiling was hand-refreshed here, cm_dollars_monthly/milestone_ladder were left on the correct fee-excluded values below.

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

Done this week

Since Oct 24: 2 things delivered, 1 finding acted on, 5 tickets closed, 1 automated run.

Delivered to Downloads 2

• 25 Oct 2026MODE 7 drift guard 180 wk at risk 2 flag s CHP PHY
• 25 Oct 2026MODE 7 drift guard 180 wk at risk 2 flag s PHY CHP

Findings acted on 1

• 25 Oct 2026Verification-only recovery: all four approved campaign NEGATIVE_EXACT entries already ENABLED fired

Tickets closed 5

• 27 Oct 2026PHY: gallery + A+ art still shows old calf ranges → mode5-update to 12–15.5 / 15–21 in
• 26 Oct 2026MODE 7 integration fixes 10-26: ship lane landing + run watch + PHY self-cancel negatives
• 26 Oct 2026[PHY] NEEDS SIZING — engine unshipped rows
• 25 Oct 2026[PHY] NEEDS SIZING — drift phy hero bid ceiling 2026 10
• 25 Oct 2026[PHY] NEEDS SIZING — drift phy acos approved fixes 2026 10 25

Automated runs 1

• 25 Oct 2026ppc-drift-guard red

What we have produced lately

• 25 Oct 20262026-10-25_MODE_7_drift_guard_180_wk_at_risk_2_flag_s_CHP_PHY.pdf
• 25 Oct 20262026-10-25_MODE_7_drift_guard_180_wk_at_risk_2_flag_s_CHP_PHY.html
• 25 Oct 20262026-10-25_MODE_7_drift_guard_180_wk_at_risk_2_flag_s_PHY_CHP.pdf
• 25 Oct 20262026-10-25_MODE_7_drift_guard_180_wk_at_risk_2_flag_s_PHY_CHP.html
• 16 Oct 20262026-10-16_MODE_7_drift_guard_92_wk_at_risk_2_flag_s_AET_PHY.pdf
• 16 Oct 20262026-10-16_MODE_7_drift_guard_92_wk_at_risk_2_flag_s_AET_PHY.html
• 15 Oct 20262026-10-15_MODE_7_drift_guard_116_wk_at_risk_2_flag_s_AET_PHY.pdf
• 15 Oct 20262026-10-15_MODE_7_drift_guard_116_wk_at_risk_2_flag_s_AET_PHY.html

8 things produced for them in the last 30 days.

Did it work

Finished and measured: $-745 a month across 1 change. This is the whole change over the period - gross, not attributed - not a claim that we caused all of it.

• work to get the listing in front of more people, made Aug 17 — $-745 a monthmode6-phy-non-branded-capture-term-plantar-fasciitis-night-splint mode6-phy-non-branded-capture-term-night-splint-for-plantar-fasciitis-women mode6-phy-non-branded-capture-term-night-splint mode6-phy-non-branded-capture-term-night-splint-for-plantar-fasciitis-men mode6-phy-non-branded-capture-term-plantar-fasciitis-socks mode6-phy-non-branded-capture-term-strassburg-sock-for-plantar-fasciitis mode6-phy-non-branded-capture-term-night-splints

7 changes are inside the waiting period and will be scored when it ends. 16 went out without anyone writing down the before-figure, so they can never be scored - not late, unmeasurable. 2 finished the waiting period and are ready to be measured now.

What needs you — 3

1. not sized raised 19 days ago

   YOU — the answer is a number or a fact that only you have

   size the PHY gap: pull sessions and stock cover so the cause can be named, then re-run pace.

   There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. Nobody has put a size on this one yet, so measuring it is the first step.

   the evidence behind it

   PHY 60-day goal 2026-09..2026-10 is BEHIND while the month is not; PHY 2026-10 revenue at 85% of pace (3,315 vs 3,915 expected to date, goal 5,760, goal_history/actuals/PHY.json (Sellerboard by-month + daily), goal_history/goal_cascade.json targets); gap type UNKNOWN (ladder rung 60d): behind, but t

   Tracked: on the task board at https://app.clickup.com/t/z8y71x09tj · finding goal-phy-2026-09_2026-10-ladder.

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

2. not sized raised 7 days ago

   YOU — Approve a 10% Night Splint coupon Oct 30-Nov 9 on the same 2 ASINs to bridge the gap before the Nov 10 leg

   I need you to give me Approve a 10% Night Splint coupon Oct 30-Nov 9 on the same 2 ASINs to bridge the gap before the Nov 10 leg. I cannot get this anywhere else — re-running /amazon-promotions PHY would only raise the same finding again, so nothing moves until you send it. Once you have, I run /amazon-promotions PHY and work it to a decision.

   This one is stuck waiting on Approve a 10% Night Splint coupon Oct 30-Nov 9 on the same 2 ASINs to bridge the gap before the Nov 10 leg — 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

   PHY 10% Night Splint coupon (2 ASINs) ends Oct 29: 529 dollars sales, 14 redemptions, down from 1,548 and 41 redemptions on the Aug 25-Sep 24 leg. Only staged follow-ons are the Sock coupons (Nov 10-Dec 9, Dec 10-15), so the main ASINs go uncovered Oct 30-Nov 9. Margin gate not verified. Action: rel

   Tracked: on the task board at https://app.clickup.com/t/z8y71x30xp · finding amazon-promotions-phy-nightsplint-coupon-continuity.

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

3. not sized raised 36 days ago

   YOU — Approve relaunch of PHYs expired coupon (ended 2026-09-24, drove 564.96 dollars / 15 redemptions) once depth/budget/ASINs are re-pulled and the margin gate is checked at current COGS -- or say retire it.

   I need you to give me Approve relaunch of PHYs expired coupon (ended 2026-09-24, drove 564.96 dollars / 15 redemptions) once depth/budget/ASINs are re-pulled and the margin gate is checked at current COGS -- or say retire it.. I cannot get this anywhere else — re-running /amazon-promotions PHY would only raise the same finding again, so nothing moves until you send it. Once you have, I run /amazon-promotions PHY and work it to a decision.

   This one is stuck waiting on Approve relaunch of PHYs expired coupon (ended 2026-09-24, drove 564.96 dollars / 15 redemptions) once depth/budget/ASINs are re-pulled and the margin gate is checked at current COGS -- or say retire it. — 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

   Coupon expired 2026-09-24 after driving 564.96 dollars sales and 15 redemptions in its window; discount depth, budget and ASIN list were not preserved before this sweep report closed out, so the AUTO-RELAUNCH margin-gate bounds cannot be verified this run. Action: re-read PHYs Manage Promotions coup

   Tracked: on the task board at https://app.clickup.com/t/86eyyt7g0 · finding amazon-promotions-phy-coupon-relaunch.

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

Their task board — 11 of them past due

Ranked by what each one is worth to the account per month, highest first. None of them carry a dollar figure — nobody has sized any of these, so they are ordered by how late they are, which is the only signal left. 11 are tickets with no finding behind them at all, so they appear on no other tab on this page.

1. 0.5 percentage points of conversion

   Add measured size guidance to both PHY listings through mode4 (Too Large is the top return reason) and re-read NCX/returns at the next VoC pull.

   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 sized at 0.5 percentage points of conversion — that is not dollars.

   Tracked: on the task board at https://app.clickup.com/t/z8y71x004j · finding amazon-feedback-reviews-PHY-too-large-sizing.

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

2. not sized

   fix the engine spec so approved PHY actions A008 (hero bid $1.45 over its $1.16 ceiling - set MAX_BID_BY_CLASS.EXACT_HERO or clamp), A014 and A019 (keyword with comma/over 80 chars) ship in the bulk file or are rewritten legal, then rebuild. Tab_07 shows all three NOT IN BULK on week 2026-10-12.

   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/z8y71x13f7 · finding phy-drift-2026-10-16-unshippable-approved-actions.

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

3. not sized

   set MAX_BID_BY_CLASS.EXACT_HERO or fix the post-clamp stage so the rank-push hold is reconciled with the ceiling; PHY A008 'plantar fasciitis night sock' hold bid $1.45 exceeds ceiling $1.16 and is not shipped, 2026-10-12 build.

   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/z8y71x121p · finding phy-hero-bid-over-ceiling-stuck-2026-10.

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

4. 27 visits a month

   mode5: test the main image against the top-3 on this query; price is the operator's call and is handed over, never changed.

   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 27 visits a month — that is not dollars.

   Tracked: on the task board at https://app.clickup.com/t/z8y71wypam · finding sqp-funnel-phy-strassburg-sock-click.

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

5. not sized

   re-check these competitor ASINs on tomorrow's mode-7-comp run and route them to the monthly strategy review once the window close dates are known. Signals (2026-10-31): B002Y2SAF4 (The Strassburg Sock) no buyable New offer: buyable on the previous run (2026-10-29), no buyable New offer now; BASE_PRODUCT not a…

   There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. 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/z8y71x4a2r · finding mktwatch-PHY-B0FP422RWB-comp-oos-B002Y2SAF4.

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

6. not sized

   Run mode5-update on the main image and check price + rating count for "strassburg sock" — shoppers see us on this query and click a competitor.

   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/86eyu6j7c · finding share-shape-PHY-strassburg-sock.

   When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id share-shape-PHY-strassburg-sock --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id share-shape-PHY-strassburg-sock --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id share-shape-PHY-strassburg-sock --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 Approve relaunch of PHYs expired coupon (ended 2026-09-24, drove 564.96 dollars / 15 redemptions) once depth/budget/ASINs are re-pulled and the margin gate is checked at current COGS -- or say retire it.. I cannot get this anywhere else — re-running /amazon-promotions PHY would only raise the same finding again, so nothing moves until you send it. Once you have, I run /amazon-promotions PHY and work it to a decision.

   This one is stuck waiting on Approve relaunch of PHYs expired coupon (ended 2026-09-24, drove 564.96 dollars / 15 redemptions) once depth/budget/ASINs are re-pulled and the margin gate is checked at current COGS -- or say retire it. — 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/86eyyt7g0 · finding amazon-promotions-phy-coupon-relaunch.

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

8. not sized

   Size a Sponsored Brands budget increase for PHY on the campaigns that share SP shoppers through mode7-strategy and hand it over for spend sign-off.

   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/86eyyj06t · finding amc-sb-overlap-PHY.

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

9. not sized

   File Help Center 'FBA product weights and dimensions' Lane B (check /cu/case-lobby for the FNSKU first; quote PANEL dims).

   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. 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/z8y71x05tb · finding amazon-fba-reimbursements-PHY-fee-weight-dims.

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

10. not sized

    size the PHY gap: pull sessions and stock cover so the cause can be named, then re-run pace.

    There is a dated opportunity on this account - a deal, a promotion or a shopping event - and the window to use it closes. Missing it is not a mistake we can fix afterwards. 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/z8y71x09tj · finding goal-phy-2026-09_2026-10-ladder.

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

11. not sized

    I need you to give me Approve a 10% Night Splint coupon Oct 30-Nov 9 on the same 2 ASINs to bridge the gap before the Nov 10 leg. I cannot get this anywhere else — re-running /amazon-promotions PHY would only raise the same finding again, so nothing moves until you send it. Once you have, I run /amazon-promotions PHY and work it to a decision.

    This one is stuck waiting on Approve a 10% Night Splint coupon Oct 30-Nov 9 on the same 2 ASINs to bridge the gap before the Nov 10 leg — 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/z8y71x30xp · finding amazon-promotions-phy-nightsplint-coupon-continuity.

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

12. not sized

    Remove or re-scope the campaign-level negative "plantar fasciitis night splint sock" (NEGATIVE_EXACT) in campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US" (161917741284431) so the positive "plantar fasciitis night splint sock" (EXACT) can serve again.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. 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/z8y71x30wf · finding ppc-t1-verify-phy-161917741284431-105371249171335-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-105371249171335-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-105371249171335-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-105371249171335-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

13. not sized

    Remove or re-scope the campaign-level negative "night splint" (NEGATIVE_EXACT) in campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US" (161917741284431) so the positive "night splint" (EXACT) can serve again.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. 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/z8y71x30wh · finding ppc-t1-verify-phy-161917741284431-145905234931098-night-splint-night-splint.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-night-splint-night-splint --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-night-splint-night-splint --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-night-splint-night-splint --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

14. not sized

    Remove or re-scope the campaign-level negative "plantar fasciitis night splint sock" (NEGATIVE_EXACT) in campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US" (161917741284431) so the positive "plantar fasciitis night splint sock" (EXACT) can serve again.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. 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/z8y71x30wj · finding ppc-t1-verify-phy-161917741284431-145905234931098-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-145905234931098-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

15. not sized

    Remove or re-scope the campaign-level negative "night splint" (NEGATIVE_EXACT) in campaign "PHY | SUPPORT | SP | SCALE_PAT | ASIN_EXACT | B0FP422RWB_US" (161917741284431) so the positive "night splint" (EXACT) can serve again.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. 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/z8y71x30wg · finding ppc-t1-verify-phy-161917741284431-205432032468410-night-splint-night-splint.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-205432032468410-night-splint-night-splint --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-205432032468410-night-splint-night-splint --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-161917741284431-205432032468410-night-splint-night-splint --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

16. not sized

    Remove or re-scope the campaign-level negative "night splint" (NEGATIVE_EXACT) in campaign "PHY | GENERIC | SP | EXACT | B0FP422RWB_US" (520678299589912) so the positive "night splint" (EXACT) can serve again.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. 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/z8y71x30wd · finding ppc-t1-verify-phy-520678299589912-329407515494018-night-splint-night-splint.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-night-splint-night-splint --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-night-splint-night-splint --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-night-splint-night-splint --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

17. not sized

    Remove or re-scope the campaign-level negative "plantar fasciitis night splint sock" (NEGATIVE_EXACT) in campaign "PHY | GENERIC | SP | EXACT | B0FP422RWB_US" (520678299589912) so the positive "plantar fasciitis night splint sock" (EXACT) can serve again.

    There is money already sitting in this account that nobody has collected. It is not new sales; it is money that is already ours. Here it is spend that produced nothing - money going out that is buying no sales. 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/z8y71x30we · finding ppc-t1-verify-phy-520678299589912-329407515494018-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock.

    When it is done, run this: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status MEASURED If we decide not to do it, run this instead: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status DROPPED The moment the change actually goes live, run this first: node ~/.claude/skills/ops/levers.mjs resolve --client PHY --id ppc-t1-verify-phy-520678299589912-329407515494018-plantar-fasciitis-night-splint-sock-plantar-fasciitis-night-splint-sock --status FIRED FIRED and MEASURED are two different points in the job, not two names for the same one.

18. nobody has sized this yet 57 days past due

    PHYS | Monitor Back End For Review TO DO · Physiovolution/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/86evktmat · 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.

19. nobody has sized this yet 53 days past due

    PHYS | PPC Script TO DO · Physiovolution/PPC

    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/86exrt9r4 · 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.

20. nobody has sized this yet 44 days past due

    RUN ON MACHINE A — PHY listing/product rebuild via /mode4 (bad reviews + declining volume) 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/86eyj4n1b · 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.

21. nobody has sized this yet 38 days past due

    Overdue brief 09-19: 10 blockers still open after the bookkeeping fix (BPS NTB lane + CHP/FCS/MR/PHY inputs) 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/86eyx8krh · 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.

22. nobody has sized this yet 31 days past due

    PHY — get physical units in hand: 2 of each size of v1 NOW + v2 samples before bulk production TO DO · Physiovolution/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/86eyujpqk · 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.

23. nobody has sized this yet 27 days past due

    MoM narrative re-asked PHY for measurements she sent 4 weeks earlier — ledger status outlived its evidence (fixed on A only; inputs_PHY is g 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/86eyujq1q · 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.

24. nobody has sized this yet 17 days past due

    PHY Brand Store: redo rows as store-native banners + About Us page, then Jackie before/after TO DO · Physiovolution/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/86eyxfkuc · 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.

25. nobody has sized this yet 13 days past due

    Need client contact email: MR, PARA, PHY (entity registry gap) TO DO · SOP & Prompts/CLAUDE OPS

    Run the check the ticket itself carries, and close it if it passes: node C:/Users/miraf/.claude/skills/ops/checks/check_mr_para_phy_contacts_resolved.mjs

    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/86eyt19km · no finding id is attached to it.

    When it is done: the check above is what closes it.

26. nobody has sized this yet 12 days past due

    [PHY] Business insurance COI must read Verified Successfully before 2026-11-02 (enhanced-safety category, 45-day deactivation clock) TO DO · Physiovolution/OPS

    Run the check the ticket itself carries, and close it if it passes: node ~/.claude/skills/ops/checks/insurance_access_granted.mjs PHY --verified

    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/86eywb2kh · no finding id is attached to it.

    When it is done: the check above is what closes it.

27. nobody has sized this yet 8 days past due

    PHY: make Large (B0FPPXFHFX) the hero, swap 3 brand video ads + store lead from Regular TO DO · Physiovolution/PPC

    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/86eyy6zq6 · 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.

28. nobody has sized this yet 6 days past due

    PHY — redraw 2 size images + rebuild A+ comparison chart (must ship WITH the flat file) CLIENT PENDING · Physiovolution/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/86eyjfk80 · 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.