panic-alert is an early-detection and panic-alert system for a fire fighting system. Its purpose is to detect fire conditions early — before they become fire incidents — and to raise panic alerts so that the people responsible for the site can acknowledge, confirm, escalate, and resolve them in time to prevent the fire from spreading.
The product is a life-safety instrument, not an administrative dashboard. It monitors the fire fighting system for early fire-detection signals, surfaces the current fire-condition status of every monitored zone, and turns any threshold breach into an unmissable panic alert that must be acknowledged and closed out.
The audience is the fire-safety crew of a monitored industrial site:
Anonymous visitors may read what the system is and what it does on the public entry surface, but all monitoring, alert handling, review, and configuration work happens behind verified identity.
panic-alert continuously monitors the fire fighting system for early fire-detection signals. When a monitored condition crosses its configured threshold, the system raises a panic alert, records the detection event, and presents the alert to the Fire Safety Operator as an unacknowledged alarm that must be triaged. The operator confirms the affected zone or asset, escalates or dispatches a response, and marks the alert resolved once it is handled. The Fire Safety Supervisor reviews the resulting alert history and detection events, verifies that alerts were acknowledged and resolved, and adjusts detection thresholds and monitored zones so coverage stays effective.
Current delivery is a first-party web application with a public entry surface, verified identity for protected work, and a set of operational and administrative destinations. Detection monitoring runs as background automation against the fire fighting system; the human-facing work of seeing, triaging, responding to, closing, reviewing, and configuring detection is delivered as custom application pages.
Actors
Narrow exclusions
Delivery ownership. The product is delivered as a first-party web application. The public entry surface is anonymously reachable and introduces the system's fire early-detection and panic-alert purpose. All protected work — live monitoring, active alert handling, alert detail, response, closure, history review, and detection configuration — is owned by the application and requires verified identity. The fire fighting system and its sensors remain external: they supply detection signals, and the application owns the evaluation, alerting, and human-facing handling of those signals.
Identity boundary. Identity is application-owned. Fire Safety Operators and Fire Safety Supervisors are invited or provisioned before they can use protected functions, and returning users verify themselves through Login. The Login surface is itself anonymously reachable — it is the interaction that establishes access to the protected destinations, so it cannot sit behind them. Identity continuity exists so that alert acknowledgement, response, resolution, and configuration remain bound to the correct participant and can be resumed across shifts.
Current vs. future. Everything described in this document is current. No future-horizon capabilities are accepted at this time.
Not applicable — no reference directive in this project declares content_source authority.
DETECT THE FIRE / BEFORE THE FLAME — at 96px with the second line indented 96px and the word BEFORE in amber #FF7A1A. Beneath it, a live-looking instrument strip of three circular gauges (SMOKE, HEAT RISE, CO) with champagne needles and a ruled row of live values in tabular numerals. Right five columns carry a macro photograph of a sprinkler head or smoke detector on black, cropped edge-to-edge, crossed by a thin amber rule with the uppercase caption ZONE 04 — SUBLEVEL 2. Bottom edge carries a full-width 1px champagne hairline with a scrolling event ticker of simulated detection pings.#C8A96A at 12% opacity behind the hero.cubic-bezier(0.22, 1, 0.36, 1) and numerals count up digit-by-digit. Error — if the illustrative strip cannot animate, it renders at final values with no motion. Recovery — reduced-motion preference renders the composed final frame with no sweep, no count-up, and no ticker scroll.#C8A96A at 12% opacity sits behind the zones map, with each monitored zone rendered as a small circular bezel that fills amber as its risk score rises.cubic-bezier(0.22, 1, 0.36, 1) and numerals count up digit-by-digit to the new value. Error — a sensor feed that stops reporting is shown as a stale row with its last timestamp rather than a blank. Recovery — when the feed resumes, the gauge sweeps to the current value and the row timestamp updates.#FF7A1A bezel pulses twice, a 1px amber scan line travels the panel edge once every 3s while unacknowledged, and the page background lifts from #0D0F12 to #14100B.#0D0F12. Success — acknowledgement is a hard 120ms state snap with no easing; the alert leaves the unacknowledged set and the count badge decrements. Error — if acknowledgement cannot be recorded, the alert remains unacknowledged with its amber treatment intact and an inline failure message appears. Recovery — the operator retries acknowledgement; the alert stays visible and unacknowledged until it succeeds.FR-1 — Early fire detection and panic alerting As a Fire Safety Operator, I should be alerted early when fire conditions emerge in a monitored zone, so that the fire is prevented from spreading.
FR-2 — Monitoring the fire fighting system for early detection signals As a Fire Safety Operator, I should see live detection inputs and current fire-condition status for every monitored zone, so that I can judge the site's state at a glance.
FR-3 — Acknowledging an active panic alert As a Fire Safety Operator, I should acknowledge an incoming panic alert, so that the team knows it has been seen and triage has begun.
FR-4 — Confirming the affected zone or asset As a Fire Safety Operator, I should confirm the affected zone or asset for an active alert, so that the response goes to the right place.
FR-5 — Escalating or dispatching a response As a Fire Safety Operator, I should escalate or dispatch a response to an active alert, so that the fire is prevented from spreading.
FR-6 — Marking a handled alert as resolved As a Fire Safety Operator, I should mark a handled alert as resolved, so that the active set reflects only what still needs attention.
FR-7 — Reviewing past panic alerts and detection events As a Fire Safety Supervisor, I should review past panic alerts and detection events, so that I can verify alerts were acknowledged and resolved.
FR-8 — Configuring early-detection thresholds and monitored zones As a Fire Safety Supervisor, I should configure early-detection thresholds and monitored zones, so that early detection stays reliable.
FR-9 — First-use identity establishment As a Fire Safety Operator or Fire Safety Supervisor, I should be invited or provisioned before using protected functions, so that alert handling and configuration stay bound to the correct participant.
FR-10 — Returning identity verification As a Fire Safety Operator or Fire Safety Supervisor, I should verify my identity through Login, so that I can resume protected monitoring, alert handling, history, or configuration.
FR-11 — Persisting detection events, alerts, responses, resolutions, thresholds, and zones As a Fire Safety Operator or Fire Safety Supervisor, I should have detection events, panic alerts, response actions, resolutions, thresholds, and monitored zones persisted, so that I can review and continue work across shifts.
Product context. The Operator works the monitoring position on long shifts, including nights, watching live sensor and detection telemetry from the fire fighting system. Their screen is a control-room instrument: a dense board of gauges and ruled data rows that must be readable at a glance across a room. They are the first person to see an early-detection alert when fire conditions emerge.
Primary goal. Every early-detection signal is seen, triaged, and acted on before it becomes a fire incident.
Distinct accepted responsibilities. The Operator monitors live detection inputs and current fire-condition status across all monitored zones; acknowledges incoming panic alerts; confirms the affected zone or asset; escalates or dispatches a response; and marks a handled alert as resolved. Their work is continuous and reactive — the value they add is speed and correct triage under an alarm, not analysis after the fact.
Relevant inputs and decisions. They read smoke density, temperature rise rate, CO ppm, sprinkler line pressure, suppression tank, and evacuation route status per zone, each with a unit and a timestamp. Their decisions are: is this alert real and which zone is it in; does it need escalation or dispatch; and is it now handled well enough to close.
Interactions with other accepted participants. The Operator is the counterparty to the Supervisor's review: the acknowledgement, response, and resolution the Operator records are exactly what the Supervisor later audits. The Operator does not configure thresholds or zones — that is the Supervisor's responsibility — so the Operator works within the detection coverage the Supervisor has set.
Observable success. Every alert the Operator saw carries an acknowledgement, a recorded response action, and a resolution with timestamps, and no early-detection signal was left unhandled.
Product context. The Supervisor owns the fire-prevention outcome across the monitored site. They do not sit the monitoring position continuously; they come to the system to audit how alerts were handled and to keep detection
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!