VIGIL CONSILIUM
Context. Not headlines.
Contents

Open Professional
Professional methodology
What Vigil Professional is

Chapter 08

Forces & Operations

Forces & Operations is a working environment over the military records Vigil maintains — how armed forces are organised, equipped, employed and sustained — not an order of battle with a score. It shows what the records state about a force, at the precision they state it and no finer.

The workbench

The Forces & Operations landing: a masthead that says the domain is derived and sits in Domain work, with the module count and the dated-entry count; three task cards — Understand a force, Read the battlespace, Trace an operation — each naming the module, area or campaign it opens on; then the six instruments, Forces, Equipment, Doctrine, Terrain, Operations and Sustainment, each with its job line and a count of records; and a Continue working list for this device.
The third domain in the rail, beneath Humanitarian & Resilience, with its six instruments; a landing built around three tasks — understand a force, read the battlespace, trace an operation — each opening an instrument on a record chosen by an authored fact; the six instruments with a count of records each, and what this browser last opened.

Forces & Operations sits in the Domain work tier beside Economy & Logistics and Humanitarian & Resilience. It works621 organisations in the Force Atlas, of which 267 are formations and 7 carry a stated posture; 164equipment records with 252 formation edges; 16forces with a doctrine block holding 3 published documents and47 dated adaptations; 30 terrain records with94 chokepoints on published markers; 35 campaigns with 117 authored phases; and 22 sustainment dependencies on 13 forces — across 7 modules. Modules are not expected to match: a module at war carries campaigns with phases and dated adaptations; a deterrence module carries command arrangements, postures and declared plans.

Where the records come from

Nothing in the workbench is its own. A force is an organisation record in the Force Atlas — the same tree the public Force Structure page draws — with its command relationships, its equipment claims (each with an evidence grade and, where the record states one, a fielding rung), its doctrine block, its posture, its published seats, its dated changes and its sustainment edges. A platform is an equipment/ record from the catalogue, with its variants, operators and producers. A campaign is a campaigns/ record with its frame, phases and participants; ground is a terrain record. A logistics record, a strategic system or an industrial organisation is an Economy & Logistics record the force names by id, opened there from the inspector rather than copied here. Each record carries two dates kept apart — the date what it states is as of, and the date Vigil last reviewed it. The public Force Atlas, unit and equipment pages print the same records in full; nothing needed to understand a force is held back from them.

What the canvases refuse to doStructure is not effectiveness, and no formation is scored. Brochure capability is not field capability, and a capability picture is a grouping. An announcement is not a delivery, a delivery is not fielding, and fielding is not observed operational use: the rungs are never merged. A maximum technical range is not operational reach. A deployment report is not permanent basing: a seat is a published address, drawn as a square, and nothing is drawn as a disposition. A sustainment edge is a dependency, not route geometry. A terrain constraint is not operational intent. No attack arrow, range ring, strength or readiness appears anywhere, because none is recorded. A movement arrow, a deployment marker and a capability label are each claims that require a basis; sparse data means sparse data.

The same shell as the two domains before it

Module, search, the instruments — Forces, Equipment, Doctrine, Terrain, Operations, Sustainment— and the view toggle; a context line with the counts that belong to the instrument; the canvas at full width with the register folded beneath it;Layers, Changes and Pinsclosed until opened; the inspector only on a selection, concise first, with five tabs; Present for a clean frame. The address carries the module, instrument, record, view, selection, phase and pins. The Economy & Logistics chapterdescribes the shell in full; everything there applies here.

Forces

How a force is organised — from its chain of command to a formation and its subordinates.

