Vivary
Menu

Public product roadmap · August 2026

Prove the loop before expanding the surface.

This is an outcome map, not a feature warehouse. The five-file Core is published, and the local read-only MCP adapter is published as an optional package that stays off by default. Vivary wins only when that smaller seed survives real work, clean release proof, and the right human gates.

See what is nowRead the canonical repo document

What progress means

Four loops. Every item must strengthen one.

  1. 01

    Comprehension

    Understand the system and run something useful.

  2. 02

    Adoption

    Feel value on the project you already have.

  3. 03

    Retention

    Return because the workspace gets healthier.

  4. 04

    Evidence

    Inspect and reproduce the claims.

Now · prove the release candidate

Make the smaller seed trustworthy on real work.

Local implementation evidence is not publication. The current bottleneck is a clean, reproducible candidate plus benchmark, dogfood, remote CI, and independent human review.

  1. 01

    Prove the lightweight release candidate

    Verify every policy-only preset starts with five files, MCP reads without materializing content, and one exact-hash transaction writes one earned record.

    Proof

    Local acceptance matrix, clean artifacts, rendered docs, and green remote CI before publication.

  2. 02

    Publish the benchmark

    Measure tokens, turns, files opened, wrong files opened, and answer quality on a fixed public repository.

    Proof

    Methodology, raw results, charts, and known limitations. No result is claimed yet.

  3. 03

    Dogfood brownfield adoption

    Run the dry-run, exact-hash apply, privacy, recovery, and Doctor path on representative real projects without taking them over.

    Proof

    At most three payload files, two bounded host integrations, explicit conflicts, and rollback evidence.

  4. 04

    Turn Doctor into the return loop

    Show what drifted, what it costs, and which reviewable repair has the highest expected value.

    Proof

    Repeat runs and repaired drift—not install counts.

Next · make the value compound

Turn findings into safe, repeatable action.

  1. 05

    Context-budget repair proposals

    Turn Ozone findings into safe, report-first actions.

  2. 06

    Module index planner

    Propose useful routers without reorganizing the project.

  3. 07

    Privacy-safe proof packets

    Leave a compact artifact another human or agent can inspect.

  4. 08

    Named-client MCP conformance

    Prove the local stdio adapter on supported agent clients without widening its authority.

Later · grow only from evidence

Add capability without turning Core into a file pack.

  1. 9

    Explicit richer workspace modes

    Add lazy records or adapters only after real work or a deliberate operator choice—never as Core seed content.

  2. 10

    Typed recall providers

    Improve optional semantic recall without creating a second truth store.

  3. 11

    Integration proof matrix

    Make install, network, storage, approval, and removal boundaries explicit.

Deliberately deferred

Weight is not progress.

These ideas are not forbidden. They wait until repeated evidence shows a problem the current plain-file and CLI surfaces cannot solve.

The working truth lives with the code

Inspect the complete roadmap, stop rules, and review cadence.

Open the repo documentSee the issues