The canvas
The screen is the ticket.
An infinite canvas where your app hangs on the wall and anyone can mark it up. No coordinates, no repro steps, no ticket template — the thing you are talking about is right there to point at.
01
Circle it. Say it.
Drag a box around whatever looks wrong and write one sentence. That sentence becomes a work item, and the region, the screen and the branch go with it.
- Draw a region — straight onto the screenshot — no coordinates to describe and no steps to write out.
- One sentence — is the whole report; the surrounding context is already attached to it.
- Nothing to learn — a board is a link, so there is no template to fill in and no field to get wrong.
02
Anyone with a link
Testers, designers, product people and clients open a browser and mark up the screen. Installing anything is only for the people whose agent does the fixing.
- No account — a board opens in a browser; nobody signs up to leave a note on it.
- No seat to buy — the people reviewing the work are not the people you pay for.
- The same canvas — everyone is looking at one board, not at an exported copy of it.
03
A fix, and the proof
A listening agent takes the item off the queue, fixes it, and hangs the after-shot beside the original so the two can be compared in place.
- The agent picks it up — the annotation is a work item on a queue, and an agent can be attached to that queue.
- The after-shot — lands beside the before, on the same board, rather than in a reply somewhere else.
- The thread stays — the conversation lives on the region it is about, so it is still there next month.
04
Decisions on the board
When an agent needs your call, it asks on the board: each question with its options, their stakes and a recommendation. You click, and nothing reaches the agent until you send.
- Picks are staged — work through a batch at your own pace and change your mind; ↑ Send hands the whole batch over at once. Every question keeps an “Other” write-in, and you can ask the agent about a question before you answer it.
- The brainstorm studio — a design session opens as its own app: one chapter per decision, the competing takes side by side at a size you can read, answered in place. Brainstorms lists every one across your projects, grouped by what waits for you.
- It ends in a record — the session closes with a decision log and a feature brief on the epic, and every question and answer stays on the board, a retracted question marked as such. /vitrinka:make-idea builds from that brief.
05
Beside your tracker, or instead of it — per project
Vitrinka is the native home for tasks, sprints, intake and the evidence around them. A project that lives in Jira mirrors into it; a project that does not simply runs here.
- The mirror is a mode — per project you pick the connector and which side is the truth; the other side is kept a copy, and a conflict settles in the truth side's favour.
- Evidence lives here — the shots, the recording and the thread, all in one place instead of pasted into comments.
- Nothing migrates — turn the mirror on for the projects that need it and leave the rest alone — teams keep both without double entry.