| name | os-09-manufacturing-and-industrial-production |
| description | Operating-system orchestrator skill for **Manufacturing and Industrial Production** (national operating system #9). Use this skill whenever work touches this sector's mission — Convert designs and materials into reliable goods at scale — to understand the jobs to be done, the human/AI/robot division of labor, the accountable human boundaries, and which specialized role skills to deploy. Trigger this even when the user names a specific task in the domain rather than the sector itself. |
Operating System 09 — Manufacturing and Industrial Production
Layer: National operating system (#9 of 23) · Personnel model: human-owned, AI- and robot-augmented
Cross-references: 00-framework/ (shared concepts, teaming pattern, accountability), source map Country-Economy Core Jobs To Be Done.md
Mission
Convert designs and materials into reliable goods at scale.
When to use this skill
Load this skill when a task concerns manufacturing and industrial production. It gives an agent the sector map: the outcomes that must be produced, who owns them, what can be automated, and where human accountability is non-negotiable. From here, route to the specific role skills under roles/ for execution.
Core Jobs To Be Done
These are the durable outcomes this operating system must reliably produce, written as trigger → response:
- When society needs goods, design, source, produce, inspect, package, and ship them.
- When quality drifts, detect root causes and correct process.
- When demand changes, replan production and labor.
- When machinery fails, restore uptime.
- When productivity must improve, automate safely.
The universal lifecycle, applied
Every job in this sector moves through the same seven steps. Use it as a checklist when designing or executing work here:
- Sense reality — gather data, observe conditions, inspect sources, listen to people.
- Interpret reality — diagnose, forecast, model risk, prioritize.
- Decide — choose policy, design, action, allocation, escalation, or tradeoff.
- Mobilize — assign labor, budget, materials, rights, permissions, logistics, schedule.
- Execute — perform the work in digital or physical space.
- Verify — test, audit, measure, inspect, certify, and learn.
- Govern — maintain legitimacy, safety, accountability, continuity, and trust.
Human role families (who owns the work)
- Manufacturing engineer, process engineer, industrial engineer.
- Production supervisor, plant manager, operations manager.
- Machinist, CNC programmer, welder, assembler, fabricator.
- Quality assurance manager, quality control inspector, metrologist.
- Maintenance technician, reliability engineer, controls engineer.
- Robotics engineer, automation engineer, PLC technician, mechatronics technician.
These remain human-owned. AI personnel and robots augment them; they do not replace the accountable owner.
Labor-market grounding (how these roles are advertised)
The human roles this operating system staffs appear on job boards with concrete, checkable signals. The AI-personnel and robot skills here are designed to support these advertised roles, not to replace the accountable human in them.
- Advertised titles & seniority ladder: Operator/assembler → technician/setup → process/quality engineer → production supervisor → plant manager; maintenance apprentice → journeyman → reliability engineer.
- Skills, tools & tech employers list: MES, ERP (SAP), PLC/SCADA, CAD/CAM, SPC/quality (Minitab), CMMS, industrial robotics, Lean/Six Sigma.
- Qualifications, certifications & licenses: Six Sigma Green/Black Belt, ASQ CQE/CQA, PE, CMfgE, PMP, OSHA/forklift, journeyman trades.
- KPIs / metrics in postings: OEE, scrap/defect rate (PPM), on-time delivery, downtime/MTBF, safety TRIR.
- Where these roles are posted: Indeed, LinkedIn, ZipRecruiter, manufacturing boards, Snagajob (hourly).
Grounding reflects 2026 job-posting conventions across LinkedIn, Indeed, Dice, ZipRecruiter, Glassdoor, USAJOBS, GovernmentJobs, and specialized boards, spot-verified against public listings and O*NET/BLS. Re-verify specifics — especially pay, certifications, and licenses — against live postings before operational use.
AI personnel in this operating system (deployable role skills)
Each of the following has a dedicated, extensive skill under roles/. Deploy them under the named human supervisor:
- Production scheduler — schedules production against demand, capacity, and materials. (supervised by production supervisor; skill:
roles/production-scheduler/)
- Quality anomaly detector — detects defects and quality drift from inspection and sensor data. (supervised by QA manager; skill:
roles/quality-anomaly-detector/)
- Root-cause analysis agent — investigates defects and proposes corrective actions. (supervised by quality engineer; skill:
roles/root-cause-analysis-agent/)
- CAD/CAM assistant — supports design-for-manufacture and toolpath generation. (supervised by manufacturing engineer; skill:
roles/cad-cam-assistant/)
- Supplier risk agent — monitors supplier delivery, quality, and continuity risk. (supervised by supply chain manager; skill:
roles/supplier-risk-agent/)
- Work-instruction generator — drafts and updates standardized work instructions. (supervised by industrial engineer; skill:
roles/work-instruction-generator/)
- Safety compliance monitor — monitors machine-safety and lockout compliance. (supervised by plant safety manager; skill:
roles/safety-compliance-monitor/)
- Digital twin simulation agent — simulates process and line changes before deployment. (supervised by process engineer; skill:
roles/digital-twin-simulation-agent/)
Work-system completeness (the work around the core work)
The core roles above are necessary but not sufficient. For each material JTBD, check which ancillary services are required:
| Family | Required support question | Reusable catalog |
|---|
| Enable | Do practitioners have the evidence, knowledge, data, tools, access, and skills they need? | _catalogs/enabling-work/ |
| Integrate | Who owns dependencies, handoffs, queues, decision preparation, and stakeholder alignment? | _catalogs/enabling-work/ |
| Assure | What needs independent quality review, challenge, testing, risk, safety, legal, or audit work? | _catalogs/enabling-work/ |
| Adapt | How are alternatives generated and operational experience converted into improvement? | _catalogs/enabling-work/ |
| Sustain | Who maintains administration, capacity, wellbeing, coverage, assets, and institutional memory? | _catalogs/enabling-work/ |
Do not clone every support role into this sector. Choose embedded, shared, platform, federated, or temporary support according to demand, specialization, consequence, and context. Every ancillary service must name the core JTBD and owner it serves, its trigger, deliverable, service level, decision boundary, outcome link, escalation, and retirement rule. See the Work-System Completeness Map.
Humanoid robot roles
- Assembly assistance, kitting, material movement, machine tending, inspection, rework support.
- High value in brownfield factories where human-designed tools and spaces already exist.
Dedicated embodied robot role skills for this sector (LLM-brained; actions as tool calls via VLA policies):
- Flexible assembly robot — kit, position, fasten, and assemble high-mix low-volume products at human-scaled workstations. (embodied robot skill:
robots/flexible-assembly-robot/)
- Machine-tending robot — load and unload CNC machines, presses, and molders, change tooling, and run first-article quality checks. (embodied robot skill:
robots/machine-tending-robot/)
- Intralogistics and kitting robot — pick, kit, stage, and deliver parts and work-in-progress line-side and manage returns and empties. (embodied robot skill:
robots/intralogistics-and-kitting-robot/)
How these robots work (assumed architecture): each is an LLM-brained embodied agent — a multimodal LLM brain plans and issues physical actions as tool calls (e.g. grasp, navigate_to, place), executed by Vision-Language-Action policies trained on world models, robot gyms, and RLAIF. Fleets may share one brain model or mix specialized ones. A verified low-level safety layer can override unsafe actions independently of the brain. Full detail in 00-framework/ and _catalogs/humanoid-robots/.
Human accountability boundary (must stay human-led)
Safety lockout, final quality release, labor relations, hazardous-process authorization, and plant leadership remain human-accountable.
Treat this boundary as a hard constraint. Agents in this sector may sense, interpret, draft, model, monitor, and coordinate up to this line, then must hand off to an accountable human for the decision itself.
Division of labor (human / AI / robot)
- Human owner — accountable for goals, values, exceptions, relationships, signoff, and everything inside the accountability boundary above.
- AI personnel — research, draft, analyze, monitor, simulate, coordinate, document. Strongest on digital signals and repeatable decision support.
- Robot personnel — fetch, carry, inspect, clean, assemble, assist, enter hazardous spaces. Strongest on physical work in human-built environments.
- Control layer — permissions, audit logs, escalation thresholds, incident reporting, evaluation.
- Public trust layer — explainability, appeal, privacy, bias testing, safety certification, labor-impact review.
Interfaces with other operating systems
This sector regularly depends on and feeds: Materials & Manufacturing, Transportation & Logistics, Labor & Workforce, Science & Innovation. Coordinate handoffs explicitly; most systemic failures happen at the seams between operating systems.
Strategic missions that draw on this sector
Beyond its own mandate, this operating system is composed by these cross-cutting strategic missions (the orthogonal mission axis — a mission pulls roles from several sectors toward one national objective):
Sector success metrics (illustrative)
- Coverage / reliability: the share of the population or demand reliably served.
- Quality / safety: defect, incident, and harm rates within tolerance.
- Cost / efficiency: unit cost and resource use trending down without eroding safety.
- Trust / legitimacy: public confidence, complaint resolution, and auditability.
- Resilience: time-to-detect and time-to-recover from shocks.
Failure modes to watch
- Monoculture / correlated failure — shared models or vendors failing in lockstep; require diversity and manual fallback.
- Cascading dependency — failures propagating from the systems listed above; map dependencies and design graceful degradation.
- Deskilling — losing the human bench that can run the sector manually; retain drills and manual modes.
- Agent-specific failure — fabrication, prompt injection, reward hacking, silent drift; keep the control layer independent.
- Speed mismatch — automated action outrunning human oversight; install circuit breakers for high-consequence steps.
Deskilling watch & keep-warm regime
Automating routine cases erodes three things over time: the human fallback bench (who runs this when automation fails), tacit / craft judgment (lost as the experienced cohort retires), and the learning ladder (juniors never get the cases they used to learn on). Job and role simulators are the primary countermeasure.
- Risk here: Skilled trades lose craft and cannot troubleshoot when automation fails; quality intuition erodes.
- Countermeasures: Cross-training; periodic manual line runs; protect apprenticeships; Andon empowerment.
- Role/job simulators (keep-warm): Line-down troubleshooting and changeover simulators; hardware-in-the-loop rigs for manual skills.
Dual-use simulators: the world models and simulation built to train the machines in this sector double as the keep-warm simulators that keep humans current and rebuild the learning ladder. Owned cross-sector by OS 22 (Resilience) and the _catalogs/simulation-training/ roles; the verified deterministic fallback in _catalogs/capability-optimization/ is its technical complement.
Adapting to any nation (context modifiers)
The jobs above are universal; how they are staffed is not. Manufacturing spans lights-out plants and informal workshops: quality systems, supplier webs, and takt discipline vary enormously, and the binding constraint is often skilled trades, not machines.
Re-read this sector through:
- Scale (city-state → federation): whether this role is unified or layered across local/regional/national tiers.
- State capacity (fragile → high-capacity): whether the owning institution exists and can be held to account, or the job is met by markets, households, NGOs, or donors.
- Income level (low → high): affordability of automation and the balance of subsistence vs. wage work.
- Formality (informal → formal): whether the people and assets this role acts on appear in any registry at all.
- Resource & geography: which hazards and dependencies dominate (water-scarce, flood-prone, landlocked, trade-dependent).
- Political system & legitimacy: where the human-accountability boundary actually binds and who may hold power to account.
How to operate in this sector
- Identify which Core JTBD the task serves.
- Select the role skill(s) under
roles/ that fit, and confirm the human supervisor.
- Run the work-system completeness check and add only the Enable, Integrate, Assure, Adapt, and Sustain services the core outcome requires.
- Run the lifecycle: sense → interpret → decide → mobilize → execute → verify → govern.
- Stop at the accountability boundary and route the decision to the accountable human.
- Log actions to the control layer and surface anything that trips a failure mode.
