Feedbacks vocabulary and selection
| User language | Meaning and action |
|---|---|
| feedback, issue, bug, task, ticket, thread, review, “feedbacks mein dekho” | A Feedbacks discussion thread here. An issue does not mean GitHub unless specified. |
| pin, point, annotation, marking, comment on an element, “yeh wala point” | An entry in context.annotations; use its UUID. Display numbers are capture-local, not IDs. A legacy single anchor may have no annotation ID: resolve the thread, never invent an ID. |
| comment, reply, discussion | Original body or a named reply. One message can describe several tasks; do not silently close them all. |
| screenshot, SS, capture, full page, point image | A private asset. Read metadata and actual pixels; filenames are insufficient. |
| recording, video, clip | Video evidence with an authenticated URL. A thumbnail is not playback. |
| page, screen, URL, mobile/desktop | Filter reviewed URL/device; a Feedbacks app URL selects feedback, not the reviewed page. |
| today, aaj, abhi, new | Establish timezone and submission versus activity. createdAfter/createdBefore filter creation; activityAfter includes updates to old threads. Today is local midnight to next midnight, not a rolling 24 hours. |
| my feedback, Suyog's issues, reviewer name | Distinguish submitted by me (authorId) from assigned to me (assignedTo). Use auth.me.actor.userId for the authenticated member; clarify an identity mismatch. |
| top priority, urgent, first | Human workPlan priority and saved timing lead. Reviewer weights/flags are advisory views; do not reprioritize or begin work from urgency language alone. |
| pending, unresolved, remaining | Usually work not resolved/declined. workState selects an exact state, or closed for both resolved and declined. New replies can need follow-up even after resolution. |
| answered, responded | Discussion dimension; not fixed/resolved. |
| fixed, done, resolve | Verify agreed scope/evidence and mutate only authorized points/threads. Tests alone do not prove deployment. |
| remove, delete, dismiss | Clarify: removed point, archived thread, declined work and permanent deletion differ. Done never means delete. |
| likes, support, votes | Anonymous unique thread/reply/view counts. Voter identities are intentionally unavailable. |
| GitHub/Jira/Linear issue | Optional external association. Read provenance; do not create or message externally without authorization. |
For “today's feedback, make a plan”, return counts and proposed order first, then discuss execution. Empty results mean only the stated filters/scopes returned no matches.
- Assigned / assigned to me: Durable ownership lives in
assignments.delegations; broad personal queues use server-sideassignedTowithauth.me.actor.userId. Read the selected scope before working on sibling points. Ownership does not mean someone started their agent. - Today / Tomorrow / Next week / Later planning:
workPlan.scheduledForis the actual persisted calendar date intimeZone. Relative preset names do not slide forward; future/Later work is not an immediate suggestion. This is separate from feedback submitted today. - Claimed / kaun kaam kar raha hai: Read
assignments.list. A claim identifies the Feedbacks member, named agent, thread and optional point IDs, plus a two-hour renewable expiry. Thread status alone does not identify a worker. Disjoint points may have different agents; overlapping active claims conflict. - My current work / abhi main X par work kar raha hoon: The member profile's
currentWorkis a broad one-line focus. It is advisory context, separate from an active thread/point claim. - Shared Codex/Claude account: A model-provider subscription, never the Feedbacks employee identity. Use separate personal Feedbacks keys. Account quota does not establish task ownership or correctness.