# Liminal Sites Demo Gallery

Use this gallery brief when showing collaborators what the product should feel like beyond a single proof page.

## Curated Demo Archetypes

| Demo | Why It Matters | What To Look For |
| --- | --- | --- |
| Operator Launch Page | Proves a plain marketing page can become more alive without losing clarity. | Body, hero, buttons, cards, layout, runtime receipt. |
| B2B Control Room | Proves dense operational UI can stay quiet and scannable while gaining motion and taste memory. | Tables, status panels, restrained contrast, reversible package. |
| Creative Portfolio | Proves Liminal can push expressive art direction while preserving content hierarchy. | Hero typography, artwork panels, shader/kinetic layer receipts. |
| Venue / Menu Page | Proves local-business pages can gain atmosphere without becoming a generic landing page. | Menu cards, call-to-action, palette continuity, rollback path. |

## Generate A Local Gallery

```bash
pnpm proof:living-sites-reliability
```

Then open:

```text
.omx/proof/living-sites-reliability-sweep/gallery.html
```

The generated gallery is intentionally file-based so it can be attached to a PR, sent to a collaborator, or inspected without a hosted service.

## Demo Talk Track

1. Start with the source page.
2. Show the ingestion receipt and screenshot.
3. Show the evolved candidate selected from taste memory.
4. Show the Full Liminal composition receipt with all domains used or explicitly accounted for.
5. Show the mutated page screenshot.
6. Show the deployment snippets and rollback/runbook receipts.
7. Show the repo patch plan as the bridge from preview to implementation.

## What Makes A Demo Trustworthy

- It changes more than background color or headline scale.
- It preserves the website's actual content hierarchy.
- It has a receipt for every generated layer.
- It has a rollback path.
- It can package or patch the result without editing the live source blindly.