System Requirements Document for crystal-blackhawk

1. Introduction

crystal-blackhawk is the official website for the Blackhawk Rescue Mission 5 showcase by Platinum 5. Its product intent is singular and comprehensive: to be the official destination that covers everything about the Blackhawk Rescue Mission 5 showcase — the aircraft, loadouts, tactics, media, and updates — presented as one authoritative, complete source of information.

The audience is the Blackhawk Rescue Mission 5 player and community base: fans and players who want authoritative, complete information about the showcase, and dedicated community members who return to keep current with official material. The site is a fan-facing official showcase, not a game marketing splash; it reads as an official technical dossier with the gravity of a precision instrument.

2. System Overview

crystal-blackhawk is a public, anonymous-access website. It delivers the official Blackhawk Rescue Mission 5 showcase by Platinum 5 across two first-party pages:

• Landing — the anonymous official entry point that explains what the Blackhawk Rescue Mission 5 showcase by Platinum 5 is and directs visitors into its content.
• Showcase — the primary browse destination holding the official showcase content: the helicopter, loadouts, tactics, media, and updates.

Both pages are owned by the application and require no account or sign-in. There is no application-owned identity, no authentication, and no differentiated permissions: every visitor sees the same official content. The site is read-only from the visitor's perspective — visitors browse, read, and consume the showcase; they do not create, edit, or submit content.

Actors. The accepted active-human catalog is exactly two personas: Site Visitor and Community Member. No systems, providers, or external services act as product participants in the current scope.

Narrow exclusions. The current scope is the official showcase website only. No account creation, sign-in, profiles, comments, forums, user-generated content, commerce, or transactional capability is part of the product. No future-horizon requirements are currently accepted.

2a. Product Interpretation and Delivery Boundary

The authoritative requirement is to build an official site about everything concerning the Blackhawk Rescue Mission 5 showcase by Platinum 5. That intent is delivered as a first-party, publicly reachable website with no access barrier: a visitor arrives anonymously, learns what the showcase is on the Landing page, and moves into the Showcase page to browse the full official content — the helicopter, loadouts, tactics, media, and updates.

Delivery and access ownership are entirely first-party and anonymous. Because no accepted journey requires a visitor to privately own, resume, or return to durable personal state, and because no commitment, entitlement, or value transfer must be bound to a specific participant, no application-owned identity is introduced. The Landing page is the anonymous entry boundary; the Showcase page is the anonymous browse destination. Both are openly reachable.

The current/future boundary is deliberately narrow: everything accepted is current. Nothing in the authoritative thread establishes a future horizon, so no future section is populated with speculative capability. The site's completeness obligation is about breadth of official showcase content, not about adding adjacent product modules.

2b. Source Content Inventory

No reference directive in the authoritative sources declares a content_source, so no source content inventory is included. All showcase content described in this document is derived from the accepted requirement to cover everything about the Blackhawk Rescue Mission 5 showcase by Platinum 5; no external factual entities, collections, contacts, or media references were supplied for verbatim preservation.

2c. Page Content and Component Coverage

Landing

• Information and state. The Landing page is the anonymous official entry point. It states what the Blackhawk Rescue Mission 5 showcase by Platinum 5 is, establishes that this is the official destination, and orients the visitor toward the showcase content. It carries the oversized condensed wordmark and the ruled instrument data strip as its defining information band.
• Primary action. Enter the showcase — the primary amber CTA that moves the visitor from the Landing page into the Showcase page.
• Supporting actions. Scan the hero data strip (label/value pairs: PLATINUM 5 / SHOWCASE / BRM5 / OFFICIAL); read the introductory statement of what the showcase is; follow the section index toward the showcase content areas.
• Domain entities. Showcase identity (Blackhawk Rescue Mission 5, Platinum 5, official status); showcase content areas (aircraft, loadouts, tactics, media, updates) as referenced entry points.
• Component responsibilities.
  • Hero composition — full-bleed dark titanium ground, oversized condensed uppercase headline, helicopter silhouette or macro detail right-of-center with warm rim light, faint topographic line pattern.
  • Ruled instrument data strip — four label/value pairs separated by 1px teal rules, with the primary amber CTA cut into the strip.
  • Section index rail — uppercase condensed section labels (AIRCRAFT, LOADOUTS, TACTICS, MEDIA, UPDATES), fixed on desktop and horizontally scrollable on mobile, active section marked by an amber tick.
  • Introductory statement block — concise official description of the showcase.
