Roadmap¶
What is planned and what has shipped, from the trilium-recall engine to a core that knows no source.
After parity, trilium-recall points here. The pull request with the migration guide is open there, for the owner's review.
Details
trilium-recall becomes a thin distribution (a passageway.toml with the Trilium connector, its plugin, docs that point here) or is archived with a pointer. It is a breaking change for its users, so it needs a migration guide:
RECALL_*becomesPASSAGEWAY_*;- the tool's
instanceargument becomessource; - configuration moves to
passageway.toml.
The prompt hook with its self-test and the setup skill in the plugin, the image with the model baked in, and passageway init with a launchd example.
An adapter for OpenAI-compatible services and Voyage; three built-in presets with a checksummed download and a measured gate each; CoreML measured and left opt-in; the models compared on the corpus.
The trilium-recall sync as a connector. On trilium-recall's public fixture (its synthetic wiki, the real model, an in-test ETAPI) it scores hit@3 0.92 and silence 1.0 against the published 0.83 and 1.0; the check against a live Trilium and the private question set is still the owner's to run.
100 public questions for the sample corpus, and the numbers they give with the multilingual e5-small model.
Weekly grouped bumps, with auto-merge for patch and minor ones once the required checks are green.
Built strictly on every pull request and published on its own domain.
Index a topic, some articles or a place, in English and German.
The connector protocol, a generic index, a sync with a deletion guard, passageway.toml, bearer and OAuth authentication.
The trilium-recall engine imported with a fresh history. The last commit with all its Trilium code is a tag.
Parked¶
Considered and wanted, not needed yet: publishing the SDK and the connectors to PyPI (#28, waits for a dependency that is not on PyPI); cleaning the formulas in the live Wikipedia connector the way the sample corpus does (#33); a reranker, and charts in evaluation reports, until a measurement shows what they would add (V3).
Decided against¶
Generation or summarisation inside passageway (it returns passages only: V4); stdio MCP, because the index and the sync loop must outlive a client session; per-connector access control, because one recall searches every source and the callers are one person's or one team's tools: index only what every caller may see; a service installer in v1.
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.