Vivary
Menu

Public product roadmap · July 2026

Prove the loop before expanding the surface.

This is an outcome map, not a feature warehouse. Vivary wins when an agent finds project truth with less context, acts with a visible blast radius, and stops at 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 adoption line

Make the value visible on real work.

The architecture exists. The current bottleneck is whether a new person can understand it, use it on an existing project, return, and verify the claim.

  1. 01

    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.

  2. 02

    Make brownfield adoption the default

    Tighten the read-first path from map to dry-run adoption to a clean doctor result on real projects.

    Proof

    Code, docs, and private-vault fixtures across Windows and Unix paths.

  3. 03

    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.

  4. 04

    Publish one honest case study

    Show the exact starting mess, approved writes, before-and-after map, friction, and follow-up issues.

    Proof

    A real project that was not arranged to flatter Vivary.

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

    Starter workflows

    Ship a few verified recurring loops instead of a pile of presets.

Later · meet agents on existing rails

Integrate only after the core proof is strong.

  1. 9

    Read-only vivary-mcp

    Expose find, query, and check on the rails agents already use.

  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