System Requirements Document for blimp-bus-fundraiser

1. Introduction

blimp-bus-fundraiser is a first-party web product for raising capital toward a 200 billion fundraising target for a flying blimp bus program tied to an RWA (real-world asset) giga factory and supplies pipeline. The product's intent is to present the flying blimp bus, the RWA giga factory, and the supplies offering as a credible, spectacular capital-raise proposition, and to let people contribute toward the 200 billion goal while letting the campaign's organizer configure and run the fundraiser.

The audience is twofold: the Fundraiser Organizer, who sets up and runs the campaign (defining the 200 billion target and the blimp bus / RWA giga factory / supplies framing, and tracking progress), and the Supporter / Contributor, who reviews the campaign and makes a contribution, then sees the campaign's progress toward the target. The product is delivered as a custom first-party application with application-owned identity, so organizers and supporters can enroll, return, and have their durable fundraiser and contribution state preserved.

2. System Overview

The current product consists of six first-party pages: Landing, Login, Sign Up, Campaign, Contribution, and Fundraiser Setup. The Landing page is the anonymous public entry that explains the flying blimp bus fundraiser, its 200 billion target, and its RWA giga factory and supplies focus. Login and Sign Up provide returning verification and self-service enrollment for both accepted personas. Campaign presents the flying blimp bus, RWA giga factory, and supplies framing to supporters before contribution. Contribution owns contribution completion and the display of progress toward the 200 billion target. Fundraiser Setup lets the organizer configure the 200 billion target and the fundraiser's framing.

Actors are the two accepted human personas — Fundraiser Organizer and Supporter / Contributor — plus the application's own backend, which persists fundraiser configuration, contributions, and progress state. There are no other accepted human personas, and no provider-owned or external destinations are part of the current scope.

Narrow exclusions: the product does not include payment-rail, custody, or securities-compliance modules beyond recording a contribution and reflecting progress; it does not include invitation or provisioning flows (enrollment is self-service); and it does not include any capability beyond the flying blimp bus fundraiser, its 200 billion target, and its RWA giga factory and supplies framing.

2a. Product Interpretation and Delivery Boundary

This is a first-party, application-owned product. All accepted human work happens inside the six pages above; there is no provider-owned surface and no external destination in the current scope. Identity is application-owned: a visitor can read the Landing page anonymously, but durable fundraiser configuration, contribution records, and progress state belong to an identified organizer or supporter, so the product establishes identity through Sign Up (self-service enrollment) and Login (returning verification). The protected destinations — Campaign, Contribution, and Fundraiser Setup — require an established identity; the anonymous entry interaction that establishes access lives on Landing, Login, and Sign Up, which are themselves anonymously reachable.

Current horizon: the flying blimp bus fundraiser, the 200 billion target, the RWA giga factory and supplies framing, organizer setup, supporter contribution, and progress toward the target. Future horizon: nothing beyond the current scope is accepted; any expansion (for example additional asset classes, additional campaign types, or third-party payment or custody integrations) is out of scope until explicitly requested.

2b. Source Content Inventory

No reference directive in this project declares content_source; therefore no Source Content Inventory is included.

2c. Page Content and Component Coverage

Landing

• Information / state: Anonymous public entry. Explains the flying blimp bus fundraiser, its 200 billion target, and its RWA giga factory and supplies focus. Shows the headline "A BUS THAT FLIES. A FACTORY THAT BUILDS THE FUTURE.", the 200,000,000,000 target as a trophy number, the currently raised total, and the funded portion as an arc.
• Primary actions: "Back the blimp bus" capsule CTA leading toward contribution; navigation to Login and Sign Up.
• Supporting actions: Scroll into the first campaign band; hover-pause the live contribution ticker.
• Domain entities: Fundraiser (target amount, raised total, framing), Contribution (recent entries shown in the ticker).
• Component responsibilities: Hero capsule blimp render (WebGL/R3F subject, cropped off right and top edges, headline type overlapping its lower-left curve with type in front); trophy-number band for the 200 billion target with lime progress arc; curved SVG arc section dividers; live contribution ticker marquee; contribution tier capsule chips at staggered offsets; CTA pill with lime underline.
• States: Loading — hero subject and ticker initialize, target number renders immediately from static configuration. Empty — no contributions yet: ticker shows an empty-state line and the arc renders at zero. Success — target, raised total, and arc render at current values. Error — if the raised total cannot be fetched, the target and framing still render and the raised total shows an unavailable state with a retry. Recovery — retry re-fetches the raised total without leaving the page.

