# Ledger Lens: example brief and prompts

Ledger Lens is a fictional educational prototype created for PotoDesign's guide, “How to build a crypto website with AI”. This is editable working material, not a client brief or live crypto service.

## Product brief

- Audience: designers and product researchers learning about crypto use cases.
- Primary task: find a category, understand an example and open related reading.
- Scope: a single responsive directory page, six fictional records, search, category filters, expandable notes and general educational links.
- Categories: Payments, Infrastructure, Research.
- Visual direction: editorial layout, warm light background, dark text, blue actions, readable type and generous space.
- Data: local sample records only. No prices, user accounts, wallet connection, transactions or live API.
- Success check: a reader can find a payments example and open its reading material on mobile or using a keyboard.
- Ownership: someone must verify real records and sources before this becomes a public research product.

## Build prompt

```text
Build a responsive, read-only crypto research hub called Ledger Lens.

Audience: designers researching crypto product use cases.
Main task: find a category, understand an example, open its reading source.
Use the supplied records; label every fictional record as sample content.

Implement search, category filters and expandable project notes.
Provide ready, loading, empty and error states.
Use real buttons, labelled inputs and visible keyboard focus.
Keep the introduction and important content in the initial HTML.
Preserve the supplied type, spacing and colour rules.

Do not add prices, investment claims, wallet connection or fabricated proof.
Explain what works locally and what still needs a backend or data provider.
Return the editable source and a list of checks I can repeat.
```

## Review prompt

```text
Review this prototype against its brief and visible browser behaviour.
Check the main task at desktop and 390-pixel widths.
Try category plus search, a query with no matches, reset, expandable notes,
keyboard navigation and all simulated states.
Report the observed problem, the user impact and the smallest useful change.
Do not claim accessibility compliance, performance results or live-data
reliability without performing the relevant checks.
```

## Sample record contract

| Field | Purpose |
| --- | --- |
| name | Fictional example name |
| category | One of the three explicit categories |
| description | Concise explanation of the imagined use case |
| note | What a designer could study in this use case |
| recordSource | Authored demo brief, clearly marked as sample content |
| reviewedAt | 2026-11-17, the creation/review date of this demo record |
| readingURL | General educational reference, not proof of this fictional project |

A future market-data integration needs a separate contract for provider, currency, units, nullable values, update timestamp, caching and errors. No external data request is implemented here.

## Repeatable acceptance checks

1. Open `demo.html` through a local HTTP server.
2. Select Payments: two sample results should remain.
3. Search for “Cedar”: one result should remain.
4. Search for an absent phrase: the empty state should appear.
5. Clear search and filters: all six records should return.
6. Expand a project note and inspect its educational link.
7. Use the state selector to display loading and error. The recovery action returns to sample results; it is not a network retry.
8. At a 390-pixel width, check reading, search, filter wrapping and horizontal overflow.
9. Use Tab and keyboard activation to reach controls and open notes.

## Source files

- `demo.html`: initial content and semantic controls.
- `demo.css`: responsive visual rules.
- `demo.js`: client-side search, filters and simulated states.

Open the demo locally; do not interpret its example records as real investment information.