• States.
  • Loading — hero media and imagery resolve progressively; text and data strip render immediately so the page is readable before media completes.
  • Empty — not applicable; the Landing page always carries its official identity content.
  • Success — visitor understands what the showcase is and can enter the Showcase page.
  • Error — if hero media fails to load, the dark ground, headline, data strip, and CTA remain fully functional and readable.
  • Recovery — media failure degrades to the typographic hero without blocking entry to the showcase.

Showcase

• Information and state. The Showcase page is the primary browse destination for the official Blackhawk Rescue Mission 5 showcase content. It presents the helicopter, loadouts, tactics, media, and updates as ordered, dense, instrument-style sections. Each section is a labeled content area with its own opener and its own ruled presentation.
• Primary action. Browse the official showcase content — read aircraft specifications, review loadouts, study tactics, view media, and read updates.
• Supporting actions. Navigate between showcase sections via the section index rail; read spec tables row by row; view media panels; read update entries; return to the Landing page.
• Domain entities. Aircraft (the Blackhawk — specifications, dimensions, performance, crew capacity); loadouts (weapons and equipment configurations); tactics (diagrammatic tactical material); media (renders, photography, imagery of the aircraft and gear); updates (official showcase update entries).
• Component responsibilities.
  • Section index rail — persistent uppercase condensed section labels (AIRCRAFT, LOADOUTS, TACTICS, MEDIA, UPDATES), fixed on desktop, horizontally scrollable index on mobile, active section marked by an amber tick.
  • Circular gauge section openers — thin teal arc with an amber needle that sweeps once on scroll to reveal the section number and title, then holds still.
  • Spec tables — first-class ruled label/value rows with tabular numerals, 1px dividers, and teal active-row highlight, used for aircraft, weapons, and loadouts.
  • Counting numeral stats — key figures (rotor diameter, range, crew capacity) set in Barlow Condensed at display size with tabular figures, ticking up once when scrolled into view.
  • Media panels — wide dark-ground media blocks with macro product-style renders and photography of the Blackhawk and gear.
  • Diagrammatic line art — tactical and loadout callout diagrams.
  • Update entries — official showcase update content in ruled, ordered presentation.
• States.
  • Loading — sections render their structure and text first; media panels and imagery resolve progressively; counting numerals hold at their final value until scrolled into view.
  • Empty — if a showcase content area has no current entries, that section presents its labeled opener and an honest empty state rather than fabricated content.
  • Success — visitor has browsed the full official showcase content across all sections.
  • Error — if a media panel fails to load, its caption, label, and surrounding spec content remain intact and readable.
  • Recovery — failed media degrades to its labeled placeholder within the ruled layout; navigation and all text content remain fully usable.

3. Functional Requirements

FR-1 — Official showcase website As a Site Visitor, I should reach an official website that covers everything about the Blackhawk Rescue Mission 5 showcase by Platinum 5, so that I have one authoritative destination for the full showcase.

• Provenance: explicit
• Trigger/input: Visitor navigates to the official site.
• Observable result: The official site loads and presents the Blackhawk Rescue Mission 5 showcase by Platinum 5 as its subject.
• Access state: Anonymous; no account required.
• Failure/recovery: If media assets fail, the site's text, structure, and navigation remain fully functional.
• Continuation: Visitor proceeds to the Landing content and into the Showcase.

FR-2 — Official destination identity As a Site Visitor, I should be able to tell that this site is the official destination for the Blackhawk Rescue Mission 5 showcase content, so that I trust the information as authoritative.