Login

• Information / state: Anonymous identity-access surface for returning organizers and supporters. Collects credentials for returning verification.
• Primary actions: Submit credentials to verify identity and continue to the destination the actor was seeking.
• Supporting actions: Navigate to Sign Up for actors without an identity.
• Domain entities: Account (identity), Session.
• Component responsibilities: Credential form with capsule inputs; submit pill; link to Sign Up; inline validation and error messaging.
• States: Loading — submit disabled with progress indication during verification. Empty — pristine form. Success — identity verified, actor continues to Campaign, Contribution, or Fundraiser Setup. Error — invalid credentials show an inline message and preserve entered values; Recovery — actor can correct and resubmit, or go to Sign Up.

Sign Up

• Information / state: Anonymous self-service enrollment surface for actors beginning to use the fundraiser product. No invitation or provisioning boundary is specified, so enrollment is open self-service.
• Primary actions: Create an identity and continue into the product.
• Supporting actions: Navigate to Login for actors who already have an identity.
• Domain entities: Account (identity), Session.
• Component responsibilities: Enrollment form with capsule inputs; submit pill; link to Login; inline validation and error messaging.
• States: Loading — submit disabled with progress indication during creation. Empty — pristine form. Success — identity created and the actor continues to the destination they were seeking. Error — validation or creation failure shows an inline message and preserves entered values; Recovery — actor can correct and resubmit, or go to Login.

Campaign

• Information / state: Protected surface for supporters. Presents the flying blimp bus, the RWA giga factory, and the supplies offering as the campaign framing, alongside the 200 billion target and current progress.
• Primary actions: Proceed to Contribution.
• Supporting actions: Review the blimp bus, giga factory, and supplies framing; review contribution tier chips.
• Domain entities: Fundraiser (target, framing, raised total), Contribution tier, Contribution.
• Component responsibilities: Framing sections for the blimp bus, the RWA giga factory, and supplies; trophy-number band with lime progress arc; tier capsule chips at staggered offsets; CTA pill into Contribution; curved arc dividers.
• States: Loading — framing and progress load with placeholder structure. Empty — no contributions yet: progress arc at zero with an empty-state line. Success — framing, target, raised total, and arc render at current values. Error — if framing or progress cannot be fetched, an inline error with retry is shown. Recovery — retry re-fetches without leaving the page.

Contribution

• Information / state: Protected surface for supporters. Owns contribution completion and the display of progress toward the 200 billion target.
• Primary actions: Enter a contribution amount and complete the contribution.
• Supporting actions: Review the resulting progress toward the target; return to Campaign.
• Domain entities: Contribution (amount, contributor, timestamp), Fundraiser (target, raised total, percentage funded).
• Component responsibilities: Amount input with capsule styling; tier capsule chips; submit pill; progress arc and percentage-funded readout in lime; confirmation state; error and retry messaging.
• States: Loading — submit disabled with progress indication while the contribution is recorded. Empty — no amount entered yet. Success — contribution recorded, confirmation shown, raised total and arc updated. Error — invalid amount or recording failure shows an inline message and preserves the entered amount; Recovery — actor can correct and resubmit, and a failed contribution leaves the raised total unchanged.

Fundraiser Setup

• Information / state: Protected surface for the organizer. Lets the organizer configure the 200 billion target and the fundraiser's flying blimp bus, RWA giga factory, and supplies framing.
• Primary actions: Set the 200 billion target and the campaign framing, then save the fundraiser configuration.
• Supporting actions: Review the configured target and framing before saving.
• Domain entities: Fundraiser (target amount, framing content, status).
• Component responsibilities: Target-amount field with trophy-number styling; framing fields for the blimp bus, RWA giga factory, and supplies; save pill; validation and error messaging; saved-state confirmation.
• States: Loading — existing configuration loads with placeholder structure. Empty — no fundraiser configured yet: fields start blank with the 200 billion target as the expected value. Success — configuration saved and confirmed. Error — validation or save failure shows an inline message and preserves entered values; Recovery — organizer can correct and resave.

3. Functional Requirements

FR-1 — Flying blimp bus fundraiser product (explicit) As a Fundraiser Organizer, I should have a fundraiser product centered on a flying blimp bus, so that the campaign presents the blimp bus as the object being funded.

