Brigade · Internal Product Roadmap
Updated 3 Sep 2026 · one ChefTec recipe round trip next
Current status

Next proof: one Brigade recipe imported into ChefTec.

The single-recipe flow and matching safety are in main. Edith is closing ChefTec sign-in. In parallel, we are improving ingredient interpretation, validating imported conversions, and then checking zero-state market prices.

Main 0b3a0e9 · matching safety merged · reference release brigade-rich-20260826.1
EdithClose ChefTec sign-inFinish the three bounded security corrections and return the exact SHA for review.
Shared nextProve one recipe transferBrigade → ChefBridge → ChefTec → a visible read-back receipt.
ThenValidate market pricesTest professional, wholesale, and grocery fallback evidence after identity and conversion are trustworthy.
Full Brigade product
IngestionCurrent focus
ComprehensionCore working
CalculationCore working
RecommendationEarly
ActionEarly
What is ready

Same data. Clear open questions.

✓
Shared development dataThe frozen reference and Edith's writable cloud database match the same certified release.
✓
Cost calculationThe deterministic engine and the 231¢ / 150¢ / 865¢ controls pass. Models still do not produce money.
✓
Unsafe generic linksSalt, olive oil, stock, and oyster no longer silently narrow to an unsafe specific ingredient.
!
Broader matchingThe LLM baseline is now exact-SHA pinned and reproducible. Strict output validation and prompt privacy must pass before model results count.
!
Conversion evidenceConversion math is tested. The truth of the imported legacy conversion corpus still needs a labeled accuracy test.
!
Market pricing evidenceThe price ladder works, but zero-state freshness and wholesale-versus-retail suitability are not yet certified.
ChefTec sign-inThe full flow exists on Edith's branch. Three bounded security corrections remain before approval.
ChefTec recipe transferThe services and connector exist separately. One real end-to-end import and receipt has not yet been proven.
Technical notes
  • Reference release brigade-rich-20260826.1 is pinned to application SHA eb1a68f. Edith's database passed all 16 row-count checks, 88 migrations, and the standing controls.
  • MATCH-002 used 750 public-domain recipes and 5,320 ingredient lines. The bounded correction moved 337 confirmed unsafe automatic links to review without creating a new automatic link.
  • The reference database is frozen. Manual app work uses each developer's writable database; destructive tests and migrations use disposable databases.
  • Batch hardening, ChefTec recipe publishing, invoice transfer, and Recipe Book/Menu separation remain separate work.
Do not combine the three data questions: first identify the ingredient, then validate the conversion, then judge the price evidence.
Edith · current bounded work

Finish the three sign-in corrections.

Keep CTB-001A bounded. Matching, conversions, pricing, recipe publishing, and invoices stay out of this branch.

1. RecheckConfirm every active ChefTec link before issuing a Brigade session.
2. RandomizeUse a random, expiring, single-use resume proof.
3. Fail closedRequire the actual production SMTP host, username, and password.
4. Hand backReturn one exact SHA to Architecture for the bounded rereview.
Authentication does not change matching, conversions, pricing, or the recipe screens.
Upcoming product slice

ChefTec customers enter through one login.

The customer-facing direction is “Continue with ChefTec,” not “create a Brigade account and connect it later.” Existing Brigade authentication remains underneath; ChefTec confirmation provisions or opens the correct Brigade user and organization.

1. ContinueThe customer selects Continue with ChefTec and enters the email used for ChefTec.
2. Verify emailBrigade sends a one-time code and confirms control of the mailbox.
3. Confirm accountBrigade's backend asks ChefBridge to match the ChefTec customer and site.
4. Start sessionBrigade creates or opens the existing user, organization, and standard session.
5. Show capabilityThe linked workspace uses the core recipe flow; recipe publishing remains a later explicit action.
ExceptionDuplicate or ambiguous accounts go to assisted onboarding. Brigade never guesses the destination.
ChefTec passwords, CustDetID, and OnlineID never enter the browser. The CTB-001A implementation packet now reflects this flow.
Core product flow

Complete single-recipe ingestion.

A chef gives Brigade one recipe and receives a reviewed, honestly costed Recipe Book entry.

