← All experiments

ORCHESTRA · ARCHIVE LAB SIMULATED DATA

A repeated path is a question.

Watch a six-month synthetic archive move through motion screening, scene review and evidence checks.

Every moment, area, count and model output here is invented. This browser-only demo uses no real recordings, camera feeds, people or live findings.

Ready to explore · about 6 seconds

New · test the evidence gates across four synthetic scenarios New · run an animated six-stage Signal Lab New · tune a synthetic motion signature in Motion Studio New · explore the synthetic neighborhood City Lens New · orbit through six synthetic footage months New · tour the V-JEPA × Cosmos pipeline New · try the interactive mTLS Bridge Lab New · trace a request and watch a video stream return Or challenge the evidence gates
ABSTRACT CITY GRID SIMULATION / 06 MONTHS
A simulated movement pattern across an abstract city grid Four fictional areas connect through glowing paths. Animated dots represent generated sample moments, not people or real camera observations. GRID 01 GRID 02 GRID 03 GRID 04 GRID 05 OCT · SAMPLE WINDOW 06 GENERATED PATHS · NO CAMERA LOCATIONS
synthetic path generated moment No people or camera feeds shown

SCENE REVIEW / SYNTHETIC FEED WALL

Three views. One careful read.

Switch between generated scene patterns and watch motion, Cosmos review and evidence gates reach different stopping points.

BROWSER SIMULATION

THE MACHINE ROOM / INTERACTIVE MAP

Trace a request. Follow the work.

Pick a route to follow the public site, private requests, live analysis, and model training through Orchestra’s service layers.

SCHEMATIC · NO LIVE TRAFFIC
  1. 01CLIENTYour browserSigned-in video or API request
  2. 02PUBLIC EDGECloudflare WorkerPublic routing and site assets
  3. 03SITE GATEWAYWebsite and relayPublic files and private-request relay
  4. 04PROCESSING SERVICEPrivate serviceAuthenticated API, media, and state

PRIVATE REQUEST · DIRECT HOST BRIDGE

mTLS protects the service-to-service hop.

The browser reaches the public edge; the site gateway relays private requests directly to the processing service over TCP 443. Both services verify certificates and encrypt that connection. The app still checks the visitor’s session or key.

Direct service-to-service hopSeparate from the public page path
PROCESSING ROLESSCHEMATIC
PROCESSING · GPU 1Live detectorYOLO tracking and counts
PROCESSING · GPU 0Cosmos 3Scene and temporal review
PROCESSING · GPU 2V-JEPAMotion-reasoner training
AUXILIARY · RTX 3090Cosmos 3 NanoOptional, restricted crop review
Ready · browser-only simulation

The animation sends no requests and moves no images. It explains the architecture; it does not report live GPU health or training progress.

THE CONNECTION LAB

Two requests. Two different paths.

Trace a public page, then compare it with a signed-in video or API request.

LOCAL SIMULATION
  1. Your browserPage or signed requestREADY
  2. CloudflarePublic edge and routingREADY
  3. Site gatewayPages and private relayREADY
  4. Private serviceVisitor auth, API and videoREADY

AUTHENTICATED MEDIA PATH

The private hop is protected in both directions.

The site gateway and private service verify each other's certificates, then encrypt the connection. The application still checks the visitor's session or key.

What mTLS does
Authenticates both services and protects traffic on that hop.

What it does not do
Create network reachability, add bandwidth or validate model findings.

Ready · local simulation only

The animation runs in this browser. It sends no requests to live services and contains no real video, identities or findings.

THE TRUST CHECK / INTERACTIVE REQUEST

See what mTLS actually checks.

Follow the request through network reachability, machine identity, and visitor sign-in. Change any layer and watch where it stops.

SIMULATION · NO NETWORK TRAFFIC
SERVICE-TO-SERVICE PATHTCP 443 · site gateway → private serviceREACHABLE
CLIENT
Site gatewayPrivate-request relay Gateway certificate · trusted
mTLS · TCP 443
SERVER
Private serviceAuthenticated API and media Server cert · presented
  1. 01
    TCP path existsFirewall and routing allow the connection.
    WAITING
  2. 02
    Service proves identityGateway checks the service certificate.
    WAITING
  3. 03
    Gateway proves identityService checks the gateway certificate.
    WAITING
  4. 04
    Encrypted channel opensBoth machine identities are trusted.
    WAITING
  5. 05
    Visitor is authorizedThe app checks the user session or key.
    WAITING

mTLS authenticates and encrypts the machine-to-machine hop after the network path exists. It does not open a firewall port or sign in the visitor. This browser-only simulation sends no requests to either machine.

01 / MOVE THROUGH TIME

Six months, one synthetic sweep

May — October 2026

SYNTHETIC SAMPLE / OCTOBER

October 2026

Generated moments are compared with similar synthetic time windows.

Sample windows29
Motion cues3
Matched moments2
Verified events0
Motion cues3 / 29
Similar in baseline2 / 29

02 / REVIEW THE SIGNAL

Three checks before a claim

SIMULATED PIPELINE
  1. 01

    V-JEPA · motion ranking

    Surfaces an unusual change in movement. A score is a cue, not a probability or an incident label.

    READY
  2. 02

    Cosmos · scene review

    Checks the selected moments and returns a description with uncertainty preserved.

    WAITING
  3. 03

    Evidence · matched baseline

    Requires provenance, independent support, adequate coverage and a comparison against similar opportunities.

    WAITING

The same synthetic cue can be promoted, rejected or left uncertain as context arrives.

SIMULATION RESULTDEMO READY

Nothing is concluded from a motion cue.

Run the sweep to see why matching activity against comparable time windows can change the read.

12synthetic motion cues
9similar baseline moments
0independently verified

A model-generated pattern is not proof of a crime, a group or a person’s identity.

03 / CHALLENGE THE SIGNAL

Replay the cue. Change the context.

Four fictional movement cues. Three different evidence states. See where a careful review stops.

ABSTRACT CAMERA WINDOWSREADY · 4 WINDOWS
Four generated movement cues on a fictional grid A glowing abstract route links four anonymous grid nodes. It shows no people, footage or real camera locations. GRID 01 GRID 02 GRID 03 GRID 04 GENERATED PATH · NO GEOGRAPHIC COORDINATES
  1. 01GRID 0116:12 · motion cue
  2. 02GRID 0216:27 · similar turn
  3. 03GRID 0316:41 · scene review
  4. 04GRID 0416:55 · baseline check

Four of twelve invented moments are shown. The path is illustrative, not a real track.

SIMULATED REVIEWROUTINE OVERLAP

The baseline explains the repeat.

Nine of twelve synthetic cues have similar matches in comparable windows. The sequence is not promoted.

Motion cues
12
Baseline matches
9 / 12
Independent references
0
  1. Complete coverage90 / 90 daysPASS
  2. Time-forward holdout30 / 30 daysPASS
  3. Comparable baseline9 / 12 matchMATCH
  4. Frame provenanceCompletePASS
  5. Independent supportNone foundHOLD

Every value is generated in your browser. No scenario can produce a crime or identity finding.

WHAT THIS DEMO IS

A visual explainer, not an archive report.

The values above are generated in your browser and are deliberately marked as synthetic. The production archive is assessed separately; this page does not query it, load video, reveal camera locations or report real-world findings.

See how the live models work