Using this OPD with an agent

opd.yaml is the whole product and its proposed line in one file. Give it to an agent and it can answer questions about the design, plan the line, or propose changes, with every answer traceable to a source.

Prototype in design. Every value is a target; nothing has been built.

Prompts to try

• "The takt is 60 s. Which station is closest to it, and what would you change first? Use the operations graph and the cycle-time targets."
• "Plus One+ adds an NFC check and a light-sensor check at S8. Does the line still meet takt? If not, what do you split?"
• "Which PFMEA rows carry over from the EC-1 lessons, and what control stops each one?"
• "What sets the thickness? Using the stack-up in docs/design-brief.md, what would it take to reach 8 mm, and what would it cost in battery?"
• "Write the S5 work instruction for a new operator, using the SOP and the control plan."
• "Using device/model.yaml, list what firmware needs to drive the ring, the mics and the haptic motor, and which pins it uses."

Rules for agents

• Say which claims an answer rests on. Here they're all inferred, low confidence: design targets.
• Never present a target as a measurement, and never quote a cost; there are none.
• Say "works with magnetic phone mounts and chargers". Never claim Qi2 or MagSafe.
• Never claim the twin is calibrated, validated or proven.
• For firmware, link open firmware only. Never link tools that break other products' locks.