05Developer handoff · 10 work items · 7 confirmed observations
Give the outside web team something testable.
An observation is not a request. Each of these carries the evidence, what happens now, what should happen instead, why it matters, acceptance criteria and how it gets verified — so an agency can estimate it and a non-technical owner can accept it.
How to read this queue — what a ticket is, and what separates the two types
Two types, never mixed. A defect is a confirmed observation: something a public page does that contradicts itself, or the company's own words. Aproposal is my design, and it is labelled as mine. A reviewer should be able to accept every defect and reject every proposal without any loss of consistency.
Every ticket names its evidence and its certainty.Where the evidence is a page, the page is linked and dated. Where a ticket rests on the modelled sample rather than on a public page, it says so — those are the proposals about the data model, and they are the weakest evidentially even though they are the most structurally important.
The status buttons are real. A ticket moves through open → in review → accepted or not accepted, and only along the transitions the process allows. Nothing jumps straight from open to accepted, because in a real queue it would not.
What a ticket is not. Not a criticism of anyone's work. Four of these are proposals about a data model that would make a dozen other things cheaper; two of them close a gap the company has already acknowledged in public.
Confirmed observation — 7 itemsDrawn from public pages retrieved 2026-09-28, or from a bounded comparison of two surfaces. These can be checked by anyone with a browser.
Proposal — 3 itemsMy design, resting on the modelled data layer. Accepting the observation does not require accepting the proposal.
0 items shown ·
Ordered by what unblocks the most.
P1 — DO FIRST
The structured promotion record, then location scope and dates on the card. Three of the four P1 items either depend on the record or are already acknowledged by the company in public.
P2 — NEXT
Terms wording, the store prefix, the eligible-product list, and the purchase-limit check. None of these can be done properly before P1 lands.
P3 — WHEN CONVENIENT
The city named in copy that has no store page. Small, real, and independent of everything else.
Dependencies are declared, not impliedFour tickets list the promotion-record work as a blocker in both directions — not because the work cannot start, but because doing them first means doing them twice. The queue shows the dependency explicitly rather than hiding it in a conversation.