• Trigger/input: Organizer opens Fundraiser Setup.
• Observable result: The fundraiser exists and is framed around the flying blimp bus.
• Access state: Protected; requires an established organizer identity.
• Failure/recovery: If configuration cannot be saved, an inline error is shown and entered values are preserved for correction.
• Continuation: Organizer proceeds to review the configured fundraiser and track progress.

FR-2 — 200 billion target (explicit) As a Fundraiser Organizer, I should set the fundraiser's target amount to 200 billion, so that the campaign's goal is the 200 billion figure.

• Trigger/input: Organizer enters the target amount in Fundraiser Setup.
• Observable result: The fundraiser's target is 200 billion and is displayed as the trophy number on Landing, Campaign, and Contribution.
• Access state: Protected; requires an established organizer identity.
• Failure/recovery: Invalid target input shows an inline validation message and preserves the entered value.
• Continuation: The target drives the progress arc and percentage-funded readout.

FR-3 — RWA giga factory and supplies framing (explicit) As a Fundraiser Organizer, I should tie the fundraiser to an RWA (real-world asset) giga factory and supplies, so that the campaign communicates the real-world asset giga factory and supplies pipeline.

• Trigger/input: Organizer enters the RWA giga factory and supplies framing in Fundraiser Setup.
• Observable result: The RWA giga factory and supplies framing appears on the fundraiser's public and supporter-facing surfaces.
• Access state: Protected; requires an established organizer identity.
• Failure/recovery: If framing cannot be saved, an inline error is shown and entered values are preserved.
• Continuation: Supporters review the framing on Campaign before contributing.

FR-4 — Self-service enrollment (required_inference) As a Fundraiser Organizer or Supporter / Contributor, I should be able to enroll myself on Sign Up, so that I can begin using the fundraiser product without an invitation or provisioning step.

• Trigger/input: Anonymous visitor opens Sign Up and submits enrollment details.
• Observable result: An identity is created and the actor continues into the product.
• Access state: Anonymous entry; the resulting identity unlocks protected destinations.
• Failure/recovery: Validation or creation failure shows an inline message and preserves entered values; the actor can correct and resubmit or go to Login.
• Continuation: The actor continues to the destination they were seeking.

FR-5 — Returning verification (required_inference) As a Fundraiser Organizer or Supporter / Contributor, I should be able to verify my identity on Login, so that I can return to my durable fundraiser and contribution state.

• Trigger/input: Returning actor opens Login and submits credentials.
• Observable result: Identity is verified and the actor reaches their durable state.
• Access state: Anonymous entry; verification unlocks protected destinations.
• Failure/recovery: Invalid credentials show an inline message and preserve entered values; the actor can correct and resubmit or go to Sign Up.
• Continuation: The actor continues to Campaign, Contribution, or Fundraiser Setup.

FR-6 — Authenticated organizer authorization before configuring (required_inference) As a Fundraiser Organizer, I should be authorized as an authenticated organizer before configuring the fundraiser, so that only the organizer can set the target and framing.

• Trigger/input: Actor attempts to open Fundraiser Setup.
• Observable result: Only an authenticated organizer can configure the fundraiser; other actors cannot.
• Access state: Protected; requires an established organizer identity.
• Failure/recovery: An unauthenticated actor is directed to Login or Sign Up; a non-organizer actor cannot configure the fundraiser.
• Continuation: The authorized organizer configures the target and framing.

FR-7 — Authenticated supporter continuity for contributions and progress (required_inference) As a Supporter / Contributor, I should have authenticated continuity for recording contributions and showing progress, so that my contribution is bound to me and the campaign's progress reflects it.

• Trigger/input: Supporter opens Contribution while authenticated.
• Observable result: The contribution is recorded against the supporter's identity and the campaign's raised total and progress arc update.
• Access state: Protected; requires an established supporter identity.
• Failure/recovery: A failed contribution leaves the raised total unchanged and shows an inline error with retry.
• Continuation: The supporter sees updated progress and can return to Campaign.

FR-8 — Public campaign presentation (required_inference) As a Supporter / Contributor, I should be able to review the flying blimp bus, the RWA giga factory, and the supplies framing on Campaign, so that I understand what I am contributing toward.

