Decisions and alternatives
These records describe current system tradeoffs. Changes require a new record with context, decision, alternatives, consequences and validation evidence. Superseded records remain readable.
ADR-001 — Portable desktop, local engine
Decision: Tauri Windows shell, shipped Node calculations, HTML/CSS/JS interface. Why: retain local data and share calculations between application and harness. Alternative: hosted account service, adding synchronization and data exposure. Cost: distributed runtime, required WebView2 and separate Windows qualification.
ADR-002 — Observe data, leave actions to the player
Decision: read SavedVariables as data, use manual exports and transactions in TSM. Alternative: automate game interactions. Consequence: refresh cannot force WoW to save; a prepared import is not an applied import. This separation is an intentional product boundary.
ADR-003 — Unknown stays unknown
Decision: never infer a sale from disappearance or invent historical cost. Alternative: fill every field with current market values. Consequence: partial but explainable accounting coverage. TSM net receipts never incur a second commission.
ADR-004 — Exact identity before aggregation
Decision: full itemString, profile and character at evidence boundaries. Alternative: group everything by base item ID. Consequence: fewer false matches, more review cases for variants and incomplete history.
ADR-005 — Explainable rules, limited trials
Decision: recent observed demand, small trials, stock deduction, reserve and fresh prices. Alternative: theoretical-margin ranking alone or opaque prediction. Consequence: the plan is conservative and greedy, not globally optimal or a calibrated sale probability.
ADR-006 — Measurable quality and attested packages
Decision: Node/Lua/Rust tests, targeted mutations, financial coverage, Fallow and source digests. Alternative: manual interface checks alone. Consequence: documentation edits can invalidate a package's source attestation; rebuild evidence before another application release. Existing delivered ZIPs remain immutable.
ADR-007 — Bilingual static documentation
Decision: VitePress 1.6.4, Vue, local search and separate package. Alternative: monolithic manual or hosted CMS. Consequence: better navigation and offline use after compilation, with two languages to maintain. Vite is overridden to 6.4.6 to avoid known advisories in the stable transitive chain; audit and build must remain green. Documentation does not add Vue to the desktop runtime.
ADR-008 — Component versions and private Git
Decision: independent desktop, Companion and documentation versions in versions.json; annotated tags, initially private repository, no real data. Alternative: one number forcing all components to be republished. Consequence: every release states its compatibility matrix. Initial tags import candidate sources; they do not reconstruct earlier history.
ADR-009 - Shared design, adapted rendering
Decision: common CSS tokens and local assets adapted to three surfaces. Alternative: rewrite all interfaces in one framework. Reason: immediate consistency without rewriting the engine or adding desktop weight. Cost: maintain adapters; CI checks generated copies and both languages.
ADR-010 - Guided, recoverable installation
Decision: NSIS installs the desktop per user; the local assistant validates the WoW client and deploys Companion with backup/journal. Alternative: multiple ZIPs or editing SavedVariables directly. Consequence: one download, no manual copying; WoW must be closed and TSM remains separate. Ambiguous choices are not guessed and uninstall retains data.
ADR-011 - Attested publication before website promotion
Decision: monorepo, Actions, immutable R2 paths per run, then Pages after public-byte verification. Alternative: manual uploads or publishing the site before the binary. Consequence: the page never advertises an unverified download; automatic Pages rollback on failure. Initial secret connection remains an account operation, separate from repository code.
