Most plants are described in a dozen places: a drawing of the floor, routing sheets, a BOM export, instruction binders. They drift apart. In Threaded, your plant is one folder of plain-text files: the map, the parts, how each part is made, and the instructions at each station. The files follow plantformat, a format for describing a factory. Because the plant is files, you can keep it in git, see every change, and let the AI edit it the same way you do.
#What it is
Plant shows those files as a plant. You change them in Code, or ask the AI (see The Plant AI Agent). When the plant is right, you commit it for your organization and push it to Run (see Plant Git and Imports).
A plant folder holds these files:
| File or folder | What it describes |
|---|---|
plant.yaml | The plant itself: its name and format version. |
map/map.yaml | The places and the flow: groups such as cells and lines, stations (operations and inspections), stores, and how material moves between them, including rework and scrap paths. |
routings/ | The stations and stores a part passes through. At each station: the changeover, setup, run and closeout work, with instructions, crew, times, tools and batch size. Parts made the same way share one routing. |
instructions/ | What the operator is told: procedures, steps, checks, named parameters, tools and step photos. |
specs/ | The parameter values at each station: targets, limits, units, and whether the station records them. |
part_recipes/ | One per part made here: which routing and specs it uses and what it consumes at each station. A part with a recipe is made here; a part only consumed is bought. |
parts.yaml | The plant’s item master. |
catalog/ | The design item master from engineering, and each part’s EBOM (its direct components). |
resources/tools.yaml | The tools. |
media/ | Document files, such as drawings. Step photos live in your organization’s media library. |
#Rules
- Every fact has one home. A spec value lives in
specs/, not in an instruction. - Some things are deliberately left out of the plant: training, costs, schedules, work order quantities, and what happened on the floor. Those live in Run and in your other systems.
- A part is made if it has a part recipe, and bought if a recipe only consumes it. Nobody types “make” or “buy”.
- The plant is checked every time the preview builds. Errors must be fixed before the plant can be pushed to Run. Warnings don’t block anything.
- Your edits are drafts in your own workspace until you click Commit. They never reach the floor until someone pushes and promotes them.
- Plant needs the Planning Workspace, which is turned on per organization. See Feature Access and Billing.
- Owners, Editors and View All members can open Plant. Operators can’t; they work in Run.
- Only Owners and Editors can commit and push. A View All member can try changes in their own workspace, but can’t share them.
#In the app
#Preview your plant
Plant’s tabs show the plant described by your files:
- Map: the stations, stores and flow. Click a station to see what it makes, the parts and tools it uses, its time and crew, and its instructions. Highlight shows the path of a routing or part.
- Instructions: every instruction, its procedures and steps, the parts that use it, and its parameter values.
- Parts: every part, grouped into finished goods, subassemblies and components, with whether it’s made or bought, its recipe and route, and whether its consumption matches the EBOM.
- Media: your organization’s media library. Owners and Editors can upload photos, videos and files here to use in instructions.
The previews are read-only. While the plant builds, the toolbar shows progress, such as Building map preview…. If your workspace has more than one plant, pick one from Plant in the toolbar.
#Edit in Code
Click Code in the toolbar to see the plant’s files. Click it again to go back to the preview.
- Click a file in the tree to open it and make your change. It saves to your workspace a moment after you stop typing, and the editor shows Draft saved.
- Click New file to add a file.
- Press Ctrl+` to show the terminal.
A file or folder you changed is marked Modified. To share your changes with your organization, click Commit. To send committed changes to Run, click Push. See Plant Git and Imports.
If the AI or a teammate’s commit changes a file you have open, Threaded keeps your edits and asks you to choose Keep my edits or Load new version.
If the toolbar shows Workspace disconnected, click Reconnect.
#Check your plant
A chip in the toolbar shows the result of the last check, such as Housing cell · 2 errors, 1 warning or checks pass:
- Green: no errors or warnings.
- Amber: warnings only. The plant still works.
- Red: errors. Fix them before you push.
Click the chip to open Validate. It lists each problem and the file it’s in. On the map, a station with problems shows how many.
Errors include unknown keys, missing references, a parameter with no spec value, or a material flow that loops. Warnings include consumption that doesn’t match the EBOM, or a routing nothing uses.
If the plant doesn’t build at all, Plant says The preview did not build and shows what plantformat reported. Click Open Code to fix it. If there’s no plant yet, add a plant.yaml in Code, or ask the AI to start one.
#Your recipes against the EBOM
Engineering’s EBOM says what a part is made of. Your part recipes say what each station actually consumes. Plant compares the two for every made part that has an EBOM in catalog/eboms/, and shows the result on the part’s page in Parts:
- matches the EBOM: each consumed part is in the EBOM at the same quantity, and each EBOM line is consumed.
- {count} from the EBOM: they differ. The part’s consumption table marks each difference.
How the comparison works:
- Consumption is added up per piece across all the part’s stations. Setup and changeover lines are never in an EBOM, so they’re not compared.
- A phantom is a grouping in the EBOM only. The plant never builds or stocks it as a unit, so its parents consume its components directly. Phantoms are expanded into their components before comparing.
- A made subassembly is checked on its own page, against its own EBOM.
Each difference, and how to clear it:
| Plant shows | It means | To clear it |
|---|---|---|
| not in the EBOM | A recipe consumes a part the EBOM doesn’t list. | Remove it from the recipe, or add it to the EBOM if engineering missed it. |
| In the EBOM, not consumed | The EBOM lists a component no station consumes. For a phantom, one of its components isn’t consumed by the parts it goes into. | Add it to the recipe at the station where it’s fitted, or have engineering remove it from the EBOM. |
| EBOM says {quantity} | The part is consumed, but at a different quantity. | Fix the quantity in the recipe, or in the EBOM. |
| no EBOM | No EBOM in catalog/eboms/ is rooted at this part, so nothing is checked. | Add the part’s EBOM to the catalog, if it has one. |
The same differences show as warnings in Validate. They never block a push: some plants consume differently from the design on purpose. Each warning, in plantformat’s own words:
| Warning | It means | To clear it |
|---|---|---|
'<part>': EBOM component '<child>' is not consumed at any station | The EBOM lists <child> on <part>, and no station on <part>’s route consumes it. | Consume <child> at the station where it’s fitted, or have engineering take it off the EBOM. |
'<part>': component '<child>' of phantom '<phantom>' is not consumed at any station | <phantom> is only a grouping in the EBOM. <part> should consume its component <child> directly, and no station does. | Consume <child> at the station where it’s fitted, or take it off the phantom’s EBOM. |
'<part>': phantom '<phantom>' is not consumed, nor are its components | The EBOM lists <phantom> on <part>, and neither the phantom nor any of its components is consumed. | Consume the phantom’s components where they’re fitted, or take the phantom off the EBOM. |
'<part>': EBOM component '<item>' consumed <have> per piece, EBOM says <qty> | <item> is consumed, at <have> per piece instead of the EBOM’s <qty>. A “(through phantom …)” suffix means the EBOM quantity comes from a phantom. | Change the recipe quantity, or the EBOM quantity, so they agree. |
'<part>' consumption: '<component>' is a design part not in the EBOM ('<ebom part>'); add it to the EBOM, or, if the plant owns it, define it in parts.yaml (part.manufacturing) | A station consumes <component>, and <part>’s EBOM (<ebom part>) doesn’t list it. | Add it to the EBOM if engineering missed it. If the plant owns it, such as a fixture the design doesn’t call out, define it in parts.yaml under part.manufacturing instead. |
'<part>' consumption: '<component>' is below '<sub>', a direct component of its EBOM; <hint> | The recipe consumes <component>, which sits inside <sub>. The EBOM lists <sub> itself, as one part, so the recipe is reaching below it. The warning ends with a hint about where. | Consume <sub>, or change the EBOM if the station really fits those pieces one by one. |
phantom '<part>' has no EBOM, so its parents cannot consume its … | <part> is a phantom with no EBOM of its own, so a parent has no components to consume in its place. The warning names what the parents can’t consume. | Add the phantom’s EBOM under catalog/eboms/. |
phantom '<part>' is in no EBOM; a phantom is consumed through its parent | Nothing’s EBOM lists this phantom. A phantom is never built or stocked on its own. It’s consumed only by being expanded into a parent’s recipe. | Add the phantom to its parent’s EBOM. If it’s a real part the plant builds, don’t mark it as a phantom. |
#Trial run
Trial run in the toolbar runs work orders on your draft, as the floor would. Nothing is saved. Only Editors and Owners can turn it on.
- Start order. Pick a Part and the number of Pieces, then click Start order. The order moves across the map, and each station’s panel shows the trial units there and the action the operator would see.
- Feeders. Set the pieces on hand before the trial starts. Shortages count against them, and Feeders shows how many are short.
- Reset clears every order and starts the trial again.
If you edit the draft while a trial runs, Threaded replays the moves on the new draft. A move that no longer runs is dropped, with every move after it.
A trial checks procedures, prep, picks and holds. Step tools, parameters and media are checked at release, not in a trial. To put a change on the floor for real, push it and promote it on Admin › Plant git imports.
#From the CLI or API
threaded plantformat validate <plant-folder>runs the same checks on a plant on your computer. Add--jsonfor a machine-readable report. It exits with an error when there’s at least one error; warnings aren’t failures.threaded plant remoteprints your organization’s plant repo URL, andthreaded plant setup-gitsets up git credentials for it, so you can clone the plant and edit it with your own tools. Push your commits todev. See Plant Git and Imports.threaded task map:export --plant <dir>writes your published Threaded map and parts into a plant folder to start from.