Doughex is small and at the design stage. The roles below are the ones the first design-partner deployments need. They open as the cohort forms; there is no openings count to inflate.
Illustrative scenario: Plant run · one bread line, flour-lot change at the silo · shared oven. Not a measured run.
Each role is written as a shape, not a job ad with a requisition number.
Own the camera and sensor pipeline: colour, shape, foreign-body and seal vision, inline moisture and weight fusion, TensorRT and Triton serving on Jetson, and the latency budget that makes a reject decision useful.
Build the connectors that read mixers, proofers, dividers and ovens and write guarded setpoints back, without ever touching an interlock. Own the allow-lists, rate limits and the audit record of every write.
Build Bakesim: GPU-accelerated simulation of oven thermal zones and airflow, proof dynamics and dough deformation, surrogates that run at the edge, and the reconciliation that keeps the twin honest against real runs.
Translate between the plant and the platform: define what in-spec means per product, review agent recommendations, design the food-safety and ROI gates, and sit with design partners on the floor.
Grounding, audit, human-in-the-loop and graduated control come before any write to a line.
A process engineer's correction is a labelled training event, not a complaint.
One line and one number first. The plant and the group follow the number.
Kill steps, metal detection, allergen changeover and release decisions stay with the plant's HACCP plan and its people.
Recipes and customer specs never cross a customer boundary. On-prem is an option, not an exception.
Golden datasets and model-as-judge evaluations gate model and prompt changes in CI.
Every Doughex run is an ordered, inspectable sequence. This is run_scn_01, an illustrative scenario: Plant run · one bread line, flour-lot change at the silo · shared oven. Scenario complete · every stage inside spec · one human approval at the oven.
Plant Orchestrator · Pulled the product spec, the recipe, the HACCP plan with its bake kill-step and metal-detection control points, the allergen status of the line and the new flour lot's certificate from MES and the lab system; locked the target envelope for the run.
Plant Orchestrator · Simulated 24 candidate profiles across mix, proof, deposit and oven on the Bakesim as-baked twin for the new flour lot; ranked them on colour and moisture margin, weight margin, energy per unit and takt, and discarded every candidate that thinned the bake kill-step margin.
Dose-and-Mix · Adjusted hydration and mix energy for the new lot's absorption so dough temperature and development landed on target; dough state was handed to the proofer with its predicted rise curve.
Ferment-and-Proof · Predicted the rise curve from inline height, temperature, humidity and CO2, then trimmed proofer humidity and dwell so rise and volume landed on target instead of running fast on the fresher lot.
Makeup-and-Deposit · Fused checkweigher readings with dough state and divider feedback and trimmed the divider in real time so portion weight sat at the minimum safe margin above the declared weight, with the underweight guardrail armed.
Plant Orchestrator · The twin's lowest-energy candidate wanted a zone-three temperature outside the site's bounded envelope. Held for the shift process engineer, who approved the step with a tighter colour alarm.
Bake-and-Cool · Ran the oven against the twin's colour and moisture prediction; stepped zone temperatures and band speed toward the minimum-energy profile while predicted crust colour and crumb moisture stayed inside spec and the core-temperature kill step was verified on every reading.
Defect-and-Inspect · 12 camera streams at oven exit, cooler exit and packing at the plant edge: colour, shape, holes, cracks, foreign-body and seal checks on every unit; two pale-top rejects were attributed to a draught at zone one and the oven agent was notified.
Robot-and-Handling · Robotic depanning, tray transfers and packaging handling paced to the line, with rejected units diverted off the belt and the safe zone around each cell monitored.
Quality-and-Conformance · Lot released: flour lot, recipe, mix and proof setpoints, portion weights, oven profile, kill-step readings, inspection rejects and every human decision written to the genealogy and checked against spec and the HACCP plan.
Dough is alive and the lines never stop, so perception has to be local and fast. Doughex runs GPU inference at the plant edge and keeps training, simulation and optimisation in the cloud, in a private cloud or on-prem. Items marked planned are on the roadmap, not running.
8 to 24 cameras per line plus inline moisture, weight, thermal and metal or X-ray streams. Design target: sub-100 ms reject decisions, 10 to 60 FPS per station, offline-tolerant operation at the plant edge.
Bake-prediction, defect, weight, shelf-life and bakery-reasoning models behind one orchestrator, with version routing by product, line and station. Plants run many lines, SKUs and models at once.
Vision, time-series, multimodal and bakery-process models fine-tuned from batch telemetry, images, engineer corrections and lab outcomes. Initial design target: 50 to 200 GPU-hours per product family per release.
GPU-accelerated oven CFD, proof heat and humidity dynamics, dough rheology and deformation, and robot cells, run as-baked before the run to find quality-safe, low-energy profiles.
Rare foreign-body, under- and over-bake, blistering, cracked-top, hole, deformation and seal or fill scenarios, generated with domain randomisation and validated against real plant events before use.
Oven and changeover scheduling, energy allocation across zones and lines, proof dwell allocation and line balancing, recomputed on the GPU when the line is disrupted.
Pan loading and unloading, tray transfers, reject diversion and packaging handling, with perception and motion policies built in Isaac Sim before they touch the line.
A bakery does not go from manual to bounded control in one step. Doughex makes the level explicit per loop, auditable and reversible at any time, and some decisions never leave the person.
| Level | What the agent does | What the person does | When |
|---|---|---|---|
| Observe | Predicts rise, weight, colour, moisture and defects; writes nothing | Runs the bakery as today; compares predictions to QA checks | First phase with every design partner |
| Recommend | Proposes mix, proof, deposit and oven moves with the evidence behind each | A process engineer or baker approves or corrects each one | After accuracy is proven against the baseline |
| Approve to apply | Prepares the write; applies it only on a named person's approval | Approves per move; reviews the shift record | Once recommendations are trusted |
| Bounded | Writes low-risk oven, depositing and inspection setpoints inside explicit limits | Approves anything above the limits; reviews exceptions | After the food-safety and ROI gates agreed up front |
| Exceptions | Escalates anything outside its envelope, CCP-adjacent moves and release decisions | Always decides these; the agent never does | Permanent |
The three people in an industrial bakery whose week changes when the line runs itself, and what each of them needs from Doughex.
Owns production rate, quality, waste, giveaway and yield, energy and food safety. Wants a bakery that holds spec at higher rate with fewer interventions, and a number that justifies the spend.
Owns recipes, dough development, proof and oven profiles, process windows and yield. Approves and corrects the agents in recommend mode; those corrections train the models.
Owns HACCP, FSMA, BRCGS, ISO 22000 and allergen conformance, foreign-body and defect conformance, and lot genealogy. Needs every action grounded, cited and written to an immutable record.
IT/OT and sustainability leads approve the deployment. There are no customer quotes on this site yet; design partners will speak for themselves when they choose to.
Doughex writes to production equipment in a food plant. Every capability is scoped, every write is policy-checked, every output is cited, and every action is written to an append-only audit log the plant owns.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I | Cloud control plane | QUEUED Roadmap, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Roadmap, 6 to 12 months |
| HACCP · FSMA · BRCGS · ISO 22000 · allergen | Grounding and record-keeping | RUNNING Design basis for retrieval and the audit log |
| Per-tenant isolation | Data, memory, models | RUNNING Design rule |
| On-prem deployment | Recipe-sensitive bakeries | RUNNING Design option |
Doughex supports your food-safety records. It is not a certification and it does not replace your HACCP plan.
The questions plant directors, process engineers and quality managers ask in the first meeting.
Only at the autonomy level your plant has set, and only to an explicit allow-list of low-risk loops inside explicit limits. Every design partner starts in observe mode, where Doughex predicts and writes nothing. Recommend mode follows, where a process engineer approves each move. Bounded autonomy on oven, depositing and inspection loops comes after the food-safety and ROI gates agreed up front.
Critical control points are not optimisation variables. The bake kill step, metal detection and X-ray reject interlocks, allergen changeover and release decisions stay with your HACCP plan and your people. Doughex verifies readings, writes them to an immutable audit log and attaches them to the lot genealogy. It supports HACCP, FSMA, BRCGS, ISO 22000 and allergen records; it is not a certification and does not replace your plan.
Doughex sits above your existing automation as a supervisory layer. If it stops, the line keeps running on its current PLC and SCADA control and the interlocks it already has. A Doughex outage degrades the bakery to the way it runs today, not to a stop.
The first phase is observe mode on one line: Doughex reads your sensors, PLC history, QA checks and MES while you run the line as usual, and we measure its predictions against your own checkweigher, colour and moisture checks. Recommendations start when accuracy is proven against that baseline, and improve as plant-specific history and engineer corrections accumulate.
Recipes, product specs, tolerance models and customer specs are tenant-scoped and never used to train another customer's models. Retrieval is multi-tenant isolated and permission-aware. On-prem deployment is available for bakeries protecting sensitive recipes or private-label specs.
You are, the same as with any control strategy. That is why every write is policy-checked, bounded, logged and reversible, every output carries a citation to the recipe or procedure it relied on, and anything above your threshold waits for a named approver. The audit log records the request, the reasoning, the limits applied and the human decision.
As a design partner, on one line, with one hard metric: giveaway in grams per unit, energy per unit through the oven, downgrade and waste from under- or over-bake, or foreign-body and defect escapes. We instrument the line in observe mode, measure the baseline, move to recommend mode when accuracy is proven, and expand only when the number holds.
Full multi-module autonomy across the whole bakery, long-tail integrations beyond the design partners' stacks, and self-serve onboarding. The first release is one wedge workflow, its connectors, the agent loop with human checkpoints, the review console and the food-safety audit log.
Send what you have built. A person reads it.
↑↓ navigate↵ openesc close
