Rosetta Core · Cartridge 01 of 05

DISPATCH

One number.
Four doors.

000 · Unified Dispatch Fail state: context lost

The tempo

It isn't a queue.
A queue waits.

The hard part of taking a 000 call is not working out which service. A call-taker knows that within seconds — the caller says smoke, or blood, or a man with a knife, and the door is obvious. The hard part is that the next one is already ringing, and the one after that, at a rate nobody chose and nobody can slow down.

So the cartridge above is a rhythm game, because that is honestly what the job is. Each call has a window. The window closes whether or not you were ready for it. You do not set the tempo — you only ever match it, and the tempo only rises.

The handoff
The transcript travels with the call

When 000 passes an incident to a service, the caller's own words, the address and the initial assessment go with it — signed, timed, attributed. The receiving crew reads what was actually said rather than a summary of a summary.

The scope
Four views of one map

Every service is looking at the same incident and seeing a different layer of it. Scoping is not a permissions afterthought here; it is the thing that makes a shared map usable rather than a firehose.

The call

A 000 call is one sentence.
Four services need four different sentences.

Someone says what is happening in the only words they have — once, badly, while it is still happening. That utterance is a single thing. What four services need from it are four different things, and today the translation is done by a human on a phone tree, re-asked at every handoff, degrading a little each time it is repeated.

Rosetta does that translation once, at the door, and keeps every reading attached to the same incident. Not a shared inbox. A shared meaning.

Caller · verbatim · 14:02:07

“There's smoke coming from the house next door and I can hear someone inside.”

Medical
  • Persons reported: 1+
  • Smoke inhalation probable
  • Airway is the priority
  • Receiving hospital on notice
Fire
  • Structure, residential
  • Exposure risk: adjoining
  • Search & rescue committed
  • Nearest working hydrant
Law & Order
  • Cordon and traffic control
  • Next of kin
  • Scene preserved if fatal
  • Caller is a witness
SES
  • Not primary
  • Standby: structural collapse
  • Make-safe after handover
  • Neighbour welfare

Same sentence. Four doctrines. Nobody asked the caller twice.

The cabinet

Five cartridges.
One machine.

The five games above are not five skins on one game. The rules genuinely do not transfer: 000 plays a rhythm game, medical plays a packing problem, fire plays an interception problem it cannot win, police plays a game whose score is a record it must not cut, SES plays a routing problem against a clock nobody set. Try to impose any one of those rule-sets on the others and you get the thing every unified system becomes — the doctrine of whichever service had the loudest procurement.

So the answer is not one rule-set for four services. It is one machine that runs all five cartridges without flattening any of them. That is what Rosetta is. The Rosetta Stone was one decree in three scripts — not three documents, and not one script imposed on three readerships. Each service keeps its own doctrine; the Core keeps what connects them.

The connective tissue

What survives
the handover.

A multi-agency response fails at its seams, not in its middle. The Core's job is narrow and unglamorous: hold the four things that get dropped every time an incident crosses from one service to the next.

One coordinate space
Everyone is on the same map

Fire sees fuel, wind and hydrants. Police sees exclusion zones. Medical sees casualties. SES sees terrain and access. One map underneath, four layers on top — scoped, so nothing leaks that shouldn't.

One identity
A person, not a wristband

The patient identified at the first triage tag is the same patient at discharge, whether or not the systems that recorded them along the way agree with each other.

One chain
Evidence that survives court

Signed at capture, hashed, geo-stamped, attributed. Custody handovers are links rather than gaps — and a chain cannot be added retrospectively, which is exactly why it has to be structural.

One memory
The run is reviewable

Every service's record links to the same event. A coronial inquiry, an insurance claim and a training review read one coherent timeline instead of four partial ones that disagree.

Graceful degradation

The network is down.
We are not.

Every cartridge runs on the device in the responder's hand. Not a thin client, not a cached view — the Core itself, holding the mission, the patient and the chain of evidence whether or not anything upstream is answering. When signal returns, the field record merges with the receiving chart rather than being typed in twice.

This is not a disaster mode bolted onto a cloud product. It is the ordinary way the thing runs. The cloud is the optimisation; the device is the system. Which matters most in precisely the places coverage is worst — and those are the same places that flood, burn and wait longest for an ambulance.

Respond with memory.

When the grid fails, the Core remembers. When staff rotate, the record persists. When seconds matter, nobody asks the caller to start again.

Talk to us about testing