VIGIL CONSILIUM
Context. Not headlines.
Contents

Open Professional
Professional methodology
What Vigil Professional is

Chapter 06

Economy & Logistics

Economy & Logistics is a working environment over one family of canonical records, not a page about them. The canvas has the whole width; the inspector opens only on what you select; every edge states why Vigil draws it.

The workbench

The Economy & Logistics landing in the Professional shell: the rail on the left with Economy & Logistics current in its Domain work tier and its six instruments beneath it; on the right three task cards — Trace a system, Work on the map, Understand an impact — each naming the record it opens on, then the six instruments in one row with a count of records each, and a Continue working list for this device.
The domain in the rail, with its six instruments beneath it, and a landing built around what you came to do: trace a system, work on the map, understand an impact. Each task opens an instrument on a record chosen by an authored fact. Beneath them, the six instruments and what this browser last opened.

Economy & Logistics sits in its own tier of the rail — Domain work, between following and analysing — because it is neither a monitoring surface nor an analysis tool. It is where the economic and logistical records of a module are worked as a structure: 54 strategic systems, 31 supply systems, 170 economic and infrastructural markers, 13 industrial organisations,38 commodities and 35 transmission chains across 7 modules, every one of them the same record Read and Explore show, with the same dates, grades and sources.

Where the records come from

Nothing in the workbench is its own. A strategic system is asystems/ record keyed by the value the module's markers carry; a facility is a locations/ record; the body that runs it is anindustry/ record whose facility edges point at those locations and whose products point at equipment records; a supply system, an exposure object and a transmission chain are the same records the public Economy, Logistics and Impact pages print. They are maintained on the weekly cycle by the same editorial process as everything else, with the same dates, grades and sources, and the workbench reads them at the moment you open it. There is no second, Professional database — which is why a correction to a record reaches the canvas, the pin and the brief block at once, and why the workbench can never show more than Vigil has established.

What the canvases refuse to doA relational flow is not a geographic route, and its arrows say so. Unknown throughput is not encoded in any width, length or arrow. A missing stage is named, never filled. An announcement, a target, a commissioning and a delivery are four different claims and are never merged. A topology is only as complete as the relationships the records author. An assessed exposure is drawn dashed because it is not a documented operational relationship.

One shell, six canvases — simple first

Every instrument renders into the same shell, and the shell shows only what the instrument's question needs:

  • Module and search at the top; Investigate beside them searches the whole corpus.
  • The instruments as a row — Systems, Flows, Infrastructure, Industry, Commodities, Impact — and the view toggle: the simple default, then the dense or geographic alternative.
  • The context line: which record the canvas is drawn for (a selector), what kind it is, and how many of its kind this module holds. Counts live here, not in the navigation.
  • The canvas, taking the whole width, with the register folded beneath it — every node as a list, the keyboard path to any of them, never removed.
  • Layers, Changes and Pins in the toolbar, each closed until you open it: the filters this instrument supports; the dated-change axis; the compare tray.
  • The inspector, hidden until something is selected, then a panel on the right (a sheet from the foot of a phone). Its first view is concise — one-sentence state, key relationships, latest change, basis, actions — and the full prose, connections, changes and evidence sit under tabs.
  • Present: the canvas alone between an identity line and a status line, for a screenshot; Esc returns.

The address is the state. Module, instrument, record, view, selection, trace, opened groups and pins all travel in the URL, so a canvas you have arranged can be sent to a colleague and reopens exactly as you left it.

Systems

A strategic system as a summary: what it rests on, what it is, what runs through it, what depends on it.

The Systems instrument on the Iran–Gulf energy system in the presentation state: four bands left to right — Inputs & dependencies (commodities and dependencies with their basis), Core system (named key nodes and the other markers grouped by type with counts), Movement (the supply systems through it, one marked with an open disruption) and Dependents & exposure (operators, exposure objects, grouped chains and Watch questions) — joined by arrows, with a row of key points beneath: key nodes, documented disruptions, operators, dependencies, Watch questions.
Four bands and a row of key points. Inputs and dependencies carry their basis; the core shows the record’s named key nodes and groups the other markers by their authored type; Movement is the supply systems through the system; Dependents and exposure is what names it — operators, exposure objects, chains and Watch questions. Groups open on request.

