os-03-defense

name

os-03-defense

description

Operating-system orchestrator skill for **Defense, Intelligence, Border, and Foreign Affairs** (national operating system #3). Use this skill whenever work touches this sector's mission — Protect sovereignty, manage alliances, understand threats, control lawful movement, and negotiate with other polities — 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 03 — Defense, Intelligence, Border, and Foreign Affairs

Layer: National operating system (#3 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

Protect sovereignty, manage alliances, understand threats, control lawful movement, and negotiate with other polities.

When to use this skill

Load this skill when a task concerns defense, intelligence, border, and foreign affairs. 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:

1. When external threats arise, detect, deter, defend, and recover.
2. When alliances and trade relationships matter, negotiate agreements and preserve channels.
3. When people and goods cross borders, verify identity, safety, legality, and compliance.
4. When adversaries hide intent, gather intelligence and assess risk.
5. When conflict occurs, coordinate logistics, medicine, communications, and rules of engagement.

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)

• Diplomat, foreign service officer, consular officer, trade representative.
• Intelligence analyst, OSINT analyst, linguist, threat analyst.
• Soldier, sailor, airman, marine, coast guard, defense planner.
• Border officer, customs specialist, immigration officer, export-control analyst.
• Defense engineer, logistics officer, acquisition manager, cyber operator.

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: Analyst/officer (entry) → senior analyst → branch chief → SES/flag officer; Foreign Service officer ranks; military O-1…O-6.
• Skills, tools & tech employers list: Classified analytic and geospatial (GIS) platforms, OSINT tooling, SIGINT/IMINT systems, language tools, defense logistics systems.
• Qualifications, certifications & licenses: TS/SCI clearance (often polygraph), Foreign Service exam, DAWIA (acquisition), language proficiency (DLPT/ILR), military commissioning.
• KPIs / metrics in postings: Mission readiness, intelligence timeliness/accuracy, interdiction rates, negotiation/treaty outcomes, force-protection incidents.
• Where these roles are posted: USAJOBS, IC Careers (CIA/NSA/DIA/NGA), Feds Hire Vets, ClearanceJobs, agency portals.

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:

• OSINT analyst agent — collects and synthesizes open-source signals into assessed intelligence drafts. (supervised by intelligence analyst; skill: roles/osint-analyst-agent/)
• Translation agent — translates and contextualizes multilingual material at speed. (supervised by linguist / analyst; skill: roles/translation-agent/)
• Sanctions-screening agent — screens parties and shipments against sanctions and export-control lists. (supervised by export-control analyst; skill: roles/sanctions-screening-agent/)
• Logistics optimizer — plans movement of personnel, materiel, and supply under constraints. (supervised by logistics officer; skill: roles/logistics-optimizer/)
• Red-team simulation agent — models adversary options and stress-tests plans. (supervised by defense planner; skill: roles/red-team-simulation-agent/)
• Defense acquisition document reviewer — reviews requirements, bids, and compliance for acquisition programs. (supervised by acquisition manager; skill: roles/defense-acquisition-document-reviewer/)
• Intelligence triage agent — prioritizes and routes incoming reporting and tips. (supervised by threat analyst; skill: roles/intelligence-triage-agent/)
• Cyber defense agent — performs continuous monitoring and incident-response assistance. (supervised by cyber operator; skill: roles/cyber-defense-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

• Base logistics, warehouse, maintenance, casualty-evacuation support, hazardous-area reconnaissance.
• Border facility support, inspection assistance, disaster-relief unloading.

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/.

Non-humanoid autonomous machines

Self-driving vehicles, equipment, and drones for this sector (LLM-planned; physical actions as tool calls; ODD + teleoperation fallback):

• ISR reconnaissance drone (UAS) — conduct intelligence, surveillance, and reconnaissance from the air under human command. (autonomous machine skill: autonomous/isr-reconnaissance-drone-uas/)
• Autonomous logistics & resupply vehicle (UGV) — move materiel, fuel, and casualties across austere terrain without a crewed cab. (autonomous machine skill: autonomous/autonomous-logistics-resupply-vehicle-ugv/)

How these machines work (assumed architecture): each is a non-humanoid autonomous machine — a foundation/LLM planning brain issues actions as tool calls (follow_route, dump_bucket, take_off, spray_zone, …) over a perception → prediction → planning → control stack trained on world models, driving/field simulation, and RLAIF. Each runs inside a defined Operational Design Domain (ODD) with a verified safe-stop and teleoperation fallback. Full detail in _catalogs/autonomous-machines/ and 00-framework/.

Human accountability boundary (must stay human-led)

Use of force, detention, asylum determinations, diplomacy, intelligence conclusions, and escalation decisions require human command authority.

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: Public Safety & Justice, Resilience & Continuity, International Relations, Communications & Software. 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):

• Semiconductor Sovereignty
• Bioeconomy
• Quantum and Space Systems
• Strategic Supply Chain
• Cyber Defense

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: Over-trust of automated assessments; loss of manual control, analog navigation, and field craft.
• Countermeasures: Degraded-comms and manual-reversion drills; maintain analog nav/comms skills; red-teaming.
• Role/job simulators (keep-warm): Wargaming and mission simulators; GPS/comms-denied and analog-fallback exercises.

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. Defense and foreign-affairs work carries the sharpest accountability boundary in this library: anything touching use of force, targeting, or treaty commitments is human-decided by law and doctrine. Assume adversarial deception in every input.

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

1. Identify which Core JTBD the task serves.
2. Select the role skill(s) under roles/ that fit, and confirm the human supervisor.
3. Run the work-system completeness check and add only the Enable, Integrate, Assure, Adapt, and Sustain services the core outcome requires.
4. Run the lifecycle: sense → interpret → decide → mobilize → execute → verify → govern.
5. Stop at the accountability boundary and route the decision to the accountable human.
6. Log actions to the control layer and surface anything that trips a failure mode.