Skip to content

Δ10-UX — per-solve routing UX (local vs company-compute) #63

Description

@jack-champagne

The UX slice carved out of Δ10 (#34) — the estimator/backend stays on #34 (plumbing, @Rchari1). Routing decision (cloud-solve-service spec, Locked decisions): routing is per-solve, explicit — the agent may suggest offload (estimator's sizeClass vs local RAM), the researcher confirms. No auto-classifier.

What (UI)

  • The "run on company compute?" surface: when the estimator (Δ10 — Estimator integration (v0 = tshirt_sizing) + per-solve routing UX #34) flags an estimate over the local-RAM threshold, present it as a confirm, not an auto-route.
  • Where the executor: remote choice sits in the solve-assembly flow (the SolveSpec carries it).
  • Surface the sizeClass / estimate at the decision point so the choice is informed.

Ties to the freezes

Feedback question

Is agent-suggest + user-confirm the right friction, or do power users want a sticky "always cloud" default?

Depends on: #34 (the estimator provides the suggestion signal). Kate owns the UI; #34 owns the estimate.

Metadata

Metadata

Assignees

Labels

area:uiarea:webviewenhancementNew feature or requesttrack:cloudTrack C — company compute / cloud solve-servicetrack:uxKrishna-interview seam UX prototypes

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions