System Requirements Document for sneaker-unboxing

1. Introduction

sneaker-unboxing is a creator studio for producing one specific deliverable: a realistic, aesthetic sneaker unboxing video in vertical 9:16, shot as a POV clip in which hands slowly open a blue shoebox, reveal the exact white sneakers with black stripes, grey suede toe and gum sole, and gently lift the sneaker for close-up detail shots — under soft natural window sunlight, on a black fluffy rug, with smooth handheld camera movement, realistic hands, no face, no text, and a premium product-review style.

The product intent is drop-culture anticipation rather than SaaS efficiency: the shoe is the product, the interface is the packaging, and the creator is a hype-adjacent reviewer who wants their output to look like a release, not a render. Because the video itself must contain no face and no text, all typographic energy lives in the studio around the 9:16 stage.

The audience is a single active human role: the Sneaker Unboxing Creator — one person producing a vertical POV unboxing clip of a specific white low-top with black stripes, grey suede toe and gum sole, and needing the finished asset to preserve the original shoe design and box exactly.

2. System Overview

The system is a first-party web studio with application-owned identity. An anonymous visitor lands on a public entry surface that explains what the studio produces; a creator establishes identity through self-service enrollment, and returns through verification to resume durable generation and delivered-video state. Once inside, the creator composes a request (sneaker, shoebox, aspect ratio, premium product-review intent), runs the realistic POV opening and sneaker-reveal generation workflow, owns generation and review of the gently lifted sneaker close-up segment, applies the requested environmental and camera conditions (window sunlight, black fluffy rug, smooth handheld movement, realistic hands, no face, no text), and receives the finished vertical video for viewing or download.

Backend execution is required: the requested source design and box must be preserved and a finished asset produced, which is not achievable as a purely client-side interaction.

Actors

• Sneaker Unboxing Creator (active human persona) — initiates, controls, resumes and completes every accepted human-facing capability.
• Generation backend (system actor) — executes video generation and persists durable generation and delivered-video state. It is not a persona and has no independent product goal.

Narrow exclusions

• No face may appear in the generated video.
• No text may appear in the generated video.
• The original shoe design and box must be preserved exactly; the studio does not restyle, recolor or substitute the shoe or the box.
• Only realistic hands appear on camera; no visible person or head.
• The deliverable is vertical 9:16 only.

2a. Product Interpretation and Delivery Boundary

Delivery ownership. The studio is first-party custom UI owned by the application. The creator's request, generation control, close-up segment review, condition settings and final delivery all live in the application's own surfaces. Video generation itself is backend execution owned by the system; the creator interacts with it through the application's generation surface and observes its progress and result there.

Access ownership. Identity is application-owned. The public entry surface is anonymously reachable and explains the product before identity establishment. Self-service enrollment and returning verification are the two access boundaries; the protected working surfaces (Request, Generate, Details, Settings, Delivery) require an established identity so that durable generation and delivered-video state remain bound to the correct creator and can be resumed on return. The entry interaction that establishes access is never owned by a protected destination.

Current vs. future. Everything in this document is current. No future-horizon requirements were accepted in the authoritative thread; nothing here is deferred.

Boundary discipline. The studio produces the video; it does not publish, distribute, schedule or monetize it, and it does not manage a shoe catalogue, inventory, orders or shipping. Those are outside the accepted scope.

2b. Source Content Inventory

Not applicable — no reference directive in this project declares content_source authority.

2c. Page Content and Component Coverage

The page inventory is the supplied final page contract, preserved exactly and in order: Landing, Sign Up, Login, Request, Generate, Details, Settings, Delivery.

Landing

• Information / state. Anonymous public entry. States the product plainly: creators generate realistic vertical 9:16 sneaker unboxing videos — POV hands slowly opening a blue shoebox, revealing the exact white sneakers with black stripes, grey suede toe and gum sole, then gently lifting the sneaker for close-up details, under soft natural window sunlight on a black fluffy rug, with smooth handheld movement, realistic hands, no face, no text, premium product-review style. No creator-specific state is shown here.
• Primary action. Enter the studio — routes an unauthenticated visitor toward enrollment or returning verification.
• Supporting actions. Read the constraint set as quoted tag strings; view the 9:16 stage motif.
• Domain entities. None owned; the page describes the deliverable, not a stored record.
• Component responsibilities. Oversized flush-left UNBOX. headline resting on a full-width shoebox-blue band; the literal blue-bordered 9:16 stage rectangle overlapping that band and bleeding off the bottom edge; rotated punched-hole tag labels reading 9:16, POV, NO FACE, NO TEXT; a single orange GENERATE pill CTA with a blinking dot; a marquee ticker of quoted constraint strings (WHITE LEATHER, BLACK STRIPES, GREY SUEDE TOE, GUM SOLE, WINDOW LIGHT, BLACK FLUFF); hazard-stripe section dividers.
• States. Loading: static-first composition; the stage rectangle renders immediately as a drawn frame. Empty: not applicable — the page has no collection. Success: the visitor understands the deliverable and the constraint set and can proceed. Error: not applicable to a static entry surface. Recovery: not applicable.

