Build the scripted interactive RelayView workflow demo #5

New Issue

2026-10-08T17:28:25-04:00

anodyine commented

2026-10-08 17:28:25 -04:00

Problem

A static description does not show how the supervised workflow and review package feel to use.

Scope

Build a self-contained browser demo from synthetic deterministic fixtures. Let visitors follow a sample request through customer-visible stages, handoffs, checks, and a human review point. The demo must not call models, expose private APIs, or import RelayView product source.

Acceptance Criteria

The demo clearly states that activity and outcomes are simulated.
Visitors can navigate stages, inspect evidence, and understand what only a human can accept.
Fixtures contain no real customer data, credentials, private prompts, benchmark tasks, or proprietary decision rules.
The published JavaScript, assets, metadata, and source maps are reviewed for unintended implementation detail.
UI state is deterministic and works without a backend.
Keyboard, focus, reduced motion, responsive layout, and failure/empty states are checked.
Focused checks and manual interaction evidence are recorded.
Documentation disposition is recorded.

Ablation decision

not_required: the demo changes no agent or evaluation mechanism.

## Problem A static description does not show how the supervised workflow and review package feel to use. ## Scope Build a self-contained browser demo from synthetic deterministic fixtures. Let visitors follow a sample request through customer-visible stages, handoffs, checks, and a human review point. The demo must not call models, expose private APIs, or import RelayView product source. ## Acceptance Criteria - The demo clearly states that activity and outcomes are simulated. - Visitors can navigate stages, inspect evidence, and understand what only a human can accept. - Fixtures contain no real customer data, credentials, private prompts, benchmark tasks, or proprietary decision rules. - The published JavaScript, assets, metadata, and source maps are reviewed for unintended implementation detail. - UI state is deterministic and works without a backend. - Keyboard, focus, reduced motion, responsive layout, and failure/empty states are checked. - Focused checks and manual interaction evidence are recorded. - Documentation disposition is recorded. ## Ablation decision `not_required`: the demo changes no agent or evaluation mechanism.