Skip to content

Latest commit

 

History

History
300 lines (240 loc) · 44.3 KB

roadmap.md

File metadata and controls

300 lines (240 loc) · 44.3 KB

Roadmap

Last ruled on: 2026-11-13. Goal, 1.0 test and rules: north-star.md.

The roadmap has one main line, built in order, with a research lane and a housekeeping lane beside it. Each numbered item is a candidate spec sized to the north star's one-outcome rule. Candidates are refined, split or dropped when their turn comes; they are not specified ahead.

Tracking. Every candidate has a GitHub issue on the 1.0 milestone, labelled by theme (theme: data-safety, theme: typed-entry, theme: locations, theme: scanner, theme: prices, theme: households, theme: hosted) or housekeeping, with spike on the spikes and design-system on candidates that change the design system. Work recorded for after 1.0 has issues on the 2.0 milestone. This file holds the order and the reasons; the issues hold the state. A candidate that is added, split or dropped changes both in the same PR. A spec's PR closes its issue. Build specs that follow a spike get their issue after the maintainer's ruling. Specs 001–015 are done and aren't listed here.

Main line

Theme A: Data safety

Foundation principle 2. Spec 004 named export and import as the next priority; specs 007–015 went elsewhere.

  1. Record whether Scryfall's terms permit a public, possibly paid, instance (research note; hosted-door rule 1). Done 2026-10-11: research 016, ruled on in decision log 27–29.
  2. #37 Define the export format: versioned, keyed by external ids (enabling slice). Done 2026-10-11: the format, ADR 0020 and spec 017, ruled on in decision log 32.
  3. #38 Export a collection as a file. Done 2026-10-14: spec 022, PR #97.
  4. #39 Preview an import: per-row errors, nothing written. Done 2026-10-15: spec 025, ADR 0021, PR #113.
  5. #40 Apply an import: all or nothing, idempotent, with a round-trip test. Done 2026-10-20: spec 028, ADR 0022.
  6. #41 Back up and restore an instance, documented and tested. Done: spec 030, ADR 0024.
  7. #42 Prove an upgrade from the previous release in CI (supports the 1.0 test's third check). Built 2026-10-24, done when its pull request merges: spec 031; this completes theme A.

Theme B: Typed entry

  1. #43 Enter cards from a set by collector number and quantity, keyboard only. Nothing in it is specific to one collectible type. Done 2026-10-15: spec 026, PR #114.

Theme C: Locations

