Flow Studio Scenario Registry

This registry tracks current Flow Studio scenarios, intended audience, coverage, and source docs.

Current scenarios

Scenario	Route	Roles	Truth status	Coverage
Complete event submission, approval, and distribution	/prototypes/whatsapp-submission?scenario=whatsapp-complete-event	Submitter, moderator, admin/operator, overview	Implemented/spec-backed	WhatsApp intake, extraction, moderator notification with source preview, approval, manual publish completion, submitter congratulations with public links, distribution hub
Rejected submission and reason notification	/prototypes/whatsapp-submission?scenario=whatsapp-rejected-event	Submitter, moderator, admin/operator, overview	Implemented	Rejection decision, source preview context, submitter rejection reason, outcome audit
Missing event fields and request-info loop	/prototypes/whatsapp-submission?scenario=whatsapp-missing-info	Submitter, moderator, admin/operator, overview	Implemented/spec-backed	Missing-field follow-up, submitter reply, moderator request-info
Full GLD source ingest, candidate review, and publish package path	/prototypes/gld-ingest-aggregator?scenario=gld-source-to-publish	Moderator, admin/operator, overview	Implemented with guarded publish behavior	Source queue, source check, manual intake, candidate review, publish package preview, daily report

Required scenario metadata

Each scenario should include:

• scenario id
• route
• release
• audience level
• allowed roles
• truth status
• source docs
• sample inputs
• steps
• role highlights
• messages
• review/operator screen state
• pipeline nodes
• state diffs
• API calls
• audit/notification events
• contextual info links

Coverage gaps

Planned later:

• deletion/cancellation request flow
• duplicate candidate branch
• approved-but-not-yet-published waiting branch
• source needs_login branch
• source bad_url branch
• publish package blocked branch
• public submitter-only training mode
• sales demo mode
• restricted moderator/admin access
• feedback/comment collection