Sign Up

• Information / state. Anonymous self-service enrollment. Explains that an established identity is what lets the creator retain and return to generated video state.
• Primary action. Create the creator's identity and enter the studio.
• Supporting actions. Move to returning verification if identity already exists.
• Domain entities. Creator identity (application-owned).
• Component responsibilities. Enrollment form with 2px-radius inputs; all-caps label tags; a single orange submit control; a link to returning verification.
• States. Loading: submit control shows in-flight state during identity creation. Empty: blank form with labels visible. Success: identity established; the creator continues into the studio. Error: invalid or incomplete input is reported inline against the offending field; an already-registered identity is reported with a route to returning verification. Recovery: the form retains entered values so the creator can correct and resubmit without re-entering everything.

Login

• Information / state. Anonymous returning verification. Explains that verification restores access to the creator's durable generation and delivered-video state.
• Primary action. Verify identity and resume.
• Supporting actions. Move to enrollment if no identity exists yet.
• Domain entities. Creator identity (application-owned).
• Component responsibilities. Verification form with 2px-radius inputs; all-caps label tags; a single orange submit control; a link to enrollment.
• States. Loading: submit control shows in-flight state during verification. Empty: blank form with labels visible. Success: identity verified; the creator resumes into the studio with prior generation and delivered-video state available. Error: unrecognized or incorrect credentials are reported without revealing which part failed; repeated failure keeps the form usable. Recovery: the creator can retry, or route to enrollment, without losing the page context.

Request

• Information / state. Protected. Collects the request details that define the clip: the sneaker, the shoebox, the aspect ratio, and the premium product-review intent. Shows the current request record and its status.
• Primary action. Submit the request and hand off to generation.
• Supporting actions. Edit request details before submission; review the constraint set that will be applied.
• Domain entities. Request record (sneaker identity, shoebox identity, aspect ratio, style intent, status), bound to the creator's identity.
• Component responsibilities. Sneaker specification fields covering the white low-top with black stripes, grey suede toe and gum sole; shoebox specification field covering the blue shoebox; aspect-ratio control fixed to vertical 9:16; premium product-review style intent; a single orange submit control; a tag block summarizing the request.
• States. Loading: the existing request record is fetched and the form renders in a pending state. Empty: no request yet — the form is blank with all labels and the fixed 9:16 value visible. Success: the request is saved and the creator is handed to generation. Error: a missing or invalid required detail is reported inline; a save failure is reported with the entered values preserved. Recovery: the creator corrects the offending field and resubmits; nothing already entered is discarded.

Generate

• Information / state. Protected. Runs the realistic POV opening and sneaker-reveal generation workflow: hands slowly opening the blue shoebox and revealing the exact white sneakers with black stripes, grey suede toe and gum sole. Shows generation progress and the resulting opening/reveal segment.
• Primary action. Start generation of the POV opening and reveal.
• Supporting actions. Watch progress; review the produced segment; re-run generation if the result does not meet the request.
• Domain entities. Generation run (status, progress, produced segment), bound to the creator's identity and to the request record.
• Component responsibilities. The 9:16 stage rectangle as the working viewport; a blinking orange record dot as the single hot accent; progress and status readouts in tabular numerals; a re-run control; a route onward to the close-up segment.
• States. Loading: generation in progress — the stage shows an active in-flight state with the record dot blinking. Empty: no generation run yet — the stage is drawn but empty, with the start control available. Success: the opening/reveal segment is produced and playable in the stage. Error: generation failure is reported on the stage with the failure reason and a re-run control. Recovery: the creator re-runs generation from the same request record without re-entering request details.

Details

• Information / state. Protected. Owns generation and review of the gently lifted sneaker close-up segment — the macro detail pass on the shoe. Shows the close-up segment and its review state.
• Primary action. Generate the close-up segment of the gently lifted sneaker.
• Supporting actions. Review the produced close-up; re-run the close-up generation; confirm the close-up preserves the original shoe design.
• Domain entities. Close-up segment (status, produced asset, review state), bound to the creator's identity and to the request record.
• Component responsibilities. The 9:16 stage rectangle showing the close-up; a single orange control for the active step; detail readouts in tabular numerals; a confirmation control that the close-up preserves the original shoe design and box.
• States. Loading: close-up generation in progress on the stage. Empty: no close-up segment yet — the stage is drawn but empty, with the generate control available. Success: the close-up segment is produced, playable, and confirmed as preserving the original shoe design. Error: generation failure is reported on the stage with a re-run control. Recovery: the creator re-runs the close-up generation; the opening/reveal segment from Generate is unaffected and remains available.

Settings

