E. UX + diagnostics + durable UX review gate #121
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Creatidy/scarcity-router#121
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Child E of #116 (Dynamic Execution Sources program).
Known UX defects to fix
worker_idfirst (server_ui.py:995-1025 workers rows, :572-577 resource-add dropdown; diagnostics.py:683-687 doctor). Display friendly worker label FIRST:Precision Codexwith the technical id below it; the exact ID remains available for diagnostics/audit.detected, authenticated, protocol_compatible, available, eligible, promotion_confirmed; diagnostics.py:50-57) usesauthenticatedfor worker PAIRING only. UX must distinguishworker authenticatedvsprovider/source authenticated; never imply ChatGPT/provider auth from worker pairing.gpt-6-solunless the user explicitly chooses an ADVANCED exact pin.No raw protocol structures exposed.
Advanced mode
Expert narrowing (allowed tracks, exact model pin, disable automatic adoption) stays OUT of the normal path; defaults work.
Durable UX review gate (governance)
Make UX a mandatory review dimension in AGENTS.md / review instructions / llm-operating-policy (Program Execution Mode rules). Every future review answers
UX impact: noneor assesses user-facing consequences across: first-run; happy path; recovery/error path; upgrade/model-change path; unnecessary technical-ID exposure; auto-discoverable configuration; actionable errors; necessary+understandable security friction; repeated manual work; understandable system state. A material UX regression isCHANGES_REQUESTEDeven when the implementation is technically correct. No large UX bureaucracy.Private PKI friction
Windows private-CA install friction observed in live acceptance: do NOT weaken TLS, no certificate-ignore. Record the friction during the UX audit; implement a secure bootstrap approach only if it naturally fits this program; otherwise a focused follow-up issue with concrete requirements. Must not derail the program.
Reliability UX
Discovery failures isolate to the source (never take down worker/other sources/server/recommendation mode); bounded timeout, inventory size, pages, refresh cadence, stale semantics, backoff; no unbounded retry, no hidden fallback. Errors must tell the user what to do.
Closeout — implemented in merged PR #124 (merge commit
a4370f0intodevelop, head9789c67; program #116 / D-053).Child E delivered: the Sources page (
/admin/sources,/control/sourcesGET/POST/DELETE) — add a Codex source with just a label + owning worker (source id derives from the label; no model slug anywhere in the normal path); each row shows source auth state, detected models with per-model adoption state, routable/restricted/error counts, and the exact two worker-side commands (login + run) with SSH device-code guidance. Worker labels are now shown before technical ids on the workers page, resource-add dropdown and doctor output. The resources ladder renders "worker authenticated (pairing)" so pairing is never mistaken for provider auth. Durable governance: AGENTS.md and docs/llm-operating-policy.md now make UX a mandatory review dimension (UX impact: noneor a ten-point assessment; material UX regression = CHANGES_REQUESTED). Advanced narrowing (allowed tracks, exact pins, auto-adopt off) stays out of the normal path; errors are actionable (bounded cadence, closed vocabularies, per-source isolation).