City emergency ops · Fallstudie

19:40 says "passable," 20:15 says "approach road flooded" — find the two reports that disagree about the same bridge before the briefing

Example · Hypothetical scenario5 Min. LesezeitConsilience Team

Was dabei herauskommtFrom a folder mixing district HWP reports, fire radio logs, and spreadsheets, ask "every report on Dongbu Bridge, in time order" and get an answer with "Dongbu district situation report #3 · line 12" attached — without sending a single document outside the government network. The two reports that disagree come back stacked in the answer, and nothing lands until a person confirms it.

The 21:00 briefing. The mayor asks: "Can people cross Dongbu Bridge right now?" The center director's laptop folder holds forty-odd files that arrived today alone. The 19:40 Dongbu district situation report #3 says "passable." The 20:15 fire radio log says "approach road flooded, entry blocked." The two files sat side by side in the same folder, and nobody had opened both.

This person runs the emergency operations center of a city of 400,000. Ninety hours until the typhoon makes landfall, and district situation reports in HWP (the Korean word-processor format), fire radio logs, weather-service and ministry bulletins, volunteer-center spreadsheets, and call-center summaries pile up dozens per hour. These documents live inside the government network, so they cannot be uploaded to an outside cloud AI. This piece shows what you can ask once that material is in a Consilience workspace. It is a hypothetical scenario, not a real customer story.

What piles up in the folder

For the three days after the typhoon warning goes out, files in wildly different formats keep landing in the center's shared folder. Districts upload HWP documents, the fire service uploads logs typed up from radio traffic, and the volunteer center uploads spreadsheets. The same incident gets written down by different departments in different files.

  • District situation reports (HWP) — one every two hours from each of 18 districts. Past 200 of them since the warning.
  • Fire radio logs — text an operator types up from radio traffic. Around 300 lines a day, and one line is one incident.
  • Weather-service and ministry bulletins — advance advisories and road-closure notices, as PDFs. Roughly 20 a day.
  • Volunteer-center spreadsheet — capacity at 11 shelters, plus blanket, water, and generator stock. One sheet, overwritten with each day's numbers.
  • Call-center summaries — a document bundled up every 30 minutes. Flooding calls and power-outage calls sit mixed in one table.

How it works today

Today's procedure is a person copying things onto a whiteboard. Two operators skim the last two hours of reports, update the entries on the status board, then photograph the board and paste it into the briefing deck. The board has room for one line per entry, so the Dongbu Bridge cell holds only the most recent report anyone read.

It breaks when the two files come from different departments at different times. The operator who read the 19:40 Dongbu report and wrote "passable" on the board is not the operator who read the 20:15 fire radio log. That the two reports disagree is written down in neither file — only someone who opened both would know.

I read the 20:15 fire report too. It just never occurred to me to go back to the 19:40 district report.

How you set it up

Setup takes about one briefing's worth of time, roughly 20 minutes. Drop in the whole shared folder, register the emergency-response vocabulary once, and reconcile the different names for the same bridge.

  1. Drag the whole shared folder in

    Put the left sidebar in Workspace mode (⌘⇧E) and open "Extract sources" (⌘⇧I) above the file tree. Drag the situation-report folder and the HWP files, spreadsheets, and PDFs all go in at once, with the processing progress shown step by step. Material that only exists on the web, like the weather-service bulletins, gets pasted in by URL on the same screen.

  2. Ask questions while extraction is still running

    Send a chat while those 200 files are still processing and a dialog asks whether to send after extraction finishes or send now as-is. If there's time before the briefing, send after; if it's urgent, send now.

  3. Register the emergency-response vocabulary once

    Register the words this field actually uses — district, closure, cut off, displaced residents, shelter opening — then have the app re-read the documents. Abbreviations that appear only in the radio logs attach to the same concepts.

  4. Reconcile the different names for the same bridge

    "Dongbu Bridge," "Dongbu Br.," and "Dongbu Bridge south end" are written differently in different files. The app only proposes merging them into one; nothing lands until a person confirms. Nothing is applied automatically, and you can undo it any time.

  5. Keep the briefing chat as a case

    Save the briefing-prep chat as a "Cases" entry (⌘⇧K) and the key questions stay alongside the fixed subjects — Dongbu Bridge, the 11 shelters. Next briefing, you reopen it right where you left it.

How you ask

Thirty minutes before the briefing: typed straight into **"New chat"** (⌘⇧C), and what came back
"every report on Dongbu Bridge, in time order"
→ 9 reports in a table. 19:40 "passable" (Dongbu district situation report #3 · line 12),
   20:15 "approach road flooded, entry blocked" (Fire radio log 20:00 · line 41).
   The two lines come back stacked, with the app flagging them as
   disagreeing and waiting for confirmation. Until you confirm, nothing changes.

"which of the open shelters have no mention of a generator?"
→ 4 of the 11 shelters. Each row carries the original sentence that said
   the shelter was open, plus a "Volunteer-center supply status · line 7" link.
   Not a blank generator cell — 4 shelters where no report mentions a generator at all.

"who decided to close Dongbu Bridge?"
→ "Dongbu Bridge fully closed as of 21:05" — attributed on the sentence
   to the Disaster Safety Division director.

This gathers up because Dongbu Bridge is a single point in the knowledge graph (⌘⇧G). HWP report, radio log, or spreadsheet — every sentence that named that bridge attaches to that point. On the entity page, hover a connection and the original sentence that stated it is quoted as "{note} · line {n}", and clicking a note link in the answer opens the source document. In front of the mayor you can say "this is the 20:15 fire report" and put that exact line on screen.

What changes

BeforeNow
Dongbu Bridge reports are scattered across 18 district files and the radio logs9 of them gather on one entity page, in time order
You learn that 19:40 and 20:15 disagree only when the mayor asksOne question brings both lines back stacked, with the app flagging the conflict and waiting for confirmation
Checking shelter generators means eyeballing the spreadsheet against the reportsOne question returns the 4 shelters, each row carrying the original sentence that said so
Government-network documents rule out an outside cloud AIThe workspace is a folder on your own disk, and the original HWP files are never altered
19:40 says "passable," 20:15 says "approach road flooded" — find the two reports that disagree about the same bridge before the briefing · Consilience