Roadmap¶
What is planned and what has shipped, from the trilium-recall engine to a core that knows no source.
Today a result is about 400 tokens, whatever was asked. It should grow or shrink with the question, and a hit should be readable in full from the index.
Details
- The budget follows the question and the room the agent has, not a fixed number.
- The full text of a hit comes from the index, so the agent no longer calls the original source.
Compare an agent that searches with passageway to one that reads whole pages, on the same questions, and publish the difference with the method.
Details
- The same questions, once with passageway and once with whole pages read.
- Tokens and cost, published with the method and the confidence interval, like every other number here.
A search and chat app that embeds the core, with an optional generator for people who want an answer instead of passages. The core stays the search.
Details
- The UI embeds the core; it does not change it.
- A generator is optional and lives outside the core, so passageway itself still returns passages.
The documentation moved to getpassageway.com; the old address and the .eu, .de and .info domains redirect there, so existing links and installed skills keep working.
trilium-recall is superseded and archived. Its last release, 0.7.0, says so and links a guide to switch; its code stays as it was, there are no users to migrate.
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: 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.