Brigade · ChefBridge strategy
First user case · proposed

One recipe from Brigade to ChefTec.

An existing ChefTec customer captures and reviews a recipe in Brigade, then sees it imported into the correct ChefTec account without downloading a file or retyping it.

One-way One recipe Create-only pilot Local or hosted ChefTec Batch and two-way sync later
1

Connect once

Authorize the correct ChefTec customer and location. Brigade stores the approved route, not the ChefTec password.

2

Review and send

The chef confirms the recipe and destination. Brigade sends one approved, versioned JSON request.

3

Verify the import

ChefTec runs its existing matching and import logic. Brigade shows imported, needs review, or failed only after ChefTec responds.

Authentication decides who and where. Recipe transfer decides what gets sent and what ChefTec accepted.
Customer journey

Three customer-facing moments.

The transfer stays in the background. The chef connects the account, reviews the full recipe, and receives a visible result.

1 · Account connection
Settings · integrations

ChefTec account

Connect the ChefTec customer that should receive approved recipes.

StatusConnected
CustomerPark City Kitchen
LocationMain kitchen
VerifiedToday
Change connection
The technical customer identifier stays in system details, not the primary chef view.
2 · Recipe approval
Recipe review

Seafood Paella

Ready to add and send to ChefTec.

Ingredients13 lines reviewed
Instructions4 steps
Yield6 servings
ChefTec targetPark City Kitchen
Add to Recipe Book & send
Save in Brigade only
If yield or another required export field is missing, the recipe can still be saved in Brigade. Sending waits for the missing field.
3 · Import receipt
ChefTec transfer

Imported

Seafood Paella was added to Park City Kitchen.

✓
QueuedBrigade sent the approved recipe.
✓
ImportedChefTec completed its matching and import.
✓
VerifiedRead-back confirmed the ChefTec recipe.
ChefTec recipe#4821
DestinationPark City Kitchen
Imported2:42 PM
Queued never means imported. Brigade shows success only after ChefTec returns a read-back receipt.
Two system flows

Connect the account. Then move the recipe.

Account authorization
BrigadeCustomer selects Connect ChefTec.
ChefTec AuthChefTec-owned sign-in or one-time code.
CalypsoValidates the customer and permitted locations.
ChefBridgeStores the scoped CustDetID connection, never a password.
Recipe transfer
Chef approvesReviewed recipe version and visible destination.
Brigade APIValidates and creates an idempotent JSON request.
ChefBridgeQueues the request for the authorized customer.
ChefTec importerRuns existing name, unit, and duplicate matching.
Status and receipt
Customer databaseLocal or hosted ChefTec receives the import.
Read-backChefTec confirms the accepted recipe and ID.
ChefBridgeStores imported, needs review, or failed.
BrigadeShows the result and a retry or review action.
Shared database communication

ChefBridge is the handoff layer.

Brigade and ChefTec keep their own databases. ChefBridge stores transfer requests and receipts between them.

Brigade ownership
Brigade appCapture, full recipe review, destination confirmation, status.
Brigade backendRecipe truth, deterministic export validation, stable recipe version.
Integration APIAuthenticated JSON request, idempotency, customer route.
→
Shared contract · ChefBridge
Customer connectionBrigade organization → authorized CustDetID and site scope.
Transfer requestOperation UUID, recipe UUID/version, request digest, versioned JSON, state.
Transfer receiptImported / needs review / failed, ChefTec ID, warnings, timestamp, read-back.
→
ChefTec ownership
ChefTec connectorRetrieves pending work for the authorized customer and reports results.
Existing importerName, item, unit, and duplicate matching remain in ChefTec.
Local databaseChefTec imports to its current local SQL Server.
Hosted databaseThe same contract targets hosted SQL Server.
ChefBridge is an isolated integration mailbox. It is not Brigade’s primary database, ChefTec’s live customer database, or permission for Brigade to edit customer tables directly.
Contract

Three durable records.

Customer connection
  • Brigade organization reference
  • CustDetID and permitted site
  • Authorization state and verification date
  • No ChefTec password
Transfer request
  • Stable external operation UUID
  • Stable recipe UUID and approved version
  • Versioned JSON and request digest
  • Queued and processing state
Transfer receipt
  • Imported, needs review, or failed
  • ChefTec recipe ID when known
  • Duplicate result, warnings, and error code
  • Import time and read-back evidence
Account
Not connected→Connecting→ConnectedConnection failed / expired
Recipe
Reviewed→ChefTec ready→Queued→Importing→ImportedNeeds review / failed
Retries reuse the same operation ID and request digest. A retry cannot create a second recipe.
Ownership

Each team owns one side of the boundary.

ChefConnect account, confirm destination, review recipe, approve send, resolve exceptions.
BrigadeCapture, validation, recipe JSON, idempotency, ChefBridge write, customer-facing status.
Shared contractSchema version, state codes, customer routing, security boundary, test fixture.
Dan / ChefTecCalypso validation, pending-work retrieval, matching, duplicate handling, import, read-back.
First proof

Prove one recipe before adding breadth.

Pilot setup

  1. One disposable hosted ChefTec customer database.
  2. One approved test CustDetID and location.
  3. One Brigade organization connected to it.
  4. One reviewed recipe with confirmed yield.
  5. One JSON transfer and ChefTec read-back receipt.
  6. Repeat against one local ChefTec installation before claiming both topologies.

Pass conditions

  • The correct customer and location receive the recipe.
  • Name, yield, ingredient order, quantities, units, and instructions match.
  • Brigade displays the ChefTec recipe ID only after read-back.
  • The same request retried creates no duplicate.
  • A possible duplicate stops for review instead of overwriting.
  • Wrong-customer and expired-authorization attempts are rejected.
Next Dan meeting

Decisions still to close.

  1. ChefTec-owned sign-in or one-time authorization code?
  2. What site or profit-center identifier accompanies CustDetID?
  3. What exact JSON fields will ChefTec accept?
  4. Does ChefTec poll, check on login, or expose a manual Check for recipes action?
  1. What result represents a possible duplicate?
  2. What exact warnings and fields return in the receipt?
  3. Which hosted and local sandbox customers prove the pilot?
  4. Can ChefTec accept an unknown yield, or does confirmed yield remain mandatory?
Not in the first recipe pilot: batch publishing, silent overwrite, ChefTec-to-Brigade sync, or making ChefBridge the future primary recipe database. Invoice transfer is the next separate operation after the recipe path proves delivery and read-back.