The Forces instrument on the Ukrainian Ground Forces in the presentation state: five bands left to right — Chain of command (the Armed Forces of Ukraine as parent), Selected (the Ground Forces as a service branch), Subordinates (its operational commands, corps, brigades and artillery formations in the Atlas’s own groups), Fields (the documented systems its record claims, each card with its evidence grade — T-64BV, Leopard 2, M1A1 Abrams, M2 Bradley, Bohdana, CAESAR, HIMARS) and Oriented · seated (what its institution publishes about its orientation and seats, or that none is published); a row of counts beneath — records beneath it, documented systems, published seats, sustainment edges, dated changes — and the capability picture grouping the documented systems by function.
One formation as a summary lane: the chain of command above it, the selected formation, its subordinates in the Atlas’s own groups, what it fields with each claim’s evidence grade and fielding rung, and its posture and published seats; a capability picture beneath grouping the documented systems by function, and a row of counts.

The lane reads left to right as the records connect: the commands above the formation, dimmed until the parent; the formation; its subordinates in the groups the Atlas itself uses, folded where a group is long; the equipment its own record claims, documented first with the grade and rung on each card and the reported, prospective and historical claims folded beneath; and what the institution says about its orientation — a posture with its basis, the published seats, the command arrangements it sits in. The capability picture beneath groups the documented systems by function; it is a grouping and never a score.Full structure draws the same tree the public Force Structure page draws, with every subordinate on request.Geography places the published seats as squares and the module’s generalised military markers hollow, points only.

The Forces instrument’s Full structure view on the Russian Ground Forces in the Ukraine–Russia module, in the presentation state: the two sides as a strip across the top, the side’s tree as a browser on the left with the Ground Forces open, and on the right the record’s banner — its category device, echelon, assessed-as-of and reviewed dates and confidence — with the Armed Forces of Russia as the plate above it and its subordinate commands, military districts and combined-arms armies as plates below, grouped by the Atlas’s own echelon groups, each plate carrying the subordination grade its record states.
The full structure of one formation, drawn by the same renderer as the public Force Structure page: the side’s roots, the selected formation’s banner and its subordinate tree in the Atlas’s groups, with the legend naming each mark. Nothing here is a strength.

Equipment

One platform through its variants, operators, formations and industry — announced kept apart from fielded.

The Equipment instrument on the T-90M Proryv in the presentation state, drawn as one family lane of six columns: Family and variants named (the T-90M record with the T-90A and T-90M Proryv variants its record names), Operators (Russia as primary operator and Ukraine as a captured operator, as the catalogue names them), Formations (the Russian Ground Forces and the 2nd Guards Motor Rifle Division, whose own records claim it, each with its evidence grade), Industrial base (Uralvagonzavod as the manufacturer the record names, marked as having no industry record), Sustainment (the Economy & Logistics records its formations depend on, marked via the formation) and Recent change; a row of counts beneath — variants named, operators, documented formation edges, producer records, status as of its date.
One family as a lane: the record and its family members, the variants it names, the operators the catalogue names, the formations whose own records claim it with their grade and rung, the industrial base that produces it, the sustainment records its formations depend on, and its recent dated change.

Families is the catalogue in columns by function, each card tagged with the record’s own status. Select a system andOne family draws its lane. An operator is a state the catalogue names, never a formation; a formation edge is the formation’s own claim, with the evidence grade the record gives it and, where the edge states one, the fielding rung. A producer is an Economy & Logistics industry record and opens there; it is a statement that the record names the product, never a quantity or a delivery. Operatorssets the systems by the state that names them, and Mapplaces the published seats of the formations that name the system, as squares.

  1. Announced

    A stated intention, a pledge, a programme.

    Nothing ordered yet.

  2. Ordered

    A contract or an order the sources state.

    Nothing delivered yet.

  3. Delivered

    Reported handed over, not yet reported in a formation’s use.

    Not fielded.

  4. Fielded

    Reported in a named formation’s use, with the source that says so.

    Never a quantity.

The fielding ladder on a formation edge, never merged. An edge moves up only on a newer sourced claim; observed in use, withdrawn and transferred are the later rungs. An edge that states no rung shows none.

Doctrine

Published doctrine, stated and observed method, assessed adaptation, and where it breaks down — four registers, never merged.