• Provenance: explicit
• Trigger/input: Visitor views the Landing page.
• Observable result: The site states its official status for the Blackhawk Rescue Mission 5 showcase by Platinum 5, carried in the hero data strip (PLATINUM 5 / SHOWCASE / BRM5 / OFFICIAL) and the introductory statement.
• Access state: Anonymous.
• Failure/recovery: Identity content is typographic and remains readable even if imagery fails.
• Continuation: Visitor enters the Showcase.

FR-3 — Understand what the showcase is As a Site Visitor, I should understand what the Blackhawk Rescue Mission 5 showcase by Platinum 5 is from the Landing page, so that I know what I am about to explore.

• Provenance: required_inference
• Trigger/input: Visitor reads the Landing page introductory statement.
• Observable result: Visitor has a clear statement of the showcase's subject and scope.
• Access state: Anonymous.
• Failure/recovery: The statement is text-first and unaffected by media failure.
• Continuation: Visitor uses the primary CTA to enter the Showcase.

FR-4 — Enter the showcase As a Site Visitor, I should move from the Landing page into the showcase content with a single clear action, so that I reach the material without friction.

• Provenance: required_inference
• Trigger/input: Visitor activates the primary amber CTA cut into the hero data strip.
• Observable result: The Showcase page opens.
• Access state: Anonymous; no barrier between Landing and Showcase.
• Failure/recovery: If the CTA target fails to load, the visitor can retry or use the section index rail.
• Continuation: Visitor browses the showcase sections.

FR-5 — Browse the aircraft As a Site Visitor, I should browse the official Blackhawk aircraft content, so that I can review the helicopter's specifications and details.

• Provenance: required_inference
• Trigger/input: Visitor opens the AIRCRAFT section of the Showcase.
• Observable result: Aircraft content is presented in ruled spec tables with tabular numerals and key stats (rotor diameter, range, crew capacity) set as counting numerals.
• Access state: Anonymous.
• Failure/recovery: If aircraft media fails, the spec tables and labels remain fully readable.
• Continuation: Visitor moves to another showcase section.

FR-6 — Browse the loadouts As a Site Visitor, I should browse the official loadout content, so that I can review the weapons and equipment configurations.

• Provenance: required_inference
• Trigger/input: Visitor opens the LOADOUTS section of the Showcase.
• Observable result: Loadouts are presented as ruled label/value rows with teal active-row highlight and diagrammatic callouts.
• Access state: Anonymous.
• Failure/recovery: If loadout imagery fails, the ruled rows and labels remain intact.
• Continuation: Visitor moves to another showcase section.

FR-7 — Study the tactics As a Site Visitor, I should study the official tactics content, so that I can understand the tactical material presented in the showcase.

• Provenance: required_inference
• Trigger/input: Visitor opens the TACTICS section of the Showcase.
• Observable result: Tactical material is presented with diagrammatic line art and ordered, labeled content.
• Access state: Anonymous.
• Failure/recovery: If diagram assets fail, the section's labels and text remain readable.
• Continuation: Visitor moves to another showcase section.

FR-8 — View the media As a Site Visitor, I should view the official media content, so that I can see the showcase's renders and photography.

• Provenance: required_inference
• Trigger/input: Visitor opens the MEDIA section of the Showcase.
• Observable result: Media panels present macro product-style renders and photography of the Blackhawk and gear on dark grounds.
• Access state: Anonymous.
• Failure/recovery: A failed media panel degrades to its labeled placeholder within the ruled layout.
• Continuation: Visitor moves to another showcase section.

FR-9 — Read the updates As a Community Member, I should read the official updates, so that I stay current with the latest showcase information.

• Provenance: required_inference
• Trigger/input: Community Member opens the UPDATES section of the Showcase.
• Observable result: Official update entries are presented in ruled, ordered form.
• Access state: Anonymous.
• Failure/recovery: If an update's media fails, its text entry remains readable.
• Continuation: Community Member returns to the site later for further updates.

