Skip to report
Chief / BettterAI · all five projectsPlan v2 · 16 Nov 2026, 01:15 UTC · updated at this address

This week's plan: 16–22 Nov 2026

Your 16 Nov answers cleared all five questions and Vlada's pre-selection spec turned out to be readable, so nothing blocks the plan any more: the platform gets pre-selection built to her spec, trousers made available with fit typology, and an internal inventory assistant, while the adapter and the Tech Design Builder continue from the reviewers' feedback.

Plan only · nothing implemented · no open questions

This week's plan items by project

RocketFrogPlatform (platform and library)5 items
BettterAIDesignBuilderTech4 items
BettterAIDesignAdapter3 items
OperationalLayer (ops)1 items
BettterAIDesignBuilder (sales, paused)0 items
Source: This plan (sections below). Sales Design Builder: paused since 5 Nov

New Year goal: the full journey in 4 categories. Where it breaks today

  1. Library data

    The weekly sheet pull runs. Trouser raw materials are not imported yet. Shirt data is still being measured.

  2. Pre-selection

    The live rules-v5 covers her eligibility rules. Her 13 Nov spec adds general size tables, a size ratio and stock reservation.

  3. Adapter engine

    Blazers v1.6.23 and trousers v0.11 went live on 13 Nov. 5 fixes Elena had accepted came back.

  4. Live jobs

    Trouser jobs are refused until the 6 trouser designs are made available (decided 16 Nov).

  5. Tech pack per size

    A tech pack per design has been live since 9 Nov. Real adapted files wait on raw-material pattern files.

  6. Shirts, T-shirts

    Data is arriving. No adapter exists for either category yet.

Pre-selection to Vlada's spec (13 Nov), in build order

  1. Data foundation

    A versioned general size table. Fill designs that have no measurements of their own. Record each design's source. Flag designs that have no table.

  2. Engine

    Keep v5's eligibility rules. Add the 3:5:5:3 size target for XS–L, traded against fit within a tolerance setting.

  3. Report

    Her field list, recommended vs target per size, exclusion reasons and defect warnings.

  4. Allocation

    The user confirms quantities, the stock is reserved in one step and the rest stays available. Built after the engine passes her tests.

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

Suggested order for the week

  1. Mon: unblock data

    Make the 6 trouser designs available, release fit typology, review today's sheet pull.

  2. Mon–Wed: pre-selection

    Data foundation, engine and report to Vlada's spec.

  3. Tue–Thu: adapter

    Blazers v1.6.24 regressions. Trousers v0.12 with the 3 new models, labelled as having no master pattern.

  4. Wed–Fri: Tech Design Builder

    Recurring drawing issues, plain language, Catarina's numbering.

  5. Thu–Fri: assistant and shirts

    Inventory assistant v1 on the subscription. Read the shirt master patterns.

Tech Design Builder: Catarina's comment tracker (shared 13 Nov)

Fixed67 comments
Open28 comments
Recurring: came back after a fix12 comments
Source: Design_Builder_Flow sheet, 'Open comments' tab, read 16 Nov 2026 00:50 UTC (107 numbered comments)

In scope this week, and what waits

This week

  • Platform: pre-selection to the spec, trousers available, typology, sheet pull, inventory assistant
  • Adapter: blazers v1.6.24, trousers v0.12, shirt master patterns
  • Tech Design Builder: recurring drawing issues, plain language
  • Ops: one milestone view, chat password follow-up

