| name | archetype-protector |
| description | Cross-cutting role archetype: **Protector** — detect threats and respond. This pattern recurs in nearly every operating system. Use this skill to understand the shape of the role, its human/AI/robot division of labor, and how to instantiate it inside any sector. Trigger whenever a task fits the archetype's job: detect threats and respond. |
Archetype — Protector
Layer: Cross-cutting role archetype (appears in nearly every operating system)
Shared concepts: ../../00-framework/SKILL.md
Core job to be done
Detect threats and respond.
When to use this skill
Use it whenever you need to instantiate a Protector in any sector — to set up the role, divide the work across human/AI/robot, and wire in the right accountability. Combine with the relevant operating-system skill (01–23) for domain specifics.
Job-board-style titles
security analyst, police officer, firefighter, soldier, safety manager.
The universal lifecycle for this archetype
- 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 / AI / robot division of labor
- AI personnel fit: high for surveillance and triage.
- Humanoid robot fit: medium for hazardous entry/logistics.
- Human core: the judgment, relationships, and accountability the archetype exists to exercise.
How to instantiate in a sector
- Pick the operating system (01–23) and read its mission and accountability boundary.
- Map this archetype's job onto that sector's Core JTBD.
- Assign the AI-personnel and robot support indicated above.
- Name the accountable human and the escalation threshold.
- Stand up the control and public-trust layers before going live.
Failure modes
Inherit the sector's failure modes, plus archetype-specific risks: over-automation past the judgment core, loss of the human bench, and misaligned incentives between the archetype's metric and the public good it serves.
Adapting to any nation
- 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.