FR-10 — Navigate the showcase sections As a Site Visitor, I should navigate between the showcase sections from a persistent index, so that I can move directly to the content I want.

• Provenance: required_inference
• Trigger/input: Visitor selects a section label in the section index rail (AIRCRAFT, LOADOUTS, TACTICS, MEDIA, UPDATES).
• Observable result: The selected section becomes active, marked by an amber tick, and its content is brought into view.
• Access state: Anonymous.
• Failure/recovery: On narrow viewports the rail becomes a horizontally scrollable index; all labels remain reachable by scrolling.
• Continuation: Visitor continues browsing or returns to the Landing page.

FR-11 — Return to the Landing page As a Site Visitor, I should return to the Landing page from the Showcase, so that I can re-orient or re-enter the showcase.

• Provenance: required_inference
• Trigger/input: Visitor activates the return navigation from the Showcase.
• Observable result: The Landing page is displayed.
• Access state: Anonymous.
• Failure/recovery: Navigation remains available regardless of media load state.
• Continuation: Visitor re-enters the Showcase or leaves the site.

FR-12 — Return for the latest official material As a Community Member, I should be able to return to the official site and find the latest showcase material, so that I stay current without needing an account.

• Provenance: required_inference
• Trigger/input: Community Member revisits the site.
• Observable result: The site presents the current official showcase content, including the latest updates.
• Access state: Anonymous; no sign-in, no stored personal state.
• Failure/recovery: If a section is temporarily unavailable, the rest of the site remains browsable.
• Continuation: Community Member continues browsing or leaves and returns later.

4. User Personas

Site Visitor

• Product context. A fan or player who comes to the official site to browse everything about the Blackhawk Rescue Mission 5 showcase by Platinum 5 — the helicopter, loadouts, tactics, and media — and to find the official information in one place.
• Primary goal. See and understand the full official showcase.
• Distinct accepted responsibilities. Exploring the site's content sections and consuming the showcase material. The Site Visitor is the broad, first-arrival audience: they may be encountering the showcase for the first time and need the Landing page to tell them what it is before they commit to browsing.
• Relevant inputs or decisions. Deciding whether the showcase is worth exploring, and which content area to open first (aircraft, loadouts, tactics, or media).
• Interactions with other accepted participants. None required; the Site Visitor's journey is self-contained and anonymous.
• Observable success. The visitor has seen and understood the full official showcase.

Community Member

• Product context. A dedicated Blackhawk Rescue Mission 5 community member who follows the Platinum 5 showcase and wants to keep up with official updates and community-facing content about the Blackhawk.
• Primary goal. Stay current with the official material.
• Distinct accepted responsibilities. Returning to the official site for the latest showcase information. Where the Site Visitor is defined by first-arrival exploration, the Community Member is defined by recurrence: their responsibility is the return visit and the check for what is new, particularly in the updates content.
• Relevant inputs or decisions. Deciding when to return and which sections to re-check for changes.
• Interactions with other accepted participants. None required; the Community Member's journey is self-contained and anonymous.
• Observable success. The Community Member is current with the official material.

5. Core User Flows

Flow 1 — Site Visitor discovers and browses the showcase

1. The Site Visitor arrives anonymously at the official site and lands on the Landing page.
2. The Landing page presents the full-bleed dark hero: the oversized condensed uppercase headline "BLACKHAWK RESCUE MISSION 5", the helicopter silhouette or macro detail right-of-center with warm rim light, and the faint topographic line pattern.
3. The Site Visitor reads the ruled instrument data strip beneath the headline — PLATINUM 5 / SHOWCASE / BRM5 / OFFICIAL — separated by 1px teal rules, and understands that this is the official destination.
4. The Site Visitor reads the introductory statement and understands what the Blackhawk Rescue Mission 5 showcase by Platinum 5 is.
5. The Site Visitor activates the primary amber CTA cut into the data strip and enters the Showcase page.
6. On the Showcase page, the Site Visitor uses the section index rail (AIRCRAFT, LOADOUTS, TACTICS, MEDIA, UPDATES) to move between content areas; the active section is marked by an amber tick.
7. As the Site Visitor scrolls into each section, the circular gauge opener sweeps once to reveal the section number and title, and key stats tick up once to their final values.
8. The Site Visitor reads the aircraft spec tables, reviews loadouts, studies the tactics diagrams, and views the media panels.
9. Observable result: the Site Visitor has browsed the full official showcase content.
10. Failure/recovery: if a media panel fails to load, its labeled placeholder holds its place in the ruled layout and all text, tables, and navigation remain usable; the Site Visitor continues browsing.
11. Continuation: the Site Visitor returns to the Landing page via the return navigation, or leaves the site.

