Docs #

One file per subject. All of it records decisions and why, so future work doesn't re-derive them; none of it is a spec to build against literally.


`roadmap.md`	Phases and scope, and what is deliberately not being built yet.
`architecture.md`	The AppView shape, the two origins, what the browser holds.
`data-model.md`	Owned versus referenced, stack identity, decks and history.
`atproto.md`	Lexicons, OAuth scopes, and what a PDS will actually take.
`scryfall.md`	The card cache and the client artifact built from it.
`scanner.md`	Reading a card out of a photograph, and what each part measures.
`search.md`	Querying that artifact, and the syntax borrowed from Scryfall.
`reports.md`	The scans a person sends back, and what happens to one.
`configuration.md`	Every variable the binary and the tools read.
`ip.md`	The WotC, Scryfall and EDHREC constraints, and the licenses.

Reasoning that belongs to one tool lives beside it instead: tools/icons/README.md is what the icon is drawn from and why.

AGENTS.md at the root is the condensed orientation for picking the project back up; these carry the reasoning behind it.