• Trigger/input: Supporter opens Campaign.
• Observable result: The blimp bus, RWA giga factory, and supplies framing, the 200 billion target, and current progress are presented.
• Access state: Protected; requires an established supporter identity.
• Failure/recovery: If framing or progress cannot be fetched, an inline error with retry is shown.
• Continuation: The supporter proceeds to Contribution.

FR-9 — Contribution completion and progress display (required_inference) As a Supporter / Contributor, I should complete a contribution and see progress toward the 200 billion target, so that my contribution is recorded and its effect on the campaign is visible.

• Trigger/input: Supporter enters an amount on Contribution and submits.
• Observable result: The contribution is recorded, a confirmation is shown, and the raised total and progress arc update toward the 200 billion target.
• Access state: Protected; requires an established supporter identity.
• Failure/recovery: Invalid amount or recording failure shows an inline message and preserves the entered amount; the raised total is unchanged.
• Continuation: The supporter reviews updated progress and can return to Campaign.

FR-10 — Organizer progress tracking (required_inference) As a Fundraiser Organizer, I should see the fundraiser's progress toward the 200 billion target, so that I can track how the campaign is accumulating contributions.

• Trigger/input: Organizer opens the fundraiser's progress view.
• Observable result: The raised total and progress toward the 200 billion target are displayed.
• Access state: Protected; requires an established organizer identity.
• Failure/recovery: If progress cannot be fetched, an inline error with retry is shown.
• Continuation: The organizer continues to run the campaign.

4. User Personas

Fundraiser Organizer

The Fundraiser Organizer is the primary human role behind the campaign: the person who sets up and runs the flying blimp bus fundraiser. Their product context is Fundraiser Setup, where they define the 200 billion target and the fundraiser's framing around the flying blimp bus, the RWA giga factory, and supplies. Their primary goal is a live, credible fundraiser that accumulates contributions toward the 200 billion goal.

Their distinct accepted responsibilities are: enrolling or verifying identity (Sign Up / Login), being authorized as an authenticated organizer before configuring the fundraiser, configuring the 200 billion target and the blimp bus / RWA giga factory / supplies framing, and tracking progress toward the target. Their relevant inputs and decisions are the target amount and the framing content they choose to present. They interact with the Supporter / Contributor indirectly: supporters review the framing the organizer configured and contribute toward the target the organizer set. Their observable success is a configured fundraiser whose target and framing are live and whose progress toward 200 billion is visible.

What makes this role's work different from the supporter's is that the organizer owns the campaign's definition — the target and the framing — and its progress tracking, whereas the supporter consumes that definition and acts on it by contributing.

Supporter / Contributor

The Supporter / Contributor is the audience for the fundraiser. Their product context is the Landing page, where they first encounter the flying blimp bus fundraiser, its 200 billion target, and its RWA giga factory and supplies focus; the Campaign page, where they review the blimp bus, giga factory, and supplies framing; and the Contribution page, where they complete a contribution and see progress. Their primary goal is to review the campaign and make a contribution, with the successful outcome of a completed contribution and visible campaign progress.

Their distinct accepted responsibilities are: enrolling or verifying identity (Sign Up / Login), reviewing the campaign framing on Campaign, entering and completing a contribution on Contribution, and observing the resulting progress toward the 200 billion target. Their relevant inputs and decisions are the contribution amount they choose. They interact with the Fundraiser Organizer indirectly: the organizer's configured target and framing are what the supporter reviews and contributes toward. Their observable success is a recorded contribution and an updated progress arc toward the 200 billion target.

What makes this role's work different from the organizer's is that the supporter does not define the campaign; they evaluate the organizer's framing and act on it by contributing, then observe the campaign's progress.

5. Core User Flows

Flow A — Organizer configures the flying blimp bus fundraiser

1. The Fundraiser Organizer arrives at Landing anonymously and reads the flying blimp bus fundraiser, its 200 billion target, and its RWA giga factory and supplies focus.
2. The organizer chooses to run the campaign and goes to Sign Up (or Login if already enrolled) to establish or verify identity.
3. On Sign Up, the organizer submits enrollment details; on success an identity is created and the organizer continues into the product. On failure, an inline message is shown, entered values are preserved, and the organizer corrects and resubmits or goes to Login.
4. The organizer opens Fundraiser Setup. Because the destination is protected, an unauthenticated actor is directed to Login or Sign Up; only an authenticated organizer can configure the fundraiser.
5. On Fundraiser Setup, the organizer sets the target amount to 200 billion and enters the fundraiser's framing for the flying blimp bus, the RWA giga factory, and supplies.
6. The organizer saves the configuration. On success, the saved state is confirmed. On failure, an inline error is shown, entered values are preserved, and the organizer corrects and resaves.
7. The organizer reviews the configured fundraiser and its progress toward the 200 billion target. If progress cannot be fetched, an inline error with retry is shown and the organizer retries without leaving the page.
8. Continuation: the organizer continues to run the campaign as contributions accumulate toward the 200 billion goal.