• Information / state. Protected. Applies the requested conditions to the generation: soft natural window sunlight, black fluffy rug, smooth handheld camera movement, realistic hands, no face, no text. Shows each condition and its current applied value.
• Primary action. Apply the condition set to the creator's generation.
• Supporting actions. Adjust individual conditions within the accepted set; review which conditions are locked by the source constraints.
• Domain entities. Condition set (lighting, setting, camera movement, hands, face exclusion, text exclusion), bound to the creator's identity and to the request record.
• Component responsibilities. Condition controls with 2px-radius inputs; locked indicators on the no-face and no-text conditions; all-caps label tags; a single orange apply control.
• States. Loading: current condition values are fetched and controls render pending. Empty: no saved condition set — controls show the accepted defaults for the requested look. Success: conditions are saved and applied to subsequent generation. Error: a save failure is reported with the selected values preserved. Recovery: the creator retries the apply; previously saved values remain in effect until the new set saves successfully.

Delivery

• Information / state. Protected. Provides the finished vertical video for viewing or download by the requester. Shows the completed deliverable and its state.
• Primary action. View or download the finished vertical 9:16 video.
• Supporting actions. Revisit a previously delivered video; return to the request to produce another clip.
• Domain entities. Delivered video (asset reference, aspect ratio, delivery state), bound to the creator's identity.
• Component responsibilities. The 9:16 stage rectangle playing the finished video; a download control; a tag block of the delivered clip's constraint strings; a route back to the request.
• States. Loading: the delivered asset is fetched and the stage renders pending. Empty: no delivered video yet — the stage is drawn but empty, with a route back to the request. Success: the finished vertical video plays in the stage and downloads successfully. Error: a fetch or download failure is reported with a retry control. Recovery: the creator retries the fetch or download; the delivered asset remains bound to their identity and is not lost.

3. Functional Requirements

FR-1 — Generate a realistic aesthetic sneaker unboxing video in vertical 9:16. (explicit) As a Sneaker Unboxing Creator, I should generate a realistic aesthetic sneaker unboxing video in vertical 9:16 aspect ratio, so that I have a finished clip in the format my audience watches.

• Trigger / input: the creator submits a request with the sneaker, shoebox, aspect ratio and style intent.
• Observable result: a finished vertical 9:16 video asset exists and is playable.
• Access state: protected — requires an established creator identity.
• Failure / recovery: if generation fails, the failure is reported on the generation surface with a re-run control; the request record is preserved.
• Continuation: the creator proceeds to review the produced segments and the delivered video.

FR-2 — POV camera with hands slowly opening the blue shoebox. (explicit) As a Sneaker Unboxing Creator, I should generate a POV shot in which hands slowly open the blue shoebox, so that the clip opens with the unboxing moment in first-person view.

• Trigger / input: the creator starts generation of the opening/reveal segment.
• Observable result: the produced opening segment shows a POV camera and hands slowly opening the blue shoebox.
• Access state: protected.
• Failure / recovery: a failed opening/reveal generation is reported on the generation surface with a re-run control.
• Continuation: the creator reviews the opening segment and proceeds to the close-up segment.

FR-3 — Reveal the exact white sneakers with black stripes, grey suede toe and gum sole. (explicit) As a Sneaker Unboxing Creator, I should have the reveal show the exact white sneakers with black stripes, grey suede toe and gum sole, so that the clip shows the actual shoe rather than an approximation.

• Trigger / input: the opening/reveal generation runs against the submitted sneaker specification.
• Observable result: the revealed sneaker in the produced segment matches the specified white low-top with black stripes, grey suede toe and gum sole.
• Access state: protected.
• Failure / recovery: if the reveal does not match the specified shoe, the creator re-runs generation from the same request record.
• Continuation: the creator proceeds to the close-up detail segment.

FR-4 — Gently lift the sneaker and show close-up details. (explicit) As a Sneaker Unboxing Creator, I should generate a segment in which the sneaker is gently lifted and close-up details are shown, so that the clip includes a macro detail pass on the shoe.

• Trigger / input: the creator starts generation of the close-up segment on the Details surface.
• Observable result: a produced close-up segment shows the sneaker gently lifted with close-up detail.
• Access state: protected.
• Failure / recovery: a failed close-up generation is reported on the Details surface with a re-run control; the opening/reveal segment is unaffected.
• Continuation: the creator confirms the close-up preserves the original shoe design and proceeds to delivery.

FR-5 — Soft natural window sunlight lighting. (explicit) As a Sneaker Unboxing Creator, I should have the generation lit with soft natural window sunlight, so that the clip reads as a real window-lit shoot rather than a studio render.

• Trigger / input: the creator applies the condition set on the Settings surface.
• Observable result: the produced video is lit with soft natural window sunlight.
• Access state: protected.
• Failure / recovery: if the applied lighting does not match, the creator adjusts the condition and re-applies; previously saved values remain in effect until the new set saves.
• Continuation: the applied conditions carry into subsequent generation.

FR-6 — Black fluffy rug setting. (explicit) As a Sneaker Unboxing Creator, I should have the generation set on a black fluffy rug, so that the clip's ground matches the intended look.

• Trigger / input: the creator applies the condition set on the Settings surface.
• Observable result: the produced video shows the black fluffy rug as the setting.
• Access state: protected.
• Failure / recovery: if the applied setting does not match, the creator adjusts the condition and re-applies.
• Continuation: the applied conditions carry into subsequent generation.

