Docs · The format
An OPD, an Open Product Description, holds a physical product and the factory line that builds it. Its parts, cost, steps, tests, risks and lessons, in the same shape for every product, with every value marked by how we know it. People read it. Agents can work from it.
01 · What it's for
Today a product lives in CAD, spreadsheets, email and the heads of the people who built it. An OPD puts all of it in one place, so the next team starts where the last one finished.
Every part with its material, process and CAD. The bill of materials, what each unit should cost, and who makes each part.
I · Product
Plus One 38 parts, CAD for 14 of them
Every step in order, the stations and fixtures, the tests and their limits, and cycle times you can simulate before you cut tooling.
II · Factory
Plus One 22 steps on 8 stations, 56 s at the slowest against a 60 s takt (targets)
What could go wrong and how badly, what did go wrong and what fixed it, and better versions, each one scored.
III · LessonsIV · Evidence
Plus One 12 failure modes scored, 3 alternatives
02 · The file
Each layer answers one question. Pick one to see what it holds, a real record from Plus One, who uses it and when it changes. Every layer opens live on the hub.
What is it made of, and how much does each part vary?
Every part with its material, process and CAD, and how much it varies from unit to unit.
part:battery
InferredLow confidence · src:design-brief
What does one unit cost, and where does the money go?
The bill of materials, line by line, from the box down to each screw, and what each unit should cost.
bom · part:battery
Plus One is in design, so no price is quoted yet.
Who makes each part, and where?
The likely maker of each part and where it is, so a factory can quote and a buyer can plan.
sup:cell-maker
InferredLow confidence · not sourced yet
What does this kind of product need that the core doesn't cover?
Fields only some products need, like a battery's cells or a controller's sticks, added as extensions. No firmware, ever.
ext.battery · cell
InferredLow confidence · design target
How does it go together, and in what order?
Each step in order, what goes in and what comes out, with the joint, the fixture and the time each one takes.
op:ring-bond
InferredLow confidence · target
Which stations, how fast, and where's the bottleneck?
The stations, their equipment and their times, the takt, the bottleneck, and a line model you can simulate.
sta:s6
InferredLow confidence · proposed
How is every unit checked, and against what limits?
Incoming inspection, in-line checks and end-of-line tests, each with what it measures, where, and its limits.
test:wireless-charge
InferredLow confidence · proposed limit
What could go wrong, and how badly?
Each way a step can fail, its effect and cause, scored for severity, occurrence and detection, and tied to its evidence.
fm:battery-unseat
Carried over from the EC-1 lessons
What did go wrong, why, and what fixed it?
Each yield hitter or defect, its root cause and each fix that was tried. Each record is public, embargoed or private on its own.
EC-1 · iss:stick-drift-flux
Plus One is not built, so it has no issues yet. EC-1 is a made-up example.
What change would be better, and what does it cost?
Other layouts and design changes, each scored on the same card as the original, so you can see what each one trades.
var:split-s8
Estimated by an agent, not built
Where did each value come from?
The build card and every source behind every value, each file pinned by its hash so you know it hasn't changed.
src:design-brief
How do I check it, or hand it to an agent?
How to rebuild every number, a validator that checks the file, and prompts to start an agent on it.
a prompt to try
"The takt is 60 s. Which station is closest to it, and what would you change first?"
Plus One is our own agent puck, in design. Nothing has been built, so every value above is a target.
03 · The record
Nothing goes in without a source. Here is one real value from Plus One, taken apart.
op:ring-bond · cycle_time_s
The value, with its unit, so it can be summed and compared.
Where it came from.
How sure we are. High, medium or low.
The evidence, by id, each pointing at a source you can open.
A note on how it was worked out. When we infer, we say so, and we ask the people who know to correct us.
Its headline numbers carry the same badges.
An OPD is private, embargoed to a date, or public. Issues and variants can be set record by record.
04 · Updates
An OPD is a folder, kept like code. You change it, check it and publish it, and every earlier version stays.
Convert your own files into a draft OPD on the hub, or edit the folder directly. An agent can draft the change for you.
The validator checks the file against the schema, that every id it names exists, and that every fix marked done has its evidence.
Each upload is one commit. Files that haven't changed are skipped, and the history is kept.
A new OPD starts private. Make it public, or embargo it to a date, when you're ready.
05 · Use it
Every record has an id and every value a source, so an agent can answer from the file and show what each answer rests on. Try these on Plus One.
"The takt is 60 s. Which station is closest to it, and what would you change first?"
Line"Which risks carry over from the EC-1 lessons, and what control stops each one?"
Risk"Write the S5 work instruction for a new operator, using the SOP and the control plan."
Assembly