Ouroboros roadmap

One workflow,
more places to use it.

Purpose

Ouroboros is building one way to turn a conversation into work that can be specified, checked, and used again. This page shows the product path, the work now under way, and the conditions that must be met before later products are opened.

Available nowOpening nextLater paths

What stays the same

The product is not a feature for one model or one app. It is the working loop that remains when the model, runtime, and channel change.

Clarity first

The work starts by finding what the person means. A prompt is not yet a specification.

A real test

A result has to meet declared criteria. Looking plausible is not a verification method.

III

Something remains

The next run should not begin from a blank page. It should inherit the useful parts of the last one.

The product loop

Five stages turn intent into work that can be checked and used again. Each stage leaves something the next run can inherit.

InterviewFind the intent and the missing decisions.

SeedWrite down the agreed specification.

ExecuteDo the work that the specification calls for.

EvaluateCheck the result against its criteria.

EvolveCarry the evidence into the next version.

↺ the evaluation changes the next Seed

Seedthe recorded intent

Workflowthe route that worked

Evaluationthe evidence behind a decision

Lineagewhat changed, and why

Who it is for

The early market is defined by a work situation, not by age or job title. The common thread is that the person has context worth carrying forward and an outcome that cannot stop at a plausible draft.

Context to delegate

Owners and operators who already spend time or money handing work to an assistant, a colleague, or an outside specialist.

Work that repeats

Advisors and service providers whose replies, documents, and decisions keep taking time away from the work they are paid to do.

III

More than a demo

People who have tried many tools but still need work that survives a second pass and can be used again.

The road ahead

The sequence begins with access, moves to repeated use, and only then opens managed and enterprise delivery.

Now

Open coreThe shared foundation

Keep the specification, evaluation, and lineage workflow open and useful across supported runtimes.

Public source and runtime guides

Now

Public entryDesktop first

Give people a practical way to start the Ouroboros loop from tools they already use, beginning with ChatGPT desktop.

Windows and Apple Silicon delivery

Work beyond codingNondeveloper use

Test whether people can turn their own material and working context into a personal system for recurring work.

A first real task, followed by reuse

Managed setupConcierge

Help early users discover their intent, set up the first workflows, and tune them through ordinary use.

A repeatable paid delivery method

Later

Persistent and governed deliveryCloud and enterprise

Add always-on operation, data boundaries, approvals, audit records, or service commitments when customers show that they need them.

Customer demand and workable economics

Product horizons

The product stays the same while access, service, and governance become broader.

Horizon	Product form	User outcome	What opens the next horizon
Open foundation	Core workflow across supported runtimes	A specification and evaluation record that survives a tool change	Reliable public entry points
Everyday use	Desktop and hosted entry	A completed task without rebuilding context on the next run	Repeated use and willingness to pay
Managed service	Concierge setup and tuning	Useful workflows without learning another tool stack	A repeatable delivery method and known service cost
Governed delivery	Cloud and enterprise options	Continuity, control, and records suited to the customer environment	Portable workflows that work across customers
Workflow distribution	Marketplace	Reusable workflows shared or sold beyond their original context	Proved portability and sustainable distribution

Delivery paths

The later paths are delivery choices, not separate identities for the product. Each one earns its place by answering a specific user need.

Concierge

A person helps discover the intent, turns it into a working setup, and tunes it with the user. It matters first because early workflows do not yet exist on their own.

Gate
A repeatable delivery method from the first pilot.

Cloud

A managed always-on path is only useful if people need their work to continue while their own computer is off, and are willing to pay for that continuity.

Gate
Observed need for continuity and a viable operating cost.

Enterprise

The same workflow may later be delivered where data boundaries, approvals, audit records, self-hosting, or service commitments matter. That is not a v0 promise.

Gate
A real customer requirement and evidence that the workflow has value.

Marketplace

A workflow can only be sold or shared when it works beyond the person whose context created it. That portability has not been proved.

Gate
Several reused workflows that transfer across users.

Runtime independence

Ouroboros already works across multiple runtimes. ChatGPT is one public entry point. Kiro, Claude Code, Codex, Gemini, Copilot CLI and other supported environments are places where the same specification and evaluation discipline can travel. None of them define the product on their own.

What counts as progress

The first proof is a completed piece of work for a user. Revenue and distribution come after that. Targets follow observed baselines, not the other way around.

Completion

The specification is fully handled and the result passes its checks.

Preservation

A later run does not break what the earlier run completed.

Reuse

The next run uses the prior Seed or workflow without making the person explain the context and procedure again.

Delegated time

The amount of agreed manual work the system actually takes over.

Human intervention

Whether people are approving expected steps or rebuilding the work from scratch each time.

Operating cost

Whether runtime, support, and maintenance cost can be traced back to each workflow.

Reading this roadmap

This roadmap shows product order rather than fixed launch dates.
Cloud, enterprise, and marketplace remain candidates until the current pilots establish demand, reuse, and workable economics.
Runtime names describe compatible places to run the workflow. They do not imply endorsement, sponsorship, or a commercial relationship.
The core workflow is open source at Q00/ouroboros. This page is updated as the work changes.

One workflow,more places to use it.