FR-7 — Smooth handheld camera movement. (explicit) As a Sneaker Unboxing Creator, I should have the generation use smooth handheld camera movement, so that the clip feels like a real handheld shoot.

• Trigger / input: the creator applies the condition set on the Settings surface.
• Observable result: the produced video shows smooth handheld camera movement.
• Access state: protected.
• Failure / recovery: if the applied movement does not match, the creator adjusts the condition and re-applies.
• Continuation: the applied conditions carry into subsequent generation.

FR-8 — Realistic hands. (explicit) As a Sneaker Unboxing Creator, I should have realistic hands appear in the generation, so that the unboxing reads as a genuine human action.

• Trigger / input: the creator applies the condition set on the Settings surface.
• Observable result: the produced video shows realistic hands performing the unboxing and lift.
• Access state: protected.
• Failure / recovery: if the hands do not read as realistic, the creator adjusts the condition and re-applies.
• Continuation: the applied conditions carry into subsequent generation.

FR-9 — Preserve the original shoe design and box. (explicit) As a Sneaker Unboxing Creator, I should have the original shoe design and box preserved exactly, so that the clip represents the real product without restyling.

• Trigger / input: the creator submits the sneaker and shoebox specification with the request.
• Observable result: the produced video preserves the original shoe design and box; the close-up segment is confirmed against this requirement.
• Access state: protected.
• Failure / recovery: if the produced result deviates from the original design or box, the creator re-runs generation from the same request record.
• Continuation: the creator confirms preservation and proceeds to delivery.

FR-10 — No face visible. (explicit) As a Sneaker Unboxing Creator, I should have no face visible anywhere in the video, so that the clip stays faceless as required.

• Trigger / input: the no-face condition is applied and locked in the condition set.
• Observable result: the produced video contains no visible face.
• Access state: protected.
• Failure / recovery: if a face appears, the creator re-runs generation with the locked no-face condition in effect.
• Continuation: the creator proceeds to delivery once the constraint holds.

FR-11 — No text in the video. (explicit) As a Sneaker Unboxing Creator, I should have no text anywhere in the video, so that the clip stays text-free as required.

• Trigger / input: the no-text condition is applied and locked in the condition set.
• Observable result: the produced video contains no text.
• Access state: protected.
• Failure / recovery: if text appears, the creator re-runs generation with the locked no-text condition in effect.
• Continuation: the creator proceeds to delivery once the constraint holds.

FR-12 — Premium product review style. (explicit) As a Sneaker Unboxing Creator, I should have the video produced in a premium product review style, so that the output looks like a release rather than a render.

• Trigger / input: the creator states the premium product-review style intent with the request.
• Observable result: the produced video reads as a premium product review.
• Access state: protected.
• Failure / recovery: if the style does not read as premium product review, the creator re-runs generation from the same request record.
• Continuation: the creator proceeds to delivery.

FR-13 — Self-service enrollment before protected video creation. (required_inference) As a Sneaker Unboxing Creator, I should complete self-service enrollment before protected video creation, so that my generation and delivered video state are retained and I can return to them.

• Trigger / input: an anonymous visitor chooses to enter the studio from the public entry surface.
• Observable result: a creator identity is established and the protected working surfaces become available.
• Access state: anonymous entry — the enrollment interaction is reachable without an established identity.
• Failure / recovery: invalid or incomplete input is reported inline with entered values preserved; an already-registered identity is routed to returning verification.
• Continuation: the creator continues into the studio with durable state bound to their identity.

FR-14 — Returning verification to resume durable generated video state. (required_inference) As a Sneaker Unboxing Creator, I should complete returning verification to resume or retrieve my durable generated video state, so that I can pick up prior generation and delivered video after leaving.

• Trigger / input: a returning creator submits verification from the returning-verification surface.
• Observable result: identity is verified and prior generation and delivered-video state are available again.
• Access state: anonymous entry — the verification interaction is reachable without an established identity.
• Failure / recovery: unrecognized or incorrect credentials are reported without revealing which part failed; the creator can retry or route to enrollment.
• Continuation: the creator resumes into the studio at their prior state.

FR-15 — Backend execution preserves the requested source design and produces the finished asset. (required_inference) As a Sneaker Unboxing Creator, I should have backend execution preserve the requested source design and produce the finished asset, so that the delivered video actually matches the shoe and box I specified.

• Trigger / input: the creator starts generation from the generation surface.
• Observable result: the backend produces the opening/reveal segment, the close-up segment, and the finished vertical video, preserving the specified shoe design and box.
• Access state: system process — no direct human interaction; the creator observes progress and results through the application's generation, close-up and delivery surfaces.
• Failure / recovery: a backend generation failure surfaces on the generation or close-up surface with a re-run control; the request record is preserved.
• Continuation: the produced asset becomes available for review and delivery.

4. User Personas

Sneaker Unboxing Creator

