Judge map

We made friction the product.

Unread takes a hard position: the right AI for reading should not make every text easier. It should make pretending harder.

Demo checklist

Judge path in three clicks.

Seed demo

Creates the polished public post used in the live walkthrough.

Public post

Open the saved public room and choose the [DEMO] post.

Dashboard analytics

Show author analytics, weak spots, reports, and saved sessions.

30%

We built Unread to study productive friction because reading tools usually remove the exact struggle that proves comprehension.

25%

The product refuses the obvious AI-summary answer. It uses AI as resistance: a gatekeeper that says, 'not clear yet.'

20%

Saved rooms, streaming AI feedback, locked sections, presence, reports, public posts, and author analytics all serve one idea.

15%

A stranger should understand it in one minute: paste text, answer the claim, get blocked when you fake it.

10%

Unread is willing to be annoying. That discomfort is the stance, not a side effect.

Demo path

1

Open the seeded post: The meeting after nobody read.

2

Show that only the first section is visible.

3

Submit a vague answer and let the AI push back.

4

Submit a precise answer and unlock the next section.

5

Open the dashboard analytics to show the weak checkpoint.