Repository navigation
docs: record that indexing runs in a worker draining a durable queue - #80
Merged
Merged
Conversation
This was referenced Nov 17, 2026
Closed
This was referenced Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Records the decision from the indexer redesign map (#65), ticket #70 "Where indexing runs and what triggers it". Docs only; no code changes.
The design the ADR records:
flowchart LR Admin[Admin pages] --> Q[(Durable queue of index jobs)] Deposit --> Q CLI[CLI: Import, pnpm index] --> Q Q --> W[Worker] Q --> CLI W --> DB[Database index] W --> S[Search index]The API only adds index jobs. The Worker runs them, and the CLI adds jobs and then runs the queue itself until it is empty.
Evidence
After: ADR 0005 and three glossary terms. The pre-commit checks (biome, tsc, knip) pass.
Merge Danger
Door: two-way
Documents a decision; reverting is a docs revert. The decision itself is the hard-to-reverse part, and it isn't implemented by this PR.
Blast Radius: docs
#79 also edits
GLOSSARY.md, so whichever merges second may need a rebase.