Process record · complete

Prompts, not alibis.

Model assistance shaped the concept and implementation. Every generated working prompt is reproduced here verbatim from the tracked source files.

prompts/design.md

Design direction

# Design prompt record

## Commission

Create a Signature stand-0 showcase called **LUCENT · House of Refraction**. It must be bright,
sunlit and architectural. Use magnesium white, spectral cyan, violet, ember and chrome. Build a
real-time spatial refraction experience, not a dark shader, centred product demo, aurora, generic
card page or scroll-scrub film.

## Concept-generation prompt

Propose three concepts with a thesis, one unforgettable signature moment, a five-to-seven beat
story, technique, risk and complete fallback. At least one concept must make physical light the
interface. Prefer original code-native material to stock or generated media. Select the boldest
concept that can still be complete with reduced motion, no JavaScript and no WebGL.

## Taste challenge

Audit the chosen concept against these failure modes:

- dark void plus luminous accent;
- a centred Three.js object on a turntable;
- glassmorphism cards or bento sections;
- editorial serif plus hairline museum labels;
- a purple-to-cyan atmospheric gradient with no physical role;
- multiple effects competing for signature status.

Revision chosen: a bright asymmetrical pavilion, one user-controlled sun rail, quiet semantic
sections and a code-native SVG first frame.

prompts/development.md

Development contract

# Development prompt record

Build the locked design in Astro and Tailwind without weakening the signature.

- Keep the homepage semantic. Canvas is decorative and never the only carrier of information.
- Use a native range input for the sun so Arrow, Home, End and touch work without custom controls.
- Share the angle with Three.js and the DOM through one state update.
- Load the SVG pavilion with HTML, then fade WebGL in only after a successful first render.
- Cap DPR, pause when offscreen, dispose resources on page exit and avoid image textures.
- Include `/guide`, `/prompts`, `/privacy` and a branded 404.
- Self-host exactly two font families.
- Keep CSP strict: no third-party requests, no inline event handlers and no external embeds.
- Make reduced-motion, no-JS, no-WebGL and no-media states complete.
- Verify 320, 390, 768 and 1440 widths, keyboard focus, axe and console output.

prompts/optical-engine.md

Optical engine

# Optical engine prompt record

Construct a pavilion, not a product:

1. Four off-axis pale stone planes frame an inhabitable void.
2. A transmissive glass fin and triangular prism split the ray.
3. A narrow chrome column and disc reflect the environment without becoming the focal object.
4. A directional sun casts soft architectural shadows.
5. A compact fragment shader paints cyan, violet and ember caustic bands onto the floor.
6. The sun angle changes light position, glass orientation, caustic direction and DOM text mask.
7. Pointer motion moves the camera by no more than 1.5 degrees; reduced motion removes this drift.
8. The SVG fallback must contain the same spatial facts and remain visible on any renderer failure.

Do not add stars, fog spectacle, bloom, neon, an orbit camera, product labels or autonomous camera
travel. The visitor's hand is the animation director.

prompts/release-deployment.md

Release and deployment

# Release and deployment prompt record

Release LUCENT as a clean Cloudflare Pages Direct Upload project without changing the visual
concept.

- Audit that the three Signature passes are substantive and that every tracked prompt is visible
  on `/prompts/`.
- Add a site-specific, reproducible Pages release sequence to `/guide/`.
- Make every local QA process honor `QA_PORT`, defaulting to 4321 but supporting isolated port 4331,
  while `QA_BASE_URL` remains the explicit live target.
- Run clean install, lint, Astro checks, static build and the full release harness locally.
- Confirm authentication and that `house-of-refraction` does not exist before creating it with
  production branch `master`.
- Deploy the committed `dist` directory with branch and Git metadata, then run live route, fallback,
  console, security and three-run Lighthouse gates against the returned production URL.
- Record the final URL, deployment identity, checks and scores without exposing credentials.
- Do not deploy from a dirty tree and do not touch another repository.

Prompt provenance

# Prompt provenance

This inventory is complete for the generated working prompts used to design and implement LUCENT.

| File | Purpose | Status |
|---|---|---|
| `design.md` | Commission, three-concept exploration and anti-slop challenge | Tracked and published verbatim at `/prompts/` |
| `development.md` | Astro, accessibility, fallback and verification contract | Tracked and published verbatim at `/prompts/` |
| `optical-engine.md` | Procedural pavilion, material and shader implementation brief | Tracked and published verbatim at `/prompts/` |
| `release-deployment.md` | Pages documentation, isolated QA harness and autonomous release brief | Tracked and published verbatim at `/prompts/` |

No hidden image, video, voice or asset-generation prompt exists because the shipped experience is
code-native. The original user commission is recorded through the durable design lock rather than
duplicated as a generated prompt.

What was rejected

A zero-JavaScript colour atlas was too close to an editorial pigment study. An AI film made the signature depend on generated media. The chosen pavilion made interaction, material and fallback one system.