Where questlog is going¶
questlog started on 2026-10-30, from a quest log, a build page and a mechanics page Claude kept in a Trilium wiki while Marcel played Lies of P. It is becoming the place Claude files a play session into and reads "where was I?" back from, for any game, without spoilers.
This page says what is planned and why, inside the values, and what has shipped. Each step links its issue and the value it serves. Planned steps have no dates, only now, next or later; shipped steps carry the day they shipped.
The idea behind all of it¶
Talking while you play is the interface; questlog keeps what is true for your playthrough, and shows only what you found.
Free tags on items, codex entries and quests, made up and reused by Claude as it files; a tag row filters the tab you are on.
Coloured tabs, readable with colour blindness, split a playthrough's page into overview, character, quests, items, codex, sessions and notes; flags switch the language.
What questlog stands for, and ADRs for the app, lookups and sign-in.
Parked¶
- A household or shared log: two players following the same playthrough. Each log is its player's alone today (V2); sharing would be an explicit choice, not a default.
- Screenshots kept as files: a shared screenshot is read and filed as text and numbers (V3); questlog doesn't store it.
Decided against¶
- A game database or a mirrored wiki: it would be the spoiler source V1 rules out and copy other people's work (V6, ADR 0002).
- Statistics across players: they would show one player's log to others (V2).
Keep it true¶
The timeline is rendered from docs/roadmap.yml; on GitHub, read that file. Finish a step in the pull request that finishes it: set status: done, replace when with a date, add the link to its pull request, and move it to the top of the shipped entries. Change the file in the pull request that changes the plan.