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

PUBLIC DEMO / NO SIGN-IN

# The agent said “fixed”.  
See what happens next.

See how your app is doing and what needs attention.  
Explore the metrics, advice and work behind each capability.

ARVO-inspired app · Illustrative data and workflow UI, not a live ARVO board. Nothing here runs an agent or changes a project.

**ARVO**/ sample workspace

SAMPLE DATA 

**Current work**Sample as of Sep 15, 2026 · 12:00 UTC

Charts & activity

14 signals[Inspect S01 ↓](https://www.orchestro.org/demo#demo-inspector)

Pick a capability

See its metric, history and next improvement.

ARVO / product mapWhat needs to keep working

Sample measurements · last 7 days

## Onboarding

Target 64%

Uses 1 agent · 2 services

Eligible sign-ups that create their first project within 24 hours.

Sep 9Latest sample · Sep 15

AdvisorFix account switching; keep the optional-step experiment separate.

How it’s measured & sources

**Sample:** 1,000 sign-ups per 14-day cohort. Each cohort has completed its 24-hour observation window. Illustrative data; a trend does not prove a fix caused it.

**Keep in check:** No increase in account-creation errors.

Sign-in screen → Session restore → First project

Repository

Sign-in screen and session restoration path

Database

Sample accounts and first-project events

Server logs

Callback requests with missing workspace context

**Missing:** No session replay attached: the reason for leaving the company-size step is still a hypothesis.

[Metric definitions](https://www.orchestro.org/docs/how-it-works#success-metrics)

ALL SIGNALS

S01 / F-17

Reopened

## It came back. The history stays.

Now

Switching accounts can leave the workspace empty.

After · target

The correct workspace opens after an account switch.

Evidence

An account-switch test reproduces the failure. The earlier fix and checks stay attached.

Next

Reopen F-17. Cover account switching and rerun the checks.

F-17 · Problem history

1.  Sep 9 · Investigate**Investigation opened**
    
2.  Sep 10 · Repair**Cause confirmed · fix started**
    
3.  Sep 11 · Release**Fix released**
    
4.  Sep 13 · Verify**Live checks + follow-up passed**
    
5.  Sep 15 · Reopen**Problem returned · reopened**
    

[↑ Back to the board](https://www.orchestro.org/demo#demo-console)[How this lifecycle works](https://www.orchestro.org/docs/work-lifecycle)

## While you were away

Sample activity · last 7 days · UTC

+2 means two more affected capabilities. Priority does not mean you need to act. [Inbox availability](https://www.orchestro.org/docs/roadmap)

Local simulation · no live connectionsWaiting items do not hold up unrelated work.

Try an Advisor decision

## From advice  
to a measured result.

Try one onboarding change. Follow the decision, release and checks.

S12 / Product improvementPriority: review next

### Let people skip company size.

120 of 1,000 sample sign-ups leave here. Goal: first-project conversion 62% → 64%.

Try an optional field. Keep saved answers and measure first-project conversion.

**Try this change?**

Sample onboarding walkthrough. Full-loop proof and broader Advisor perspectives remain [roadmap work](https://www.orchestro.org/docs/roadmap). No real changes run here.

PUT YOUR OWN APP ON THE MAP

## Bring one repo.  
Start with observation.

Request the developer preview to try the underlying system with your coding agent. This board is a public workflow demonstration.

[Request the preview](https://www.orchestro.org/early-access) [Read the setup guide](https://www.orchestro.org/docs/quickstart)