Demo and contributors — prepare one repeatable scene and public invitation #156

Outcome

Prepare one founder-reviewed demo and contributor invitation from useful working evidence. Marketing preparation runs alongside the selected engineering work and can begin before the full native stack is delivered.

Primary: Anshuk (@geeked-anshuk666) — coordinates the first scene and reviewable packet.
Partner: Nav (@NavSrijan) — capture/visual material, audience clarity and media experiments.
Acceptance/reproduction support: Debayan (@morichika33), linked to #133. Chirayu/Kiran contribute the product view when their work is used.
Editorial/release decision: founder (@zenithruneblade). These are starting responsibilities; agree a small preparation slot and rotate contributions as useful.

First result

• Select one scene with a clear user purpose, starting action and observable result. Reuse current repeatable engineering work and existing authoring, capture and editing tools.
• Record source revision/profile, reproduction steps, expected observation and limits. Clearly label fixtures, prototypes, branch experiments and dated evidence; no native Composition delivery claim follows from a mockup or external tool.
• Prepare a short script/storyboard and one reviewable capture or visual example. Explain what a viewer can learn or try and what is unfinished; include understandable captions/text alternatives where the format needs them.
• Keep Atelier visual creation distinct from Broadcast editing/publication. If the scene reveals a useful native Atelier or Broadcast experiment, record it for later selection through Future capability register — preserved outcomes and selection boundaries #62; building that application is not required to prepare this demo.
• Draft a contributor invitation linking to public Start here — team foundations, agent-assisted delivery and contributor entry #52 and the bounded opportunity prepared under Enter — prepare the shared reproduction and acceptance journey #133. Ask for a specific reproduction report, usability observation or contribution, name the response location and acceptance contact, and explain the purpose. The invitation and entry instructions must work without private-board access or a Discord account.
• Use public or synthetic inputs and inspect captures for credentials and private conversations. Have another participant follow the scene and newcomer entry steps. Fix discrepancies or reduce the claim, then submit the packet and proposed destination for founder editorial review.

Quest routing: this is a bounded shared outreach side activity for Anshuk and Nav. Their native Atelier side quest is separately recorded in #162; preparing a demo does not implement Atelier or Broadcast. YouTube as a publishing destination here does not require a native YouTube Reach adapter.

Capacity and completion

Keep one small demo packet active and count production, review and community follow-up within ordinary capacity. No video quota, assumed external contributor capacity or simultaneous media-platform implementation is introduced.

This issue completes with the reviewable packet and accepted entry route. Actual external publication is a separate deliberate action; record its own outcome if later selected. #133 owns shared reproduction and onboarding; #52 owns current selection. Existing code/review rules remain unchanged.