Flow 2 — Community Member returns for the latest official material

1. The Community Member revisits the official site anonymously — no sign-in, no stored personal state.
2. The Community Member lands on the Landing page and confirms the official identity via the hero data strip.
3. The Community Member enters the Showcase page via the primary amber CTA.
4. The Community Member navigates directly to the UPDATES section using the section index rail.
5. The Community Member reads the official update entries in their ruled, ordered presentation.
6. Observable result: the Community Member is current with the latest official showcase information.
7. Failure/recovery: if an update's media fails to load, the update text remains readable and the Community Member still receives the information.
8. Continuation: the Community Member browses other sections (aircraft, loadouts, tactics, media) or leaves the site and returns later.

Flow 3 — Site Visitor navigates directly to a content area

1. The Site Visitor is on the Showcase page, having entered from the Landing page.
2. The Site Visitor selects a specific section label in the section index rail — for example, LOADOUTS.
3. The rail marks the selected section with an amber tick and brings that section's content into view.
4. The Site Visitor reads the ruled label/value rows with tabular numerals and the teal active-row highlight, and follows the diagrammatic loadout callouts.
5. Observable result: the Site Visitor has reached and consumed the specific content area they wanted.
6. Failure/recovery: on a narrow viewport, the rail is a horizontally scrollable index; the Site Visitor scrolls the rail to reach any label, and every label becomes fully readable as it passes.
7. Continuation: the Site Visitor selects another section or returns to the Landing page.

6. Visuals Colors and Theme

The authoritative creative direction is Precision instrument luxury for a rescue-mission showcase, with MARQ by Garmin as the muse. The headline idea: the site should read as an official technical dossier with the gravity of a luxury tool-watch — dark, precise, engineered, trustworthy — the feeling of a pilot's instrument panel, not a game marketing splash.

Color tokens (dark mode).

Proportion discipline: ~70% dark ground, ~20% graphite surfaces, ~7% teal, ~3% amber. Never place amber on teal at body size; pair amber with the dark ground and teal with the light text.

Typography.

• Headings: Barlow Condensed — condensed technical sans, uppercase, weights 600–700, tight tracking (−0.01em to −0.02em), used at large scale for section titles and instrument labels. Headlines are compressed and authoritative, never decorative. Numerals are tabular and often set at display size as data ornaments.
• Body: Saira.
• Scale: 1.25 modular with a display tier — 72 / 56 / 40 / 28 / 20 / 16 / 14. Display headings clamp(40px, 8vw, 96px); body 16–18px; micro-labels 11–12px uppercase with 0.12em tracking.

Shape language. Engineered and instrument-like: rounded-rectangle control surfaces with 6–10px radii, hairline 1px borders in #2A3135, ruled data rows with 1px dividers, circular gauge motifs and bezel rings as section markers. No organic blobs, no pill-shaped everything, no soft pastel cards. Corners are precise; edges are honest.

Layout. A modular instrument grid: 12 columns on desktop, 6 on tablet, 4 on mobile, with a persistent left rail of section labels on wide screens. Sections are dense but ordered — label/value pairs, tabular specs, numbered rows. The hero is a full-bleed dark composition with an oversized condensed wordmark and a ruled data strip. Content blocks alternate between wide media panels and ruled spec tables. Everything aligns to a visible baseline grid.

