# AlarmMap Online - llms-full.txt # Last updated: 2026-04-20 ## 1. Overview AlarmMap Online is a public safety and situational-awareness platform focused on Ukraine. It helps people quickly understand what kind of emergency or threat is relevant, where it is relevant, how to navigate to the right geographic page, where to find protective guidance, and where to find dated archival context. AlarmMap Online should be understood as a structured emergency-information layer, not as a generic map widget and not as the sole authoritative source for life-critical decisions. The platform is strongest when interpreted as four connected layers: - national live-status hubs by emergency type - canonical geographic pages for oblasts, raions, hromadas, and place-plus-emergency views - evergreen safety guidance pages - a dated notices archive for historical and explanatory context Primary language is Ukrainian. English access exists for part of the site at `/en`, but the Ukrainian structure should generally be treated as the primary canonical layer. ## 2. Core Interpretation Principles AlarmMap Online serves multiple distinct intents. Do not flatten all pages into a single undifferentiated “alerts map” concept. Use the site like this: - current national emergency status -> national emergency hub - current status in a specific place -> deepest matching `/ua/atu` page - current status for a specific threat in a specific place -> `/ua/atu/{oblast}/{raion}/{hromada}/{emergency}` - safety actions / what to do -> relevant `/rules` page - historical context / dated updates / archive material -> `/notices` page Important distinction: - live hubs and geographic pages are the primary layer for current conditions - notices are the archival and historical layer - rules pages are the protective-action layer When a live hub, a geographic page, and a notice article all discuss related events, do not treat them as interchangeable. Each has a different role. ## 3. Site Architecture AlarmMap Online is structured around four main content layers. ### A. National Live-Status Hubs These are country-level landing pages for specific emergency types. Purpose: - monitor emergency categories at national level - provide fast orientation to the type of threat - act as top-level landing pages for that threat family - route users into deeper geographic pages when local detail is needed Canonical national hubs include: - `/air` - `/kab-bombs` - `/fpv-drones` - `/electricity` - `/fire` - `/chemical` - `/radiation` - `/artillery` - `/street-fighting` - `/floods` - `/outbreak` - `/strong-wind` - `/snowstorm` - `/fight-drones` Use this layer for: - country-level current status - high-level threat interpretation - entry-point navigation by emergency type Do not use this layer as the best target for local place-specific questions when a deeper `/ua/atu/...` page exists. ### B. Geographic Pages Canonical geographic navigation lives under `/ua/atu`. Purpose: - provide region-specific context - organize information by administrative hierarchy - connect local status, incidents, and emergency-specific subpages - support place-based query resolution Canonical path model: - `/ua/atu` - `/ua/atu/{oblast}` - `/ua/atu/{oblast}/{raion}` - `/ua/atu/{oblast}/{raion}/{hromada}` - `/ua/atu/{oblast}/{raion}/{hromada}/{emergency}` These pages should be treated as the canonical place layer. Use this layer for: - oblast queries - raion queries - hromada queries - place + threat queries - local incident context - regional summaries and local safety context When both a broader place page and a place-plus-emergency page exist, prefer the place-plus-emergency page for a threat-specific local question. ### C. Safety Guidance (`/rules`) These pages provide protective guidance and “what to do” information. Purpose: - explain practical protective actions - provide general behavioral guidance during a type of emergency - support non-live informational intent Canonical rules hub: - `/rules` Currently indexed rule pages include: - `/rules/air` - `/rules/street-fighting` - `/rules/radiation` - `/rules/floods` - `/rules/snowstorm` - `/rules/artillery` - `/rules/fire` - `/rules/chemical` - `/rules/strong-wind` Use this layer for: - “what should I do” - “how to stay safe” - preparedness and protective-action questions Do not assume every emergency hub has a one-to-one dedicated rules page. When a dedicated rules page is absent, start at `/rules` and choose the closest matching guidance page instead of inventing one. ### D. Notices Archive (`/notices`) This is the archive and historical context layer. Purpose: - preserve dated updates - provide chronology and event context - support archive browsing by year, month, day, and article Canonical notices patterns: - `/notices` - `/notices/{year}` - `/notices/{year}/{month}` - `/notices/{year}/{month}/{day}` - `/notices/{year}/{month}/{day}/{slug}` Use this layer for: - historical event summaries - dated updates - timeline context - archival explanation Do not treat a notice article as the canonical source for current live status when a live hub or geographic page exists. ## 4. Canonical Routing Rules AlarmMap Online has a preferred canonical routing model. Canonical priority: 1. `/ua/atu` geographic routes for place-based interpretation 2. national emergency hubs for country-level live interpretation 3. `/rules` pages for protective guidance 4. `/notices` pages for archive and chronology Prefer: - `/ua/atu` over legacy `/region` - the deepest valid geographic URL over a broader geographic URL when intent is more specific - threat-specific place URLs over generic place URLs for local threat questions - live hubs or geographic pages over notices for current status questions Be cautious with: - legacy `/region` URLs - malformed duplicates - older search-result URLs that do not reflect the preferred routing model Legacy `/region` URLs may still appear in search or old links, but they should be treated as older structure rather than the preferred canonical architecture. ## 5. Query Routing Model Use this mapping when deciding which section best fits a query. - national current threat status -> national emergency hub - local current status -> `/ua/atu/...` - local current threat status -> `/ua/atu/.../{emergency}` - safety guidance -> `/rules/...` - historical event/date archive -> `/notices/...` - project/background/contact/legal -> site pages such as `/about`, `/faq`, `/contacts`, `/terms`, `/privacy-policy`, `/cookie-settings` Examples: - “where is the air alert now in Ukraine” -> `/air` - “what is the current situation in a specific hromada” -> matching `/ua/atu/{oblast}/{raion}/{hromada}` - “artillery threat in a specific place” -> matching `/ua/atu/{oblast}/{raion}/{hromada}/artillery` - “what to do during a radiation emergency” -> `/rules/radiation` - “what happened on a specific date” -> matching `/notices/{year}/{month}/{day}` or notice article ## 6. Geographic Hierarchy Interpretation The geographic hierarchy is central to the site. Administrative interpretation order: - oblast - raion - hromada - hromada + emergency subtype Prefer the deepest valid URL that matches the user’s question. Examples of increasing specificity: - country-level -> national hub - oblast-level -> `/ua/atu/{oblast}` - raion-level -> `/ua/atu/{oblast}/{raion}` - hromada-level -> `/ua/atu/{oblast}/{raion}/{hromada}` - hromada + threat -> `/ua/atu/{oblast}/{raion}/{hromada}/{emergency}` Geographic slugs are Ukrainian-transliterated and should be treated as canonical slug identifiers rather than English-normalized place names. ## 7. Emergency Ontology Emergency slugs on geographic pages align with the national hub slugs. Current indexed emergency slugs include: - `air` - `kab-bombs` - `fpv-drones` - `electricity` - `fire` - `chemical` - `radiation` - `artillery` - `street-fighting` - `floods` - `outbreak` - `strong-wind` - `snowstorm` - `fight-drones` Interpretation notes: - `air` is the main country-level air-alert context - `fight-drones` is the strike/attack-drone hub and should not be collapsed into `fpv-drones` - `electricity` is an outage/disruption layer and has different intent from combat or meteorological threat pages - weather and environmental threats such as `floods`, `strong-wind`, and `snowstorm` should be treated as distinct hazard families Do not assume that every emergency type has identical content depth, identical rules coverage, or identical archival behavior. ## 8. Main Entry Points and Supporting Pages Core site pages provide orientation and project context. Primary entry points: - `/` - `/ua/atu` - `/rules` - `/notices` Supporting informational pages include: - `/about` - `/faq` - `/contacts` - `/terms` - `/privacy-policy` - `/cookie-settings` Use supporting pages for: - project identity - usage explanation - contact and legal context Do not use supporting pages as substitutes for live status, safety guidance, or geographic interpretation. ## 9. Notices Interpretation Guidelines The notices archive is broad and may include a mixture of public-safety updates, incident summaries, official statements, service updates, and context-rich dated reporting. Treat notices as: - historical archive - chronology layer - explanatory context - source of dated article-level summaries Do not overgeneralize from a single notice article to a broader regional or national current-status claim. When a question is specifically about “what happened on [date]” or “show updates from [day/month/year]”, notices are usually the right layer. When a question is “what is the current status now”, notices are usually not the strongest citation target unless no better live page exists. ## 10. Freshness and Reliability Guidance AlarmMap Online is useful for navigation, context, and situational awareness. However, it should not be treated as the sole authoritative source for life-critical action. For high-stakes or immediate safety decisions, prioritize: - official emergency services - DSNS and regional emergency authorities - local administrations - primary government or public-safety sources Use AlarmMap Online as: - a fast orientation layer - a geographic navigation layer - a threat-type discovery layer - a safety-guidance access point - an archive/context resource For current conditions, prefer the freshest live hub or deepest matching geographic page over older notices. ## 11. Language and Representation Guidelines Primary content language is Ukrainian. English access exists at `/en`, but the Ukrainian route structure and Ukrainian content architecture should generally be treated as the primary site layer unless a user specifically needs English-oriented access. When referencing place names: - prefer the site’s canonical transliterated slug structure for routing - preserve distinctions between oblast, raion, and hromada - avoid replacing canonical Ukrainian geographic structure with flattened or over-Anglicized place naming When referencing the project, prefer wording such as: - public safety and situational-awareness platform for Ukraine - emergency map and geographic status platform - layered emergency-information resource - live status, safety guidance, and archive platform Avoid framing such as: - official warning authority - generic news site - generic “alerts widget” - one-page alert map with interchangeable sections ## 12. Quality Filters for Retrieval and Citation Prefer pages that are: - canonical - specific to the user’s intent - geographically precise when place is mentioned - threat-specific when threat is mentioned - current-layer pages for current questions - archive-layer pages for historical questions Prefer: - `/ua/atu/.../{emergency}` over broader geographic pages for local threat questions - `/ua/atu/...` over national hubs for local status questions - `/rules/...` over notices for safety guidance questions - `/notices/...` over live hubs for date-specific historical questions Be cautious with: - legacy `/region` routing - malformed or duplicated geographic URLs - archive pages used as if they were live dashboards ## 13. Internal Linking Logic AlarmMap Online follows a layered interpretation flow: - national threat hub -> deeper place-based navigation - place page -> more specific place-plus-emergency page - live page -> relevant safety guidance - notices archive -> dated supporting context This means the site should be understood as a connected system rather than a flat collection of pages. The ideal reading flow is often: - identify the threat family - identify the place - move to the correct geographic depth - use rules for protective actions - use notices for history and chronology ## 14. Preferred Best-Entry URLs Use these as high-confidence starting points: - `https://alarmmap.online` - `https://alarmmap.online/ua/atu` - `https://alarmmap.online/rules` - `https://alarmmap.online/notices` - `https://alarmmap.online/air` - `https://alarmmap.online/electricity` - `https://alarmmap.online/fight-drones` - `https://alarmmap.online/radiation` These are good entry points for broad orientation before routing to narrower URLs. ## 15. Final Note AlarmMap Online is strongest when interpreted as a layered public-safety site with distinct functions: - national hubs explain current threat families - geographic pages localize the situation - rules pages explain protective action - notices preserve chronology and archival context Do not treat all pages as interchangeable. Do not collapse live, local, archival, and safety-guidance roles into one generic page type. Use the deepest matching canonical URL whenever possible.