Worked workflows

Open the Gulf Energy & Maritime Risk scope and follow it, and follow the two or three questions inside it your exposure actually turns on.

Read what moved this cycle and what was checked and held. Select a question to see its current reading and its observables.

Open the observable the reading rests on and walk its evidence down to the dated entries and the named sources.

Collect the records you used into a collection named for the exposure, so next week starts where this week finished.

Insert the questions that moved, the observables beneath them, the locations they name and the activity series that bears on them.

Write the summary in your own voice, annotate the one block that needs a caveat, and export as PDF.

Query the instrument, the actors and the places by name. Read the family facets to see what the corpus holds before reading anything.

Select the records that bear on the question and collect them.

Put the two records the answer turns on side by side, and read what one carries that the other does not.

Hold the client’s stated assumption and read which parts of the recorded system become relevant, affected or stressed. Save the run.

Build the answer from the collected blocks, state the assumption explicitly as the client’s, and export with the evidence pack.

Select the question and read the actors and places its records name.

Open the question in Network. Read the relationship records and institutions its fields name, and trace the documented path to the dependency — reading each step’s basis, and remembering that a path is a chain of references, not a cause.

Open the observables that check it and read their stated limits before their readings.

Assemble the dated sequence that produced the current position, and keep it as a set.

Hold the one condition the policy question turns on, and read the invalidators as carefully as the implications.

Produce a note whose first section is what the reading cannot establish.

Open the module, follow its questions and its recorded-activity series, and save the workspace as a view.

Read the series over the window you care about. Open a bin to see the records it counts, with their bases and sources.

Trace a period that changed down to the events and developments behind it.

Build the sequence from those canonical records.

Produce the structured brief, with the Tempo strip printed beside the chronology.

Open Conditions on the module and read where each civilian system stands — running, flagged, stated or not stated — with its date and the evidence behind it.

Switch to Access: the crossings and corridors by the access state their records state, then Services on the service that matters — what it rests on, and what rests on it.

Open Exposure on the civilian chain the service files and select an edge to read why Vigil connects two steps; pin the service, the crossing and the chain.

Open the Civil resilience lens and select the observables that bear on continuity, reading their stated limits.

Add the pinned records from the tray and produce a structured output whose gaps section is drawn from the records’ own stated limits rather than written.

Open Forces on the module and select the formation: the chain of command above it, its subordinates in the Atlas’s own groups, what it fields with the grade and rung each claim carries, and its posture and published seats. Open Full structure when you need the whole tree.

Switch to Equipment on the system that matters and read its lane — variants, operators, formations with their rungs, industrial base, sustainment, recent change — with announced kept apart from fielded; then Doctrine on the force, reading the four registers in order and the exceptions before the method.

Open Operations on the documented campaign and walk its phases; select an edge to read that it is a sequence and not a manoeuvre. Then Sustainment on the formation and follow the handoff into Economy & Logistics on the record it depends on.

Pin the formation, the system and the campaign and open the compare tray: documented systems, published seats, sustainment edges and dated changes side by side, with NOT COMPARABLE where a record cannot answer.

Add the pinned records from the tray and produce a structured brief whose claims carry the records’ own dates, grades and sources, and whose gaps section is drawn from what the records do not state.

Open Systems on the module, choose the strategic system, and read its topology: what it depends on, the operators and commodities on it, the supply systems through it, the chains and questions that name it. Select an edge to read why Vigil connects the two.

Switch to Flows on the supply system that matters, select the node you care about, and trace downstream: the authored sequence after it, and the chains and exposures that land on it. Expand one step where another flow shares the node.

Pin the system, the flow and the two or three markers, and open the compare tray: dependencies, documented disruptions, newest dated change and review dates side by side, with NOT COMPARABLE where a record cannot answer.

Follow the Watch question the system names, so the next reviewed change reaches your desk without being looked for.

Add the pinned records to a brief from the tray, write what the topology showed in your own words, and export with the records’ own dates, grades and sources.