Flow B — Supporter reviews the campaign and contributes

1. The Supporter / Contributor arrives at Landing anonymously and reads the flying blimp bus fundraiser, the 200 billion target, and the RWA giga factory and supplies focus, including the raised total and the funded arc.
2. The supporter chooses to back the blimp bus and goes to Sign Up (or Login if already enrolled) to establish or verify identity.
3. On Sign Up, the supporter submits enrollment details; on success an identity is created and the supporter continues into the product. On failure, an inline message is shown, entered values are preserved, and the supporter corrects and resubmits or goes to Login.
4. The supporter opens Campaign and reviews the flying blimp bus, the RWA giga factory, and the supplies framing, along with the 200 billion target and current progress. If framing or progress cannot be fetched, an inline error with retry is shown and the supporter retries.
5. The supporter proceeds to Contribution, enters a contribution amount, and submits.
6. On success, the contribution is recorded against the supporter's identity, a confirmation is shown, and the raised total and progress arc update toward the 200 billion target. On failure, an inline message is shown, the entered amount is preserved, and the raised total is unchanged; the supporter corrects and resubmits.
7. The supporter reviews the updated progress and can return to Campaign.
8. Continuation: the supporter's recorded contribution remains bound to their identity and is reflected in the campaign's progress on subsequent visits.

Flow C — Returning supporter checks progress

1. The Supporter / Contributor returns and opens Login.
2. The supporter submits credentials. On success, identity is verified and the supporter reaches their durable state. On failure, an inline message is shown, entered values are preserved, and the supporter corrects and resubmits or goes to Sign Up.
3. The supporter opens Campaign or Contribution and sees the current raised total and progress arc toward the 200 billion target, including their own recorded contribution.
4. Continuation: the supporter can make a further contribution or leave and return later with their state intact.

6. Visuals Colors and Theme

The creative direction is authoritative for this section. Muse: Karim Rashid — sensual pop minimalism for a blimp bus that flies money into a giga factory. Headline register: spectacle, optimism, and a hint of glorious absurdity, with real numbers treated as trophy objects rather than spreadsheet cells.

Mode: dark.

Colour tokens (exact hex by role):

Ratio target: roughly 55% ground, 25% pink, 12% surface, 8% lime. Lime never exceeds a single-digit share of any screen and is used only for numbers that matter (the 200B target, contribution amounts, percentage funded) and for the live ticker.

Typography:

• Headings: Unbounded, weight 700–800 for display, sentence case, tight 0.92 line-height, -0.02em tracking.
• Micro-labels: Unbounded 500 at 12–13px, 0.28em letterspacing, uppercase (e.g. RWA / GIGA FACTORY / SUPPLIES).
• Body: Quicksand 500 at 17–18px, 1.65 line-height.
• Numbers: Unbounded 800 with tabular figures at clamp(40px, 6vw, 88px) for the 200B target and progress totals.
• Scale (1.333 modular): display clamp(52px, 9.5vw, 132px) / h2 clamp(34px, 4.4vw, 58px) / h3 28px / lead 20px / body 17px / label 13px / micro 11px.

Shape language: capsules and blobs only — border-radius: 999px for every button, chip, tab, and input; 48–72px organic radii for cards and panels; section boundaries are curved SVG arcs sweeping the full viewport rather than straight rules. Zero sharp corners except the 1px glossy rim strokes. Buttons are glossy pills with a soft inner highlight along the top edge (inset 0 1px 0 rgba(255,255,255,0.35)) and a 12px pink bloom shadow beneath. Progress is an arc, never a rectangle.

