LAKANA SOS · Emergency Management Review
A guided review of civilian-safety architecture, degraded communications, responder-scoped information sharing, environmental context, evidence boundaries, and safety without continuous surveillance. Start here if you evaluate emergency management, fire/EMS, disaster resilience, communications resilience, responder workflow, privacy, or public-safety systems.
Each path is a static route list. Every step is an ordinary link, so the whole review works with JavaScript disabled, on a phone, and with a keyboard alone.
For deciding whether this is worth a deeper look.
For emergency management, fire/EMS, and communications reviewers.
For systems, security, research, and academic reviewers.
SOS — the Sovereign Operating System — is LAKANA's civilian-safety branch. It is designed to identify a safety-relevant event on the person's own device, reduce that state to a small bounded representation, evaluate whether the state is strong enough to justify action, select among available delivery routes when communications are degraded, and record bounded execution evidence for later review. This describes the evaluated architecture, not a claim about field performance.
Emergency systems tend to solve availability by collecting continuously. That makes the safety system a permanent data source, and a permanent target, long before any emergency occurs.
Keep raw state local. Minimize before release. Scope every release to a role and a bounded window. Treat denial, expiration, and non-release as recorded events rather than silent absences.
The person may be unable to speak, unable to unlock a device, or unreachable. The architecture treats degraded power and network availability as expected operating conditions rather than exceptional edge cases.
A bounded public simulation of that behavior, plus the architecture and evidence structure behind it. Not a deployed service, and not a field result.
Looking for the complete SOS public research and evaluation environment? Open Full SOS Simulation. Reviewing the academic engineering project itself? Open Capstone Review. The Capstone page does not replace the flagship SOS research and evaluation surface.
The public SOS research and evaluation environment. This is the surface an emergency-management, fire/EMS, privacy, or systems reviewer should exercise.
Boundary: not a live emergency-dispatch system, and not field validation.
The academic engineering and project evidence dossier for the capstone itself. It answers what was built and tested for the course, not how the public evaluation environment behaves.
Boundary: the Capstone page does not replace the flagship SOS research and evaluation surface.
These are navigation lenses only. They route different reviewers to different starting points; they do not present different truths, different claims, or different maturity states to different audiences.
We are not asking anyone to endorse LAKANA. We are asking experienced practitioners to pressure-test it against real emergency-management, fire/EMS, communications, and human-factors practice.
These terms are used consistently across every LAKANA reviewer surface. Nothing below is softened for readability.
Controlled tabletop and human-factors evaluation is the next validation stage. Those exercises are designed to align with HSEEP concepts. They have not been conducted, and no tabletop exercise is presented as completed.
BFB is the Blue Force Bridge — the bounded responder handoff. TAB is the Tactical Audio Bridge, a feature nested inside BFB, not a peer system. These distinctions are load-bearing; collapsing any of them would turn a bounded coordination surface into an implied dispatch claim.
A request being made is not a request being granted.
An audio-bridge request is separately authorized from the BFB handoff that contains it.
State held locally through a degraded window has not reached anyone.
Forming a responder-scoped packet is not dispatching a unit.
Arrival at a destination is not confirmation that a human received it.
Acknowledgement is not tasking.
A completed handoff says nothing about anyone reaching a scene.
An unreachable user does not widen what the system may release.
A candidate is an admissibility question, not a determination.
A simulation receipt records what the system did, never what happened in the world.
For this reviewer phase the public review order is SOS first, then W-X, then WX-Ag, then SSI. That is reviewer information architecture. It does not redefine the scientific or authority architecture: W-X owns environmental truth, and CivOS, TSARO, and NICOLE remain shared architectural and authority layers underneath all of them.
What environmental state has evidentiary support? W-X evaluates support, contradiction, degradation, withholding, and expiry. It does not replace the National Weather Service, Mesonet-class observing networks, radar, satellite systems, meteorologists, emergency managers, or official warnings.
What bounded agricultural consequences follow from supported W-X state? WX-Ag consumes W-X environmental truth. It does not define environmental truth independently of W-X, and it claims no official weather authority.
What bounded civilian-safety communication or action may occur under SOS's own authority rules? SOS may consume permitted W-X environmental context. SOS does not recompute W-X environmental science.
CivOS: what physical and operational capability remains available. TSARO: what evidence and state is admissible, and how authority must contract. NICOLE: what access, release, custody, revocation, and audit are permitted. The human holds ultimate authority.
Stated before the evidence, not after it.