Waits

  • Sales Design Builder: paused by Vlada on 5 Nov
  • Bermudas, shorts, skirts: 'No need to do the Bermudas now' (Vlada, 13 Nov)
  • Pre-selection stock reservation: after the engine passes her tests
  • 3D improvements: wait on Catarina's keep-or-stop decision
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.
Plan · RocketFrogPlatform: get the journey working end to end
  • P1.1 · Pre-selection rules-v6, built to Vlada's spec v1.0 (13 Nov) in three steps: data foundation, engine and report. Why: it's the first step of the journey, she called it critical on 4 and 10 Nov, and her spec is final. Done when: the spec's 18 acceptance tests pass on prod data and Vlada confirms the results on prod.
  • P1.2 · Make the 6 trouser designs available (decided 16 Nov) and import the prepared trouser tracker package (42 examples, 6 new raw materials). Feedback comes from whoever has platform access. Why: trousers v0.11 is live in the adapter, but the platform refuses live trouser jobs. Done when: a live trouser job runs on prod on library data.
  • P1.3 · Release fit typology for every trouser design (decided 16 Nov); Grade stays held. Why: Vlada, 13 Nov: it's missing though it's in the test pre-selection sheet, and pre-selection needs it to match fits. Done when: the typology on prod matches the sheet for each trouser design.
  • P1.4 · Push today's weekly sheet pull (06:00 UTC on QA) to prod, with a check that lists cells holding two values. Restore the pattern file for raw material 0171-B 56. Why: shirt and T-shirt data lands this week, the team agreed on one value per cell on 13 Nov, and 8 blazer pairs fail on 0171-B 56. Done when: the QA diff is approved for prod, the two-value cells are listed for the team, and the 8 pairs run.
  • P1.5 · Inventory assistant v1 in the raw-material library: internal only, read-only over the library, run on Claude Code with Vlada's Bettter subscription (decided 16 Nov). Why: Vlada asked on 13 Nov for an assistant that answers any question about the inventory. Done when: it's on prod for the Bettter team, answers stock questions with links to the records, Vlada has tried it, and an exhausted subscription shows an error instead of falling back to paid use.
Plan · BettterAIDesignAdapter: fix regressions, new trousers, prepare shirts
  • P2.1 · Blazers v1.6.24: bring back the 5 regressed steps (bz-016, bz-105, bz-134, bz-138, bz-140), bz-022's vent edge and bz-108; then Elena's answers to the v1.6.23 questions. Why: fixes she'd already accepted came back in v1.6.23. Done when: it's live on adapter.bettter.us and Elena's review confirms each item.
  • P2.2 · Trousers v0.12: Elena's 3 new models labelled as having no master pattern (decided 16 Nov), her answers to the v0.11 questions, and the double-waistband backs. Why: Elena, 13 Nov: three more trouser models are ready in the tracker. Done when: they show on /trousers/ with the label and a verdict, and Elena's review confirms.
  • P2.3 · Shirts: read the shirt master patterns into pieces and zones now; run the first pairs in the lab when they arrive. Why: the New Year goal is 4 categories and about 6½ weeks remain. Done when (this week): the shirt master patterns read correctly in the lab.
Plan · BettterAIDesignBuilderTech: work from Catarina's tracker
  • P3.1 · Number each lab item to match Catarina's sheet (#1–#108) and publish its status so she can update the sheet. Why: on 13 Nov she asked to track everything there as Open / Fixed / Recurring. Done when: all 40 open or recurring items carry a sheet number and a status.
  • P3.2 · The 9 recurring technical-drawing issues: shoulder slope, proportions, pockets, side panel read as darts, extra armhole lines, rigid sleeve V, missing back vents, hem curve, dashed lines. Why: they keep coming back; her note says what's missing now is fine-tuning, drawings and language. Done when: Catarina marks them Fixed in her sheet.
  • P3.3 · Plain language: rule codes written out in full, Grade A/B/C/0 explained, labels explained, 'awaiting ranges table' shown once, and an open/closed filter on feedback. Why: 10 open items in the Language, Titles and Feedback areas of her sheet. Done when: it's live on tech-builder.bettter.us and Catarina confirms.
  • P3.4 · Send Catarina one message listing her pending inputs: the S ranges table, the keep limit, minutes per operation, digitised Braga / Mayer / G&H samples, and keep or stop for the 3D. Why: they gate several of her open items. Done when: the message is sent and her answers go into the builder as they arrive.
Plan · OperationalLayer: one view of the New Year goal
  • P4.1 · One milestone view on ops: for each category, which journey steps work on prod. Also confirm that the 'Ask ✦' chat password was removed. Why: no single place tracks Vlada's 5 Nov goal, and the password removal was requested in an earlier task but never confirmed. Done when: the view is live on ops.bettter.us.
Plan · BettterAIDesignBuilder (sales): paused
  • Nothing this week. Why: Vlada paused it on 5 Nov so the team could focus on adaptations and the Tech Design Builder.
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.
Update log
  • 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.