Spacing rhythm: asymmetric fluid 12-column grid with a 96px max gutter bleed; hero capsule blimp breaks the right edge; headline column offset left by one column so nothing is dead-centre. Sections alternate between full-bleed colour fields and 720px measured text columns, separated by curved arc dividers. Contribution tiers are overlapping capsule chips at staggered vertical offsets, never a row of equal cards. The 200B target number sits alone in a full-width band. At 375px everything collapses to a single column, arcs flatten to shallow 24px curves, and the blimp crops to a top-third band above the headline.

Imagery style: glossy 3D renders on the aubergine ground — the blimp bus as a soft pink capsule with a visible panoramic window band and small vector thrusters, rendered with a hard specular highlight so it reads as injection-moulded plastic; the giga factory as a stack of rounded white and pink modules with lime light strips; supplies as floating capsule icons (solar cells, battery cells, airframe ribs), glossy and toy-like. No photography of people, no flat clip art, no gradient blobs; every form has a defined silhouette and a single light source.

Avoid: blue, indigo, or violet primary accents on a white ground; Inter, Roboto, Arial, Helvetica, Poppins, Montserrat, or system-ui for any heading or body text; a centred headline + subtext + button hero or any gradient-blob backdrop; a grid of identical rounded cards with hover-lift shadows; straight-edged section dividers, sharp-cornered buttons, or rectangular progress bars; stock photography of people, handshake imagery, or flat vector clip art; neon-on-pure-black "cyberpunk" treatment; literal cartoon blimp mascots with faces or googly eyes. The generic indigo/blue-on-white SaaS template is forbidden.

7. Signature Design Concept

The public entry is a poster composition, not a centred SaaS stack. A full-bleed aubergine stage holds a single oversized glossy pink blimp capsule dominating the right 60% of the viewport, cropped by the right and top edges, lit from upper-left with a hard specular streak, its window band glowing lime. The headline "A BUS THAT FLIES. A FACTORY THAT BUILDS THE FUTURE." is set in Unbounded 800 at clamp(52px, 9.5vw, 132px), flush-left, stacked over four lines, and deliberately overlaps the blimp's lower-left curve so type and object share the same plane — with the overlapping portion of the blimp set behind the type, never over it. Beneath the headline, a lime-underlined capsule CTA "Back the blimp bus" sits beside a live counter reading 200,000,000,000 in Unbounded 800, with the raised total ticking beneath it in pink. Below the fold line, a curved arc divider reveals the first campaign band. Nothing is centred; nothing is a gradient blob.

The concept recomposes only accepted content and controls: the flying blimp bus framing, the 200 billion target, the raised total and funded arc, the CTA toward contribution, and the navigation to Login and Sign Up. It introduces no new behaviour, page, or destination.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: webgl

Landing Hero Motion Brief

• Focal subject: the glossy pink blimp capsule render, cropped off the right and top edges, with a lime-glowing window band and small vector thrusters.
• Input → transformation → outcome thesis: as the visitor arrives and scrolls, the blimp capsule breathes with a 6s ease-in-out scale/translate loop; the lime progress arc draws itself on scroll into view to the current funded value; contribution tier chips rise with a soft spring (stiffness 180, damping 18) and settle; the live contribution ticker marquees horizontally at 40s linear and pauses on hover. The outcome is a visitor who has read the flying blimp bus framing, seen the 200 billion target as a trophy number, and can act on the "Back the blimp bus" CTA.
• Motion vocabulary: liquid and continuous — breathing capsule, self-drawing arc, spring-settled chips, marquee ticker, hover morph on tier chips (slight radius morph plus bloomed shadow).
• Composed first frame: aubergine ground; blimp capsule occupying the right 60%, cropped top and right; headline stacked flush-left over four lines overlapping the capsule's lower-left curve with type in front; lime-underlined CTA pill beside the 200,000,000,000 counter; raised total ticking in pink beneath; curved arc divider at the fold.
• Reduced-motion state: the ticker becomes a horizontally scrollable row where each entry can be brought fully into view; the arc renders at its final value; the blimp capsule, chips, and dividers render as a static arrangement.

Landing Hero 3D Scene Brief — DIRECTION-DERIVED

A single crafted real-time object: the blimp bus as a soft pink capsule with a visible panoramic window band and small vector thrusters, rendered with a hard specular highlight so it reads as injection-moulded plastic, lit from upper-left on the aubergine ground. The scene shows the product's defining state — the flying blimp bus as the object being funded — and is cropped by the right and top edges so the headline type overlaps its lower-left curve with type in front. The scene must degrade to a static arrangement under prefers-reduced-motion.