The design system's "where is it" (docs/design-system/README.md). The comics research findings feed this design if the research has run by then; it is deferred (ruling 26), and locations don't wait for it.

  1. #44 Manage locations (create, rename, remove). Built 2026-10-21, done when its pull request merges: spec 029, ADR 0023: locations make the export format version 2 (the pull request is recorded here when it merges).
  2. #45 Put a lot in a location. Built 2026-10-24, done when its pull request merges: spec 032, ADR 0025: a lot's location is part of its identity, so a printing in two places is two lots (the pull request is recorded here when it merges; ADR 0019 named the question). It raises the export format to version 3 (locations alone made version 2, ADR 0023, superseding ADR 0020's consequence).
  3. #46 Show the location on tiles and rows. Built 2026-10-26, done when its pull request merges: spec 033: a tile names the place with most copies and counts the others, a row has a Location column (the pull request is recorded here when it merges).
  4. #47 Filter the collection by location. Built 2026-11-06, done when its pull request merges: spec 037: a Location select in the filter bar (all, one location or "No location"), honoured by the grid, the table and bulk mode's selection (PR #174).
  5. #48 Move many lots at once (the "Move to…" deferred in spec 006). Planned: spec 041 (approved 2026-11-06): "Move to…" in bulk mode, for the selected lots or every matching lot, to a location or none (the distillation step records the build date and the pull request).
  6. Decks, one candidate per outcome, scoped on 2026-11-09 in the decks and locations issue design from the maintainer's v1 design and an interview with mock-ups. The design-system candidates go first, so later candidates build on written patterns; 14c and 14d are independent and may run beside them. The later work (deck checks first) is on the 2.0 milestone: #258, #259, #260, #261.
    • 14a. #248 Design system: deck rules, navigation and pickers.
    • 14b. #249 Design system: deck components and previews (after 14a).
    • 14c. #187 Open a location's lots in bulk mode from its refusal page (the shortcut spec 041 decision 5 left out). Built 2026-11-10, done when its pull request merges: spec 059: a "Move them in bulk mode" button on the refusal page opens the bulk table filtered to the location with every lot selected (the pull request is recorded here when it merges).
    • 14d. #250 Store each card's mana value from the catalog.
    • 14e. #49 Create, rename and remove a deck (after 14a and 14b). It raises the export format to version 4.
    • 14f. #251 Change a deck's format (after 14e).
    • 14g. #252 Deck zones in every location picker and in the collection filter (after 14e).
    • 14h. #253 Deck page: owned cards by zone (after 14b, 14e and 14g).
    • 14i. #254 Proxies: add, change and remove a proxy in a deck zone (after 14h).
    • 14j. #255 Add to deck from the card page (after 14i). Done 2026-11-11 (#325, merged): spec 071: an "Add to deck" action in the card page's head opens a page that moves the card's free copies (any printing, in the order the spec states, all or nothing through Lot::MoveIntoZone) or records a proxy of the shown printing, one option per finish, into a zone of a deck of that card's type; "Free to use" and "In decks" on the card page stay with #50.
    • 14k. #256 Deck shape panel: mana curve, card types and coloured mana symbols (after 14d, 14h and 14i). Spec 069.
    • 14l. #257 Replace a proxy with a copy (after 14i). Built 2026-11-11, done when its pull request merges: spec 070: a proxy row's menu gains "Use my copy" (free copies moved into the zone, the proxy lowered by the copies used) and "Add a new copy" (the Add a copy form for the proxy's printing); the shared Lot.free and Lot::MoveIntoZone are what 14j builds on (the pull request is recorded here when it merges).
    • 14m. #302 Open a deck's lots in bulk mode from its removal refusal page (the shortcut spec 062 decision 7 and spec 065 left out; after 14g). Spec 067.
    • 14n. #258 Deck checks, the first of the 2.0 milestone's deck work (after 14h, 14i and 14k). Built 2026-11-12, done when its pull request merges: spec 079: a "Check deck" link on the deck page shows, on demand and stored nowhere, the deck's size and copy limits judged by its format's rules (Magic's in code in its extension) and every card with owned copies and proxies in one zone, for any deck (the pull request is recorded here when it merges).
  7. #50 "Free to use" and "In decks" on the card page (after 14e and 14i). Done 2026-11-12 (#333, merged): spec 073: the card page's stats (Owned, In decks, Free to use) and an "In decks" table of the decks and zones that hold the card's copies and proxies.
  8. #51 Choose a location during typed entry. Built 2026-10-26, done when its pull request merges: spec 034.

The deck builder follows on the 2.0 milestone (maintainer, 2026-11-12; design), design system before features. It rewrites #260 as build mode. Build mode and its views need no data change; planned cards raise the export format to version 5.

  • #347 Design system: the deck builder.
  • #260 Build mode: whittle a deck on its page (after #347).
  • #350 Find a card in build mode (after #260).
  • #351 Build mode: the cards view (after #260).
  • #352 Build mode: one card at a time (after #351).
  • #348 Planned cards: a deck slot that is planned, not proxied (after #347).
  • #349 A planned slot fills itself when a copy arrives (after #348).
  • #353 Add cards from inside build mode (after #348 and #260).
  • #354 The pull list (after #348).
  • #355 Start a deck from a pasted list (after #348).
  • #356 Start a Commander deck from its commander (after #353).

Not yet placed: #357 a wish list section and #358 suggested cards in build mode, recorded on 2026-11-12 from the deck builder design. The maintainer places them.

Theme D: Scanner bulk entry

The scanner as built (specs 005 and 007–011) stays as it is until this theme. The spikes may run earlier as measurement only.

The phone-first layout comes first (maintainer, 2026-11-12; design), design system before features, each depending on the one before:

  • #343 Design system: the phone-first scanner.
  • #344 Scanner: capture always in view. It changes the guide's geometry and re-measures the reading.
  • #345 Scanner: the selection pane.

