Data and Packets Flow is a browser-based product that presents a 3D working model of data and packet flow. The user supplies a source, and the product renders that source's data and packets moving through a three-dimensional scene: nodes, links, and packets in motion, inspectable by the viewer.
The product intent is joyful technical discovery. The audience is network-curious viewers — people who want to see how data moves in three dimensions and to touch it, rather than read about it in a diagram. The model is the product: a full-bleed, playable 3D scene is the first screen, not a picture of one.
The requester, Gajalafirdos S, asked for a 3D working model of data and packet flow from a supplied source. This document specifies that product.
The product is a first-party web application with two current destinations:
Both destinations are public and require no account or sign-in. There is no application-owned identity, no private per-user state to resume, and no differentiated permissions: the model is a shared, inspectable visualization, and nothing in the accepted requirements creates a durable relationship, entitlement, or value transfer bound to a particular person. The viewer's source selection and inspection state live in the working session of the Model page.
The 3D scene is rendered in the browser with real-time WebGL. The shared backend serves the application's APIs and domain modules; the database stores application-owned persistent data. Neither the backend nor the database adds product behavior beyond what is specified in Section 3.
Everything specified here is current. No future-horizon capabilities are accepted.
Not applicable — no reference directive supplies a content_source.
Information and state
Primary action
Supporting actions
Domain entities
Component responsibilities
clamp(40px, 9vw, 112px), positioned lower left over the scene, never centred; subline in Nunito; call-to-action control. Stays whole and uncovered at 375px, 768px, and 1280px.States
Information and state
Primary action
Supporting actions
Domain entities
Component responsibilities
States
FR-1 — 3D working model of data and packet flow (explicit) As a Model Viewer, I should see a 3D working model of data and packet flow, so that I can understand how data and packets move.
FR-2 — Model reflects the supplied source (explicit) As a Model Viewer, I should see the model show the flow from the source I supply, so that the model is about my source rather than a generic example.
FR-3 — Supply a source (required_inference) As a Model Viewer, I should be able to supply a source for the flow model, so that the model has something to show.
FR-4 — Inspect flow paths and nodes (required_inference) As a Model Viewer, I should inspect the flow paths and nodes of the model, so that I can understand the movement in detail.
FR-5 — Drive the model with flow controls (required_inference) As a Model Viewer, I should use the side rail flow controls to drive the model, so that I can explore the movement at my own pace.
FR-6 — Entry to the model (required_inference) As a Model Viewer, I should reach the model from the public entry page, so that I know what the product is before I start.
Product context. The Model Viewer is network-curious: someone who wants to see how data and packets move and to touch the model rather than read a static diagram. They arrive at the public Landing page, see the 3D scene as the first screen, and open the model.
Primary goal. See a 3D working model of data and packet flow for a source they supply, and understand the movement by inspecting it.
Distinct accepted responsibilities.
Relevant inputs and decisions. What source to model; which node or flow path to inspect; how to drive the flow with the controls.
Interactions with other accepted participants. None. The Model Viewer is the only accepted active human persona; there is no counterparty, recipient, or approver in the accepted behavior.
Observable success. The scene shows nodes, links, and packets in motion for the supplied source; hovering a node pulses it; inspecting a node or flow path identifies it; the flow controls change the model's flow.
Muse and headline. Bruno Simon — playable 3D worlds with toy physics. The headline idea: a technical demo you can touch, staged on a deep navy ground with coral packets in motion and mint nodes and links.
Mode. Dark mode only.
Colour tokens (exact hex, by role)
#101828 — deep navy ground covering most of the screen.#1B2440 — chunky rounded panels (HUD legend, side rail, source input).#F4F1E8 — cream, readable on navy.#FF6B4A — coral; marks packets in motion and the primary call to action.#7CE0C3 — mint; marks nodes and links.#8A93AD — secondary labels and inactive controls.Typography
clamp(40px, 9vw, 112px).Shape language. Low-poly spheres and capsules for nodes. Thick rounded links. Soft shadows. Chunky rounded panels for controls.
Layout. The 3D model fills the first screen. A small HUD panel sits at the lower left; a ruled legend sits at the top right. The Model page adds a side rail of flow controls.
Imagery. Low-poly 3D nodes and packet cubes. Soft pastel lights. No photographs and no flat clip art.
Readability rule. Headlines, wordmarks, labels, numbers, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit, with no other element covering them. Imagery and decoration may bleed, crop, or overlap freely.
The Landing page's first screen is a full-bleed playable 3D scene, not a picture of one. A deep navy field (#101828) holds one low-poly source node at the left and a receiver cluster at the right, joined by thick rounded mint links (#7CE0C3). Coral packet cubes (#FF6B4A) travel the links with a small bounce, slowing at each node. The pointer eases the camera with slow, cinematic damping so the viewer looks around the model. A chunky rounded HUD legend panel at the top right lists node types with colour chips. The headline — Fredoka at clamp(40px, 9vw, 112px), cream (#F4F1E8) — sits on the lower left over the scene, never centred, with the subline beneath it and the "Open the model" control below that. No gradient blobs, no glass cards, no centred headline stack, no stock photography, no grid of identical hover-lift cards.
Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: webgl
Landing Hero Motion Brief
Landing Hero 3D Scene Brief — DIRECTION-DERIVED One crafted real-time scene: a low-poly source node (sphere/capsule) at the left, a receiver cluster at the right, thick rounded mint links, and coral packet cubes travelling the links with a small bounce and node-by-node slowdown. Soft pastel lighting, soft shadows, no photographs. The scene is the hero subject and fills the first screen; the camera is pointer-eased. Built with WebGL/R3F.
prefers-reduced-motion, a usable static arrangement is provided in which every readable item can be brought fully into view.webgl hero dimensionality.frontend, backend, database. The backend is reused for feature APIs; no additional service is required by the accepted workflows.
A three-dimensional flow model: one source node on the left, relay nodes in the middle and a receiver cluster on the right, joined by mint links, with coral packets travelling along them.
Data and Packets Flow
Follow each packet from the source to the receiver and inspect every node on the path.
Open the model
A three-dimensional flow model: one source node on the left, relay nodes in the middle and a receiver cluster on the right, joined by mint links, with coral packets travelling along them.
Data and Packets Flow
Follow each packet from the source to the receiver and inspect every node on the path.
Open the model
No comments yet. Be the first!