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

# What Factory does for your project.

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

Factory gives your coding agents a shared understanding of the product they’re working on: what it does, what’s going wrong, what matters, and what has already been tried.

It connects the evidence in your repository and configured sources to a product map. From there, it helps you decide what to improve, gives agents bounded work and keeps the evidence needed to check the result.

## Start with the user’s job

“Sign up” is a product capability. The form, authentication service and verification email are the pieces behind it. Factory links them so a technical issue has a human context.

User goalProduct capabilityCode + evidence

## Keep two questions separate

*   **Did the change work?** Check the actual released behavior, with verification separate from the agent that made the change.
*   **Did it help?** Look at a meaningful user or business outcome. An improvement in a metric alone does not prove what caused it.

**Try the public demo board.**

Explore seven capabilities and 14 sample signals, including automations and paid upgrades. The board shows current work; Last 7 days / Last 30 days filters charts and activity. Each capability has one main metric and up to two supporting measures, with one chart and a practical Advisor suggestion. Chat quality is a score out of 100. Open F-17 to inspect its repair and recurrence history, or Project creation to try the evidence counter. The inbox tags updates by capability, priority and affected surface (Web, Mobile or Backend). Surface tags are declared in each example, not inferred from its log source. Expand Uses to inspect agents and services. Session service links three capabilities to one F-17 repair; Not measured means a check is missing, even if no issues are linked. All data is illustrative; the full pilot and expanded inbox remain roadmap examples.

[Open the interactive demo](https://www.orchestro.org/demo)

## Get oriented

[**Factory lifecycle**A report in the backlog is not a promised PR. Follow classification, shared problems, selection, root cause, verification, evidence waits and Backlog Zero.](https://www.orchestro.org/docs/factory/lifecycle)[**Quickstart**Set up Agent Factory, check your coding CLI and connect a project in observation mode.](https://www.orchestro.org/docs/quickstart)[**How the loop works**How Factory connects product mapping, recommendations, owner decisions, agent work and verification.](https://www.orchestro.org/docs/how-it-works)[**Work, waits & evidence**Follow 12 signals into actionable work, evidence waits and independent verification. See incremental sample targets, return conditions and shared-cause history.](https://www.orchestro.org/docs/work-lifecycle)

**Early access, actively being built.**

The website’s examples explain the design; they are not connected to live customer data. The [availability page](https://www.orchestro.org/docs/roadmap) separates implemented pieces from the complete loop we’re working toward.