1. AcceptOne photo, PDF, pasted recipe, or UTF-8 text source.
2. ReadName, ingredients, quantities, units, instructions, yield, sections, and source spans.
3. UnderstandMatch ingredients, qualify evidence, convert units, and surface material uncertainty.
4. CostShow batch cost when yield is unknown. Show per-serving cost and planning guidance only when yield makes them valid.
5. ReviewShow extracted content and only the corrections that affect the promised result.
6. AddCreate or update the Recipe Book entry with source, version, receipt, and Undo.
Single-flow requirement
Status
Completion target
Source input
Mostly built
Photo, PDF, text, paste, limits, source access, and single-attempt idempotency exist. A no-key fallback must never count as a successful production parse.Open complete capture flow →
Recipe content
Partial
Name, ingredients, quantities, units, instructions, and yield state land. Sections, source references, and content versioning remain.Open source-to-content visual →
Incomplete content
Mostly built
Missing instructions and missing yield are represented honestly. Yield skip/confirm, adding a missed line, and editable instructions exist; Product still needs to verify the exception sweep.Open incomplete-content states →
Ingredient comprehension
Safe · incomplete
Unsafe generic links now fail closed. On the 750-recipe holdout, 18.6% auto-link and 54.7% receive an estimate. MATCH-003 is testing semantic interpretation under the same deterministic gates.Open ingredient correction flow →
Cost result
Math green · data open
Deterministic costing and reference totals pass. Conversion-fact accuracy and zero-state market-price accuracy now receive their own validation gates instead of being implied by a passing total.Open costing UX flow →
Review and save
Walkthrough passed
Proposed recipes stay out of visible Menu results and explicit promotion exists. Recipe Book/Menu separation and proposal-memory scope remain hardening work.Open review-and-save flow →
Duplicate and update safety
Partial
Single attempts and duplicate pauses exist. Batch retry idempotency, indexed matching, stale-decision binding, and a calibrated duplicate policy remain.Open duplicate/update flow →
Recipe and Menu boundary
Blocked
Book and Menu must become separate product relationships. Until then, the UI cannot promise that saving to the book leaves Menu unchanged.Open Recipe-to-Menu continuation →
Edith now
Close CTB-001A authMake the three security corrections and pass the exact-SHA rereview.
Edith + Architecture
Finish MATCH-003Reject malformed outputs, remove money/vendor text from prompts, then compare Haiku and Sonnet.
Product + Engine
Certify conversion factsLabel imported density, package, and unit-size facts independently from the resolver.
Product + Engine + Architecture
Shared next
One ChefTec recipeSend one approved recipe through ChefBridge and Dan's connector; show the read-back result in Brigade.
Edith + Product + Architecture + Dan
Zero-state pricing validationMeasure professional-kitchen estimates and explicit wholesale or grocery fallbacks.
Product + Architecture + Engine
Passed slice
430px salt journeyLow-impact assumption, material question, explicit kosher, chooser action, and mobile layout passed on the certified SHA.
Product
Later
Batch and invoicesReuse the proven single-recipe transport only after the first round trip works.
Edith + Architecture + Product + Dan
Design
Schema sessionSeparate recipe content, Recipe Book, Menu items, versions, decisions, and external references.
Architecture + Product
Single-recipe screen flow

Show the full recipe and let the chef correct it in place.

Current app · capture
Current Brigade capture screen with camera and upload actions
Keep the current entry point for one recipe.
Current app · cost result
Current Brigade Seafood Paella result showing a lower-bound cost and open lines
Keep the useful result. The review path now keeps proposed work out of visible Menu results until the chef explicitly promotes it.
Proposed · review and add
Recipe review

Seafood Paella

Ready to add with open items.