Product context. A single creator producing one specific deliverable: a realistic, aesthetic sneaker unboxing video in vertical 9:16, shot as a POV clip. Their recurring work is generating the POV unboxing clip — hands slowly opening the blue shoebox, revealing the exact white sneakers with black stripes, grey suede toe and gum sole, then gently lifting the sneaker for close-up detail shots under soft natural window sunlight on a black fluffy rug. They are hype-adjacent: they want their output to look like a release, not a render.

Primary goal. A finished, realistic vertical video that preserves the original shoe design and box, with no face and no text, in a premium product-review style.

Distinct accepted responsibilities. This role is the sole initiator and controller of every accepted capability: composing the request (sneaker, shoebox, aspect ratio, style intent), running the POV opening and reveal generation, owning generation and review of the gently lifted close-up segment, applying the environmental and camera conditions, and viewing or downloading the finished video. No other human role shares or splits this work.

Relevant inputs and decisions. The sneaker specification (white low-top, black stripes, grey suede toe, gum sole), the shoebox specification (blue shoebox), the fixed vertical 9:16 aspect ratio, the premium product-review style intent, and the condition set (window sunlight, black fluffy rug, smooth handheld movement, realistic hands, no face, no text). The creator decides when a produced segment matches the request and when to re-run generation.

Interactions with other accepted participants. The creator is the only active human participant. Their counterpart is the generation backend, which executes the video generation and persists durable state; the creator observes its progress and results through the generation, close-up and delivery surfaces and re-runs it when a result does not match. There is no other human handoff, approval or receipt in the accepted scope.

Observable success. A finished vertical 9:16 video plays in the delivery stage and downloads successfully; it shows the POV opening of the blue shoebox, the exact specified sneaker, the gently lifted close-up, window sunlight, the black fluffy rug, smooth handheld movement and realistic hands, with no face and no text, and it preserves the original shoe design and box.

5. Core User Flows

Flow 1 — Anonymous visitor understands the studio and enters

1. The visitor arrives at Landing without an established identity.
2. The page presents the oversized UNBOX. headline resting on the full-width shoebox-blue band, with the literal blue-bordered 9:16 stage rectangle overlapping it and bleeding off the bottom edge, and the rotated punched-hole tags reading 9:16, POV, NO FACE, NO TEXT.
3. The visitor reads the marquee of quoted constraint strings (WHITE LEATHER, BLACK STRIPES, GREY SUEDE TOE, GUM SOLE, WINDOW LIGHT, BLACK FLUFF) and understands what the studio produces.
4. The visitor activates the single orange GENERATE pill CTA.
5. Result: the visitor is routed to the access boundary — enrollment if they are new, returning verification if they already have an identity.
6. Next step: Flow 2 or Flow 3.

Flow 2 — New creator completes self-service enrollment

1. From Landing, the visitor arrives at Sign Up without an established identity.
2. The creator fills the enrollment form; labels are all-caps tag strings and inputs have 2px corners.
3. The creator submits using the single orange control.
4. Result: a creator identity is established and the protected working surfaces become available.
5. Failure / recovery: if input is invalid or incomplete, the error is reported inline against the offending field and the entered values are preserved so the creator can correct and resubmit. If the identity is already registered, the creator is routed to returning verification instead.
6. Next step: Flow 4 — compose the request.

Flow 3 — Returning creator verifies and resumes

1. From Landing, the returning creator arrives at Login without an established identity.
2. The creator submits verification.
3. Result: identity is verified and the creator's durable generation and delivered-video state are available again.
4. Failure / recovery: unrecognized or incorrect credentials are reported without revealing which part failed; the creator retries, or routes to enrollment, without losing page context.
5. Next step: the creator resumes at their prior state — the request record, the produced segments, or the delivered video — and continues from there.

Flow 4 — Creator composes the request

1. The creator opens Request with an established identity.
2. The creator specifies the sneaker — the white low-top with black stripes, grey suede toe and gum sole — and the blue shoebox.
3. The creator confirms the aspect ratio, fixed to vertical 9:16, and states the premium product-review style intent.
4. The creator submits using the single orange control.
5. Result: the request record is saved and bound to the creator's identity, and the creator is handed to generation.
6. Failure / recovery: a missing or invalid required detail is reported inline; a save failure is reported with the entered values preserved, and the creator corrects and resubmits without re-entering everything.
7. Next step: Flow 5 — generate the POV opening and reveal.

Flow 5 — Creator generates the POV opening and sneaker reveal

1. The creator arrives at Generate with the saved request record.
2. The creator starts generation of the realistic POV opening and sneaker-reveal workflow.
3. The 9:16 stage shows an active in-flight state with the blinking orange record dot; progress and status read in tabular numerals.
4. The generation backend executes the work, preserving the specified shoe design and box.
5. Result: the produced segment plays in the stage — a POV camera with hands slowly opening the blue shoebox, revealing the exact white sneakers with black stripes, grey suede toe and gum sole.
6. Failure / recovery: if generation fails, the failure is reported on the stage with the reason and a re-run control; the creator re-runs from the same request record without re-entering request details.
7. Next step: Flow 6 — generate and review the close-up segment.

Flow 6 — Creator generates and reviews the gently lifted close-up

