Docs / Roadmap

Follow the project from what already works to what comes next.

This page tracks the project as a vertical roadmap: the working base at the top, the active build-out in the middle, and the upcoming deployment and catalog work further down the page.

Implemented In progress Upcoming Longer term

Implemented

The working base is already here

The core model is not hypothetical. The hosted demo, local runtime, admin workflows, and collection architecture already exist as a working system.

Hosted demo

Implemented

The public app already shows the main interaction: ask a question, search a bounded collection, and inspect the source behind the answer.

Open the demo

Local runtime

Implemented

The same runtime can already run locally, including offline-oriented and Raspberry Pi deployments.

See hosted vs local

Local admin and ingestion

Implemented

Source creation, validation, translation workflows, PDF handling, and ZIM ingestion are already part of the public project.

Read local admin docs

Collection and pack model

Implemented

The knowledge layer is already separated from the runtime, which makes the current preparedness library reusable instead of one-off.

Read collections model

In progress

The current push is making the self-host path clearer

The project is moving from "interesting demo" toward "clear path to running your own version," with the site, docs, and deployment story being tightened around that goal.

Download-first site path

In progress

The site is being rewritten so the demo leads naturally into understanding the model, inspecting the collection, and then going to GitHub when you are ready to install it.

Progress

Cleaner deployment model

In progress

The product surfaces are settling into a clearer shape: hosted demo, local runtime, advanced local admin, and the future private control layer around them.

Progress

Read platform overview

Public/private split

In progress

The public repo is staying the engine. The private side is becoming the product shell, catalog, and future control-plane layer around it.

Progress

Upcoming

The next gains come from visibility, packaging, and updates

The next stage is less about proving the engine works and more about making collections, updates, trust signals, and deployment choices easier to understand and use.

Data-driven collection pages

Upcoming

The site should expose real collection metadata, visible source composition, trust badges, and richer profile pages instead of relying mostly on editorial copy.

See current collection page

Update and manifest layer

Upcoming

Local installs need a clearer way to discover app updates, collection updates, model changes, and compatibility notices.

Read deployment context

OCR for scanned PDFs

Upcoming

Image-only PDFs are still a major blind spot. OCR preprocessing is one of the most practical near-term upgrades for archival and historical material.

Read local admin docs

Public trust signals

Upcoming

Collection quality, validation status, licensing, and hosted-versus-offline readiness should become easier to understand at a glance.

Read the trust model

Longer term

The longer arc is a smoother hosted-to-local ecosystem

The long-range direction is a more complete system where hosted use, local installs, selected packs, profiles, and update flows fit together without losing the project's offline-first character.

Downloadable runtime experience

Make the self-hosting path feel more like a real product download and less like a raw code handoff.

Selected packs and profile syncing

Let the hosted side and local installs share more of the same selection and update model over time.

Offline-first distribution layers

Keep improving the path for air-gapped, Raspberry Pi, and constrained-network deployments instead of treating them as edge cases.

Richer public catalog

Present collections as inspectable, versioned knowledge artifacts with visible quality and publication status.