Epic: Launch the public RelayView site and simulated workflow demo #2

New Issue

2026-10-08T17:27:16-04:00

anodyine commented

2026-10-08 17:27:16 -04:00

Problem

RelayView needs a public, inspectable explanation of its product vision and user experience without releasing its proprietary orchestration source. The product-level requirements are in RelayView #277.

Scope

Create a separate public marketing-site codebase for relayview.app. Explain current behavior and planned direction truthfully. Provide a scripted interactive workflow demo with no model calls or private product code.

Acceptance Criteria

The site and demo are accessible, responsive, and publicly reachable.
Simulated activity is labeled as simulated.
Product claims are checked against the private RelayView authoritative documentation before release.
The public repository contains no proprietary RelayView source, prompts, credentials, or benchmark internals.
The deployed revision and review evidence are recorded.

Child Issues In Priority Order

#3 — Define the public claims, site structure, and simulated demo story.
#4 — Build the accessible RelayView marketing page.
#5 — Build the scripted interactive RelayView workflow demo.
#6 — Deploy and verify the public RelayView site.

Ablation decision

not_required: publication and demonstration work do not change agent behavior.

Documentation disposition

Expected updated for site deployment and claims documentation.

## Problem RelayView needs a public, inspectable explanation of its product vision and user experience without releasing its proprietary orchestration source. The product-level requirements are in [RelayView #277](https://tea.kyle-merritt.com/anodyine/relayview/issues/277). ## Scope Create a separate public marketing-site codebase for relayview.app. Explain current behavior and planned direction truthfully. Provide a scripted interactive workflow demo with no model calls or private product code. ## Acceptance Criteria - The site and demo are accessible, responsive, and publicly reachable. - Simulated activity is labeled as simulated. - Product claims are checked against the private RelayView authoritative documentation before release. - The public repository contains no proprietary RelayView source, prompts, credentials, or benchmark internals. - The deployed revision and review evidence are recorded. ## Child Issues In Priority Order - [ ] #3 — Define the public claims, site structure, and simulated demo story. - [ ] #4 — Build the accessible RelayView marketing page. - [ ] #5 — Build the scripted interactive RelayView workflow demo. - [ ] #6 — Deploy and verify the public RelayView site. ## Ablation decision `not_required`: publication and demonstration work do not change agent behavior. ## Documentation disposition Expected `updated` for site deployment and claims documentation.