Decisions and audit

Synthetic: modeled for the demo, not response guidance

Choose a plan, review what it changes against the current state, then approve it with your name and a rationale. Every value and record here is modeled for the demo, not response guidance.

1. Choose a plan

Seeded scenarios, drafts approved earlier, and any draft carried over from Scenarios. Reviewing never changes anything.

2. Review: B: Split NORTE and HENDERSON

What this plan would change, compared with the current state. Nothing is applied yet.

What changes

5 of 5 teams change

Engine Strike Team 1from Wildfire HENDERSON to Wildfire NORTE
Engine Strike Team 2from Unassigned to Wildfire HENDERSON
Hand Crew 7from Unassigned to Wildfire NORTE
Dozer Group 2from Unassigned to Wildfire HENDERSON
Helicopter 41from Unassigned to Wildfire NORTE

Team assignments: current versus plan
Team	Current incidentSynthetic	Planned incidentSynthetic	Change
Engine Strike Team 1	Wildfire HENDERSON	Wildfire NORTE	Changed
Engine Strike Team 2	Unassigned	Wildfire HENDERSON	Changed
Hand Crew 7	Unassigned	Wildfire NORTE	Changed
Dozer Group 2	Unassigned	Wildfire HENDERSON	Changed
Helicopter 41	Unassigned	Wildfire NORTE	Changed

Decision engine: current state versus plan

The plan is ahead by 0.3135: stronger on protection, unmet demand, equity and response time; the current state is not stronger on any factor.

Current state total: 0.2462 = 0.0718 Modeled residential protection + 0.0000 Community equity (worst-served) + 0.1208 Response time + 0.0536 Unmet demand
The plan total: 0.5597 = 0.2324 Modeled residential protection + 0.0704 Community equity (worst-served) + 0.1319 Response time + 0.1250 Unmet demand

Factor weights (fixed, sum to 1)

Modeled residential protection: 0.40
Community equity (worst-served): 0.20
Response time: 0.15
Unmet demand: 0.25

Contribution of each factor for Current (solid) and Plan (striped). Each track is as long as the factor's weight, the most it can add; the fill is what the allocation earns. Values are listed in the engine factor table.

Engine factor table

Same values as the bars. Contribution = weight x normalized; delta is plan minus current. Read the factors, not just the total.

Decision engine: current state versus plan
Factor	Weight	Current rawSynthetic	Current normalizedSynthetic	Current contributionSynthetic	Plan rawSynthetic	Plan normalizedSynthetic	Plan contributionSynthetic	Delta (Plan minus Current)Synthetic	Favors
Modeled residential protection	0.40	11,015.3 weighted residents protected	0.1795	0.0718	35,652.7 weighted residents protected	0.5811	0.2324	+0.1606	Favors the plan
Community equity (worst-served)	0.20	0 worst-served community's met ratio	0.0000	0.0000	0.352 worst-served community's met ratio	0.3519	0.0704	+0.0704	Favors the plan
Response time	0.15	47.5 minutes (mean)	0.8055	0.1208	40.9 minutes (mean)	0.8793	0.1319	+0.0111	Favors the plan
Unmet demand	0.25	55 personnel unmet	0.2143	0.0536	35 personnel unmet	0.5000	0.1250	+0.0714	Favors the plan
Total	1.00			0.2462			0.5597	+0.3135	Favors the plan

3. Approve

Read this before you approve.

Approving applies B: Split NORTE and HENDERSON to the demo state (5 of 5 team assignments change) and writes one audit record with your name, your rationale, the time, and the assignments before and after.
Nothing executes automatically: no team is dispatched and no message is sent. Only this demo's in-memory state changes.
This is a portfolio demo with modeled values, not response guidance.Synthetic

Current team assignments

The demo state as it is now, after any approvals.

Current team assignments
Team	Type	CapacitySynthetic	Assigned incidentSynthetic
Engine Strike Team 1	engine	15	Wildfire HENDERSON
Engine Strike Team 2	engine	15	Unassigned
Hand Crew 7	hand-crew	20	Unassigned
Dozer Group 2	dozer	4	Unassigned
Helicopter 41	helicopter	6	Unassigned

Audit history

0 records

Every write to the demo state, newest first: plan approvals, direct team assignments, incident acceptances, simulated incidents and demo resets are all recorded.

No audit records yet. Nothing has been approved, assigned, accepted or simulated since the seed.

Reset the demo

Destructive: permanently erases every approval and audit record in this demo session and restores the seed assignments. The reset itself is recorded with your name. Use it between demo runs.