← Back to catalogue
Previous version

Defense & Security Forces

vr.wm-pol-007 · world-a17-defense-and-security-forces

Forces, assets, mandates (breadth placeholder; detail = G3)

World Models Society, people and institutions SOC.POL.DEF

Bundle → Layer → Finding → Questions Incomplete

3 bundles · 6 layers · 0 findings · 0 questions

forceStructure Forces and units as organizations

unit

forces, units and their ordering

command

command and subordination lines

assetsAndReadiness What forces hold and how ready they are

assetReference

identifiers of held assets, never their operational detail

readiness

coarse readiness states per unit

mandate Why forces exist and may act

legalMandate

founding and empowering acts

deploymentAuthorization

decisions permitting deployment

Note: Legacy card: layers named, findings and questions never written.

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
standalone-mm
Navigation path
NAV.SOC.POL.DEF
Domain
SOC.POL.DEF
Industry
Cross-industry
Tags
defenseforcesoc.pol.def
Also called
A17

What it is Derived, awaiting review

This meta-model is a breadth placeholder describing a polity's forces: their units and command lines, references to the assets they hold, the legal mandates under which they exist and may deploy, and coarse readiness states.

Note: First sentence of the legacy card introduction.

Why it exists Filled

Forces, assets, mandates (breadth placeholder; detail = G3)

Distinguishing features Derived, awaiting review

  • It is its own model because even a placeholder must anchor the catalogue's references to forces and their mandates, and because it carries the most restrictive default access in the catalogue.

What robots and AI may and may not do Missing, in the backlog

Not described yet. This gap is in the card backlog.

Moral aspects Missing, in the backlog

Not described yet. This gap is in the card backlog.

Owners Filled

Steward

The defense authority stewards this model under the tightest default access in the catalogue: nothing is visible beyond the public transparency summary except by explicit owner grant.

Links to other meta-models Filled

references

  • world.defenseOperations - all operational depth, plans and engagements live there; this model only anchors identity, structure and mandate
  • world.lawmaking - mandates and deployment authorizations trace to enactments
  • world.publicOffice - the command apex and civilian control sit in branch bodies
  • world.interstateRelations - alliance obligations shape structure and govern allied exchange

composes

  • world.auditTrail - every structural and mandate change is append-only

imports

  • nato-standards - ALIGN: interoperability terminology for units, echelons and readiness categories, referenced not adopted

requires

  • vr.wm-org-009
  • vr.wm-pol-002
  • vr.wm-pol-005

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Derived, awaiting review

  • assetReference: an identifier of an asset held by a unit, resolved elsewhere; key attributes: assetIdentifier, assetClass, custodyUnitRef, snapshotDate

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Derived, awaiting review

  • forceEstablished: a force was constituted under a legal mandate
  • unitFormed: a unit was formed and placed in the command structure
  • unitDisbanded: a unit was dissolved and its references closed
  • mandateGranted: a founding or empowering act took effect for a force
  • readinessAssessed: a dated coarse readiness state was recorded for a unit
  • deploymentAuthorized: a competent authority permitted a deployment
  • deploymentConcluded: an authorized deployment ended and reporting closed

Legacy events listed as state transitions.

Hazards and failure modes optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Derived, awaiting review

  • oversightDisclosure: graded access for mandated oversight bodies, scoped by clearance class
  • alliedExchange: treaty-based exchange of structure and readiness data with allied polities per A15
  • publicTransparencySummary: periodic aggregate disclosure of force posture and spending class
  • publicDefenseSummary: high-level posture and mandate summary; omits units, assets and readiness
  • oversightView: structure, mandates and authorizations for mandated committees; omits operational detail held in G3
  • orderOfBattle: the restricted full structure with asset references and readiness; omits nothing within this model's breadth

Context of use required Filled

  • All grants, including oversight and allied exchange, flow through S1 ownership and S2 access, with S4 audit on every disclosure.

Sources Missing, in the backlog

Not described yet. This gap is in the card backlog.

Open questions

  • Superseded by a researched world model? Map this legacy card to its successor or retire it.

Machine files

Provenance

legacy MMAS card (world-models v0.2) · legacy

Built from: models/world-a17-defense-and-security-forces/spec.yaml, models/docs/polity/A17-defense-and-security-forces.md