2026 10 03 direction decisions

October product-direction decisions

Status: Record. Date: 2026-10-03. Followed by the 2026-10-04 Composer decision. Provenance: Mateo's RISE development conversation and supplied October roadmap. This is a summary, not a verbatim transcript. It records available decisions; it cannot recover discussions outside that conversation or repository.

Two products, one foundation

Mateo requested equal management of the audiovisual Reader website (Seth's active product direction) and the Live plugin + RiseSDK. The Reader remains a product worth making more capable and beautiful. Shared score, playback, source coordinates and instruments connect the products; neither lane's completion establishes the other's readiness.

Composer first

The original October vision describes model-authored scores and realtime performance. The subsequent approved first-edition promise is: turn an answer into a coherent audiovisual experience you can explore and return to. Composition happens before playback; reader controls are immediate; follow-up occurs at an explicit boundary. Full realtime mutation is a parallel experiment, not a first-edition release prerequisite.

The Experience Program remains the semantic center. Current is a model-facing adapter. Do not introduce a second runtime or event vocabulary through transport convenience. SDK expansion and large instrument catalogs wait for demonstrated needs.

Host evidence and limits

Mateo heard narration during an earlier ChatGPT black-hole demonstration. That observation is historical acceptance of that demonstration, not exact-current-release acceptance. Original Gate 0 mutations arrived in separate widgets. Mateo heard “Done”, was uncertain about “Set”, and reported the model could not see the fixed marker. Persistent-view and reciprocal Live behavior remain unproven. The decoupled render/data experiment was prepared but still needs a real-host run.

Temporary Workers and tunnels were shut down when Mateo requested cleanup. A new public exposure requires the applicable reviewed scope; this tracker does not authorize it.

Tracker decision

Mateo approved repository/local dashboard first, then hosting after content/access review. Tasks have explicit owners, dependencies and evidence. Implemented, merged, deployed and accepted are different facts. Agents update task records in their normal reviewed work. No custom database or write service is needed for the initial edition.

Sources and authority

• Original October performance roadmap: historical Intent, supplied by Mateo, dated October 2026; retained without rewriting its claims.
• Composer-first roadmap: current Live/Composer delivery Intent, approved in the conversation.
• Reader direction: current tracking scope; historical release obligations retain their original authority.
• Tracker design: approved tracker boundaries.

Later evidence belongs in task records and linked handoffs. Add dated decisions instead of rewriting this record to fit a new direction.

---

Published from docs/product/discussions/2026-10-03-direction-decisions.md. Edits made here are overwritten on the next push to main.