1. The creator arrives at Details with the opening/reveal segment already produced.
2. The creator starts generation of the close-up segment.
3. The 9:16 stage shows the close-up generation in progress.
4. Result: the produced close-up segment plays in the stage, showing the sneaker gently lifted with close-up detail.
5. The creator reviews the close-up and confirms it preserves the original shoe design and box.
6. Failure / recovery: if the close-up generation fails, the failure is reported on the stage with a re-run control; the creator re-runs it, and the opening/reveal segment from Generate is unaffected and remains available.
7. Next step: Flow 7 — apply the requested conditions, or Flow 8 — receive the finished video.

Flow 7 — Creator applies the requested conditions

1. The creator opens Settings with an established identity.
2. The creator reviews the condition set: soft natural window sunlight, black fluffy rug, smooth handheld camera movement, realistic hands, and the locked no-face and no-text conditions.
3. The creator adjusts the conditions within the accepted set and applies them with the single orange control.
4. Result: the conditions are saved and applied to subsequent generation.
5. Failure / recovery: a save failure is reported with the selected values preserved; previously saved values remain in effect until the new set saves successfully, and the creator retries.
6. Next step: the creator returns to Flow 5 or Flow 6 to regenerate with the applied conditions.

Flow 8 — Creator receives the finished vertical video

1. The creator opens Delivery with an established identity and a completed generation.
2. The finished vertical 9:16 video plays in the stage, with the delivered clip's constraint strings shown as tags.
3. The creator views the video and downloads it.
4. Result: the finished vertical video is viewed and downloaded successfully; it preserves the original shoe design and box, contains no face and no text, and reads as a premium product review.
5. Failure / recovery: a fetch or download failure is reported with a retry control; the delivered asset remains bound to the creator's identity and is not lost.
6. Next step: the creator returns to Request to produce another clip, or leaves and later resumes via Flow 3.

6. Visuals Colors and Theme

Muse and headline. Virgil Abloh — industrial label language for a premium sneaker unboxing studio. The headline idea: the product is the shoe, the interface is the packaging. The shoebox is literally the design system: industrial tags, quoted labels, hazard stripes, exposed seams, safety orange on concrete grey.

Mode. Dark mode only.

Colour tokens (exact hex, by role).

Ratio. Roughly 70% black/grey, 22% box blue, 8% orange. Nothing is a gradient; every field is a flat plane separated by a hairline or a stripe.

Typography.

• Headings: Archivo Black, all-caps, 900 weight, tracking +0.02em at display sizes and +0.14em at label sizes, quoted with literal quotation marks ('UNBOX.', '9:16', 'NO FACE'), tight leading 0.92 so stacked lines lock together like a shipping label. Display sizes: clamp(52px, 11vw, 168px) for the hero word, clamp(28px, 5vw, 56px) for section heads. Never sentence case, never medium weight.
• Body: Space Grotesk.
• Scale: 1.414 modular — 168 / 96 / 56 / 28 / 18 / 15 px. Body copy 18px/1.6; labels 15px/1.4 all-caps +0.14em; data numerals in Space Grotesk tabular.

Shape language. Hard 0px corners on type blocks and colour fields; 2px on inputs; 999px only for the single record pill. Everything reads as packaging: hairline 1px rules at #2A2A2A, 8px hazard-stripe bands, exposed 1px grid lines that run past content edges, tag rectangles with a punched 6px hole, and a diagonal cut (clip-path polygon) on one corner of media cards. No soft shadows, no glass, no rounded cards.

Spacing rhythm. Sections are separated by full-bleed hazard-stripe rules rather than whitespace. A vertical-first 9:16 stage column (max 420px) is centred on a 12-column desktop grid, flanked left by a fixed rail of rotated label text and right by a metadata block of tag strings. At 375px the stage goes full-bleed and the rails collapse into a top ticker and a bottom tag row; at 768px the stage sits left with metadata stacked right; at 1280px the three-column label/stage/metadata arrangement appears.

Imagery style. Real product photography only, shot as evidence: the blue shoebox lid mid-lift, the white sneaker with black stripes and grey suede toe on black fluff, macro of the gum sole edge, a hand entering frame from the bottom. All images sit inside flat colour blocks with hard crops and 1px borders; some are half-covered by a hazard stripe or a quoted label tag as if the frame were taped. No illustration, no 3D blobs, no stock people, no faces.

Accessibility. Readable text and controls stay whole at 375px, 768px and 1280px — headlines, wordmarks, labels, numbers, card text and controls stay entirely inside the viewport and their container, 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, provided they cover no readable text or control.

7. Signature Design Concept

The first screen is not a centred SaaS hero — it is a shipping label.

A full-bleed #121212 ground carries an oversized 'UNBOX.' in Archivo Black at clamp(52px, 11vw, 168px), flush-left, its baseline sitting directly on a solid #1B4FD8 band that spans the full viewport width and is 18% of the screen height. The vertical 9:16 video stage overlaps that blue band on the right and bleeds off the bottom edge of the viewport, wrapped in a 2px #1B4FD8 border with a punched-hole tag label reading '9:16 / POV / NO FACE' rotated 90° along its left edge. Bottom-left sits a single #FF4D00 pill CTA 'GENERATE' with a blinking dot, and beneath it a horizontal marquee of quoted constraints. The dominant element is the type-and-colour-block stack, not the video.

