Keep the bag on the launch critical path, or pause it?¶
Pause the bag line entirely and pivot the effort to hats; decide on revival after launch.
Backfilled record — written 2026-07-08
This decision predates the wiki. Reasoning reconstructed from business/STATE_OF_BUSINESS.html, ledger-claude/iverywhere_context.md, and the products index — not a contemporaneous record. Statements marked inferred are reconstruction, not documented reasoning.
At a glance¶
| Decided | April 2026 (Haley, April 3: "OK pivoting to hats only and putting a pause on the bag concept") |
| Decided by | Haley |
| Status | Active — bags are out of the launch catalog. Revival vs. kill is an open post-launch decision |
| Owner | Haley (with Joanna at Cloth Portico on the deposit resolution) |
The question¶
The bag was in the original assortment — sampled in R1 (Nov 2024 feedback covered vest, bag, and hat), planned in all four AMEDEO colorways, deposit paid to Romi. In spring 2026 an issue at the AMEDEO mill created a fabric shortage. With September 1 fixed, does the bag stay on the critical path or come off it?
The options considered¶
Option A — Keep pushing the bag for launch¶
The bag rounds out the capsule, the deposit is already paid, and R1 sample work (nickel I/W hardware, YKK Excella zippers) is sunk into it. The argument: don't strand paid-for work.
Option B — Pause the bag, pivot to hats¶
Take the bag off the launch SKU set entirely. Available fabric and vendor attention go to the SKUs that can actually make September 1. Revisit the bag after launch.
The call¶
Option B. Bags are not in the current catalog.
The reasoning¶
The fabric shortage forced a choice. The AMEDEO mill issue meant not everything planned in that fabric could happen on the launch timeline. The sources record the pivot, not a long deliberation — the mill issue is the stated cause in every doc that mentions the pause.
The launch date wins over the SKU. Inferred: this is the launch-date decision applied — the date holds, scope flexes. The bag was the flexed scope; hats (a simpler, non-AMEDEO-dependent chain via Jointop) got the attention instead, and 400 hats landed for launch.
Paused, not killed — deliberately. The State of Business explicitly keeps the question open ("revive post-launch or kill entirely?"), and the Business Plan lists "bag revival" as a V2 (Spring 2027) candidate. The pause preserved the option without spending pre-launch capacity on it.
The bag deposit paid to Romi remains an open issue tracked on the Cloth Portico vendor page — to be applied to a future run or refunded. Amounts and payment history live in the ledger.
What would change our mind¶
- The V2 (Spring 2027) roadmap review — bag revival is already a named candidate
- Resolution of the Romi deposit (applied-to-next-run would naturally reopen the bag conversation; a refund or write-off would push toward kill)
- Inferred: AMEDEO fabric availability normalizing at the mill, since the shortage was the proximate cause
Related¶
- Launch date — the fixed date this pause protected
- Olmetex + Romi supply chain — the chain the mill issue hit
- Products index — pause noted in the catalog
- Sources:
business/STATE_OF_BUSINESS.html§3/§11 ·ledger-claude/iverywhere_context.md(HQ repo)