This week's plan: 16–22 Nov 2026
All 13 plan items are now being built in 5 sessions; nothing is developed or deployed yet, and 3 of your open questions hold back parts of the platform and adapter work.
Where the 13 plan items are
Blocked — needs you 3
- B1Raw material 0171-B 56: which pattern file is right?
Its file was replaced on 11 Nov (revision 8) with one that has no readable front, so 8 blazer pairs Elena approved fail on every version.
Recommended: Put back revision 6 and keep revision 8 in the history.
Holds back: P1.4, P2.1 (bz-010, 108, 128, 148, 160, 183, 195, 205)
- B2ANDES WOOL (tr-061): remove it from the platform library?
Elena asked for it: it is cut directly from fabric, not adapted. The adapter already leaves it out.
Recommended: Yes. Archive it (reversible) rather than delete it.
Holds back: P1.2 if it is one of the 6 trouser designs
- B3Trousers release gate: score against Elena's latest platform verdicts instead of the tracker?
Her platform verdicts (tr-007, tr-108) disagree with the tracker, so every trousers release has needed your exception. Blazers already use her platform verdicts.
Recommended: Yes, as for blazers; the tracker score stays visible next to it.
Holds back: P2.2 release
Everything else in these items goes ahead while they wait. Answer in the group chat or in Chief's Feedback tab.
Every plan item, by project
Developed = built and merged. Deployed to users = live on the version users open. Verified on prod = checked there by the session. Updated 16 Nov 2026, 03:45 UTC.
- Started
- Developed
- Deployed to users
- Verified on prod
Platform and library
RocketFrogPlatform · platform.bettter.us · library.bettter.us- P1.1Pre-selection rebuilt to Vlada's spec (rules-v6)Session started: reading the spec and the live rules-v5.StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: First step of the journey; Vlada's spec v1.0 (13 Nov) is final and adds a general size table, the 3:5:5:3 size target and stock reservation.
Done when: The spec's 18 acceptance tests pass, v6 runs on prod on real library data, and Vlada confirms.
- P1.26 trouser designs available, trouser package importedSession started.Partly held: B2StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: Your decision 16 Nov. Today the platform refuses live trouser jobs.
Done when: A live trouser job runs on prod on library data.
- P1.3Fit typology released for trousers (Grade stays held)Session started.StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: Your decision 16 Nov; Vlada, 13 Nov: typology is missing for all trousers.
Done when: Typology on prod matches the sheet for every trouser design.
- P1.4This week's sheet pull to prod, with a two-values checkSession started. The QA pull runs at 06:00 UTC today.Partly held: B1StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: Shirt and T-shirt data lands this week; the team agreed on one value per cell (13 Nov).
Done when: The pull is on prod and the cells holding two values are listed for the team.
- P1.5Inventory assistant v1 (internal, on Vlada's subscription)Session started.StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: Vlada asked for it on 13 Nov; your decision 16 Nov: internal only, on Claude Code with her Bettter subscription, no API key.
Done when: Live on prod for the team, answers stock questions with links to the records, Vlada has tried it.
Adapter
BettterAIDesignAdapter · adapter.bettter.us- P2.1Blazers v1.6.24: bring back what v1.6.23 lostSession started: re-checking the 27 open feedback items on the live site first.Partly held: B1StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: Fixes Elena had accepted came back in v1.6.23 (steps on 14 + 28 pairs, sleeve vents, pocket openings).
Done when: v1.6.24 is live on adapter.bettter.us and each item is checked there.
- P2.2Trousers v0.12 with Elena's 3 new models (no master pattern)Session started.Partly held: B3StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: Elena, 13 Nov: three more models are ready in the tracker; your decision 16 Nov: add them with a label.
Done when: The new models show on the live trousers pages with the label and a verdict.
- P2.3Shirts: master patterns read into pieces and zonesSession started. The first shirt pairs come from the team when ready.StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: The New Year goal is the full journey in 4 categories.
Done when: The shirt master patterns read correctly in the lab.
Tech Design Builder
BettterAIDesignBuilderTech · tech-builder.bettter.us- P3.1One numbering with Catarina's sheet (#1–#108)Session started.StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: She asked on 13 Nov to track everything in her sheet as Open / Fixed / Recurring.
Done when: All 40 open or recurring numbers carry a status on the site.
- P3.2The 9 recurring technical-drawing issues (#35–#43)Session started.StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: They keep coming back after fixes.
Done when: Live on tech-builder.bettter.us; Catarina marks them Fixed.
- P3.3Plain language and feedback filtersSession started.StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: 10 open items in Language, Titles and Feedback of her sheet.
Done when: Live on tech-builder.bettter.us; Catarina confirms.
- P3.4Catarina's pending inputs, asked once in the builderSession started.StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: Her S ranges table, keep limit, minutes per operation, samples and 3D decision gate several items.
Done when: Asked in one message through the builder; each answer built as it arrives.
Ops
OperationalLayer · ops.bettter.us- P4.1New Year goal view on ops; 'Ask ✦' password; widget fixesSession started.StartedDevelopedDeployed to usersVerified on prodUsers: not yet
Why · done when
Why: No single place tracks Vlada's 5 Nov goal; the chat password removal was never confirmed.
Done when: The view is live on ops.bettter.us and the widget fixes are checked.
Sales Design Builder
BettterAIDesignBuilder · pausedPaused by Vlada on 5 Nov so the team can focus on adaptations and the Tech Design Builder. No session this week.
Also open, not blocking this week (3)
- Sales Design Builder (paused): restart it, perhaps on a lighter category, or keep it paused? Nothing this week depends on it.
- Sales Design Builder: rebuild the October SDA library report from the platform library, or retire it?
- Sales Design Builder: for brands' raw material, read the online shop, the outlet, or their unsold-stock file next?
New Year goal: the full journey in 4 categories. Where it breaks today
- Library data
The weekly sheet pull runs. Trouser raw materials are not imported yet. Shirt data is still being measured.
- Pre-selection
The live rules-v5 covers her eligibility rules. Her 13 Nov spec adds general size tables, a size ratio and stock reservation.
- Adapter engine
Blazers v1.6.23 and trousers v0.11 went live on 13 Nov. 5 fixes Elena had accepted came back.
- Live jobs
Trouser jobs are refused until the 6 trouser designs are made available (decided 16 Nov).
- Tech pack per size
A tech pack per design has been live since 9 Nov. Real adapted files wait on raw-material pattern files.
- Shirts, T-shirts
Data is arriving. No adapter exists for either category yet.
Pre-selection: already live vs new in her spec
Live today (rules-v5, 9 Nov)
- Measurement must fall between the min and max, both included
- Construction excludes, fit typology must be allowed, an empty rule is skipped
- Defects only add a notice
- One design size per record (SKU + size + height)
- Fit measured from the middle of each measurement band
New in spec v1.0 (13 Nov)
- A general size table for designs without their own ranges (blazers by chest, XXS–XL)
- A 3:5:5:3 size target for XS–L, weighed against fit
- Moves a record off its best size only within the tolerance (v5 has no limit)
- Flags missing or suspicious measurements; never converts a size label silently
- Confirmed quantities are reserved in one step; over-allocation is blocked
Tech Design Builder: Catarina's comment tracker (shared 13 Nov)
Decided on 16 Nov: your answers and what they change
- Q1 Inventory assistant: an internal interface, run on Claude Code with Vlada's Bettter Claude subscription. P1.5 changes from spec-only to build: internal and read-only, with no API key and no paid fallback.
- Q2 Fit typology for trousers: release it. P1.3 goes ahead; Grade stays held.
- Q3 Elena's 3 new trouser models: add them and label them as having no master pattern. P2.2 goes ahead.
- Q4 The 6 pending trouser designs: make them available; whoever has platform access gives feedback. P1.2 goes ahead.
- Q5 Shirt pairs: they're ready when they're ready. That's no longer a question; P2.3 prepares the shirt master patterns and runs the pairs once they arrive.
Vlada's pre-selection spec: read in full
- Access: the shared link opens without a login and was read in full on 16 Nov: 'Unified Preselection Logic', functional specification v1.0, 12 sections.
- Goal: recommend the best design size for each raw-material record (SKU + size + height). The user then picks the design and confirms quantities. Nothing is reserved during pre-selection.
- One set of rules with two measurement sources: a design's own ranges, or a general table for designs without them (blazers by chest width, XXS–XL; other categories need their own table).
- Eligibility: the measurement is within range (inclusive), construction excludes, fit typology must be allowed, an empty rule is skipped, and defects only warn.
- Optimisation: exactly one size per record, fit first, a 3:5:5:3 size target for XS–L, and a record moves off its best size only within a tolerance.
- Allocation: confirmed quantities are reserved in one step, two users can't take the same stock, and released stock returns to available.
- Acceptance: 18 tests. For example, the same SKU and size at two heights gives two records, and taking 30 of 50 leaves 20 available.
- The spec leaves five technical points open and says how to handle them meanwhile. A, the tolerance: make it a setting, test several levels on real inventory, and let Vlada and R&D choose. B, ratios beyond XS–L: invent none and only show the distribution. C, the trouser size table: flag trouser designs without their own ranges rather than guess. D, data quality: flag missing or suspicious measurements and never convert UK/US labels silently. E, stock integrity: reserve in one step.
Waiting on the team (not questions)
- A general size table for trousers (spec point C). Until then, trouser designs without their own ranges are flagged.
- Size ratios beyond XS–L (spec point B). Until then, the distribution is shown but not optimised.
- The tolerance choice after the test runs (spec point A): Vlada and R&D.
- Catarina's inputs for the Tech Design Builder (P3.4).
- The first shirt adaptation pairs (P2.3).
What happened since Friday
- Fri 13 Nov 09:33 UTC · Catarina · Slack #rnd_adaptations_tech: shared the 'Design_Builder_Flow' sheet with the target flow, sizing rules and 107 comments, each with a status. Goes to P3.1–P3.4.
- Fri 13 Nov 10:11 UTC · Elena · Slack #rnd_adaptations_tech: three more trouser models are ready in the Adaptation Tracker, without a master pattern. Goes to P2.2.
- Fri 13 Nov 10:18 UTC · Sara · Slack thread on the 2 Nov plan: trouser and shirt selection and measurements are done; T-shirts are selected; measuring of 23 shirts has started. Goes to P1.4 and P2.3.
- Fri 13 Nov 10:20 UTC · Vlada · Slack DM to Bohdan: sent the final pre-selection logic. Bohdan replied 'will do' at 14:33. Goes to P1.1.
- Fri 13 Nov 10:51 UTC · Vlada · Slack DM to Bohdan: fit typology is missing for all trousers; asked for an AI agent in the raw-material section. Goes to P1.3 and P1.5.
- Fri 13 Nov 10:55 UTC · Vlada to Inês and Catarina · Slack thread of 5 Nov: shirts come after trousers in the data priority; no Bermudas now. Goes to P1.4 and Waits.
- Fri 13 Nov 11:16 UTC · Vlada, with replies from Sara, Catarina and Inês · Slack #rnd_adaptations_tech: one value per cell; shirt sizes as letters only. Goes to P1.4.
- Mon 16 Nov 00:13 UTC · Bohdan · Slack DM to Vlada: the AI agent is an assistant that answers any question about the inventory, 'medium complexity'. Goes to P1.5.
Shipped Thursday night and Friday (don't redo)
- Adapter: blazers v1.6.23 and trousers v0.11 went live on prod on 13 Nov with Elena's 12 Nov review built in (32 items, 44 editor versions). PRs #76–#78.
- Tech Design Builder: v0.8.6 went live on prod and QA at 00:54 UTC on 13 Nov, with Catarina's 31 notes of 12 Nov built in (26 done, 5 with a question).
- Platform: a feedback screenshot can no longer block a comment (release #94, 00:09 UTC on 13 Nov). This fixes the freeze Vlada reported on 12 Nov; she hasn't confirmed it yet.
- Platform: the Tech Design Builder shows the raw material as a product card and the designs as a gallery (release #96, 00:51 UTC on 13 Nov).
- These come from the projects' own status pages and merge records. I didn't open the live sites; they need a login.
Sources and coverage
- Slack: all 26 chats this group can read, from 21:00 UTC Thu 12 Nov to 00:45 UTC Mon 16 Nov. I also checked replies on threads started since 25 Oct.
- Telegram: no chats are connected to this group. Calls: none recorded.
- Sheets: Design_Builder_Flow (3 tabs) and the Adaptation Tracker (trousers tab), read 16 Nov. Vlada's spec: her shared link, read 16 Nov.
- The live pre-selection: the platform repository's main branch (rules-v5). Project state: each repository's main branch and status page.
- This page leaves out credentials, payment details, private links and the spec's size numbers.
- Status of each item: the five sessions' own status tables and Chief's session records. A stage moves only on the session's evidence (merge, release, check on the live site).
Update log
- v3, 16 Nov 2026 03:45 UTC: you asked to implement all items; 5 sessions started (2 platform, adapter, Tech Design Builder, ops), one per project or group of items. The plan became a status board. 3 owner questions recorded by earlier adapter tasks hold back parts of P1.2, P1.4, P2.1 and P2.2.
- v2, 16 Nov 2026 01:15 UTC: your answers to Q1–Q5 went into the plan; Vlada's pre-selection spec was read and mapped against the live rules-v5; P1.5 changed from spec-only to build on the subscription; no open questions remain.
- v1, 16 Nov 2026 01:00 UTC: first plan from the Friday–Monday sources, with 5 open questions.