marine-atom

byPoshmark Support

1 slide for atom

Atom Slide
Atom Slide

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Atom

1. Introduction

Atom is a single-slide science explainer about the atom. The product exists to give a casual public viewer one calm, self-contained frame that shows what an atom is made of — the nucleus, the shells, and the electrons — and states a few clear facts alongside it. There is exactly one slide, and that slide is the whole product.

The audience is the casual viewer who arrives with no prior context and no account: a member of the public curious about the atom, reading the slide once, in one sitting, on whatever screen they have. The experience is a public entry surface, not a course, a tool, or a library of content.

This document is the System Requirements Document for Atom. It records the accepted product intent, the single-slide constraint, the one public page, the viewer's journey, and the visual and technical direction that make the slide legible and calm.

Page 1 of 20

2. System Overview

Atom delivers one full-viewport slide about the atom. The slide is the public entry and the only destination. A viewer opens it, reads a headline, sees a live generative atom rendered in real time, and reads three short fact rows. Nothing else is required of them, and nothing else is offered.

The product has one active human actor, the Slide Viewer, who reads the slide and takes away a short science explainer. There are no other human participants: no author, editor, moderator, or administrator is part of the accepted product. The only non-human actor is the rendering runtime that draws the atom on the viewer's device.

Delivery is a first-party custom web UI: a React frontend that renders the slide, a shared FastAPI backend that serves the slide's content, and a MariaDB database that holds that content. The backend and database exist to serve the one slide's facts; they do not introduce accounts, roles, or user-generated content.

Removed from scope

  • Multiple slides, slide decks, slide navigation, or slide sequencing (also: carousel, pager, deck).
  • Any account, sign-in, profile, or saved state for the viewer.
  • Any editing, authoring, or content-management surface for the slide.
  • Any quiz, assessment, or interactive exercise about the atom.
Page 2 of 20

2a. Product Interpretation and Delivery Boundary

Atom is a public, read-only explainer. The single slide is anonymously reachable: a viewer needs no identity, no invitation, and no setup to read it. Because the viewer's work is a one-time read with no durable personal state, no commitment, and no value transfer bound to a person, the product establishes no application-owned identity and no session continuity. There is no sign-in, no registration, and no returning verification.

The one-slide limit is a hard product boundary, not a starting point. The current delivery is exactly one page, Atom Slide, which is both the public entry and the slide itself. There is no separate landing page, no index, and no "next" destination. The call to action on the slide ("Read the slide") moves the viewer within the same single frame to the fact content; it does not open a second page.

The backend and database are delivery infrastructure for the slide's content, not a viewer-facing capability. Future ideas about additional slides or deeper material are out of scope for this delivery and are not represented in any current page.

2c. Page Content and Component Coverage

Page 3 of 20

Atom Slide

The single public page. It is one full-viewport frame, anonymously reachable, with no navigation away from it.

