# Test — Phase 11.1

The public demo deliberately does **not** display the full catalogue.

## What the tester sees

On first load:

**What are you wondering about?**

A real demonstration thought is already entered:

> How did taking photographs become a world where strangers watch one another through screens?

The page explicitly says:

> **FRIEND TEST · START HERE**  
> Press Find a path. Read what it gives you, and follow any door that interests you.

No typing is required for the first demonstration.

## Discovery

The homepage does not show "the library."

**My Library** contains only Books the current reader:
- already owns;
- has encountered in a generated Path;
- has encountered as a visible Portal;
- has started reading.

The application never tells the reader how many Books or Shelves exist.

The full catalogue remains server-side Atlas infrastructure.

## Fragment behavior

The fragment rail is deliberately conservative.

While the user is in the middle of typing a word, that word is ignored.

Examples:

- `pho` → no `pho` fragment
- `photo` → still no fragment while the cursor is directly after the `o`
- `photo ` → `photo` appears
- `photo,` → `photo` appears

The UI displays the reader's exact completed fragment, not a semantic expansion such as `photography`.

The server-side route engine may still understand `photo` as related to `photography`; that interpretation is hidden from the fragment rail.
