EMRCS Workspace:No incident declared. Select Start New Incident to establish an incident profile, unlock document ingestion, and begin baseline extraction. To see a manually authored illustration of a completed DCB, select View Reference DCB Example.
Active incident:No incident declared.
Incident Profile
Declare the incident this Decision Continuity Brief will serve. This establishes the incident identity. Document ingestion unlocks once the profile is confirmed.
Incident Name, Incident Type, and Operational Period are required.
Starting a new incident clears the current incident session. The Palisades worked example remains available through Return to Palisades Example.
The content below was written by hand by the EMRCS Triad to illustrate what a complete, Coordinator-reviewed Decision Continuity Brief would contain after a full operational period. Every node was authored, not extracted. This is the intended destination of the EMRCS workflow. It does not represent what the EMRCS engine currently produces from document ingestion.
Current EMRCS engine capability
Deterministic extraction of candidate reasoning nodes. Planning/Intelligence Section Coordinator review (Accept, Edit, Reject). Baseline lock with metadata. Drift detection against the locked baseline. Generation of a Decision Continuity Brief from accepted nodes is a future development objective and is not available in this build.
AUTHORED ILLUSTRATION: The following header and incident metadata were written by hand to illustrate the target state of a completed DCB. This content was not produced by the EMRCS extraction engine.
Fire grew to 15,832 acres overnight following aircraft grounding. CAL FIRE Type I IMT assumed management with Unified Command at Zuma Beach. Communications infrastructure destroyed. Water supply failed in elevated sectors. OP1 documentation incomplete. Eaton Fire competing for regional resources. All major assumption categories require validation before the Action Planning Meeting.
This augments existing ICS documentation. It does not replace it.
At each Action Planning Meeting, the Planning/Intelligence Section develops objectives and validates assumptions for the next operational period. The reasoning behind those decisions is rarely documented in a form that survives the transition. The assumptions that were treated as ground truth, the alternatives that were analyzed and rejected, the constraints that shaped the options, and the uncertainties that remained unresolved leave with the outgoing team. The Decision Continuity Brief preserves that reasoning so each Planning Meeting builds on what the last one actually knew, rather than reconstructing it.
The EOC Action Plan tells incoming personnel what was decided. The Decision Continuity Brief tells them why it made sense at the time it was made.
Operational Boundaries
Experimental R&D prototype. Not for live EOC deployment without validation. The system flags candidate reasoning and drift; the Planning/Intelligence Section Coordinator decides. No Decision Continuity Brief is released without Coordinator review and confirmation. All processing runs locally in the browser. Incident content remains under agency custody.
How to Use EMRCS
Review the worked example below to see what the tool produces.
Select Start New Incident and declare your incident profile.
Load founding documents and establish a baseline.
Review candidate reasoning nodes: accept, edit, or reject.
Lock the baseline.
Evaluate drift across operational periods before each Action Planning Meeting.
▸Understanding the Decision Continuity Brief (DCB)
What current systems preserve well
What happened
What decisions were made
What resources were assigned
What objectives were set
What current systems rarely preserve
Why decisions were made
What assumptions influenced them
What alternatives were considered
What uncertainties existed at the time
At each Action Planning Meeting, standard SEMS/ICS documentation captures what was decided. It rarely preserves why those specific decisions made sense at the time they were formulated. The assumptions treated as ground truth. The alternatives analyzed and rejected. The constraints that shaped available options. When planning rationale exists only in the minds of the outgoing team, the next Planning Meeting reconstructs settled logic rather than building on it.
Reduces time required for incoming command staff to achieve full cognitive alignment with the current operational period by converting dense text logs or meeting transcripts into structured rationale maps.
Preservation of discarded alternatives
Explicitly archives why specific courses of action were rejected, preventing incoming shifts from wasting critical operational cycles re-analyzing solutions that were already found to be unfeasible.
Auditable uncertainty mapping
Isolates unverified assumptions and active variables so that subsequent operational planning sessions can target specific informational blind spots systematically rather than discovering them mid-period.
Current planning documentation vs. Decision Continuity Brief
Current planning documentation
With Decision Continuity Brief
What happened
What happened
Objectives
Objectives
Resource assignments
Resource assignments
Actions taken
Actions taken
not preserved
Assumptions active at time of decision
not preserved
Alternatives considered and rejected
not preserved
Uncertainties at time of decision
not preserved
Reasoning continuity across shifts
01
The problem
When shifts change, reasoning disappears. The incoming Operations Section Coordinator learns what was decided. Rarely why it made sense at the time it was made.
02
The consequence
Repeated debates on settled decisions. Assumptions that were already tested get tested again. Institutional memory that evaporates between operational periods.
03
What this is
A structured reasoning record extracted from existing operational activities. It augments current turnover practices by preserving what is usually communicated verbally and lost.
04
System boundaries
The system operates as an analytical overlay that integrates directly with existing ICS workflows. It isolates, maps, and preserves the cognitive rationale behind operational decisions.
Read the turnover brief. Review active assumptions. Verify whether the reasoning chain still applies. Update as conditions evolve. Validate through Section Coordinator review.
How it works: Planning/Intelligence Section integration with the Planning P
The EMRCS does not add a new role, a new meeting, or a new form. It produces one additional output from work the Planning/Intelligence Section is already doing at each step of the Planning P cycle.
Step 1
Planning/Intelligence Section collects forms
SEMS/ICS 201, 202, 214s, Situation Analysis Reports, resource status: everything the Planning/Intelligence Section already gathers before the Action Planning Meeting. No additional documentation required.
Step 2
Forms loaded into EMRCS
Planning/Intelligence Section loads the operational period forms into the EMRCS locally: Situation Analysis Reports, position logs, SEMS/ICS forms. This is the only new action required. Everything runs on-device. Nothing is transmitted.
Step 3
EMRCS generates the DCB
The system extracts the reasoning structure from those forms and generates a draft Decision Continuity Brief before the Action Planning Meeting begins.
Step 4
Planning/Intelligence Section reviews the DCB
A qualified Planning/Intelligence Section member reviews and approves the draft. This is the mandatory Section Coordinator validation step. No DCB is released without human sign-off.
Step 5
DCB delivered at OP Briefing
At the EOC Action Plan Briefing, the DCB is delivered alongside the EOC Action Plan. The EOC Action Plan tells incoming personnel what was decided. The DCB tells them why it made sense at the time it was made.
Step 6
Cycle repeats each OP
The next shift's Planning/Intelligence Section loads the next period's forms, generates the next DCB, and the cycle continues. Reasoning continuity is preserved across every shift change for the duration of the incident.
Data Sovereignty and Local Containment Protocol
The system operates under a localized containment architecture to guarantee total data custody to the activating agency.
✓Executes entirely within the local browser runtime on isolated, agency-controlled hardware.
✓Processes all ingested artifacts locally, eliminating external server or cloud service routing.
✓Maintains strict compatibility with air-gapped EOC network configurations by disabling external backhaul dependencies.
✓Isolates Protected Critical Infrastructure Information (PCII), Law Enforcement Sensitive (LES) data, and Personally Identifiable Information (PII) from external search exposure or third-party storage frameworks.
Sensitive incident communications remain under the custody of the activating agency at all times. The system enforces zero sub-processor data transmission protocols.
Who owns this process
The Planning/Intelligence Section owns the EMRCS workflow under SEMS. No new role is created. No existing role is replaced. The Planning/Intelligence Section Coordinator already collects the forms, already facilitates the Action Planning Meeting, and already produces the EOC Action Plan distributed at the start of each operational period. The Decision Continuity Brief is one additional output from that existing function: prepared by the Documentation Unit, reviewed by the Section Coordinator, and delivered at the EOC Action Plan Briefing alongside the Action Plan.
AUTHORED ILLUSTRATION: Every reasoning node, assumption, constraint, and evidence entry shown below was written by hand by the EMRCS Triad. These nodes were not extracted from documents by the EMRCS engine. They illustrate what a fully Coordinator-reviewed baseline would contain.
The Decision Continuity Brief worked example follows below
Palisades Fire Response
Operational Period 2 · January 8, 2025, 06:00 AM onwards · CAL FIRE Type I IMT, Unified Command at Zuma Beach · Pacific Palisades / Malibu, Los Angeles
Executive Summary: 30-second briefing for incoming leadership
🔴 Immediate action required
Command transfers in OP1 were never documented. Confirm current command relationships before any decisions.
Water supply failure in elevated areas reported at 20:00. Current status unknown.
All aircraft grounded at 19:45. Reassess wind conditions before requesting air operations.
🟠 Validate at Action Planning Meeting
Mutual aid availability: Eaton Fire competing for same regional resources.
Staffing assumptions: coded-assign hire still not activated, 11 vacancies carried forward.
Evacuation zone coordination with LAPD: sub-zone confusion unresolved.
RECONSTRUCTED
This artifact represents an inferred reasoning reconstruction generated from available operational records. It is not a definitive record of participant intent and requires Section Coordinator review before operational use.
Purpose: Detects whether assumptions and reasoning from prior operational periods may no longer reflect current incident conditions.
Run before each Action Planning Meeting. Load OP documents from the current period, then run drift analysis. The system compares incoming terminology against the OP1 baseline to flag reasoning nodes that may no longer reflect the operational picture. Assumes reviewer is Planning/Intelligence Section Coordinator. All proposed changes require your confirmation. The system flags; you decide.
This DCB is incident-specific. The drift detector compares incoming documents against the reasoning baseline extracted from this incident's nodes. Loading documents from a different incident, activation, or agency will produce drift scores with no operational meaning. To use EMRCS for a different incident, a new DCB must be built from that incident's source documents. Do not load unrelated documents into this tool.
Current OP Documents
Drop current OP documents here (.txt or .docx) : ICS forms, situation reports, position logs, planning briefings. Each document added expands the corpus. No text is stored beyond this session.
No documents loaded.
0 words
min: 200 words
⚠ Corpus below minimum threshold. Drift analysis may produce unreliable signals. Load additional documents.
🚨 Drift Alerts, Proposed Status Changes Require Your Decision
Since last operational period, OP1 → OP2
This section tracks every material change between Operational Period 1 (January 7, 2025) and Operational Period 2 (January 8, 2025). Each entry is sourced. No inference. This is the most operationally critical section for incoming leadership.
New constraints
Fire growth to 15,832 acres overnight. Fire was estimated at over 3,000 acres when aircraft were grounded at approximately 19:45 on January 7. By January 8 the fire had grown to 15,832 acres without aerial suppression. Structure-to-structure ignition and downrange ember cast unchecked overnight.
[Source: Malibu AAR p.12 timeline : 15,832 figure confirmed as final CalFire daily status; LAFD AARR p.36, 17,000 acres within 24 hrs of grounding]
Command post relocated to Zuma Beach, Malibu. On January 8, CAL FIRE established the multi-jurisdictional regional Unified Command Post at Zuma Beach, 3000 Pacific Coast Highway. Located 20 miles from the LAPD staging area at Will Rogers. Physical separation created dual ReStat and SitStat boards, double work, and documented miscommunication between UCP and LAPD CP.
[Source: LAPD AAR p.37 (location), p.19-20 (dual boards, miscommunication)]
Land Mobile Radio and cellular infrastructure destroyed. Critical LMR and cellular infrastructure in the affected area was destroyed on the first day of the incident. LAPD personnel at Zuma Beach UCP could not effectively communicate with personnel at LAPD CP. Radio frequencies could not be shared with other law enforcement agencies. Zuma Beach UCP had no internet connectivity for the first days; 211s and critical documents were hand-delivered by vehicle.
[Source: LAPD AAR p.39 (comm failure), p.20 fn.14 (hand delivery), p.40 (Critique 1)]
Malibu EOC relocated from City Hall to Westlake Village EOC. City of Malibu EOC evacuated City Hall and relocated to Westlake Village EOC. A second relocation to Camarillo Police Department followed January 9 due to the Kenneth Fire. EOC Action Plans remained inconsistent; whiteboard information not translated to planning documents across relocations.
[Source: Malibu AAR p.12 timeline, p.22 (planning gaps), p.22 (whiteboard/Action Plan failure)]
Over 180,000 people under evacuation orders. Gas shutoffs activated. Additional road closures implemented. Santa Monica-Malibu Unified School District closed. Some telecommunications providers deployed Cell on Wheels to Malibu area.
[Source: Malibu AAR p.12 timeline (January 8 entries)]
Invalidated assumptions
Assumption invalidated: Mutual aid resources available without Eaton Fire competition. Resources enroute to the Palisades Fire were redirected to the Eaton Fire after its ignition at 18:18 on January 7. Over the following days both fires competed for the same resources, with assets initially assigned to Palisades diverted to Eaton within the first 12 hours.
[Source: LAFD AARR p.35 : Eaton Fire ignition and resource redirection]
Assumption invalidated: ICS documentation continuity maintained across command transfer. The OWB IMTs who managed the incident overnight did not complete standard ICS documentation required for an incident with multiple operational periods. No chronological log, no objectives documentation, no resource deployment record beyond a basic ICS 201 was available when IMT-2 assumed command at 06:00. IMT-2 assumed command without a complete operational record from OP1.
[Source: LAPD AAR p.20 fn.15, p.41-42 (Critique 3 : Documentation)]
Assumption invalidated: Water infrastructure adequate for firefighting operations at scale. Confirmed failed. Volume of water in hydrants decreased throughout OP1 and resulted in a complete loss of water in elevated areas above Sunset Boulevard at approximately 20:00 on January 7. Entering OP2, firefighting operations in elevated Palisades sectors are without functional hydrant water supply.
[Source: LAFD AARR p.47-48 (Secondary Challenge 3), confirmed failure at ~2000 hours January 7]
New assumptions entering OP2
CAL FIRE Type I IMT transition assumed to resolve command continuity gap. LAFD FIMT produced an IAP for January 8 to transition with the CAL FIRE Type I IMT. Transition described in AAR as executed well with professionalism and clear guidance. Incoming leadership should verify this assumption : the IMT is new to the incident and inheriting a degraded operational picture.
[Source: LAFD AARR : Successes 76, 78 (p.42-43)]
Night air operations assumed viable once wind conditions permit. Twenty-six night aircraft were available. LAFD and CAL FIRE conducted night air operation briefings prior to each operation. Aircraft resumption contingent on wind gusts falling below aircraft operational limits. Conditions must be reassessed at each OP.
[Source: LAFD AARR : Successes 46, 47, 48 (p.40)]
Citywide IMT-2 assumed to rotate command with IMT-1 on three-day cycle. LAPD activated four Citywide Incident Management Teams. IMT-2 briefed and officially assumed LAPD command at 06:00 on January 8. IMT-1 and IMT-2 scheduled to rotate every three days with internal A/B watches.
[Source: LAPD AAR p.19 (IMT-2 assumption of command, rotation schedule)]
Major decision changes
Incident command transferred from LAFD to CAL FIRE Type I IMT. Management of the incident shifted on the morning of January 8 when CAL FIRE took over management and established the Unified Command Post at Zuma Beach in the City of Malibu. This is a fundamental change in incident governance structure. All incoming OP2 personnel must verify their chain of command under the new UCP structure before taking any action.
[Source: LAPD AAR p.19 (CAL FIRE assumes management, Zuma Beach UCP); LAFD AARR Successes 78 (p.43)]
LAPD command structure formalized: Citywide IMT-2 assumes incident command at 06:00. The OWB IMT that managed OP1 overnight transferred command to Commander 20A at 00:05 on January 8. At 06:00, Citywide IMT-2 was briefed and formally assumed command of LAPD operations. IMT-2 IC and OSC responded directly to Zuma Beach UCP; Planning Section Chief managed LAPD CP at Will Rogers, creating a split command.
[Source: LAPD AAR p.57 (00:05 and 06:00 log entries), p.19-20 (split command structure)]
Phase 2 Limited Recall in effect; firefighters working 36+ hours without rest. Recall posted at approximately 19:15 on January 7, over eight hours after ignition. Entering OP2, most firefighters have worked in excess of 36 hours without rehabilitation. Physical exhaustion causing performance and safety concerns. Recall producing personnel but insufficient apparatus available. Most 200 series engines deployed, remainder mechanically unavailable.
[Source: LAFD AARR Primary Challenge 3 (p.44) : 36 hours without rehabilitation; p.36 (recall timing and apparatus shortage)]
Layer 1: Turnover Brief
Operational Period 2 begins at approximately 06:00 on January 8, 2025 when Citywide IMT-2 was briefed and assumed command of LAPD operations at the Palisades Fire. The previous night's command, the OWB IMT, transferred to Commander 20A at 00:05, who advised he had adequate resources and would reevaluate in the morning with 100-mile-per-hour winds still active and PPE distributed. The OWB IMTs did not produce standard ICS documentation required for a multi-operational period incident: no chronological log, no objectives record, no resource deployment documentation beyond a basic ICS 201 was available to IMT-2 upon assumption of command.
By dawn, the fire had grown from approximately 3,000 acres at the time of aircraft grounding to 15,832 acres confirmed by the CalFire daily status report for January 8. The overnight growth was unchecked: all aircraft remained grounded, water infrastructure in elevated Palisades areas was exhausted as of approximately 20:00 on January 7, and structure-to-structure ignition with downrange ember cast drove the fire into residential areas throughout the night. Every community across the Palisades was ablaze by nightfall on January 7. Entering OP2, incoming leadership inherits the most destructive WUI fire in Los Angeles history in progress.
On the morning of January 8, CAL FIRE took over management of the incident and established a multi-jurisdictional regional Unified Command Post at Zuma Beach in the City of Malibu, 20 miles from the LAPD staging area at Will Rogers State Beach. LAFD FIMT produced an IAP for January 8 to transition with the CAL FIRE Type I IMT, which the LAFD AAR described as executed well. The LAPD IMT-2 IC and OSC responded directly to Zuma Beach; the Planning Section Chief remained at Will Rogers, creating a split command structure with severely degraded communications between the two locations. LMR and cellular infrastructure in the affected area had been destroyed on the first day. Zuma Beach UCP had no internet connectivity; critical documents were hand-delivered by vehicle.
More than 180,000 people were under evacuation orders by January 8. Gas shutoffs activated. The City of Malibu EOC had evacuated City Hall and relocated to Westlake Village EOC on January 7; it would relocate again to Camarillo Police Department on January 9 due to the Kenneth Fire. EOC Action Plans remained inconsistent across shifts; whiteboard information was not translated to planning documents. The Eaton Fire, ignited at 18:18 on January 7, continued to compete directly for the same regional resources, with assets initially assigned to Palisades diverted to Eaton within the first 12 hours.
Incoming shift: monitor closely
Water supply in elevated Palisades areas remains failed, confirmed at approximately 20:00 January 7. Aircraft resumption contingent on wind conditions. Reassess before any air operations order. ICS documentation gap: OP1 documentation incomplete. IMT-2 inherited incident without full operational record. Zuma Beach UCP communications unreliable. Verify command chain before acting on any order. Eaton Fire resource competition unresolved. Do not assume mutual aid availability confirmed in OP1 plans still holds. Recall producing personnel but insufficient apparatus available. Firefighters working 36+ hours. Fatigue and safety risk elevated for all OP2 personnel.
Top 5 reasoning risks: critical continuity findings : OP2
Operational picture: Rapid overnight fire growth to 15,832 acres, degraded command continuity from incomplete OP1 documentation, split command structure with destroyed communications infrastructure, resource competition with Eaton Fire ongoing, and critical water supply infrastructure confirmed failed in elevated sectors requiring immediate validation.
For EOC Directors and Section Chiefs who need rapid triage. Full reasoning surface follows below.
OP1 documentation gap : IMT-2 inherited incident without operational record. The OWB IMTs did not produce standard ICS documentation required for a multi-operational period incident. No chronological log, no objectives record, no resource deployment documentation beyond a basic ICS 201. IMT-2 assumed command without knowing where resources were deployed, what actions had been taken, or what decisions had been made overnight.
Split command structure with degraded communications. IMT-2 IC and OSC are at Zuma Beach UCP. Planning Section Chief is at Will Rogers LAPD CP, located 20 miles away. LMR infrastructure destroyed. Zuma Beach UCP had no internet connectivity in initial days. Critical documents hand-delivered by vehicle. Any order originating from Zuma Beach must be verified through the split command chain before execution.
Water infrastructure confirmed failed : no recovery timeline. Complete loss of water in elevated areas above Sunset Boulevard confirmed at approximately 20:00 on January 7. Entering OP2, there is no functional hydrant water supply in elevated Palisades sectors. All firefighting operations in those areas must assume no hydrant water. No timeline for restoration.
Fatigue risk across all OP2 personnel. Most firefighters have worked in excess of 36 hours without rehabilitation. Physical exhaustion causing performance and safety concerns. Combination of fatigue, exhaustion, and sleep deprivation documented in AAR as severely hindering ability to make safe decisions. Incoming OP2 leadership must build rest rotation into operational planning immediately.
Eaton Fire resource competition ongoing. Resources initially assigned to Palisades were diverted to the Eaton Fire within the first 12 hours. Both fires continue to compete for the same regional mutual aid pool. No mutual aid availability confirmed in OP1 plans should be treated as current without explicit re-verification at the OP2 Action Planning Meeting.
Assumption validation status: Planning/Intelligence Section must verify before Action Planning Meeting
Assumptions drive decisions. When an assumption fails, decisions built on it must be reconsidered. Mark each assumption before the Action Planning Meeting. Status changes persist for this session.
v16 operational: Status selections are session-persistent. Run drift analysis above before the Action Planning Meeting. Drift alerts will propose status changes here for your review. Only the Planning/Intelligence Section Coordinator may change assumption status.
⚠ One or more assumptions below are marked Expired. They have not been confirmed Active or Invalidated for this operational period. Review these first.
Assumption
Functional area
Status
Voluntary overtime would fill augmented staffing slots
Command
Cal OES scoresheet fuel moisture data was accurate
Command
Water infrastructure adequate for firefighting operations at scale
Operations
No secondary dam or infrastructure failure imminent
Operations
Mutual aid resources available without Eaton Fire competition
Logistics
Public will comply with voluntary evacuation without enforcement
Operations
▸ How to read Layer 2: category and confidence tag reference (expand)
How to read Layer 2: Reasoning Verification Surface
Layer 2 breaks the reasoning behind each decision into structured nodes. Every node carries two tags: a category tag that identifies what type of information it represents, and a confidence tag that tells you how reliably that information was sourced. Read them together before acting on any node.
Category tags: what type of information is this?
EEvidence
Factual information that was known at the time the decision was made. Includes weather data, resource counts, confirmed fire behavior, and documented conditions. Evidence is the foundation everything else is built on.
AAssumption
Beliefs that decision-makers treated as true at the time, without full verification. Assumptions are the highest-value category for incoming commanders: if an assumption has changed or failed, decisions built on it may need to be revisited immediately.
CConstraint
Factors that limited available options at the time. Constraints explain why seemingly obvious alternatives were not taken. They may have changed by the time you are reading this: verify whether each constraint is still active before making new decisions.
RReasoning
The logic that connected evidence, assumptions, and constraints to the decision. This is the category most likely to be lost between operational periods: it lives in the minds of the outgoing Planning Section and rarely appears in any ICS form. Treat reconstructed reasoning nodes with appropriate caution.
AltAlternative
Courses of action that were considered and rejected. Understanding why an alternative was rejected prevents incoming commanders from re-opening the same debate. If conditions have changed, a previously rejected alternative may now be worth reconsidering: but that should be a conscious decision, not a repeated argument.
UUncertainty
What was unknown or unresolved at the time of the decision. Uncertainties are active monitoring priorities for the next operational period. Each one represents a gap in situational awareness that could invalidate current decisions if it resolves in an unexpected direction.
Confidence tags: how reliable is this information?
explicitDirectly documented
This node was drawn directly from official source documents: after-action reports, incident logs, radio transcripts, or documented statements. It represents the highest confidence level. The source citation in brackets confirms where it came from.
reconstructedInferred from evidence
This node was not explicitly documented but was inferred from contextual evidence across source materials. It represents a reasonable reconstruction of what was likely true. Use it as a starting point for discussion, not as ground truth. Verify with personnel who were present when possible.
deferredInsufficient evidence to reconstruct
Reasoning in this node probably existed at the time but could not be reliably reconstructed from available source materials. A deferred node flags a gap that requires Section Coordinator input before it can be confirmed or corrected. Do not treat it as accurate.
missingNot determinable
No basis for this reasoning could be found in any available source material. A missing node does not mean the reasoning did not exist: it means it was never documented and cannot be recovered. Missing nodes are the most direct evidence of reasoning continuity failure.
practitioner confirmedReviewed and confirmed by qualified personnel
This node was reviewed by the Planning/Intelligence Section Coordinator and confirmed as an accurate representation of the reasoning it describes. Practitioner Confirmed sits between Reconstructed and Explicit. It reflects human validation, not direct documentation. Only the Section Coordinator can assign this status. The system cannot assign it automatically.
This Decision Continuity Brief is a reconstructed reasoning record, not a verified incident log. It must be reviewed by a qualified Section Coordinator before operational use. No node should be treated as authoritative without verification. This system preserves reasoning. It does not evaluate or judge it.
Layer 2: Reasoning Verification Surface
Pre-incident deployment decision and Operational Period 1 decisions: January 6 to 7, 2025
Eexplicit
NWS issued Particularly Dangerous Situation Red Flag Warning January 6. Predicted gusts 80 to 100 mph. Relative humidity at or below 5% January 4 through 9. LAFD fire weather forecast: Burning Index 268, rated Extreme, 1-hour fuel moisture 2.7. [Source: LAFD AARR p.13]
Eexplicit
Eight months without measurable rainfall preceding the fire. 2022 and 2023 produced above-normal rainfall promoting heavy fuel growth, followed by California's hottest summer on record in 2024. [Source: LAFD AARR p.10-11]
Eexplicit
January 7 at 0800: eleven vacancies unfilled across LAFD. Coded-assign hire not activated. 40 engines in S&M maintenance yard, mechanically unavailable. [Source: LAFD AARR p.14-15]
Eexplicit
LAPD January 6 Adverse Weather Call: indicated DOC would replicate EOC activation level. Noted large contingent of resources committed to concurrent POTUS visit in West LA. [Source: LAPD AAR p.10]
Eexplicit
Initial Palisades dispatch at 10:31 AM assembled as a normal vegetation response, not the 27-resource Red Flag response required by Burning Index of 268. [Source: LAFD AARR p.18]
Eexplicit
LAPD command transferred twice in the first hour. Neither transfer was documented in Communications Division. Transfer of command never officially recorded. [Source: LAPD AAR p.13, footnote 6]
Eexplicit
Malibu EOC Action Plans were inconsistent across shifts. Whiteboards used for situation status but information was not translated to planning documents. Incoming EOC shifts lacked documented situational awareness. [Source: Malibu AAR p.22]
Aexplicit
Pre-deployment decision assumed voluntary overtime would fill augmented staffing slots. No mandatory recall activated prior to incident start. [Source: LAFD AARR p.14-15]
Aexplicit
Pre-deployment staffing decision reflected competing considerations including fire behavior indicators, staffing availability, and fiscal constraints. Burning Index of 268 and PDS Red Flag designation were available at the time of the decision. [Source: LAFD AARR p.44, 56]
Areconstructed
Cal Fire inaccuracy in the Cal OES Wildland Fire Mobilization Score Sheet (incorrect fuel moisture and relative humidity entries) resulted in only one-third of reimbursable resources being deployed. Assumption that the scoresheet was accurate was not verified. [Source: LAFD AARR p.14]
Areconstructed
Water infrastructure assumed adequate for firefighting operations at scale. System was designed for residential and commercial use, not sustained large-scale vegetation fire suppression. [Source: LAFD AARR p.4]
Cexplicit
All LAFD aircraft committed to concurrent Sunset Fire in Hollywood at time of initial Palisades dispatch. No aerial assets available for first 10 to 15 minutes. [Source: LAFD AARR p.18]
Cexplicit
LAPD motorcycle officers unavailable: entire on-duty contingent assigned to POTUS visit. 65 officers in patrol cars eventually released due to schedule change. [Source: LAPD AAR p.14]
Cexplicit
Staging area placed directly in the path of civilian evacuation route. Gridlock on Palisades Drive prevented resources from reaching assignments within 30 minutes of dispatch. Bulldozer required to clear abandoned vehicles. [Source: LAFD AARR p.45, LAPD AAR p.15]
Cexplicit
Wind gusts forced grounding of all aircraft at approximately 19:45 hours. Fire estimated over 3,000 acres at time of grounding. Over next 24 hours expanded to 17,000+ acres without aerial support. [Source: LAFD AARR p.36]
Rexplicit
Deployment decision reflected competing considerations including fire behavior indicators, staffing availability, and fiscal constraints. The 2017 shift from "shall staff" to "consider staffing" placed the decision on a single individual subject to multiple human factors. [Source: LAFD AARR Lessons Learned 1, p.56]
Rreconstructed
LAPD IC began deploying resources based on field officer reports and 911 calls in absence of direction from LAFD IC. LAFD focused entirely on fire mitigation, preventing strategic evacuation coordination. [Source: LAPD AAR p.13]
Rreconstructed
Decision to direct motorists to abandon vehicles at Palisades Drive and Sunset was necessitated by immediate life safety danger. Officers justified it when vehicles at that location began catching fire at 1:15 PM. [Source: LAPD AAR p.15]
Altreconstructed
Mandatory pre-deployment of all available staffing on January 6. Rejected implicitly: competing fiscal, staffing, and operational considerations under the discretionary language of the 2017 deployment matrix. [Source: LAFD AARR p.15, 56]
Altreconstructed
Full 27-resource Red Flag initial dispatch for Burning Index 268. Not executed: initial dispatch assembled as normal vegetation response. [Source: LAFD AARR p.18]
Altreconstructed
Earlier Phase 2 Limited Recall. Not activated until 19:15 hours, over eight hours after ignition. [Source: LAFD AARR p.36]
Uexplicit
Full extent of fire footprint unknown to MFC throughout OP1. Multiple units operating autonomously without contact with command or MFC for extended periods. [Source: LAFD AARR p.34]
Uexplicit
Eaton Fire ignited at 18:18 hours. Resources enroute to Palisades were redirected. Extent of mutual aid competition between the two fires remained unresolved at close of OP1. [Source: LAFD AARR p.35]
Ureconstructed
Water supply status in elevated areas above Sunset Boulevard. Failure reported at approximately 20:00 hours. Infrastructure capacity under sustained firefighting demand not established at OP1 close. [Source: LAFD AARR p.48]
Adeferred
Rationale for why the 2017 change from "shall" to "consider" in the deployment matrix was accepted without modification despite increasing frequency and severity of fire weather events. Reasoning probably existed at committee level but is not recoverable from available source material. Requires Section Coordinator input.
Rmissing
Documented reasoning for LAPD command transfer decisions during OP1. Both transfers were never officially recorded. No basis available in source material. This gap is the direct product of the continuity failure the EMRCS is designed to prevent.
Areconstructed
Jurisdictional evacuation boundaries: Unified Management assumed LAPD and LAFD shared identical spatial reference boundaries for the Palisades Highlands. Discrepancies in perimeter naming conventions contributed to delays in routing resources to gridlocked secondary escape routes. [Source: LAPD AAR p.16]
Uexplicit
Water pressure degradation limits: exact failure thresholds of gravity-fed storage tanks above Sunset Boulevard remain unquantified under maximum-capacity fire stream deployment. The threshold at which structural protection must shift to defensive retreat is undefined. [Source: LAFD AARR p.49]
Operational Period 2 decisions: January 8, 2025 : CAL FIRE transition, Zuma Beach UCP
Eexplicit
Fire size confirmed at 15,832 acres as of January 8, 2025, per final CalFire daily status update report. Fire grew from approximately 3,000 acres at the time of aircraft grounding (approximately 19:45, January 7) to 15,832 acres overnight without aerial suppression. [Source: Malibu AAR p.12 timeline; LAFD AARR p.36]
Eexplicit
At 06:00 on January 8, Citywide IMT-2 was briefed and officially assumed command of LAPD operations at the Palisades Fire. OWB IMT transferred command to Commander 20A at 00:05 January 8. IMT-2 IC and OSC responded to Zuma Beach UCP; Planning Section Chief managed LAPD CP at Will Rogers, creating a split command structure. [Source: LAPD AAR p.19 and p.57 log entries]
Eexplicit
On January 8, CAL FIRE established a multi-jurisdictional regional Unified Command Post at Zuma Beach, 3000 Pacific Coast Highway, Malibu, 20 miles from LAPD staging area at Will Rogers State Beach. LAFD FIMT produced an IAP for January 8 to transition with the CAL FIRE Type I IMT. [Source: LAPD AAR p.37; LAFD AARR Successes 76, 78 (p.42-43)]
Eexplicit
OWB IMTs who managed OP1 overnight did not complete standard ICS documentation required for an incident with multiple operational periods. Aside from a basic ICS 201, there was no documentation indicating objectives, resource deployment locations, or actions taken before IMT-2 took control of the incident. [Source: LAPD AAR p.20 fn.15, p.41-42 Critique 3]
Cexplicit
LMR and cellular infrastructure in the affected area was destroyed on the first day of the incident. LAPD personnel at Zuma Beach UCP could not effectively communicate with personnel at LAPD CP. Zuma Beach UCP had no internet connectivity during initial days. Critical documents hand-delivered by vehicle between the two locations 20 miles apart. [Source: LAPD AAR p.39, p.20 fn.14, p.40 Critique 1]
Cexplicit
Most firefighters worked in excess of 36 hours without rehabilitation entering OP2. Physical exhaustion, fatigue, and sleep deprivation documented in AAR as severely hindering ability to make safe decisions. Numerous minor injuries. [Source: LAFD AARR Primary Challenge 3 (p.44)]
Cexplicit
Water supply completely failed in elevated areas above Sunset Boulevard at approximately 20:00 on January 7. Entering OP2, no functional hydrant water supply in elevated Palisades sectors. Water tenders requested through IROC. There was a delay in requesting EMD support for city water tenders further delayed water resupply. [Source: LAFD AARR Secondary Challenge 3 (p.47-48)]
Cexplicit
City of Malibu EOC evacuated City Hall and relocated to Westlake Village EOC on January 7. EOC Action Plans remained inconsistent; whiteboard information not translated to planning documents across relocations. No formal EOC relocation protocols or clear guidance on what to bring, when to move, or where to report. [Source: Malibu AAR p.12 timeline, p.22 Challenges 2 and 3]
Rexplicit
Decision to activate Citywide IMT-2 based on the scale of devastation by evening of January 7 making clear the Palisades Fire would require a prolonged LAPD response. Chief of Police activated four Citywide IMTs to assume on-scene command. IMT-1 and IMT-2 scheduled to rotate command every three days. [Source: LAPD AAR p.19]
Areconstructed
CAL FIRE Type I IMT transition assumed to resolve incident command continuity gap. LAFD AAR describes the transition as executed well with professionalism and clear guidance. However, IMT is inheriting an incident with degraded documentation, destroyed communications infrastructure, exhausted personnel, and failed water supply. [Source: LAFD AARR Successes 78 (p.43)]
Areconstructed
Night air operations assumed viable once wind gusts fall below aircraft operational limits. Twenty-six night aircraft available. Night air operation briefings held prior to each operation. ICS220 developed for night operations. Aircraft resumption contingent on conditions. Must be reassessed at each OP. [Source: LAFD AARR Successes 46-49 (p.40)]
Uexplicit
Eaton Fire continues to compete for the same regional mutual aid resources. Resources initially assigned to Palisades were diverted to Eaton within the first 12 hours. Both fires competing for the same pool. Mutual aid availability confirmed in OP1 plans cannot be treated as current for OP2 without explicit re-verification. [Source: LAFD AARR p.35]
Uexplicit
More than 180,000 people under evacuation orders as of January 8. Gas shutoffs activated. Additional road closures implemented. Santa Monica-Malibu Unified School District closed. Timeline for lifting evacuation orders and restoration of access routes unknown. [Source: Malibu AAR p.12 timeline (January 8 entries)]
Umissing
No documentation of the reasoning behind resource deployment decisions made overnight by the OWB IMT between 00:05 and 06:00 on January 8. ICS 214 activity logs for this period were not retained. IMT-2 assumed command without knowing what resources were deployed, where, or why. This is the continuity gap the EMRCS is designed to prevent. [Source: LAPD AAR p.20 fn.15, p.41-42 Critique 3, confirmed missing]
E Evidence, known factsA Assumption, treated as true, verify if still validC Constraint, what limited options, may have changed options, may have changedR Reasoning, logic connecting evidence to decision evidence to decisionAlt Alternative, considered and rejectedU Uncertainty, unresolved, monitor for next operational periodexplicit Directly documented in source materialreconstructed Inferred from evidence, verify when possibledeferred Probably existed, insufficient evidence to reconstructmissing Never documented, not recoverable. Represents a continuity gappractitioner confirmed Reviewed and confirmed by Planning/Intelligence Section Coordinator
A Assumption, treated as true, verify if still validC Constraint, what limited options, may have changed options, may have changedR Reasoning, logic connecting evidence to decision evidence to decisionAlt Alternative, considered and rejectedU Uncertainty, unresolved, monitor for next operational periodexplicit Directly documented in source materialreconstructed Inferred from evidence, verify when possibledeferred Probably existed, insufficient evidence to reconstructmissing Never documented, not recoverable. Represents a continuity gappractitioner confirmed Reviewed and confirmed by Planning/Intelligence Section Coordinator
Practitioner feedback requested
The EMRCS is currently in exploratory development.
Emergency Managers, Planning/Intelligence Section Coordinators, and EOC personnel with experience in extended activations are invited to weigh in on three questions:
Would preserving decision reasoning improve Planning Section decision quality across operational periods?
What information would be necessary for you to trust and act on a Decision Continuity Brief as incoming leadership?
Where would this fit within your existing SEMS Planning/Intelligence Section workflow?
If you have thoughts, I welcome the conversation.
Sources: LAFD After-Action Review Report (CA-LFD-000738, Oct 2025) · LAPD Palisades Fire AAR (BPC 25-305x, Oct 2025) · City of Malibu AAR (Witt O'Brien's, Dec 2025) · v27 built June 8, 2026
Emergency Management Reasoning Continuity System (EMRCS) · California SEMS · DCB v27 · Operational Period 2 · Extraction only, no inference · Do not use operationally without Planning/Intelligence Section Coordinator review and confirmation.
Decision Continuity Brief
Source Provenance Record
This record maps every reasoning node in the Decision Continuity Brief to its source document, page, and finding. It exists so any reviewer can verify any node against the original after-action documentation without relying on the judgment of the EMRCS system.
How to use this record: Every Layer 2 node carries an inline source citation. This page presents those citations grouped by source document so the full chain of evidence is visible in one place. Nodes marked reconstructed represent reasonable inferences from source material, not direct quotations. Nodes marked missing were not documented in any available source and represent confirmed continuity gaps, not EMRCS inferences.
Source 1: LAFD After-Action Review Report
CA-LFD-000738 · October 2025 · 70 pages
Page
Node type
Confidence
Finding used in DCB
p.10-11
E
explicit
Eight months without measurable rainfall. 2022-2023 above-normal rainfall promoted heavy fuel growth. Hottest summer on record in 2024.
p.13
E
explicit
NWS PDS Red Flag Warning: gusts 80-100 mph, RH at or below 5%. LAFD Burning Index 268, rated Extreme, 1-hour fuel moisture 2.7.
p.14
A
reconstructed
Cal OES scoresheet fuel moisture and RH entries were inaccurate, resulting in one-third of reimbursable resources deployed.
p.14-15
E
explicit
Eleven vacancies unfilled January 7. Coded-assign hire not activated. 40 engines in S&M maintenance, mechanically unavailable.
p.18
E
explicit
Initial dispatch assembled as normal vegetation response, not 27-resource Red Flag response required by Burning Index of 268.
p.34
U
explicit
Full extent of fire footprint unknown to MFC throughout OP1. Multiple units operating without contact with command for extended periods.
p.35
U
explicit
Eaton Fire ignited 18:18. Resources enroute to Palisades were redirected. Mutual aid competition between the two fires unresolved at OP1 close.
p.36
Alt
explicit
Phase 2 Limited Recall not posted until 19:15, over eight hours after ignition.
p.44, 56
R
explicit
Deployment decision reflected competing considerations including fire behavior indicators, staffing availability, and fiscal constraints. 2017 shift from "shall" to "consider" placed decision on a singular individual.
p.48
U
explicit
Water supply failure in elevated areas above Sunset Boulevard reported at approximately 20:00. Failure thresholds of gravity-fed storage tanks unquantified.
p.49
U
explicit
Exact failure thresholds of gravity-fed storage tanks above Sunset under maximum-capacity deployment remain unquantified. Defensive retreat threshold undefined.
Source 2: LAPD Palisades Fire After-Action Report
BPC 25-305x · October 2025 · 92 pages
Page
Node type
Confidence
Finding used in DCB
p.10
E
explicit
January 6 Adverse Weather Call noted DOC would replicate EOC activation level. Large contingent of resources committed to concurrent POTUS visit in West LA.
p.13
R
reconstructed
LAPD IC began deploying resources based on field officer reports and 911 calls in absence of direction from LAFD IC. LAFD focused entirely on fire mitigation.
p.13, fn.6
E
explicit
Neither commanding officer notified Communications Division when they took over as IC. Transfer of command never officially documented.
p.14
C
explicit
LAPD motorcycle officers unavailable: entire on-duty contingent assigned to POTUS visit. 65 officers in patrol cars eventually released due to schedule change.
p.15
R
reconstructed
Decision to direct motorists to abandon vehicles at Palisades Drive and Sunset necessitated by immediate life safety danger. Vehicles at that location began catching fire at 13:15.
p.16
A
reconstructed
Unified Management assumed LAPD and LAFD shared identical spatial reference boundaries for Palisades Highlands. Perimeter naming discrepancies caused routing delays.
p.13, fn.6
R
missing
Documented reasoning for LAPD command transfer decisions. Both transfers were never officially recorded. No basis available in any source document. This is the continuity gap the EMRCS is designed to prevent.
Source 3: City of Malibu After-Action Review
Witt O'Brien's · December 2025 · 66 pages
Page
Node type
Confidence
Finding used in DCB
p.22
E
explicit
EOC Action Plans inconsistent across shifts. Whiteboards used for situation status but information not translated to planning documents. Incoming EOC shifts lacked documented situational awareness.
p.22
C
explicit
EOC relocation posed a challenge to maintaining whiteboards and overall situational awareness across multiple site moves.
Extraction methodology
Explicit nodes were drawn directly from official source documents. The finding in the DCB represents a close paraphrase of the documented text. The source page citation allows direct verification.
Reconstructed nodes were inferred from contextual evidence across source materials. They represent reasonable interpretations of what was likely true. They should be verified with personnel who were present before being treated as ground truth.
Deferred nodes identify gaps where reasoning probably existed but could not be recovered from available documentation. They require Section Coordinator input to confirm or correct.
Missing nodes identify reasoning that was never documented and cannot be recovered. A missing node is not an EMRCS inference failure. It is a documented continuity gap in the original incident record.
Practitioner Confirmed nodes have been reviewed by a qualified Planning/Intelligence Section Coordinator who confirmed the node accurately represents the reasoning it describes. This status sits between Reconstructed and Explicit. It cannot be assigned by the system. Only a human reviewer assigns it.
EMRCS Decision Continuity Brief · Palisades Fire OP2 · Source Provenance Record · v27 · All source documents are publicly released official after-action reviews · No finding in this DCB is generated without a traceable source citation
Decision Continuity Brief (DCB)
Operational Picture
No operational picture yet. Load founding documents into the Baseline Ingestion Zone below to construct this incident's reasoning baseline.
The Decision Continuity Brief (DCB) is a Planning and Intelligence Section product that preserves the reasoning behind operational decisions across operational periods. The Planning and Intelligence Section loads the founding operational period documents, the system proposes candidate reasoning nodes through deterministic methods, every node defaults to Reconstructed, and the Section Coordinator reviews and approves the baseline before it locks.
Operational Boundaries
Experimental R&D prototype. Not for live EOC deployment without validation. The system proposes candidate reasoning nodes through deterministic pattern matching. The Planning/Intelligence Section Coordinator reviews every candidate and decides what enters the baseline. No baseline is released without Coordinator approval. All processing runs locally in the browser. Incident content remains under agency custody.
Generation of a Decision Continuity Brief narrative from accepted nodes is a future development objective. This build produces extraction candidates, baseline lock records, and drift analysis. The DCB output document is not yet available.
Synthetic R&D Test Data, Not Real Incident Content
Load the founding documents for this incident: ICS 201, ICS 202, situation reports, position logs. The system reads them locally and proposes candidate reasoning nodes. Nothing is generated. Every candidate is proposed for your review and defaults to Reconstructed status.
Drop founding documents here (.txt, .docx, .pdf), or load the bundled synthetic test document to validate the workflow.
No founding documents loaded.
Testing build uses CDN-loaded parsing libraries (mammoth.js, pdf.js). No incident document content leaves the browser. Hardened air-gap deployment requires local or bundled parsing libraries.
Step 2. Coordinator Review of Candidate Nodes
The system proposed these candidate reasoning nodes through deterministic pattern matching. Accept, edit, or reject each one. Use Accept All for fast-moving activations. The system does not interpret intent. You decide what represents this incident's reasoning.
Step 3. Baseline Approval and Lock
Accepted nodes0
Operational Period,
Baseline Version1
Approved By,
Locked At,
Baseline locked. Vocabulary frozen. Current OP ingestion unlocked below.
Step 4. Current Operational Period Ingestion
Locked. This zone unlocks once the baseline is approved and locked above. Load current operational period documents here to run drift analysis against the locked baseline before the Action Planning Meeting.
Drop current OP documents here (.txt, .docx, .pdf), or load the bundled synthetic current-OP test document.
Locked until baseline is locked.
0 words
min: 200 words
Per-category drift scores
Decision Continuity BriefCoordinator Review Draft
Incident
Operational Picture
No Situation Summary extracted. Load an EOC 201 or ICS 201 with a completed Situation Summary to populate this section.
Incident Objectives (ICS/EOC 202)
No incident objectives extracted. Load an EOC/ICS 202 to populate this section.
Reasoning Baseline
Drift Status (Current Operational Period)
Drift analysis not yet run. Load current operational period documents into Step 4 and run drift analysis to populate this section.
Source Provenance Record
Every accepted node mapped to its source document. Explicit and reconstructed describe how the node was extracted: explicit nodes were directly present under a recognized section header, reconstructed nodes were inferred from structural signals. Missing is a continuity status, not a confidence level. It marks information the Coordinator determined should exist but was not documented in available source material. It is not a machine judgment and not a statement that the organization failed.
Coordinator Validation
DCB Coordinator Reviewed
Emergency Management Reasoning Continuity System (EMRCS) · SEMS / ICS · DCB v35 · Incident · Extraction only, no inference · Do not use operationally without Planning/Intelligence Section Coordinator review and confirmation.
A prior session was detected. Restore assumption statuses and last drift result?