Information and state

  • Headline: "One atom, one slide".
  • Subline: "See the nucleus, the shells and the electrons that make all matter."
  • Call to action: "Read the slide".
  • Three fact rows, each pairing a number in Space Grotesk with a small uppercase label and a thin divider. The rows carry short, factual statements about the atom (for example, the count of protons in the simplest atom, the number of electrons that fill the first shell, and the scale of the nucleus relative to the atom). The exact fact values are served by the backend as the slide's content.
  • A live generative atom: mint electron rings and paths, an orange nucleus, and drifting dust particles on the near-black ground.
  • Page states: loading (the slide's facts are being fetched), success (facts and the live atom are shown), error (facts could not be loaded), and reduced-motion (a static arrangement of the atom and facts).

Primary actions

  • Read the slide: the viewer reads the headline, subline, and fact rows. The call to action brings the fact content into view within the same frame.

Supporting actions

  • None that change product state. The viewer may scroll within the single frame if the viewport is short; this is layout behavior, not a separate destination.
Page 4 of 20

Domain entities

  • Slide: the single slide, identified as the only slide in the product. Holds the headline, subline, call-to-action label, and the ordered set of fact rows.
  • Fact row: an ordered item on the slide with a numeric value, a short uppercase label, and a position in the row order.

Component responsibilities

  • Hero canvas: renders the generative atom — mint rings and electron paths, an orange nucleus, and drifting dust — as a full-bleed near-black field occupying the right two thirds of the frame. Runs a slow continuous electron orbit and a soft light sweep across the rings every eight seconds. Honors prefers-reduced-motion by presenting a static arrangement.
  • Headline block: left column, flush left over a hairline rule, with a 12px uppercase label above a large quiet sentence-case headline in Space Grotesk.
  • Subline: body copy in IBM Plex Sans beneath the headline.
  • Call to action: the "Read the slide" control, kept whole and legible at every viewport.
  • Fact rows: three rows, each with a number in Space Grotesk, a small uppercase label, and a thin divider; separated by hairlines.
  • Content loader: fetches the slide's facts from the backend and drives the loading, success, and error states.
Page 5 of 20

States

  • Loading: the headline and subline render immediately; the fact rows show a quiet placeholder while the slide content is fetched.
  • Empty: not applicable — the product has exactly one slide with fixed content; if the backend returns no fact rows, the page shows the headline and subline with an inline notice that the facts are unavailable.
  • Success: headline, subline, call to action, three fact rows, and the live atom are all shown.
  • Error: if the slide content cannot be loaded, the page keeps the headline, subline, and live atom, and shows a short inline message with a retry control that re-requests the slide content.
  • Reduced motion: the atom is drawn as a static composition and the light sweep and orbit are not animated; all text and controls remain fully readable.
Page 6 of 20

3. Functional Requirements

FR-1 — One slide about the atom As a Slide Viewer, I should see exactly one slide about the atom, so that the whole product is a single self-contained frame.

  • Provenance: explicit.
  • Lifecycle: the viewer opens the product's only page; the slide renders as one full-viewport frame; there is no navigation to any other slide or page.
  • Acceptance: the product exposes exactly one page, Atom Slide; no slide navigation, pager, or deck control is present.
  • Failure/recovery: not applicable — there is no alternate slide to fail over to.
  • Continuation: the viewer reads the slide and leaves.

FR-2 — Science explainer content on the slide As a Slide Viewer, I should get a short science explainer of the atom on the slide, so that I understand the nucleus, the shells, and the electrons.

  • Provenance: explicit.
  • Lifecycle: the viewer opens the slide; the headline, subline, and three fact rows present the explainer; the live atom illustrates the structure described.
  • Acceptance: the slide shows the headline "One atom, one slide", the subline "See the nucleus, the shells and the electrons that make all matter.", and three fact rows, each with a number, a short uppercase label, and a thin divider.
  • Failure/recovery: if the fact content cannot be loaded, the headline and subline remain and an inline message with a retry control is shown (see FR-4).
  • Continuation: the viewer finishes reading the fact rows.
Page 7 of 20

FR-3 — Read the slide As a Slide Viewer, I should be able to act on "Read the slide" to reach the fact content, so that the explainer is easy to enter.

  • Provenance: explicit (entry hero copy).
  • Lifecycle: the viewer sees the call to action in the left column; activating it brings the fact rows into view within the same single frame.
  • Acceptance: the control is labeled "Read the slide", stays whole and legible at 375px, 768px, and 1280px, and does not navigate to a second page.
  • Failure/recovery: not applicable — the action is local to the frame.
  • Continuation: the viewer reads the fact rows.

FR-4 — Slide content loading and recovery As a Slide Viewer, I should still get a usable slide if its facts are slow or fail to load, so that the explainer is never a blank frame.

  • Provenance: required_inference (indispensable mechanics for serving the slide's facts from the backend).
  • Lifecycle: the page requests the slide content on open; on success the fact rows render; on failure the headline, subline, and live atom remain and an inline message with a retry control appears; retry re-requests the content.
  • Acceptance: loading shows a quiet placeholder in the fact-row area; error shows an inline message and a working retry control; success shows the three fact rows.
  • Failure/recovery: retry re-requests the slide content and restores the fact rows on success.
  • Continuation: the viewer reads the slide once content is present.
Page 8 of 20

FR-5 — Live generative atom As a Slide Viewer, I should see a live generative atom on the slide, so that the structure of the atom is shown rather than only described.

  • Provenance: explicit (creative direction: WebGL hero, slow orbit, light sweep).
  • Lifecycle: the hero canvas renders on open; electrons orbit slowly and a soft light sweep crosses the rings every eight seconds; with prefers-reduced-motion the atom is drawn as a static composition.
  • Acceptance: the atom shows mint rings and electron paths, an orange nucleus, and drifting dust on a near-black ground; motion is slow and continuous; reduced-motion yields a static, fully readable arrangement.
  • Failure/recovery: if the real-time renderer is unavailable, the slide falls back to a static rendering of the atom so the explainer remains complete.
  • Continuation: the viewer reads the slide alongside the atom.

4. User Personas

Page 9 of 20

Slide Viewer

Product context. The Slide Viewer is a member of the casual public who arrives at Atom with no account and no prior context. They have one frame in front of them and a short amount of attention to give it. They are not a student following a curriculum and not a researcher checking a source; they want a clear, calm answer to "what is an atom made of?"

Primary goal. Understand, in one read, that an atom has a nucleus, shells, and electrons, and take away a few concrete facts about them.

Distinct accepted responsibilities. The Slide Viewer is the only human actor. Their work is to open the single slide, read the headline and subline, look at the live atom, and read the three fact rows. They make no decisions that change product state, submit nothing, and own no durable record. This is what makes the role different from a typical application user: there is no account, no history, and no return visit to resume.

Relevant inputs or decisions. The viewer's only input is choosing to open the slide and, optionally, activating "Read the slide" to bring the facts into view. They decide when they have read enough and leave.

Interactions with other accepted participants. None. There is no author, editor, or other viewer interaction in the accepted product. The only counterpart is the rendering runtime that draws the atom and the backend that serves the facts, neither of which the viewer addresses directly.

Observable success. The viewer has seen the headline, the subline, the live atom, and all three fact rows, fully legible, on their viewport — and can state what the nucleus, the shells, and the electrons are.

5. Core User Flows

Page 10 of 20

Flow 1 — Read the one slide

  1. Start. The Slide Viewer opens Atom's only page, Atom Slide, anonymously. No sign-in or setup is required.
  2. Frame appears. The near-black full-viewport frame renders. The left column shows a 12px uppercase label above the hairline rule, the headline "One atom, one slide" in Space Grotesk, and the subline "See the nucleus, the shells and the electrons that make all matter." in IBM Plex Sans.
  3. Atom renders. The hero canvas draws the generative atom on the right two thirds: mint rings and electron paths, an orange nucleus, and drifting dust. Electrons orbit slowly and a soft light sweep crosses the rings every eight seconds.
  4. Content loads. The page requests the slide's facts from the backend. While loading, the fact-row area shows a quiet placeholder.
  5. Facts appear. On success, three fact rows render, each pairing a number in Space Grotesk with a small uppercase label and a thin divider.
  6. Viewer reads. The viewer reads the headline, subline, and fact rows, optionally activating "Read the slide" to bring the facts into view within the same frame.
  7. Completion. The viewer has read the whole slide and leaves. There is no next page and no saved state.

Failure and recovery. If the facts fail to load, the headline, subline, and live atom remain, and an inline message with a retry control appears in the fact-row area. The viewer activates retry, the page re-requests the slide content, and the fact rows render on success. If the real-time renderer is unavailable, the atom is shown as a static composition so the explainer stays complete.

Reduced motion. With prefers-reduced-motion, the atom is drawn as a static arrangement and the orbit and light sweep do not animate; all text and controls remain fully readable and the flow completes identically.

Page 11 of 20

6. Visuals Colors and Theme

The visual direction is Data made physical for one atom slide, after the muse Refik Anadol: a luminous field of data turned into a calm, museum-grade frame.

Mode. Dark mode only.

Color tokens (exact hex, by role)

  • Background / ground: #07090C — near-black, holds roughly 80% of the frame.
  • Surface: #101720 — used sparingly for the fact-row area and any inline notice.
  • Text: #F2F6F8 — headline, subline, fact values, labels.
  • Primary: #5FE3C0 — cyan-mint; electron paths and rings.
  • Accent: #FF7A45 — orange; the nucleus and key numbers only.
  • Muted: #8A99A6 — secondary labels and dividers.

Typography

  • Headings: Space Grotesk, Light to medium weights, wide tracking on labels, large quiet headline in sentence case.
  • Body: IBM Plex Sans.
  • Scale: 1.25 modular — 72 / 56 / 40 / 24 / 16 / 14, with 12px uppercase labels.
  • The 72px headline scales down with clamp(...) so it stays whole at 375px, 768px, and 1280px.

Shape language. Soft radial rings and thin luminous strokes. The nucleus is a tight cluster of small spheres. No hard cards.

Page 12 of 20

Layout. One full-viewport slide. The generative atom sits center-right and fills the right two thirds. A left column carries the headline and three short fact rows with hairlines.

Spacing rhythm. Generous, museum-like margins; hairline rules separate fact rows; the left column is flush left with a consistent vertical rhythm between label, headline, subline, and rows.

Imagery style. A generative particle field forms the atom; fine dust particles drift on the dark ground. No stock photography.

Motion. Slow continuous orbit of electrons; a soft light sweep crosses the rings every eight seconds. No scroll-linked morph — the slide is one frame.

Avoid. No gradient blob behind centered text; no blue or indigo accent; no grid of identical cards; no stock photography of people; no bouncy or playful motion. The generic indigo/blue-on-white SaaS template is forbidden.

Page 13 of 20

7. Signature Design Concept

The public entry is a single full-bleed near-black canvas. A large glowing atom — mint rings and electron paths around an orange nucleus — fills the right two thirds of the first screen, with fine dust drifting across the dark ground. The left third holds the headline flush left over a hairline rule, with a 12px uppercase label above it, the subline beneath, and three fact rows below that, each pairing a number in Space Grotesk with a small uppercase label and a thin divider.

The signature moves, recomposed only from accepted content and controls:

  • A live particle atom in mint and orange fills the right of the first screen.
  • The headline sits flush left over a hairline rule with a 12px uppercase label above it.
  • Fact rows pair a number in Space Grotesk with a small uppercase label and a thin divider.
  • A slow light sweep passes the electron rings and dims the ground behind it.

The entry hero copy is the accepted copy: headline "One atom, one slide", subline "See the nucleus, the shells and the electrons that make all matter.", call to action "Read the slide". The call to action brings the fact rows into view within the same frame; it does not open a second page.

Page 14 of 20

8. Interaction Model & Motion Direction

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

Landing Hero Motion Brief

  • Focal subject. The generative atom: mint electron rings and paths around a tight orange nucleus, with fine dust drifting on the near-black ground.
  • Input → transformation → outcome thesis. On load, the atom assembles from drifting dust into a stable nucleus and orbiting rings; the electrons then orbit slowly and continuously, and a soft light sweep crosses the rings every eight seconds, dimming the ground behind it. The outcome is a calm, living diagram of the atom that the viewer reads alongside the facts.
  • Motion vocabulary. Slow continuous orbit; soft eight-second light sweep; drifting dust; no scroll-linked morph; no bounce or playfulness.
  • Composed first frame. Near-black full-bleed ground; the atom already present on the right two thirds with the nucleus lit orange and the rings mint; the left column holding the uppercase label, the 72px headline, the subline, and the three fact rows with hairlines.
  • Reduced-motion state. With prefers-reduced-motion, the atom is drawn as a static composition — nucleus, rings, and dust held still — and the orbit and light sweep do not animate. All text and controls remain fully readable and the slide is complete.

Landing Hero 3D Scene Brief — DIRECTION-DERIVED

Page 15 of 20

A single real-time WebGL scene (React Three Fiber) renders the atom as the hero subject: a tight cluster of small spheres for the orange nucleus, thin luminous mint rings for the shells, and small mint particles traveling the rings as electrons. A particle field of fine dust drifts across the dark ground. The scene is lit to keep the near-black ground dominant, with the mint glow marking the electron paths and the orange reserved for the nucleus and key numbers. The scene runs a slow continuous orbit and an eight-second light sweep, and renders a static composition under reduced motion.

Page 16 of 20

9. Non-Functional Requirements

  • Single-slide constraint. The product has exactly one slide and one page. No additional slides, pages, or navigation may be added. (explicit)
  • Public, anonymous access. The slide is reachable without identity, account, or setup; no authentication is required to read it. (explicit via access requirement none)
  • Readability at every viewport. Headlines, wordmarks, labels, numbers, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (for example font-size: clamp(...)) to fit; no other element covers any part of them. (explicit)
  • Reduced motion. With prefers-reduced-motion, the slide provides a usable static arrangement with all text and controls readable. (explicit)
  • Performance. The hero renders in real time without blocking the text; the headline and subline are readable before the atom finishes assembling. (required_inference)
  • Graceful degradation. If the real-time renderer is unavailable, a static rendering of the atom keeps the explainer complete. (required_inference)
  • Content availability. The slide's facts are served by the backend; a failure shows an inline message and a retry control rather than a blank frame. (required_inference)
  • Accessibility. Text meets contrast against the near-black ground; the call to action is keyboard reachable and has a visible focus state. (required_inference)
Page 17 of 20

10. Tech Stack

  • Frontend. React application UI, rendering the single Atom Slide page. The hero atom is rendered with React Three Fiber / WebGL per the creative direction. Typography uses Space Grotesk and IBM Plex Sans.
  • Backend. Shared FastAPI process serving the slide's content (headline, subline, call-to-action label, and ordered fact rows) as application APIs and domain modules. No additional service is needed for this product.
  • Database. MariaDB holding the single slide and its ordered fact rows.
  • Infrastructure. Docker / docker-compose with the three provisioned services: frontend, backend, and database. No Kubernetes is required for this single-slide product.
Page 18 of 20

11. Assumptions and Constraints

  • One slide, one page. The exact one-slide limit is a hard constraint; the single page Atom Slide is both the public entry and the slide. (explicit)
  • No identity. The viewer reads anonymously; the product establishes no account, session, or saved state. (explicit access requirement none)
  • Fact content. The three fact rows carry short, factual statements about the atom; their exact values are the slide's content served by the backend. The specific values are not fixed by the source and are treated as content, not as new capability. (required_inference)
  • Call to action scope. "Read the slide" brings the fact content into view within the same single frame; it does not navigate to a second page. (required_inference, consistent with the one-slide constraint)
  • Dark mode only. The palette is dark mode; no light theme is specified. (explicit)
  • No authoring. There is no editing, authoring, or content-management surface; the slide's content is fixed product content. (explicit exclusion)
Page 19 of 20

12. Glossary

  • Atom — The subject of the slide: a nucleus of protons and neutrons surrounded by shells of electrons.
  • Slide — The single full-viewport frame that is the entire product.
  • Atom Slide — The one page of the product; the public entry and the slide itself.
  • Slide Viewer — The single active human actor who reads the slide.
  • Fact row — An ordered item on the slide pairing a number in Space Grotesk with a small uppercase label and a thin divider.
  • Hero canvas — The full-bleed real-time rendering of the generative atom on the right two thirds of the slide.
  • Light sweep — The soft light that crosses the electron rings every eight seconds and dims the ground behind it.
  • Reduced motion — The prefers-reduced-motion state in which the atom is drawn as a static composition.
Page 20 of 20
Live
Atom Slide design preview

Atom Slide: Open slide anonymously

Atom Slide: Read headline and subline

Atom Slide: Watch live atom render

Atom Slide: Wait for facts placeholder

Atom Slide: Activate Read the slide

Atom Slide: Read three fact rows

Atom Slide: Activate retry control

Atom Slide: Read facts unavailable notice

Atom Slide: Finish reading and leave

Live
Atom Slide design preview

Atom Slide: Open slide anonymously

Atom Slide: Read headline and subline

Atom Slide: Watch live atom render

Atom Slide: Wait for facts placeholder

Atom Slide: Activate Read the slide

Atom Slide: Read three fact rows

Atom Slide: Activate retry control

Atom Slide: Read facts unavailable notice

Atom Slide: Finish reading and leave