Choose a system in the selector. A system with a full record draws its dependencies and constraints with their basis; a system that exists only as a value on the module's markers says no record and draws what the markers and the other records give it. Full networkdraws every id the records carry as a column graph, each edge with its basis; Geography shows the same system on the module outline as points. Nothing joins two points.

Flows

A supply system as a journey in its authored order, traced upstream and downstream.

The Flows instrument on Hormuz crude exports in the presentation state: the supply system’s nodes in their authored order as a left-to-right journey of role runs — entry ports, a processing complex, more entry ports, the Strait of Hormuz as chokepoint, Sohar as transit node — each run banded origin, process or movement and joined by schematic arrows; the strait is selected and traced downstream so the nodes after it stay lit and the earlier ones dim; a Documented disruptions strip beneath.
The nodes of one supply system in the record's own order, in runs of one role, each run banded origin, process, movement or delivery from the role and the marker type, joined by schematic arrows. A node is selected and traced downstream; the documented disruptions sit beneath.

A band is derived from the node's authored role and then from the marker's type, so the journey is a projection of the record and not a model of a process. Trace upstream lights the nodes before the selection; trace downstream lights the nodes after it. Where another flow shares the node, Expand one step adds that flow as a branch beneath; Collapse removes it.

A sequence is not a routeThe arrow between two runs says the record names them in that order. It is drawn schematic so it is never read as a line on the ground, and the Map view draws no line between them at all.

Infrastructure

Map first. Points only.

The Infrastructure instrument on Iran–Gulf in the presentation state: the module’s economic and infrastructural markers as one-size points on the Gulf outline, coloured by category, the Strait of Hormuz selected and labelled, and a legend at the foot of the map naming the categories in view with their counts — corridors and routes, energy and industry, economic geography, ports and maritime, sea areas and straits, border and regional zones.
Every economic and infrastructural marker of the module at its published coordinate and at one size, coloured by category, with the categories in view named in a legend at the foot of the map. The layers hold everything else and stay closed until opened.

Select a marker to open its record; shift-click to pin several. From a marker: Trace system opens Systems on the system it belongs to, Show impact opens Impact on the first chain that names it, Show changes opens the axis on what touches it, and Show relationships redraws the marker as a small graph of who operates it, what it belongs to, what passes through it and what names it.

Industry

An organisation by what it has built, kept apart from what it has announced.

The Industry instrument on Rheinmetall in the NATO Eastern Flank module in the presentation state: five bands — Organisation, Facilities (the Unterlüß plant with its facility edge and status), Production role (the sectors and the kinds of dated claim it carries, announcement, target and commissioned kept apart), Outputs (Boxer and PzH 2000 as documented producer, the defence-industry system it runs) and Dependencies (artillery ammunition and propellant as input commodities, the Watch question that names it) — with a Dated claims strip beneath, each claim tagged by kind.
Organisation, facilities, production role, outputs, dependencies. The production role is the record’s own sectors and the kinds of dated claim it carries; the dated claims sit beneath, each tagged by kind.

A claim is drawn by its kind and never merged: announcement,target, commissioned, delivered are four different tags, and an organisation whose claims are all announcements says so. A product is the record's statement that it produces the equipment; it is not a quantity and not a delivery. The Defence Industrial Base is this instrument filtered to the sector, not a second record.

Commodities

One commodity from production to use.

