Description: Consolidate per-scenario ergonomics notes (captured during CHOR-02) into a single review document covering both Stagger and Sequence. Audit: per-child motion override, conditional sequencing, dynamic child counts, server-rendered children, per-step timing, branching, cancellation/replacement semantics, completion callbacks, type ergonomics. Output: review doc + concrete API change proposals (kept / changed / removed).
Why it matters: Beta = API design validated. Validation requires lived consumer experience (CHOR-02). CHOR-04 is the write-up, distilled into actionable API decisions feeding Robert's CHOR-01 final criteria and Group 5 item drafting. Combined Stagger+Sequence review reflects how the two components are actually used (compositionally).
- Difficulty: Medium
- Dependencies: CHOR-02 with at least 3–4 scenarios landed (ideally including Sequence-heavy and Stagger-inside-Sequence scenarios)
- Sequencing: M3 W10
- Pairing: 1× synchronous review with Robert (~1 hr) — Robert is final decision-maker on API direction
- Mode: UXE-driven; Robert decides
- Output: Ergonomics review doc + proposed API changes (input to Group 5)
- Tags:
partner-pickup, api-input
Description: Consolidate per-scenario ergonomics notes (captured during CHOR-02) into a single review document covering both Stagger and Sequence. Audit: per-child motion override, conditional sequencing, dynamic child counts, server-rendered children, per-step timing, branching, cancellation/replacement semantics, completion callbacks, type ergonomics. Output: review doc + concrete API change proposals (kept / changed / removed).
Why it matters: Beta = API design validated. Validation requires lived consumer experience (CHOR-02). CHOR-04 is the write-up, distilled into actionable API decisions feeding Robert's CHOR-01 final criteria and Group 5 item drafting. Combined Stagger+Sequence review reflects how the two components are actually used (compositionally).
partner-pickup,api-input