The spikes' build specs and 21c then build on that layout.

  1. #52 Spike: the art margin on unseen cards (the 300-bit threshold, kept by ruling in spec 011).
  2. #53 Spike: detection on live frames. A build spec follows if the maintainer rules for it.
  3. #54 Spike: continuous capture (trigger, duplicates, rate). The build spec follows.
  4. #55 Spike: recognising Japanese cards. The build spec follows.
  5. Sitting-wide choices, one spec each. This reverses spec 009's deferral of sitting-wide defaults.
    • 21a. #56 Scan a sitting into a location. Built 2026-11-06, done when its pull request merges: spec 040. It ran before the spikes (17–20) by the maintainer's ruling of 2026-11-03 (spec 040 decision 1): the control and the add path are server-rendered and independent of capture; only 21c keeps the order (spec 042 amends this: 21b ran first as well).
    • 21b. #57 Set a condition for a sitting. Built 2026-11-06, done when its pull request merges: spec 042. It ran before the spikes (17–20) by the maintainer's ruling of 2026-11-06 (spec 042 decision 1), for spec 040's reason: the control and the add path are server-rendered and independent of capture.
    • 21c. #58 Set a language for a sitting.

Not yet placed: #262 separate "add" and "look up" scanning modes, recorded on 2026-11-09 from the v1 decks design. The maintainer places it.

Theme E: Comics

Last on the line, so that it can leave 1.0 without reordering anything. Its candidates are written after the maintainer rules on the research. The ruling has three outcomes: in 1.0 at a stated scope, after 1.0, or more research.

Research lane