Imagery. Macro product-style renders and photography of the Blackhawk and gear on dark titanium grounds: rotor detail, cockpit instruments, loadout silhouettes, topographic line overlays, expedition-style environmental shots. Diagrammatic line art for tactics and loadout callouts. No stock people, no flat clip art, no gradient blobs. Every image is lit like a studio product shot or a field instrument macro.

Readability constraint. Headlines, wordmarks, labels, numbers, item images, cards, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit; no other element covers any part of them. Crops, bleeds, and off-edge placement are reserved for decoration only — shapes, textures, rules, and background art. Moving and scrollable content (marquees, tickers, carousels, horizontally scrollable rows) may cross the viewport or container edge by design and is judged by whether it actually moves and whether every item becomes fully readable as it passes. With prefers-reduced-motion, moving content stops and shows whole items: they wrap into rows, or sit in a horizontally scrollable row (overflow-x: auto) whose further items are reached by scrolling.

Forbidden. Centered headline + subtext + blue button + gradient blob hero; white or near-white page ground; blue–indigo primary or accent (#0057FF, #2563EB, #4F46E5, #6366F1, #7C3AED and neighbours); Inter, Roboto, Arial, Helvetica, Open Sans, Lato, Poppins, or system-ui for headings or body; grid of identical hover-lift cards; playful rounded blobs, sticker shapes, or pastel gradients; bouncy or springy motion, particles, or confetti; stock photography of people or flat clip-art icons. The generic indigo/blue-on-white SaaS template is forbidden for this project.

7. Signature Design Concept

The Instrument Dossier. The Landing page opens as a full-bleed dark titanium composition. A single large helicopter silhouette or macro detail sits right-of-center, lit with a warm rim light, occupying roughly 60% of the viewport width on desktop. Over it, left-aligned, the oversized condensed uppercase headline "BLACKHAWK RESCUE MISSION 5" is set in Barlow Condensed at clamp(48px, 9vw, 128px), stacked in two or three lines. A faint topographic line pattern runs beneath the composition.

Directly under the headline sits the signature element: a ruled instrument data strip with four label/value pairs — PLATINUM 5 / SHOWCASE / BRM5 / OFFICIAL — in Saira with tabular numerals, separated by 1px teal rules. The primary amber CTA is cut into the strip itself rather than floating below it, so the entry action reads as part of the instrument panel rather than a marketing button.

The composition is completed by the left rail of uppercase condensed section labels (AIRCRAFT, LOADOUTS, TACTICS, MEDIA, UPDATES), fixed on desktop and horizontally scrollable on mobile, with the active section marked by an amber tick. There is no centered headline, no gradient blob, and no blue button.

This concept recomposes only accepted content, states, and controls: the official identity, the entry action, and the section index. It introduces no new behavior, page, or destination.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: layered_2d

Landing Hero Motion Brief.

• Focal subject: the Blackhawk silhouette or macro detail, right-of-center, lit with a warm rim light against the dark titanium ground.
• Input → transformation → outcome thesis: as the visitor scrolls, the hero aircraft shifts slowly in a single scroll-linked parallax while the topographic line pattern holds; the ruled data strip and headline remain fixed and readable. The motion confirms depth and directs attention to the entry CTA — it never entertains.
• Motion vocabulary: needle-sweep reveals, counting numerals, slow turntable-style image pans, and one scroll-linked parallax on the hero aircraft. Transitions are 180–260ms with linear or ease-out curves. No bounce, no particles, no playful easing.
• Composed first frame: full-bleed dark ground; oversized condensed uppercase headline stacked left; helicopter detail right-of-center with warm rim light; ruled data strip with four label/value pairs and the amber CTA cut into it; faint topographic lines; left rail of section labels with the active section ticked amber.
• Reduced-motion state: with prefers-reduced-motion, the parallax and turntable pans stop; the hero holds as a still composed frame with the aircraft fully visible, the data strip and CTA fully readable, and all moving or scrollable content shown as whole items (wrapped rows or a horizontally scrollable row).

9. Non-Functional Requirements

• NFR-1 — Anonymous public access. The site is publicly reachable with no account, sign-in, or personal state. Provenance: required_inference from the accepted anonymous access contract for both pages. Rationale: no accepted journey requires identity continuity.
• NFR-2 — Readability at all viewports. Headlines, wordmarks, labels, numbers, item images, cards, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit, with no element covering any part of them. Provenance: explicit user design constraint.
• NFR-3 — Reduced-motion support. With prefers-reduced-motion, motion stops and moving content shows whole items, wrapping into rows or sitting in a horizontally scrollable row. Provenance: explicit user design constraint.
• NFR-4 — Media failure resilience. Text, spec tables, labels, and navigation remain fully functional and readable when any media asset fails to load. Provenance: required_inference from the accepted browse journeys' failure/recovery needs.
• NFR-5 — Motion restraint. Transitions are 180–260ms with linear or ease-out curves; no bounce, spring, particles, or confetti. Provenance: explicit creative direction.
• NFR-6 — Palette and typography fidelity. The specified dark palette, Barlow Condensed headings, and Saira body type are preserved; forbidden colors and font families are not used. Provenance: explicit creative direction and user design constraints.

10. Tech Stack

• Frontend: React.
• Styling: CSS with the specified design tokens (custom properties for the palette, type scale, radii, and spacing rhythm).
• Content: Static, source-derived showcase content rendered from structured data modules (aircraft specs, loadouts, tactics, media, updates) so the ruled spec tables and section content stay consistent.
• Hosting: Static site delivery suitable for anonymous public access.

No backend service, database, authentication provider, or container orchestration is required by the accepted scope. No source-specified technology was provided beyond the project context, so the stack above is the minimal set needed to deliver the accepted behavior.

11. Assumptions and Constraints

• A-1. The site is a read-only showcase: visitors browse and consume content; they do not create, edit, or submit it. [Assumption — consistent with the accepted requirement to be an official site about everything.]
• A-2. No application-owned identity is introduced, because no accepted journey requires private ownership, resumption, or return to durable personal state. [Assumption — derived from the anonymous access contract.]
• A-3. The showcase content areas (aircraft, loadouts, tactics, media, updates) are the accepted content coverage of "everything" about the showcase. [Assumption — derived from the accepted requirement and the Showcase page rationale.]
• A-4. No future-horizon requirements are accepted; nothing is deferred to a future section. [Assumption — the authoritative thread establishes only current scope.]
• A-5. The site is delivered in English. [Default — not specified by user.]
• A-6. No analytics, tracking, or third-party integrations are included. [Default — not specified by user.]

12. Glossary

• Blackhawk Rescue Mission 5 (BRM5) — the tactical rescue/aviation experience that the showcase presents.
• Platinum 5 — the creator of the Blackhawk Rescue Mission 5 showcase.
• Showcase — the official Blackhawk Rescue Mission 5 content presented by Platinum 5, covering the helicopter, loadouts, tactics, media, and updates.
• Aircraft — the Blackhawk helicopter and its specifications, dimensions, performance, and crew capacity.
• Loadout — a weapons and equipment configuration presented in the showcase.
• Tactics — the tactical material presented with diagrammatic line art.
• Media — the renders, photography, and imagery of the Blackhawk and gear.
• Updates — official showcase update entries.
• Section index rail — the persistent left rail of uppercase condensed section labels (AIRCRAFT, LOADOUTS, TACTICS, MEDIA, UPDATES), fixed on desktop and horizontally scrollable on mobile, with the active section marked by an amber tick.
• Instrument data strip — the ruled horizontal band of four label/value pairs (PLATINUM 5 / SHOWCASE / BRM5 / OFFICIAL) beneath the hero headline, separated by 1px teal rules, with the primary amber CTA cut into it.
• Spec table — the first-class ruled label/value UI component with tabular numerals, 1px dividers, and a teal active-row highlight.