9. Non-Functional Requirements

• NFR-1 — Readable text and controls stay whole (explicit, creative direction): headlines, wordmarks, labels, numbers, cards' text, 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, and no other element covers any part of them. Imagery, decoration, and motion may be cropped, bled off an edge, rotated, overlapped, or cut as the direction asks, as long as they cover no readable text or control. 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 or scrolls and whether every item becomes fully readable as it passes.
• NFR-2 — Reduced-motion usability (explicit, creative direction): with prefers-reduced-motion, provide a usable static arrangement — wrap items into rows or allow horizontal scrolling so each item can be brought fully into view; the ticker becomes a horizontally scrollable row and the arc renders at its final value.
• NFR-3 — Palette and typography fidelity (explicit, creative direction): the palette is pink and lime on aubergine; headings and body use Unbounded and Quicksand respectively; the forbidden fonts and the indigo/blue-on-white SaaS template are not used.
• NFR-4 — Durable fundraiser and contribution state (required_inference): fundraiser configuration, contribution records, and progress state persist so returning organizers and supporters reach their durable state after verification.
• NFR-5 — Contribution integrity (required_inference): a failed contribution leaves the campaign's raised total unchanged, and a recorded contribution is bound to the contributing supporter's identity.
• NFR-6 — Responsive layout (explicit, creative direction): at 375px everything collapses to a single column, arcs flatten to shallow 24px curves, and the blimp crops to a top-third band above the headline.

10. Tech Stack

• Frontend: React (custom first-party UI), with a real-time WebGL/R3F hero subject for the Landing blimp capsule as required by the creative direction's webgl hero dimensionality.
• Backend: Python / FastAPI, providing the fundraiser configuration, contribution recording, progress, and identity endpoints.
• Storage: a persistent datastore for accounts, fundraiser configuration, contributions, and progress state.
• Packaging: Docker / docker-compose for local and deployment packaging.

No other technology choices are specified by the source; no additional stack items are introduced.

11. Assumptions and Constraints

• A-1 (required_inference): Identity is application-owned, established through self-service enrollment on Sign Up and returning verification on Login, because durable fundraiser configuration, contribution records, and progress state must remain bound to the correct participant.
• A-2 (required_inference): Campaign, Contribution, and Fundraiser Setup are protected destinations; Landing, Login, and Sign Up are anonymously reachable, and the anonymous entry interaction that establishes access lives on those surfaces rather than on a protected destination.
• A-3 (required_inference): The organizer is authorized as an authenticated organizer before configuring the fundraiser; no broader role or permission model is established beyond this.
• A-4 (explicit): The fundraiser's target is 200 billion, and the fundraiser is tied to a flying blimp bus and an RWA giga factory and supplies.
• A-5 (explicit): The product is delivered as a custom first-party application; no provider-owned or external destination is part of the current scope.
• A-6 (explicit): No invitation or provisioning boundary is specified, so enrollment is open self-service.
• A-7 (explicit): The creative direction is authoritative for palette, typography, shape language, layout, motion, and imagery; the generic indigo/blue-on-white SaaS template is forbidden.
• A-8 (explicit): Payment-rail, custody, and securities-compliance modules beyond recording a contribution and reflecting progress are out of scope; any expansion is a future horizon until explicitly requested.

12. Glossary

• Flying blimp bus — the object being funded by the campaign; a soft organic capsule airship presented as the fundraiser's centerpiece.
• RWA (real-world asset) — a real-world asset; here, the giga factory and supplies pipeline the fundraiser is tied to.
• Giga factory — the large-scale real-world asset manufacturing facility the fundraiser is tied to.
• Supplies — the real-world asset supplies (for example solar cells, battery cells, airframe ribs) presented as part of the fundraiser's framing.
• 200 billion — the fundraiser's target amount, displayed as the campaign's trophy number.
• Fundraiser Organizer — the accepted human persona who sets up and runs the campaign, defining the target and framing and tracking progress.
• Supporter / Contributor — the accepted human persona who reviews the campaign and makes a contribution, then sees progress toward the target.
• Contribution — a recorded amount contributed by a supporter toward the 200 billion target, bound to the supporter's identity.
• Progress arc — the lime arc that renders the funded portion of the 200 billion target; progress is an arc, never a rectangle.
• Trophy number — the 200 billion target rendered as a single large number in Unbounded 800, alone in a full-width band.