The Doctrine instrument on the Republic of China Armed Forces in the presentation state, drawn as one force lane: Published doctrine (the documents the record cites by title, issuer and date, among them the Quadrennial Defense Review), the stated and observed Method with its date, the force and equipment the method rests on, the observed employment the module’s campaign records carry, and the assessed Adaptations, each dated and graded, with the record’s own exceptions — where the generalisation stops holding — kept apart; a row of counts beneath by register.
One force as a doctrine lane: the documents it has published, the method it states and is observed to use, the force and equipment the method rests on, its observed employment in campaign records, and the adaptations Vigil assesses from repeated evidence — each dated and graded, with the exceptions the record states against itself.

The Registers board sets every force with a doctrine block across four columns — published doctrine, stated and observed method, assessed adaptation, where it breaks down — and a fifth for the declared plans and assessed contingencies the module’s campaign records carry, which are concepts and not operations. One force draws the same registers as a lane from the published document through the method to the force and equipment it rests on, its observed employment and its adaptation. What a force publishes is never read as what it does; a module where no force carries a doctrine block says so.

Terrain

What the ground does to movement, and what rests on it.

The Terrain instrument on the Ukraine–Russia module in the presentation state, drawn as one area lane on the terrain record with the most chokepoints: Ground (the record and its region), What the ground does to movement (the constraints the record states — relief, water, season, urban area — each as its own card), Chokepoints · published markers (the markers the module already publishes, each with the record’s reason), Movement that depends on it (the logistics records sharing a node with the ground) and Operations · forces (the campaigns, forces and Watch questions that name it); a row of counts beneath — chokepoints, logistics records, campaigns, forces with an edge onto it, confidence as of its date.
One area of ground as a lane: the terrain record, the constraints it states on movement — relief, water, season, urban area — its chokepoints on published markers with the record’s own reason, the logistics records that share a node with it, and the campaigns, forces and Watch questions that name it.

Ground is every terrain record in the module as a row, with the chokepoints it names as static place cards. One area draws the lane; Map places the chokepoints as points. A chokepoint is a marker the module already publishes, with the record’s reason; a constraint is the record’s own statement at the level of published analysis. No key terrain is ranked, no corridor is drawn, and no intent is read from a constraint.

Operations

A documented campaign as its authored phases — a sequence, never a manoeuvre.

The Operations instrument on the February 2022 invasion and the failure at Kyiv in the presentation state, drawn as a phase ladder: the four phases the record authors in its own order — the opening strikes and the four axes, the northern advance stalling, Mariupol and the southern land corridor, the withdrawal from the north and what it revealed — each with its period, its confidence and the dated events inside it, joined by authored-sequence edges labelled then; a final stop that says the record stops here; and beneath, the rail of participants with their roles, the published markers the campaign names, the ground and supply records it names, its stated and assessed objectives, and the Watch questions and Notes on it, ending at the recorded outcome.
One campaign as a phase ladder: the phases the record authors in its own order, each with its period and confidence and the dated events inside it, joined by authored-sequence edges that say then; beneath, the rail of participants with their roles, the published markers, the ground and supply the record names, its stated and assessed objectives, and the Watch questions on it; the outcome at the end, where the record stops.

The Board sets campaigns by frame and lifecycle: observed and ongoing, observed and concluded, declared plan, assessed contingency. The last two are concepts a party published or Vigil described, and carry no timeline, status or outcome by construction. Phasesdraws one campaign as its ladder with the rail beside it; select an edge and the inspector says it is a sequence. Map shows only the published markers of the events inside each phase, stepped by phase: no line, arrow or axis joins two phases.

Sustainment

What keeps a formation operating — read from Economy & Logistics records, each edge with its basis.

The Sustainment instrument on the Russian Ground Forces in the presentation state, drawn as one force lane: Industrial base (the defence-industry system the Armed Forces of the Russian Federation author a dependency on, marked via that command), Strategic rear (the Russian strategic rear system, an assessed dependency), Depots · repair, Transport · networks (the military logistics system, an assessed dependency), Operational logistics (Russian rear-area sustainment, a documented dependency, and the refining-and-fuel record inherited via the parent, assessed) and Formation (the Ground Forces); each card carrying the edge’s basis as a tag, and a row of counts beneath — own sustainment edges, inherited from the chain, industrial records, logistics records, documented.
One force as a sustainment lane: industrial base, strategic rear, depots and repair, transport and networks, operational logistics, and the formation — each card an Economy & Logistics record the force or a command above it authors a dependency onto, with the edge’s basis on the card and inherited edges marked via the command that authors them.