The Commodities instrument on grain and oilseeds in the Ukraine–Russia module in the presentation state: the journey’s stages that the records support — Storage (the Lviv logistics hub), Movement (Odesa, the Kerch bridge and strait, Berdyansk, Mariupol, the Chop–Záhony crossing) and Use & exposure (the grain and oilseeds exposure object) — joined by schematic arrows, with the systems and chains that carry the commodity as chips beneath and a note naming the stages with no record.
The journey’s stages that the records support — production, processing, storage, movement, use and exposure — each holding the markers of the flows that carry the commodity, with the systems and chains that carry it as chips beneath. A stage with no record is not drawn; the note names it.

A commodity is a member of the module's economy block rather than a record of its own, so its evidence is on the objects, systems and flows that carry it, and the inspector says so. No volume, price or share is drawn anywhere, because none is recorded.

Impact

A transmission chain as a ladder, every edge with its basis.

The Impact instrument on the Ukraine grid-strikes-to-economy chain in the presentation state: a ladder from the dated trigger through four principal steps — affected asset, operational disruption, exposed sector, broader significance — to what the chain lands on, each step a card with its basis tag and a count of the records it names, joined by edges whose line is the downstream basis; the edge between the first and second steps is selected.
The trigger, the principal steps in order and what the chain lands on. Each step is a card with its basis tag and a count of the records it names, which open beneath it on request; the edge between two steps carries the downstream step's basis, and one is selected.

A chain can only weaken left to right — a confirmed step may lead to a plausible one, never the reverse — and it stops where the evidence stops. Select a step to read the claim it rests on; select an edge to read why the chain continues; open a step's records to select any of them. Other chains of the module are in the selector, not beside the canvas.

Reading an edge

An edge is drawn only where two records name each other by id. Its stroke is its basis.

  1. Documented

    A published source or the record’s own authored field names the relationship.

    Solid.

  2. Assessed

    Vigil’s reading of the records; no source states it directly.

    Dashed.

  3. Derived join

    Two authored ids that match — a node carrying a system’s value, a step naming a member marker.

    Dotted.

  4. Authored sequence

    A supply system’s own order of nodes. An order, not a route.

    Schematic, on Flows.

Four bases, four strokes. Select an edge and the inspector states which one, prints the sources where the basis carries them, and says in a sentence why Vigil connects the two records. Nothing else is ever drawn between two nodes.

Nothing encodes a quantityNo width, length, arrow or position on any canvas stands for throughput, capacity, volume or price. Those are not recorded, so they are not drawn. A thicker line would be a claim; the workbench makes none.

Pins and compare

Pin up to six records of any kind from the inspector or with shift-click;Pins in the toolbar opens the tray. It sets them side by side in three groups — recorded attributes; dependencies and relationships; change and freshness — on the fields their own records carry. A field one record lacks says not comparable rather than blank, and nothing is ranked. Add to brief from the tray sends the records to the Brief Builder as canonical blocks.

Dated changes

Changes in the toolbar opens an axis of every dated change the module's records carry — structural changes on systems, documented disruptions on flows, claims on organisations, events, Watch reviews — at its own date and at one size. Only the selection narrows it to what touches the selected record. It shows when something was recorded to change; it does not reconstruct how the system looked before.

Into work

The Systems summary of the Iran–Gulf energy system with a supply system selected in its Movement band and the inspector open beside the canvas: the record’s one-sentence state, its key relationships as chips, its latest documented change, its basis and register, and the actions — Pin, Show on map, Centre the canvas on it, Show changes, Add to a collection, Add to brief, Send to Analyse, Open the public record, Open in Explore.
A supply system selected in the Movement band of a system summary, with the inspector open beside it: one-sentence state, key relationships, latest change, basis, and the actions that move the record into work. Nothing leaves the canvas to do it.

The inspector offers only what makes sense for the selection: Pin; Trace upstream and downstream; Expand or collapse; Trace system, Show impact, Show on map or Show relationships; Show changes; Add to a collection; Add to brief; Send to Analyse; and the public record and Explore views of the same record. A commodity has no reference of its own, so it points you to the objects and flows that carry it; an edge is read, not saved.

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