miton

In development. The beta will be a downloadable desktop app with automatic updates. Access is not open yet.Request an invitation.

Roadmap / qualified commitments only

V1 closes the loop. The roadmap extends it.

This page says what is intended, what evidence would make it real and what remains a direction. It deliberately contains no invented dates.

Building for v1

The complete real-software promise.

These outcomes remain future tense until their release evidence and claim gates are green.

01

Equivalent Windows, Linux and macOS outcomes

The v1 programme targets the same core features and project outcomes across Windows, Linux and macOS.

Gate: v1-cross-platform-release

02

Documentation produced with the project

The v1 programme joins project knowledge, Writer and delivery workflows into a maintained documentation suite.

Gate: real-software-documentation

03

Front end and back end in one delivery loop

The v1 programme extends Canvas and Code from the shipped supported projection into complete framework write-through, verification and repository delivery.

Gate: real-software-front-back

04

A shippable project artifact

The v1 programme closes the loop from project intent to a verified, packaged artifact with an inspectable hand-off.

Gate: real-software-artifact

Directional roadmap

Useful direction without a release fiction.

External SDK and control plane

The roadmap extends project and goal control beyond the desktop through a documented SDK, CLI and local control plane.

Subject to change as the beta and v1 evidence changes.

What will not move.

  • Bring your own models. Workspace value does not depend on reselling a token allowance.
  • Local models stay first-class. Privacy is not a degraded execution tier.
  • Safety remains inspectable. More agency does not justify fewer visible controls.
  • One project remains the unit of work. New surfaces must join project context rather than fragment it.