13 ingredients · 1 instruction · serves 6
Minimum menu price$8.47+$2.54+ ingredient cost · 2 of 13 priced
Target food cost
Why 30%?
Ingredient review3 need attention · 13 total
! changes result✓ costed— open
Seafood stock · 6 cups!
Saffron threads · 1 pinch!
Frozen peas · 1 cup!
Bomba rice · 2 cups—
Large shrimp · 1 lb—
Mussels · 1 lb—
Calamari · 0.5 lb✓
Yellow onion · 1 each—
Garlic · 4 cloves—
Red bell pepper · 1 each—
Olive oil · 0.5 cup—
Lemons · 2 each—
Smoked paprika · 1 tsp✓
Instructions · 1 stepPrepare all ingredients, cook following standard technique, season to taste, and serve.
Add recipe to book
11 open lines remain editable after saving.
The full ingredient list stays on the page. Attention flags guide the chef to important rows; they do not hide the rest. “Add recipe to book” saves the recipe without automatically creating a Menu item.
Single-recipe outcomes

One flow handles four common cases.

Clean recipeShow the extracted content and cost result. The chef selects “Add recipe.” No extra correction flow is required.
Important uncertaintyAsk only the ingredient, package, conversion, or yield question that materially changes the result. Recalculate immediately.
Missing yieldShow the known batch ingredient cost and allow the recipe to be saved. Keep per-serving cost, margin, and pricing unavailable until yield is supplied.
Possible duplicateShow the likely existing recipe and let the chef update it, keep a separate recipe, or treat an exact duplicate as a no-op. Open the complete decision flow →
Single-flow finish line

Complete means one real recipe reaches the Recipe Book without cleanup.

The chef can

  • Upload one supported source without re-entering ingredients.
  • Review ingredients, instructions, yield, and the cost result together.
  • Save an honest incomplete recipe and finish it later.
  • Add or update the intended Recipe Book entry with one clear action.

Brigade prevents

  • Invented yield or $0.00 treatment for unknown lines.
  • Low-impact questions that do not change the promised result.
  • Accidental duplicate recipes and unwanted Menu items.
  • Lost source material, untraceable corrections, or irreversible changes.
Capability layers

Existing surfaces stay in the product; availability follows account state.

Demo and sandbox

Batch and invoice capture already exist for testing. Keep them available to a configured demo organization while their production contracts and tenancy safeguards are completed.

100received
83ready
9attention
4duplicates
2failed · 2 running

ChefTec-linked workspace

Use the same recipe screens after “Continue with ChefTec.” Brigade verifies the email, ChefBridge confirms the customer and site, and Brigade creates the normal session. No ChefTec password or internal ID enters the browser.

ContinueChefTec email + one-time code
ConfirmChefBridge + Calypso customer/site match
Enter Brigadeuser + organization + normal session
Linked capabilitylater unlocks explicit recipe publishing
Open the ChefBridge system architecture →
Capability rule: ChefTec sign-in is not recipe publishing. Local invoice capture is not invoice transfer. Batch capture is not batch certification.
Implementation reference

Recipe review storage.

Today extraction creates permanent Recipe and Menu state before the chef confirms the result. The first correction is a review status on the existing Recipe path, keeping it out of Menu and export until the chef adds it to the Recipe Book.

Review status nowReuse the existing Recipe, costing, projection, decision, receipt, and Undo paths. Filter unapproved recipes from Menu, export, and repair jobs until promotion.
Versioned content laterDesign RecipeContentVersion—and a separate RecipeDraft only if still needed—during the schema session for sections, source spans, updates, and bulk ingestion.
SourceArtifactPrivate original, checksum, type, location, retention, and source spans.
IngestionJob / AttemptProcessing state, extractor version, retries, typed failure, idempotency, and candidate results.
Recipe review statusCurrent content proposal, issues, duplicate state, and explicit promotion into the Recipe Book.
RecipeContentVersionImmutable ingredients, instructions, yield, source references, and component targets.
Action / ReceiptActor, base/result version, memory effect, idempotency, and exact Undo basis.
ExternalReferenceChefTec or other external identity, location, version, mapping, operation, and read-back state.
Full product direction

What follows complete ingestion.

Plate and MenuBuild sellable items from recipes and components.
InvoicesReplace the current SpoonFed-assisted ChefTec entry flow, then use confirmed prices and packages to update affected Brigade recipes.
MemoryRetain scoped chef decisions and corrections.
ActionsShow affected recipes and approve a response.
SimulationsTest changes without changing current truth.
SensoryShow qualified flavor, texture, and swap effects.
ConversationOperate validated tools through chat or voice.
Multi-location and purchasingApply the system across locations and operating work.