| name | mission-quantum-and-space-systems |
| description | Strategic mission (cross-cutting national capability): **Quantum and Space Systems** — Develop quantum and space capabilities that improve sensing, communications, computation, navigation, science, defense, and competitiveness. Unlike the sector operating systems, a mission composes several of them toward one strategic objective. Use this skill to plan or coordinate this mission end-to-end; trigger whenever work concerns quantum and space systems, even if the user only names a piece of it. |
Strategic Mission — Quantum and Space Systems
Layer: Strategic mission (cross-cutting capability that composes multiple operating systems)
Shared concepts: ../../00-framework/SKILL.md · Imported/adapted from the Agentic-Workforce operating models
Purpose
Coordinate two high-leverage frontier domains that depend on deep science, hardware, software, manufacturing, security, and mission alignment.
Mission
Develop quantum and space capabilities that improve sensing, communications, computation, navigation, science, defense, and competitiveness.
Operating systems this mission composes
A strategic mission is an orthogonal axis to the sectors: it pulls roles and capabilities from several of them toward one objective. This mission primarily draws on:
- 15. Science, Research, Standards, and Innovation
- 08. Mining, Materials, Chemicals, and Industrial Inputs
- 09. Manufacturing and Industrial Production
- 03. Defense, Intelligence, Border, and Foreign Affairs
- 12. Communications, Software, Cybersecurity, and Digital Infrastructure
Deploy the relevant sector and role skills under those operating systems as the building blocks; this skill coordinates them toward the mission.
Core capabilities
- Quantum computing, sensing, networking, cryptography.
- Cryogenic, photonic, vacuum, RF, precision instrumentation.
- Space launch, satellites, ground systems, mission operations, remote sensing.
- Aerospace manufacturing and testing.
- Secure communications and timing.
- Standards, export control, mission assurance.
Human command roles
- Quantum program director.
- Quantum engineering lead.
- Cryptography transition lead.
- Space mission director.
- Aerospace systems engineering lead.
- Ground systems lead.
- Mission assurance lead.
These hold accountability for the mission. Strategic prioritization, public legitimacy, security, and ethical tradeoffs stay human-owned.
AI personnel
- Quantum algorithm assistant.
- Error-analysis agent.
- Instrumentation data analyst.
- Mission planning agent.
- Trajectory optimization agent.
- Remote sensing analyst.
- Anomaly detection agent.
Many of these map to existing role skills in the composed operating systems (e.g. _catalogs/ai-personnel/ and the sectors' roles/). Reuse them rather than rebuilding.
Robot / machine personnel
- Cryo-lab support robot.
- Precision lab assistant robot.
- Aerospace manufacturing inspection robot.
- Cleanroom logistics robot.
See _catalogs/humanoid-robots/, _catalogs/autonomous-machines/, and the sectors' robots/ and autonomous/ folders.
Operating loop
- Define national mission and capability gap.
- Build research and engineering roadmap.
- Develop hardware/software prototypes.
- Test under realistic operating conditions.
- Secure supply chain, facilities, and data.
- Transition to operational systems or standards.
- Monitor and update architecture.
Human accountability boundary
Strategic prioritization, public legitimacy, national-security judgment, scarce-resource allocation, export-control and safety decisions, and final signoff on irreversible commitments remain human-accountable. AI personnel and robots accelerate the work up to that line.
How to use this skill
- Read the mission and the operating systems it composes.
- Pull the specific sector and role skills you need from those OSs.
- Run the operating loop, coordinating across sectors at the seams.
- Apply the command & cadence model (
00-framework/) and stop at the accountability boundary.
Adapting to any nation (context modifiers)
Whether a nation pursues this mission at all — and how (sovereign build, ally-and-buy, or import) — depends heavily on scale, income, resource endowment, and geopolitics. Re-read 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.