The edge lives on the force record and points at a logistics record or a strategic system by id; the record it points at stays owned by Economy & Logistics. One force draws the lane, folding in the edges the formation inherits from the chain above it, each markedvia; the producers of its documented systems appear in the industrial base. Systems lists every military-sustainment record in the module with the forces that depend on it — a record with no dependent force is a coverage statement, not a finding. A dependency is never a route, a capacity or a stock.

The Economy & Logistics Flows instrument on Russian rear-area sustainment in the presentation state — the record the Russian Ground Forces depend on, opened where it lives: the supply system’s nodes in their authored order as a left-to-right journey of role runs, banded by role and marker type and joined by schematic arrows, with the record’s documented disruptions in a strip beneath and the status line giving its assessment date, review date and confidence.
The handoff: the same logistics record opened in Economy & Logistics Flows, where it lives — its nodes in their authored order, its documented disruptions beneath, its status line. The force’s dependency on it is drawn in Forces & Operations; the record itself is drawn here, once.

Across the domains

Wherever a force authors a sustainment edge, the inspector offersOpen in Economy & Logistics on the record it names — Flows for a logistics record, Systems for a strategic system, Industry for a producer — and nowhere else: a handoff exists only where an authored edge exists. A location a formation is seated at, a terrain record a campaign names and a Watch question on a force open in their own homes the same way. Nothing is copied between the domains; each record is drawn where it is owned.

Pins, compare and dated changes

Pin up to six records — formations, systems, campaigns, terrain, logistics records — from the inspector or with shift-click. The tray sets them side by side on their own fields: one formation’s documented systems, published seats and sustainment edges beside another’s, a campaign’s phases and participants beside a formation’s. A field one record lacks saysnot comparable, records of different kinds sayNOT COMPARABLE where they share nothing, and nothing is ranked. Changes opens an axis with ten lanes — dated change, formed or reorganised, subordination, equipment claim, command arrangement, posture, adaptation, campaign phase, event and Watch review — one mark each at its own date. It shows when something was recorded to change; it does not reconstruct a past order of battle.

Present

Present strips the shell to the canvas and an identity line — Vigil Professional, the domain, the module, the instrument — with the record’s name and its status line in the footer. Every picture in this chapter is cut from it. The device keeps what this browser last opened on the landing; nothing of it is sent anywhere.

Into work

The inspector offers what fits the selection: Pin; Centre the canvas on it; Show full structure or Show structure; Trace the family; Trace the operation; Show terrain; Show on map; Show changes; Add to a collection and Add to brief (a phase, a claim, an adaptation or a change travels through the record that carries it); Send to Analyse; the public record and Explore; and, wherever a force names one, the record it depends on in Economy & Logistics. A pinned set goes to the Brief Builder from the tray with the records’ own dates, grades and sources.

When something looks wrong

  • A formation has no position. The Atlas records a published seat only, drawn as a square; a deployment report is not permanent basing, and nothing is inferred.
  • A formation shows no equipment, or no rung. It fields only what its own record claims; an edge that states no rung shows none, because announced, ordered, delivered and fielded are four facts.
  • Doctrine is empty for a module. No force in it carries a doctrine block; nothing is inferred from structure or equipment to stand in for a method.
  • A campaign has no phases, or no map. It authors none, or its events name no published marker; a plan or a contingency has no phases by construction.
  • A sustainment lane is empty. Neither the force nor the chain above it authors an edge; the Systems view shows the module’s records so the gap is visible as coverage.

The Reference chapter carries each of these at length.

Next: Analyse — two records side by side, and one condition held.