Signature moves, implementable as specified:

• Oversized flush-left 'UNBOX.' headline whose baseline rests on a full-width #1B4FD8 colour band that the 9:16 video stage overlaps and bleeds off the bottom edge.
• Every label is a physical tag: all-caps Archivo Black inside a 1px-bordered rectangle with a punched 6px hole, rotated 90° along the left edge of the video stage, reading '9:16', 'POV', 'NO FACE', 'NO TEXT'.
• Hazard-stripe section dividers (8px diagonal #FF4D00 / #121212 bands) replace whitespace between every major section, and the primary CTA is the only orange element on its screen.
• The 9:16 viewport is drawn as a literal blue-bordered phone rectangle that scales 0.86 → 1.0 and thickens its border on scroll, so the deliverable's aspect ratio is the page's structural motif.
• A continuous marquee ticker of quoted constraint strings ('WHITE LEATHER', 'BLACK STRIPES', 'GREY SUEDE TOE', 'GUM SOLE', 'WINDOW LIGHT', 'BLACK FLUFF') crossing the viewport edge, wrapping to static rows under prefers-reduced-motion.

Avoid. Any gradient, glassmorphism, blur panel or soft drop shadow; rounded 16–24px cards with hover-lift in a grid; blue-on-white or indigo primary buttons — the blue here is a flat field (#1B4FD8), never a button fill on a white ground; Inter, Roboto, Helvetica, Poppins or system-ui for headings or body; faces, models or any human head in photography (hands only, entering from the bottom edge); readable text baked into the video frame — all type lives in the studio UI around the 9:16 stage; centred headline + subtext + button hero composition; more than one orange element visible per screen. The generic indigo/blue-on-white SaaS template is forbidden for this project.

8. Interaction Model & Motion Direction

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

Landing Hero Motion Brief

• Focal subject. The type-and-colour-block stack: the oversized flush-left 'UNBOX.' headline whose baseline rests on the full-width #1B4FD8 band, with the blue-bordered 9:16 stage rectangle overlapping that band and bleeding off the bottom edge of the viewport.
• Input → transformation → outcome thesis. As the visitor scrolls, the 9:16 stage scales from 0.86 to 1.0 and its blue border thickens — the deliverable's aspect ratio literally drawing itself into the page — while the marquee of quoted constraint strings ('WHITE LEATHER', 'BLACK STRIPES', 'GREY SUEDE TOE', 'GUM SOLE', 'WINDOW LIGHT', 'BLACK FLUFF') crosses the viewport edge continuously. The outcome is a first frame that reads as packaging: the visitor understands the format and the constraints before reading a single sentence.
• Motion vocabulary. Snappy and mechanical, ceiling expressive: 140–220ms cubic-bezier(0.2, 0.8, 0.2, 1) for entrances, hard cuts rather than fades, a continuous horizontal marquee ticker of quoted tag strings, a stamp-in scale (1.06 → 1.0 with 2px overshoot) on the primary CTA, and a blinking orange record dot.
• Composed first frame. Full-bleed #121212; 'UNBOX.' flush-left at clamp(52px, 11vw, 168px) with its baseline on the #1B4FD8 band; the 9:16 stage overlapping the band on the right and bleeding off the bottom edge, wrapped in a 2px #1B4FD8 border with the rotated punched-hole tag '9:16 / POV / NO FACE' along its left edge; bottom-left the single #FF4D00 'GENERATE' pill with its blinking dot; beneath it the marquee of quoted constraints.
• Reduced-motion state. Under prefers-reduced-motion all marquees become static wrapped rows, the stage renders at 1.0 with no scroll scaling, the record dot stops blinking, and the CTA appears at its final scale — the same composition, fully readable and fully operable.

9. Non-Functional Requirements

NFR-1 — Vertical 9:16 aspect ratio. (explicit) The generated video must be vertical 9:16. This is a hard constraint on the deliverable, not a preference; the studio's layout treats the 9:16 stage as its structural motif. Rationale: the source states the aspect ratio explicitly.

NFR-2 — No face visible in the video. (explicit) The generated video must contain no visible face. Rationale: explicit hard constraint in the authoritative source.

NFR-3 — No text in the video. (explicit) The generated video must contain no text. All typographic energy lives in the studio UI around the 9:16 stage. Rationale: explicit hard constraint in the authoritative source.

NFR-4 — Preserve the original shoe design and box exactly. (explicit) The generated video must preserve the original shoe design and box; the studio must not restyle, recolor or substitute them. Rationale: explicit hard constraint in the authoritative source.

NFR-5 — Realistic hands only. (explicit) Only realistic hands may appear on camera; no visible person or head. Rationale: explicit hard constraint in the authoritative source.

NFR-6 — Durable generation and delivered-video state. (required_inference) Generation runs and delivered videos must persist and remain bound to the creator's identity so that a returning creator can resume or retrieve them. Rationale: required to make the accepted resume-and-retrieve journey executable.

NFR-7 — Backend execution for video generation. (required_inference) Video generation must execute server-side; preserving the requested source design and producing the finished asset is not achievable as a purely client-side interaction. Rationale: required to make the accepted generation capability executable.

NFR-8 — Readable text and controls stay whole. (explicit, from the creative direction) At 375px, 768px and 1280px, headlines, wordmarks, labels, numbers, card text and controls must stay entirely inside the viewport and their container, wrapping or scaling to fit, with no other element covering any part of them. Moving and scrollable content may cross the viewport or container edge by design, provided every item becomes fully readable as it passes; under prefers-reduced-motion a usable static arrangement must be provided. Rationale: explicit accessibility rule in the creative direction.

NFR-9 — Reduced-motion support. (explicit, from the creative direction) Under prefers-reduced-motion, all marquees become static wrapped rows and the 9:16 stage renders at 1.0 with no scroll scaling. Rationale: explicit motion rule in the creative direction.

10. Tech Stack

• Frontend: React (web), single-page studio with the eight surfaces in the page contract.
• Backend: Python / FastAPI, extended with routes and modules for the request record, generation orchestration, condition set, and delivery of the finished asset. One shared backend process — no separate service is warranted for the current product.
• Storage: a relational database for creator identity, request records, generation runs, close-up segments, condition sets and delivered-video references; object storage for produced video assets.
• Containerization: Docker with docker-compose.yml as the runnable-service inventory — the frontend and the single backend, plus the database. Video generation runs inside the existing backend process; a separate queue worker is added only if generation latency requires asynchronous execution, in which case it is a distinct process in the same compose file.
• Kubernetes: not required for the current product; deployment does not demand it.

11. Assumptions and Constraints

Assumptions

• A-1 (narrow). The creator supplies the sneaker and shoebox specification as descriptive input; the studio does not maintain a shoe catalogue, inventory, orders or shipping. No accepted requirement asks for these.
• A-2 (narrow). "Preserve the original shoe design and box" is satisfied by generating against the creator's submitted specification and by the creator's confirmation on the close-up segment; no external product database is assumed.
• A-3 (narrow). The creator is the only active human participant; the generation backend is a system actor with no independent product goal.
• A-4 (narrow). Application-owned identity is used solely for continuity of the creator's own durable state. No differentiated permissions, roles or shared-state visibility controls are established by the source, and none are introduced.
• A-5 (narrow). The studio produces the video; it does not publish, distribute, schedule or monetize it.

Constraints

• Vertical 9:16 aspect ratio only.
• No face visible in the video.
• No text in the video.
• The original shoe design and box must be preserved exactly.
• Realistic hands only; no visible person or head.
• The generic indigo/blue-on-white SaaS template is forbidden for this project.
• No gradients, glassmorphism, blur panels or soft drop shadows; no rounded 16–24px cards with hover-lift in a grid; no Inter, Roboto, Helvetica, Poppins or system-ui for headings or body; no faces or models in photography; no readable text baked into the video frame; no centred headline + subtext + button hero composition; no more than one orange element visible per screen.

Presentation and technology defaults [Default — not specified by user]

• Exact database engine and object-storage provider are not specified by the user; a relational database plus object storage is assumed as the practical minimum for durable generation and delivered-video state.
• Exact authentication mechanism (session cookie vs. token) is not specified by the user; either satisfies the accepted enrollment and returning-verification boundaries.
• Exact video-generation model or provider is not specified by the user; the requirement is the observable result — a realistic vertical 9:16 clip preserving the specified shoe and box, with no face and no text.

12. Glossary

• Sneaker Unboxing Creator — the single active human persona; the person producing the vertical POV unboxing clip.
• Vertical 9:16 — the required aspect ratio of the deliverable; also the studio's structural layout motif, drawn as a literal blue-bordered stage rectangle.
• POV — point-of-view camera framing in which the viewer sees the unboxing as the creator's own hands would.
• Blue shoebox — the specific box opened in the clip; its blue is the studio's primary colour field (#1B4FD8).
• The exact sneaker — the white low-top with black stripes, grey suede toe and gum sole that the reveal and close-up must show.
• Gum sole — the translucent amber rubber outsole of the specified sneaker.
• Close-up segment — the portion of the clip in which the sneaker is gently lifted and its details are shown in macro.
• Condition set — the applied generation conditions: soft natural window sunlight, black fluffy rug, smooth handheld camera movement, realistic hands, no face, no text.
• Request record — the creator's saved specification of sneaker, shoebox, aspect ratio and style intent, bound to their identity.
• Generation run — one execution of the backend video-generation workflow against a request record.
• Delivered video — the finished vertical 9:16 asset available for viewing or download on the Delivery surface.
• Hazard stripe — the 8px diagonal #FF4D00 / #121212 band used as a section divider in place of whitespace.
• Tag label — an all-caps Archivo Black label inside a 1px-bordered rectangle with a punched 6px hole, rotated 90° along the left edge of the 9:16 stage.