Runs beside the main line, when the maintainer starts it.

  • Comics source research (issue #23), deferred on 2026-10-11 (ruling 26); no start is set. It will report the candidate sources, their terms against hosted-door rule 1, and what the data supports for reading state and barcodes.
  • Theme D's spikes (items 17–20).

Prices lane

Runs beside the main line, when the maintainer starts it (rulings 35–41; design). Market prices were parked until after 1.0 by ruling 14; the maintainer moved them into 1.0 on 2026-11-13, because price history can only be recorded from the day an instance starts recording it. In 1.0 the data has one use, a basic display. Each candidate depends on the ones before it:

  • #361 Spike: prices on non-English printings. Done: research 083, ruling 41.
  • #362 Ask Scryfall in writing about recording prices and showing their history. Not code; it doesn't block the rest.
  • #363 A prices database that the backup holds.
  • #375 A start refuses a volume that holds a prices database and no primary (after #363; spec 081 decision 8). Done: spec 086.
  • #364 A price source contract, and Scryfall's prices through it (after #361 and #363). Done: spec 085.
  • #365 Prices refresh once a day, and each change is recorded once. Done: spec 089.
  • #366 Each price refresh records what it did and how large the database is.
  • #367 An admin reads the price refresh log.
  • #368 An operator chooses how much price history the instance keeps (after #365).
  • #369 A card's market price on its page and in the collection (after #365).
  • #370 Operator documentation: what each price history level costs (after #366 and #368).

After 1.0: #371 prices follow a printing that Scryfall merges into another (it needs /migrations, parked below).

Households lane

Runs beside the main line (rulings 43 and 44; design). Personal and household collections side by side were parked until after 1.0 by ruling 6; the maintainer moved them into 1.0 on 2026-11-13, alongside the deck and location work, because the change to who owns a row gets dearer with each table added. An account stays the unit of ownership and privacy, and a household is a group of accounts: each member's own and one the household shares. Design system before features:

  • #379 Design system: households.
  • #380 Every user has a household. Its spec writes the ADR that supersedes the one-user half of ADR 0017.
  • #381 Join a household with an invitation code (after #379 and #380).
  • #382 Leave a household, or be removed from it (after #381).
  • #383 Hand the manager role to another member (after #381).
  • #384 Work in the household's shared collection (after #379 and #381). It raises the export format.
  • #385 Move copies between my collection and the household's (after #384).
  • #386 Move many lots between collections from bulk mode (after #385).
  • #387 Move a deck between my collection and the household's (after #385).
  • #388 Borrow copies from the household's collection (after #384 and #385). In 1.0 by ruling 47: a household doesn't work well without it. Lending outside the household stays on the 2.0 milestone (#259).
  • #389 Households on the admin users page (after #380).

Hosted lane

Runs beside the main line, after #380 (rulings 42 and 45; the same design). Hosted-service features were parked until after 1.0 by ruling 14; the maintainer moved them into 1.0 on 2026-11-13, to take a hosted service to market sooner. Collector stays AGPL-3.0 as one codebase (ruling 42): each candidate is a feature of that code, switched on by configuration, and a self-hosted instance loses nothing. Ruling 46 narrows ruling 27: the plan and billing code is built behind hosted mode, and no paid plan is offered at a hosted instance until #390 closes.

  • #390 Settle Wizards of the Coast's position on charging for a hosted instance. Not code.
  • #391 Ask Scryfall in writing about the free plan's cap. Not code.
  • #392 Hosted mode: one operator setting.
  • #393 A household has a plan (after #392 and #380).
  • #394 A plan's limits are enforced (after #393).
  • #395 Reset a password by email. The first email the app sends.
  • #396 Public sign-up that resists abuse (after #395).
  • #397 Pay for a plan, manage it and cancel it (after #394 and #395). Not offered at a hosted instance before #390 closes (ruling 46).
  • #398 What a household keeps after a downgrade (after #397).
  • #399 Off-host backups for a hosted instance, with a restore drill (after #392).
  • #400 Terms, privacy and refund pages, with the rule for children's sign-ins. Before the first sale.

The source offer on every page is #374.

Housekeeping lane

Taken between specs.

  • #34: show the unofficial-content notice and the source attribution in a footer on every page (research 016). Done 2026-10-12: spec 018, PR #67.
  • #35: fit card images without cropping (research 016). Done 2026-10-12: spec 019, PR #66.
  • #59: browse the catalog without signing in: search and card pages open to everyone, with the collection parts shown only to a signed-in collector (ruling 27). It is an operator setting, off by default (ruling 30), and a hosted instance turns it on. In progress: spec 023, PR #98 (draft).
  • #19: tighten bin/image-smoke's catalog:status check. Done 2026-10-13: PR #82.
  • #21: record the remaining spec 012 evidence.
  • #31: local image builds contain the OCR engine twice. Done 2026-10-13: PR #82.
  • #60: the catalog page reads "Running." after a crash until a retry or 15 minutes pass (noted in spec 015). Done 2026-10-13: PR #69.
  • #61: a retried job shows "Attempts 0" (noted in spec 015). Done 2026-10-13: PR #70.
  • #62: the catalog search system spec that times out on GitHub CI only. Done 2026-10-13: PR #71.
  • #63: the README introduction still says accounts and collections aren't built. Done 2026-10-13: spec 020, PR #72.
  • #64: currency is an instance setting and should be a per-account one (hosted-door rule 3). Built: spec 038, PR #173.
  • #65: decide whether fading the tiles of unowned cards fits Scryfall's image guidelines, and mark them another way if it doesn't (found while specifying #35; research 016 didn't examine it). Done 2026-10-13: ruled on in decision log 33, spec 021, PR #88.
  • #73: the art index reads "Building." after a crashed build until the build goes stale (issue #60's flaw in the art operation; found while fixing #60). Done 2026-10-13: PR #75.
  • #74: the Scryfall client sleeps for whatever Retry-After says, with no upper bound (found while fixing #60). Done 2026-10-13: PR #76.
  • #77: an admin can run a waiting rate-limit retry now (spec 055); discarding one from /admin/jobs is out of scope (review of PR #76).
  • #78: a second refresh can ask the source while another waits out a rate limit (review of PR #76). Done 2026-10-14: spec 024, PR #96.
  • #79: a hung art build reads "Interrupted" with a disabled button, where a refresh reads as stalled (review of PR #75). Done 2026-10-13: PR #85.
  • #80: the art index panel reads plain "Queued." while its retry waits, with no reason and no time (reviews of PR #76). Done 2026-10-13: PR #85.
  • #81: after a 429 with no usable Retry-After, the Scryfall client retries inside the 30 seconds the rate limit lasts (noted by the author of PR #76). Done 2026-10-13: PR #87.
  • #84: the admin catalog shows raw exception classes when a refresh or build fails (found in the review of the fix for #79 and #80). Done 2026-10-14: PR #95.
  • #86: rate-limit retries count over a job's whole life, so a long build can run out (found in the review of the fix for #81).
  • #102: keep the current architecture in area docs, starting with catalog operations, with a specs index, frozen specs and plans retired after merge (maintainer rulings 2026-10-15). In progress: spec 027.
  • #103: adopt YARD for the Ruby code's documentation, with the area docs linked in (spec 027 slice B). In progress: spec 054, ADR 0027.
  • #104: area doc for catalog core (spec 027 slice C).
  • #105: area doc for collection and lots (spec 027 slice C).
  • #106: area doc for tenancy and accounts (spec 027 slice C).
  • #107: area doc for the scanner (spec 027 slice C).
  • #108: area doc for data portability (spec 027 slice C).
  • #109: area doc for release and deploy (spec 027 slice C).
  • #118: system specs follow the host's dark mode, so light-theme examples fail; the default driver is pinned to light, and the dark drivers take the first driver's Firefox binary (found while running bin/ci for spec 028). Done 2026-10-20.
  • #145: spike: why bin/ci grew from minutes to 20–30, and why the pre-push hook stopped gating past its timeout. Done 2026-10-31: findings in research.md; the fixes in #147 (the parity example) and #148 (the hooks block on a timeout).
  • Spec 035, from #145: bin/ci groups, used by GitHub's RSpec shards and by the pre-push hook, which skips RSpec for a documentation-only branch. Shipped 2026-11-01: spec 035, PR #149, with its verification, review fixes and four shards in a follow-up pull request; GitHub's verdict went from a median 348 s to 140 s.
  • #164: dependency advisories: Dependabot's security updates for the Ruby gems as one group, a daily scheduled run of both audits on main, and the response to a red audit written into the release-and-deploy area doc (found on 2026-11-03, when five Dependabot pull requests failed on advisories for gems that no Dependabot pull request covered). Done 2026-11-03: spec 036, PR #163; the maintainer's post-merge checks are in its verification.md.
  • #401: contribution policy: a sign-off on every commit, and licence identifiers in the source (accounts design, 2026-11-13).
  • #402: CI fails on a dependency whose licence isn't allowed (accounts design, 2026-11-13). In progress: spec 091: a bin/ci checks step judges the gems and the manifest's JavaScript, OCR, font and icon entries against an allowed list in config/licence_policy.yml, with named exceptions.
  • #122: the art index panel and catalog:status say "ready" when the finished build's index file is missing (after a restore, or a lost directory). Done when its pull request merges: spec 039.
  • #374: show the running version, the commit it was built from and Collector's licence (AGPL-3.0, with a link to the source of the running build) in the footer on every page; the image carries its build facts and bin/image-smoke checks them. In progress: spec 084.
  • #376: list the licences of the third-party software and assets in the image (the gems, the OCR engine, the JavaScript, the fonts), readable from the app (split from #374 by the maintainer's ruling of 2026-11-13, spec 084 decision 8). In progress: spec 087.

Parked until after 1.0

Item Deferred by
Estimated value, price charts, value over time, price alerts, "Update prices" Specs 002, 004, 006; ruling 2026-10-11. Market prices themselves moved into 1.0 on 2026-11-13 (rulings 35–40, the prices lane)
Wishlists Spec 004; ruling 2026-10-11
Lending outside the household Spec 006; ruling 2026-10-11. Borrowing within a household is in 1.0 (ruling 47, #388)
Importing files from other tools Ruling 2026-10-11
Art matching on the photo path Spec 011; ruling 2026-10-11
Native apps Spec 005; ruling 2026-10-11
Quick filters (set, finish, condition), grid sort Specs 004, 006
Scryfall /migrations, set-change probe, digital-only printings, search syntax Spec 002
A general jobs console, settings for schedule and languages in the app Spec 015
Attestations and SBOMs, GitHub Releases, a version shown in the app Spec 012

The second half of the table wasn't ruled on in the interview. Those items were deferred by their specs and no 1.0 theme needs them.

Decision log

Rulings by the maintainer. Later planning builds on these and doesn't ask them again.

2026-10-11: north-star interview

# Question Ruling
1 What outcome means success in a year? The maintainer's own and family's collection hosted in Collector, and a hosted offering available.
2 What form does the hosted offering take? Undecided. Keep the door open; no commitment to paid, free or invite-only.
3 What must exist before the family's real collection moves in? Data safety, locations, comics. Market value is not a blocker. (Comics made conditional by ruling 18.)
4 In what order? Data safety, then locations, with the comics source research alongside. (Typed entry placed between them by ruling 16.)
5 How do family members' collections relate? Both personal collections and a shared household one.
6 When does that land? After 1.0, with no early decision on the ownership model. A format bump and migrations are accepted then.
7 Where does the scanner stand? The scanner as built is parked. Bulk entry is the 1.0 need.
8 Which bulk entry paths are needed for 1.0? Continuous scanning and fast typed entry. Not importing other tools' files. (Sitting-wide defaults reversed by ruling 20.)
9 What does comics in 1.0 include? It depends on the research; the maintainer rules on the scope from its findings.
10 Which rules keep a hosted service possible? All four hosted-door rules in the north star.
11 What marks 1.0? The three checks of the 1.0 test. No date.
12 How large is a spec? One outcome, one PR.
13 What about foundational decisions with no ADR? Backfill the load-bearing four: ADRs 0016–0019, each statement confirmed by the maintainer. Hotwire without Node and Solid Queue inside Puma stay as rules.
14 Which items are confirmed as after 1.0? Market prices and value; wishlists and lending; hosted-service features.
15 Which parts of the scanner's tail are in 1.0? Japanese cards, the unseen-card margin sitting, detection on live frames. Art on the photo path and native apps are after 1.0.
16 Where does bulk entry sit? Typed entry after data safety; the scanner work after locations.
17 Are the instance settings a breach of rule 3? Only currency. Catalog languages and art matching are operator settings. Scryfall's terms are unchecked and become item 1.
18 May comics leave 1.0? Yes: comics may move out of 1.0 entirely on the research ruling. Theme E is last on the line.
19 Does new collector-owned data extend the export in the same PR? Yes ("export covers it").
20 What does a sitting set once? Location, condition and language.
21 Which language does the non-English spike target? Japanese.
22 What about the milestone titled "MTG & Comics"? Renamed on 2026-10-11 to drop comics; they are added back if the ruling puts them in.
23 Spec 004's admin users page shows copy counts and deletes collections with their users. Is that a breach of "the operator is not the user"? No. The rule is narrowed to the items in a collection: an admin page never shows or edits them. Account management and aggregate counts are allowed.
24 Does the goal name the hosted offering? Yes, as an outcome wanted after 1.0, kept open and not scheduled.
25 What does issue #23's research produce? Findings and a recommendation. The maintainer rules on them before any comics spec is written; the issue was updated to say so.
26 When does the comics source research start? Deferred for now, with no start set. This replaces "alongside" in rulings 4 and 18; theme C doesn't wait for it.
27 Does Scryfall pass the "source terms allow hosting" rule? Yes for a free hosted service. For a paid one: any Wizards of the Coast or Scryfall data is publicly accessible on a hosted instance, with search open to everyone including unauthenticated visitors, and no paid plan is built until Wizards' position is settled.
28 What about the notice, attribution and image-fit gaps? A footer notice on every page (issue #34), and the image-fit fix (issue #35).
29 Are anonymous card pages parked with the hosted-service features? No. Ruling 27 covers them: card pages are opened with search, as one housekeeping candidate.
30 Is the catalog open to visitors on every instance? No. It is an operator setting, off by default; a hosted instance turns it on.
31 How is the backlog tracked ahead of 1.0? In GitHub issues on the 1.0 milestone and in this roadmap: one issue per candidate, created on 2026-10-11 (#37–#64, with #19, #21, #31, #34 and #35).

2026-10-11: export format (spec 017)

# Question Ruling
32 What is the export format? One JSON document per account, keyed by the catalog source's ids, holding the profile, one currency and the lots. Its version is a whole number that rises when an older reader would misread a file or lose the collector's data from it, so locations will make version 2. The rulings are decisions 1 to 20 of spec 017, recorded in ADR 0020.

2026-10-13: unowned tiles (spec 021)

# Question Ruling
33 Does fading the tile of an unowned card fit Scryfall's image guidelines? The fade goes. The card image is shown as supplied, with nothing over it, and an unowned tile carries a visible "Not owned" marker under the image. Chosen from four rendered looks at desktop and phone width in both themes (#65, spec 021). Whether the quantity badge on the image counts as a "stamp" under the same guideline is not ruled on.

2026-10-21: locations (spec 029)

# Question Ruling
34 Do locations make the export format version 2, as ruling 32 says? Yes: ruling 32 stands for the locations list (the places themselves, spec 029 decision 1, ADR 0023). Putting a lot in a location (item 10) is a further change to data the collector owns and raises the format to version 3.

2026-11-13: market prices (price data design)

# Question Ruling
35 Do market prices stay parked until after 1.0 (ruling 14)? No. Recording prices, and a basic display of them, move into 1.0 as the prices lane (design). Estimated value, charts, value over time and alerts stay after 1.0.
36 Where do prices come from? Scryfall's bulk file, the catalog's own source. Sources are pluggable, and only Scryfall's is built. Card Kingdom's price list is left out because its terms for commercial use are unclear.
37 Who sees prices and their history? Everyone who can see the card: anonymous visitors of an open catalog and free accounts as well as paid ones (ruling 27). No price API or dataset is published.
38 How much history is kept? A hosted instance keeps it for the whole catalog. A self-hosted instance chooses a level, and the documentation says what each costs in disk.
39 How is history stored? Changes only: a row when a price differs from the last one recorded. Thinning old history is a later concern.
40 What does the price refresh record about itself? Each run's work and the prices database's size, to measure growth in the beta environment. This covers the price refresh only, not the catalog refresh.

2026-11-13: prices on non-English printings (research 083)

# Question Ruling
41 What price does a non-English printing show? Option C of research 083: Scryfall's file carries no price of its language for a non-English printing that has an English twin (the English printing of the same set code and collector number), so such a printing shows the twin's price for the same finish, labelled as the English printing's, and nothing for a finish the twin hasn't. A printing with no twin is a product of its own and shows its own price. The consequences for #364, #365, #368 and #369 are listed in the research note.

2026-11-13: households and the hosted service (accounts design)

# Question Ruling
42 What form does the hosted offering take (ruling 2), and under which licence? A paid service with a free plan, on the same AGPL-3.0 code. Collector stays one codebase with no proprietary add-ons, and a hosted instance differs from a self-hosted one by configuration only. The service sells hosting, backups, catalog upkeep, household sharing, support and, later, AI features on the operator's keys. Plans are priced per household (design, decisions 1 and 5 to 8).
43 Do personal and household collections side by side stay after 1.0 (ruling 6)? No. They move into 1.0 as the households lane, alongside the deck and location work.
44 What is the ownership model? A household of accounts: an account stays the unit of ownership and privacy, and a household has each member's own account and one shared account. A member or the household can own a deck, a binder or any other location. A kid's collection is treated like any other member's and isn't visible to other members by default. The ADR that supersedes the one-user half of ADR 0017 is written with #380.
45 Do hosted-service features stay after 1.0 (ruling 14)? No. Hosted mode, plans, limits, billing, email, public sign-up and operator backups move into 1.0 as the hosted lane, to take a hosted service to market sooner. The 1.0 test is unchanged.
46 Does ruling 27's "no paid plan is built until Wizards' position is settled" hold the billing code back? No. Ruling 27 is narrowed from "built" to "offered": the plan and billing code is built behind hosted mode while the position is being settled (#390), and no paid plan is offered at a hosted instance before it is. The rest of ruling 27 stands.
47 Is borrowing from the household's collection in 1.0? Yes (#388). Borrowing and lending are needed for a household to work well, so the scope is accepted.