VSI GLOBAL // ENTERPRISE ARCHITECTURE

_SHAPES

5 min read

Process Maps - Build Spec & Target Shapes (Protective Operations)

How the per-cell XMind process skeletons are built for D-02. Each planning or playbook cell in deliverables/<type>/ gets a companion skeleton in collections/<type>/<did>-<slug>-collection.md that the operator imports into XMind and works through during the operation. Sibling spec: _SHAPES.md (intelligence collection maps). Exemplar / gold standard: EP-020-advance-planning-cycle-collection.

1. What these files are

XMind-import Markdown. D-01 collection maps stage what the analyst gathers; D-02 process maps stage what the operator does and decides. The central topic is the operation (a movement, a detail, an advance, a crisis response), branches are the ordered phases and gates of the process, and leaf nodes are step checkboxes, decisions, and fields to fill as the operation runs.

These are execution workspaces, not vault documents. The finished order or after-action product lives in deliverables/; the process map is the running board the operator ticks against.

2. Import conventions (XMind) - follow exactly

  • First line is the central topic - # [OPERATION / DETAIL] - <Process Name> Map. No YAML frontmatter. A leading --- corrupts the import (first line must be the # topic).
  • Headings #–###### and list items (-) both become topics, nested by heading level and by list indentation (4 spaces = one level deeper). Up to 6 levels.
  • Blockquote > directly under a heading = that node’s Notes / guidance. Use it for “what happens here” and the → §N mapping to the parent deliverable section the branch executes.
  • Step / decision leaves use checkboxes and brackets: - [ ] step to complete, - Decision: [ ], - [value - e.g. example]. Brackets and empty boxes signal “fill / tick me.”
  • Numbered branches ## 00 · … through ## 99 · … so XMind preserves order.
  • Lawful-effects rule (DOCTRINE.md): every action leaf renders to a lawful protective effect (deny access, increase standoff, evacuate, hand off to law enforcement). No offensive language.
  • Personnel by initials only (CLASSIFICATION.md); the principal by codename or designator.

3. The recursive step / serial block (the core mechanic)

Any element that recurs across the operation (a movement leg, a venue, a post, a drill, a shift handover) is seeded once as a clonable block: a serial node with indented step children. The operator duplicates the block per instance.

### Movement serial
> → executes EP-004 / EP-023 §Movement. Clone per leg.
- [leg - e.g. Lodging → Site (Ruta 21)]
    - [ ] Route confirmed open (SYS-008 alert check, OSINT-065 brief)
    - [ ] Primary / alternate / emergency routes briefed
    - Timings (SP / RP): [ ]
    - Safe havens en route: [ ]
    - Actions-on rehearsed: [vehicle contact / blocked route / medical]
    - Notes / decision log: [ ]
- [leg 2]

4. Required spine (every shape)

  • ## 00 · Process Plan - Gates & Triggers - the trigger that starts this process and the gate checklist it must clear, as checkboxes mapped to the parent cell’s gates/phases. (Analog of the D-01 “Collection Plan - PIRs & EEIs” spine.)
  • …shape-specific phase branches (§5)…
  • ## 99 · Execution Admin - running decision/deviation log, product register (which deliverables this process produced or updated), sign-offs, and open actions / RFIs.
  • Continuous / battle-rhythm processes (a running detail, a standing watch) also add ## 00b · Battle Rhythm & Triggers (daily/shift cadence, handover checklist, escalation triggers).

5. Target shapes (branch palettes)

Each cell is assigned ONE primary shape; the writer adapts branches to the cell’s actual sections. ★ marks branches that carry a recursive serial block. All shapes build on D-01 shape E (EVENT / PROTECTIVE / OPERATIONAL).

P · PLANNING-CYCLE - root = an engagement / movement being planned

00 Process Plan (gates G1–G5) · 01 Tasking & Inputs (engagement order, region package, principal) · 02 Intelligence Baseline (D-01 tasking, PIRs, threat posture) · 03 Advance Production ★(per venue/route) · 04 Plan Assembly (package, OPORD, annexes) · 05 Compression Decision (72h/24h variant, risk acceptance) · 06 Rehearsal & Brief-out · 99 Execution Admin (deviation log)

W · WARNING-ORDER - root = the movement being alerted

00 Process Plan (issue trigger, LTIOV) · 01 Situation snapshot · 02 Draft mission · 03 Execution - general concept, timeline, Be-Prepared-To tasks ★(task per element) · 04 Admin & Logistics to initiate · 05 Command & Signal (next order time, acknowledgement) · 99 Execution Admin (acknowledgement tracker)

AV · ADVANCE - root = a venue / route being advanced

00 Process Plan · 01 Advance Tasking & Kit · 02 Venue Walk ★(8-step sequence per venue) · 03 Route Recon ★(per route: primary/alt/emergency) · 04 Liaison (LE/medical/venue security) · 05 Vulnerabilities & Mitigations · 06 Advance Report Handoff (EP-002/EP-003) · 99 Execution Admin

DX · DETAIL-EXECUTION - root = a deployed detail (continuous)

00 Process Plan · 00b Battle Rhythm & Triggers · 01 Shift Start / Handover ★ · 02 Static / RON Posture · 03 Movement Serials ★(per leg) · 04 Arrival / Departure sequences · 05 Principal Interface Standard · 06 Running Decision Points ★ · 99 Execution Admin

CV · COVERT / SURVEILLANCE-DETECTION - root = a covert or SD task

00 Process Plan · 01 Mode Selection & Legal Boundary · 02 SD Box / Coverage plan · 03 Detection Serials ★(observation → correlation, N-of-3 rule) · 04 Compromise Discipline · 05 Transition-to-Overt Drill · 99 Execution Admin

CR · CRISIS-ACTIONS - root = a crisis response (drill library)

00 Process Plan (universal crisis sequence) · 01 Drill Serials ★(per drill: AOP/medical/contact/…) · 02 Comms Formats (contact report, MEDEVAC 9-line) · 03 Notification Matrix · 04 CASEVAC plan · 05 Post-Incident & Rehearsal Standard · 99 Execution Admin

6. Cell → shape map

ShapeCells
P PLANNING-CYCLEEP-020
W WARNING-ORDEREP-026
AV ADVANCEEP-022
DX DETAIL-EXECUTIONEP-021, EP-023
CV COVERT / SDEP-024
CR CRISIS-ACTIONSEP-025

Blends are expected. EP-021 (battle rhythm) is DX with the cadence spine dominant; EP-023 (detail execution) is DX with the movement/arrival serials dominant. The writer keeps the primary shape’s spine and grafts the branches the specific cell needs, mapping every branch to a parent section.

Graph View