Four builds you can drive right now.

1. 01Open /portfolio for the operator surface: bookings, clients, invoice state.
2. 02Switch to /design-system for the theme tokens the Reflex app is built from.
3. 03Compare /features against /help: same primitives, two page patterns.

This deploy is a static export of the Reflex UI, so the screens are real but the forms do not submit. The interactive build runs on Postgres with Alembic migrations.

1. 01Submit a request and read the preview before confirming. That gate is the whole point.
2. 02Confirm it, then watch the lifecycle timeline move the task through its states.
3. 03Reset the session and run it again: the sequence is deterministic, so it replays identically.

Runs entirely on local synthetic state. The mechanism is what is on display, not a model's output.

1. 01What is framed here is the smoke target, the synthetic page the end-to-end suite drives.
2. 02/health is the check the suite asserts against, served as plain JSON.
3. 03The engine itself is a CLI, so the policy file is its honest interface, not a screen.

This project has no product UI, and the allowlist is where the engineering is: hosts, commands, environments, ceilings, and an explicit allowMutation of false.

1. 01Cycle the live filters and face stickers. Every frame is processed on your own machine.
2. 02Shoot the four-shot sequence, then retake only the frame you did not like.
3. 03Export a strip and a poster: aspect ratio is preserved from capture through to the PNG.

Open it in its own tab to use the camera. Nothing you capture leaves the browser; the build has no upload path.