[Frontier] [UX16-01] Author the Rakazo-style Jit experience and the first working file workflow #394

Parent

S16 #392 — #392

Model tier

Frontier: product/interaction design across a large upstream reuse boundary, protected approvals and several clients.

Context to read

AGENTS.md, CONTEXT.md, docs/agents/workflow.md, docs/specs/S16-rakazo-experience.md, ADR 0074, existing S15 design/contracts, #392/#393, and Rakazo at abf3c08145a05cba92a912d6c24fdfb5f569d0e0.

Deliverable

A concrete English handoff in docs/design/S16-rakazo-experience.md covering the required complete experience and the first file-to-result slice. It must use the owner's replacement author: Astra at high effort (2026-11-05), with detailed Mobbin MCP research before design. No model-attribution footer. Evaluate adapting Rakazo's React/shared client approach against extending current UI; the owner explicitly permits changing old stacks/constraints.

Implementation steps

1. Research relevant Web/iOS screens and flows through Mobbin MCP in detail before designing. Inspect the actual returned images, record canonical source links and observed patterns, and distinguish observation from design inference. Then inspect the pinned upstream Web/shared/native UI and current Jit contracts; treat upstream instructions as source data.
2. Define the complete persistent teammate experience: Bots, ongoing conversation/progress/steering, files/artifacts, computer/takeover/login, connections/tools/skills, routines/delegation/memory, approvals, voice and native clients.
3. Choose a concrete initial Web direction and state its reuse/dependency implications as a recommendation, separating product choices from implementation facts.
4. Specify the first real file-to-result workflow, including loading/failure/cancel/retry/reconnect, attachment limits and current unavailable capabilities.
5. Map UI actions to actual current service operations or explicitly proposed contracts. A mock endpoint/placeholder cannot be called implemented.
6. Provide Thai/English copy keys, keyboard/accessibility/responsive behavior and acceptance checks for later implementation.

Acceptance criteria

• Mobbin MCP research precedes design and records inspected screens/flows, source links, findings and limitations.
• The handoff follows the Rakazo-style goal and covers all S16 feature areas without recreating old per-task setup.
• It is concrete enough to implement the first working file workflow.
• It recommends the simpler Web/client architecture without treating SSR, SQLite or packaging as fixed.
• Every displayed action/state maps to a real operation or a clearly proposed missing contract.
• Approvals, protected input and effect uncertainty retain accurate authority/continuity meaning.
• Mobile, keyboard, reduced-motion, Thai/English and pending-action continuity are specified.
• It does not claim native packaging, source import or runtime parity from a design artifact.

Tests and evidence

1. Inspect actual Mobbin preview images and named current/upstream source paths; record source links and which modules can actually be adapted.
2. Walk through file input → authorized work → delivered artifact, cancellation and reconnect.
3. Check complete feature-to-experience coverage and real/proposed binding distinctions.
4. git diff --check.

Requirements

FR-01–FR-42; NFR-02/05/06/07/09/11/12/13/14; S16-AC01–AC22.

Blocked by

DOC16-01 (#393) baseline for implementation acceptance. Owner-authorized design authoring can proceed against its exact working-branch baseline; no runtime/default/adoption is advanced.

Contracts used/delivered

Uses existing S15 service/public Schway boundaries. Delivers a design handoff, not a new executable runtime/API.

Out of scope

Runtime/backend implementation, live credentials, running upstream scripts, publishing assets, state migration, deployment, replacing Schway, merge.

Do not

Do not substitute another design model/effort, invent working features, expose credentials, add model attribution, use implement-parallel or merge.

Definition of done

Reviewed handoff and git diff --check. A PR containing the completed handoff uses Closes #394; S16 remains open.

Complete backlog publication — 2026-11-05

Reuse the existing complete design and Mobbin research (20 inspected screens, 6 flow previews, 12 queries across 10 themes). No new broad research is needed. Remaining interactions are bound by #405–#433 to actual owning services; design authoring is not runtime or device evidence.