Roadmap

This page says where PremAgentic is going: what is built, what comes next, and what is under consideration. It gives directions, not dates or version numbers. What is proven today is on the Known state page, and what changed in each release is in the repository's CHANGELOG.

01What is built

The four gates, access, lifecycle, trust and freshness, as hard SQL conditions over stock PostgreSQL with no extension; users, groups, agents and tokens administered from the command line and the portal; folder rules; password sign-in with sessions, agent tokens, and MCP over HTTP; one seam for the ways a person signs in, with groups from an outside directory mapped by an administrator; a filesystem connector with permission-change detection; readers for Markdown and plain text behind a reader seam; chunkers chosen per source; hybrid retrieval with the vector leg in process; the extension host with its allow list, the sample extension and the conformance kit; profiles validated, applied and shown; tuning per deployment, judged by a golden set; the review queue for machine-written content; an append-only change record with audit retention; setup on an existing PostgreSQL with least-privilege roles and row-level security; HTTPS, service hosting and a bundled PostgreSQL on Windows; removal; and an install proven on a bare container with no network route out.

02What comes next

• Word, PDF and Excel readers, as the first extensions. The reader seam is there; these are the formats most corpora arrive in.
• A connector that reads a file share's own permissions, so a document's access comes from the share that holds it rather than from a rule written beside it.
• Sign-in through a company directory, as a way of signing in on the existing seam: the directory says who you are, and the administrator's mapping says what that means here.
• An installer, so a deployment starts from a package rather than from a build.
• The clean Windows machine proof: the Windows service and the bundled database service starting under their own accounts, and removal taking them away, on a machine that has never seen the code.
• A packed conformance kit, so an extension author takes the fixtures as a package instead of a project reference.
• A calibration command for the no-answer floor, so a deployment can set, from its own golden set, the score below which search says it found nothing.

03Directions under consideration

• A deployment's own instructions for connected assistants, served over MCP. An administrator writes, in one place, how assistants should use this deployment's knowledge, and every connected client receives it at connect time rather than each one carrying its own file.
• The MCP authorization flow, so a third-party client signs a person in without a pasted token.
• An administration API, reads first, with writes as reviewed profiles: an assistant may propose a configuration, validation names what it would change, and a person applies it.

The invariants do not move: agents never write, the store holds no generated text, and nothing from a document is executed.