Source: https://www.orchestro.org/docs/roadmap
Updated: 2026-09-15

# Built, next, and still being explored.

Updated September 15, 2026[Read as Markdown ↗](https://www.orchestro.org/docs/roadmap.md)

Factory is in private development. Here is the difference between code that exists and the complete product experience we’re working toward.

Implementation snapshot · 15 September 2026

## Implemented foundations

*   **Product mapping and engineering memory:** connect capabilities and implementation context, with project history.
*   **Product-aware Advisor V1:** recommendations grounded in known work and available evidence.
*   **Owner decisions:** record what the owner accepts, rejects or defers.
*   **Capability success and benefit verification contracts:** define meaningful measurements and distinguish technical success from product benefit.
*   **Governed remediation execution:** bounded agent work, recorded evidence and separate verification.

Implemented foundations are not a claim that the entire product-outcome loop has been proven across production projects.

## Decision bridge and next product proof

1.  **Bridge owner decisions to governed work: implemented.** Explicit promotion connects accepted recommendations to the existing intake, checks current facts and preserves scope and authorization. Promotion does not start execution.
2.  **Run the complete product-outcome pilot.** Follow a real recommendation through work, release, technical verification and benefit measurement.

## Then: a wider view

*   Combine opportunity discovery with product, user and market perspectives.
*   Extend the living map to distinguish what is in code, released, enabled and observed.
*   Create a work inbox showing what happened and what needs someone’s attention.
*   Evaluate lessons before promoting them into durable operating rules.

## What the website demos show

The [Factory tour](https://www.orchestro.org/factory) connects signals, shared problems, fixes and verification. Its web/mobile testing switches illustrate a planned integrated journey runner, not available product settings. Project test and verifier commands are implemented. Complete Backlog Zero certification remains roadmap; see the [lifecycle reference](https://www.orchestro.org/docs/factory/lifecycle) for the current terminology and supported evidence waits.

The diagrams and seven-day onboarding example are interactive explanations with sample content. They are not customer dashboards, production metrics or evidence of a successful release. The full-loop walkthrough includes roadmap behavior.

## Help shape the next step

A small, real project with readable signals is more useful than a perfect demo. If you want to work through a pilot, [tell us what you’re building](https://www.orchestro.org/early-access).