codex-slides-structured-intake

1# Codex Slides Structured Intake
2 
3The Codex Slides Browser owns the canonical intake form. Structured intake must
4produce one durable project and one shared clarification state, not a separate
5chat-only questionnaire.
6 
7## Flow
8 
91. Call `open_codex_slides` without a project id and follow its
10   `browserHandoff` to the home/create workspace.
112. When a workflow preset fits, call `list_scenarios`, then open the selected
12   scenario deep link. Use product-owned defaults and source slots.
133. Submit the user's topic and available files in the Browser. Assign every
14   uploaded file its scenario role; do not flatten datasets, source decks,
15   brand assets, and visual references into one undifferentiated list.
164. Let the product create the durable project before clarification. Keep the
17   clarification checkpoint visible and persist answers in project workflow
18   state.
195. Ask only questions that materially change the result: audience, purpose,
20   page count, language, aspect, research depth, evidence constraints, and
21   visual direction. Use recommendations already present in the form.
226. Continue through outline and inspiration checkpoints in the same Browser
23   project. Do not call the unattended `create_deck` path unless the user asked
24   for a headless run.
25 
26If Browser submission is unavailable, use `start_project` as the deterministic
27fallback, immediately follow its clarification handoff, and keep later choices
28…