GLD Flow Studio

GLD Flow Studio Delivery Lanes

Use this switchboard to work on the submission tool and aggregation tool at the same time without mixing their routes, scenario ids, or ownership boundaries.

Submission tool/prototypes/gld-event-submission

Event link intake and review

Mock chat intake for links, pasted text, and flyer notes with visible extraction, guarded review-row storage, and moderator review.

Admin editor Submitter view Moderator view

Owns

Submitter chat
Mock extraction
Guarded Supabase review storage
Moderator review

Does not own

Source queue checks
Publish-package generation
Calendar connector writes

Aggregation tool/prototypes/gld-ingest-aggregator

Source ingest to publish package

Operator lane for due sources, candidate review, dedupe/rule context, publish package preview, and reports.

Operator console Reviewer app Developer view

Owns

Source queue
Candidate review
Dedupe/rule flags
Publish package preview

Does not own

Submitter copy editing
Mock chat input samples
Live public publishing

Delivery contract

Separate by default

Each lane owns a separate Flow Studio product id and prototype route.
Scenario validation blocks the submission and aggregation scenarios from sharing one product/route again.
Shared docs links can point to both lanes, but scenario copy edits stay lane-local.
Supabase review writes require a loopback write gate, and connector writes, public publishing, WhatsApp, TEC/EventON, and social posting remain disabled unless separately approved.

System links Flow Studio requirements Chat intake plan