pure-3d is a website whose content is presented in three dimensions. The product intent is deliberately narrow and complete: a visitor arrives at the site and experiences content as an interactive 3D scene that they can view, orbit, and navigate through. The artefact is the 3D — there is no stated product category, catalogue, commerce flow, or editorial archive behind it. Success is a working, explorable 3D web experience.
The audience is the Visitor: an anonymous, first-time or returning person who opens the site expecting to be inside something volumetric, motion-led, and slightly futuristic. The emotional register is awe and play, not commerce. The site must feel like a place, not a page.
This document specifies the current delivery: one publicly reachable page, Landing, that renders a full-viewport real-time 3D scene with a glass-and-HUD overlay, plus the visual, motion, and technical constraints that make that experience coherent.
pure-3d is delivered as a single first-party, publicly accessible web page. The page is a full-bleed real-time WebGL scene; all interface chrome is an overlay floating above the canvas rather than a document column. There is no sign-in, no account, no stored user data, and no server-side product state — the experience is entirely client-rendered and stateless from the visitor's point of view.
Actors
Accepted behaviour
Ownership
The Landing page is owned by the application and is anonymously reachable. No provider-owned or external destination carries accepted product behaviour. No identity, session, or permission layer is required, because no accepted journey creates durable actor-specific state, a commitment, an entitlement, or a value transfer that must remain bound to a particular person.
Exclusions
The entire product is one page that behaves like a place. Everything the visitor can do — look around, orbit the subject, scrub the camera through the scene, read telemetry, jump to a section — happens inside that single continuous 3D viewport. There is no second screen to reach and nothing to sign into, so the delivery boundary is simply: open the URL, and you are inside the scene.
Because the experience is anonymous and stateless, there is no protected area and therefore no access boundary to reconcile. The page is public by design, and the only "state" that exists is transient view state (camera angle, zoom, scroll position) that lives in the browser for the duration of the visit and is not persisted or attributed to anyone.
Everything described in this document is current. No future-horizon capabilities have been accepted, and none are specified here.
Not applicable. No reference directive in this project declares a content_source, so there is no verified factual inventory to preserve. All copy in the product is generated from the creative direction (wordmark, section labels, telemetry readouts, CTA label) and is not sourced from an external factual corpus.
The single page of pure-3d. A full-viewport real-time 3D scene with a glass-and-HUD overlay. Anonymous access; no identity required.
Information and state
Primary actions
Supporting actions
Domain entities
Component responsibilities
PURE 3D display type, set in two lines with the second line indented two columns, anchored to the left edge and overlapping the object's silhouette so the geometry passes behind the counters of one letter.θ 042.7°).Drag to orbit micro-label right.Enter the scene control with a cyan border and a magenta hover fill.States
initialising readout occupies the telemetry rail until live values are available.FR-1 — Present content in 3D As a Visitor, I should see the site's content presented as a real-time 3D scene, so that the experience itself is three-dimensional rather than a flat page.
FR-2 — Orbit the subject with the cursor As a Visitor, I should be able to orbit the 3D subject with my cursor, so that I can inspect it from any angle.
FR-3 — Navigate the scene by scrolling As a Visitor, I should be able to scroll to move through the scene, so that the page reads as one continuous shot rather than stacked sections.
FR-4 — Enter the scene from the hero As a Visitor, I should be able to start the experience deliberately, so that I choose when to leave the hero framing.
Enter the scene.FR-5 — Jump directly to a section As a Visitor, I should be able to jump to a named section, so that I can reach a part of the scene without scrubbing through it.
FR-6 — Read live telemetry and stay oriented As a Visitor, I should see live readouts of the camera and render state, so that I understand where I am in the scene and that it is running.
initialising readout; if the renderer is degraded or unavailable, the rail shows the last known or unavailable values rather than stale numbers presented as live.FR-7 — Read section content beside the 3D object As a Visitor, I should be able to read each section's content alongside the 3D object, so that the text and the geometry are experienced together.
FR-8 — Respect reduced-motion and performance limits As a Visitor, I should have the experience adapt when my system requests reduced motion or the renderer struggles, so that the site stays usable.
Product context. The Visitor arrives at pure-3d anonymously, most likely from a link, with no prior relationship to the site and no account. They have not been told what the site is for, because the site does not have a stated product category — the 3D experience is the product. They arrive expecting to be inside something volumetric, motion-led, and slightly futuristic, and they judge the site within seconds on whether it actually feels like a place.
Primary goal. To experience the 3D website: to see content presented in three dimensions, to look around it, and to move through it. Success is a working, explorable 3D web experience — the scene renders, responds to them, and lets them travel through it.
Distinct accepted responsibilities. The Visitor is the sole human actor and carries every human-facing responsibility in the product:
Relevant inputs and decisions. The Visitor's inputs are pointer movement, pointer drag, scroll, and activation of the CTA and section links. Their decisions are: whether to keep looking at the hero or enter the scene; which section to travel to; and how long to keep exploring. They make no commitments, submit no data, and create no durable state.
Interactions with other accepted participants. There are none. The Visitor is the only accepted human participant; no counterparty, recipient, or beneficiary is affected by anything the Visitor does. The rendering runtime and static host execute work on the Visitor's behalf but are non-persona system actors, not participants.
Observable success. The subject is visible and lit; the idle orbit loop runs; pointer parallax responds within 400ms; drag rotates the camera; scroll scrubs the camera between section keyframes; the telemetry rail updates live; and the visitor can reach every section and read its content. If the renderer fails, the visitor still sees the fallback frame and can still read the page.
Constraints carried from source. The Visitor is anonymous — no account, sign-in, or permission is required or offered. Nothing the Visitor does is persisted or attributed to them.
PURE 3D headline and the overlay chrome (top bar, telemetry rail, CTA, telemetry block) render, and the telemetry rail shows an initialising readout.initialising with live camera θ/φ, zoom, frame time, and node count.Failure and recovery: if WebGL is unavailable or the context is lost, the canvas is replaced by a static fallback frame of the subject with a monospace notice that the 3D scene could not start. The headline, section text, and telemetry rail remain readable and the page remains scrollable. A lost context is re-requested automatically; if it cannot be restored, the fallback frame remains.
θ 042.7°) and the telemetry rail's θ and φ values track the change live.Failure and recovery: if the pointer leaves the viewport, the subject eases back to its idle orientation rather than snapping. If the canvas is unavailable, no orbit is offered and the fallback frame is shown.
Enter the scene.Failure and recovery: if the camera move cannot run, the page scrolls to the first section instead, so the Visitor still reaches the content.
Failure and recovery: if the camera cannot be scrubbed — reduced motion is requested, or the renderer is degraded — the sections remain reachable as ordinary scrollable content with their text intact. Under performance pressure the bloom pass and dust layer are dropped before the subject itself.
Failure and recovery: if the camera move cannot run, the page scrolls to that section's band instead.
Failure and recovery: before live values exist the rail shows initialising; if the renderer is degraded or unavailable, the rail shows the last known or unavailable values rather than stale numbers presented as live.
Muse: Gleb Kuznetsov. Dark voids, glowing volumetric forms, HUD-like data, and scroll-scrubbed camera moves as the hero itself. The artefact is abstract, luminous, and interactive — which is precisely "a 3D website." The register is awe and play, not commerce: the site must feel like a place, not a page.
Headline direction: Cinematic future-tech — a 3D world you can orbit with your cursor.
| Role | Hex | Usage |
|---|---|---|
| Background (void) | #05060A | The canvas itself; near-black, no white anywhere in the hero |
| Surface (glass) | #0C1018 | Slightly lifted panel surface for glass overlays |
| Text | #EAF2FF | Cool glassy white; 90–100% for headings, 70% for body |
| Primary | #7CF9FF | Cyan light source: rims the 3D object, draws HUD strokes, colours the primary CTA |
| Accent | #FF4FD8 | Magenta hot accent, used sparingly: one radial glow behind the object, one active-state underline, one hover fill |
| Muted | #6B7A93 | Micro-labels and monospace data |
Ratio: 80% void, 12% glass white, 5% cyan, 3% magenta.
Forbidden: blue–indigo accents (#2563EB, #6366F1, #7C3AED and neighbours); white or near-white backgrounds anywhere in the hero; the generic indigo/blue-on-white SaaS template.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!