How it was made

This is the design decision.

Three hard gates first. An option that fails one is out, whatever else it scores.

• The guest never overwrites the host. Status and severity sync both ways between the two products, so one silent write changes two systems at once. Pass or fail, not a degree.
• Buildable from what the host already lets a guest use. A dashboard widget, a case-wall entry, a playbook result. Anything that needs the host to change its own chrome is solving a different problem.
• It passes the count on the console page. Every mark the card adds is legible on screen, and it reuses no glyph the host already uses for something else.

Then six weighted criteria, each scored across five dimensions — user impact, failure severity, frequency, strategic alignment, competitive leverage — to earn its weight rather than be assigned one.

Proposed at 17 Sep, 18:17, ninety minutes before the first option existed: seven criteria, with a recommendation to cut one. The six were confirmed on 18 Sep, after all six options existed and before either scorer ran. That is a proposal, not pre-registration. The seventh became a briefed requirement instead, checked and reported.

Corrected 25 Sep 2026. This page said the criteria were “committed 90 minutes before the first option”. Seven were proposed then, and the six were confirmed only after all six options existed. That is not pre-registration. The claims on this page that rested on it have been taken down, as has the claim that the counting rules were published before the count: they were committed together.

Five were generated by an agent working from a written brief. The brief is the work; the generation is a method note.

The brief carried the criteria, the three gates, the host’s documented extension points, the synthetic case data and the six states every option had to draw — including the ones nobody enjoys drawing: analysis pending, analysis failed, and no widget installed at all. Each run got the same brief and one difference in how it was seeded. One run was given no direction beyond the rules and the data.

The sixth is Option 0: the original ask made literal — verdict, confidence, evidence, provenance, accept and override — generated by a model, like the other five, before the criteria were applied to anything. It is in the set so the criteria have something unexamined to be measured against.

Corrected 25 Sep 2026. This page said Option 0 was mine — “the one I built myself”. It was generated by a model, like the other five, and the page now says so.

Option 0 runs in the prototype too: open it.

Two AI scorers worked the same rubric independently, and neither could see the other’s notes. They are the same kind of reader, though: a human pass is still missing.

They agree on first place and disagree on second. AI scorer B put R5 5.0 points clear of R3; AI scorer C put it 8.6 clear of R2. Neither margin clears the 10-point close-call rule fixed before any option existed, so no winner is declared. R5, the run given no direction at all, leads both passes; the runner-up changes identity between them.

Two findings do more work than the ranking.

• Both scorers found the same hole, independently and in near-identical words. Low confidence changes what every card says and what almost none of them offers. None withdraws the action.
• The option built literally from the original ask came last in both passes, and it failed two gates. One is the bar. It coloured the card’s left edge by verdict, red for Malicious and green for Benign, with no label. The host already uses a left-edge bar for priority, just above it on the same screen, and in the host’s colours red means Critical. That is the exact class of error the count exists to catch.

What the refusal forced. With no winner, the answer could not be a coronation. It is a hybrid: the parts that scored best, wherever they came from. And three things no option produced.

The card, moment by moment, and where each part came from.

What it refuses to do. No colour down the card’s left edge, where the host shows priority. No host field changes without an explicit act. One decorative mark on the whole card, and it sits after words.

The card is then put through the study’s own gate, mechanically, and passes. A check that only ever passes proves nothing, so it runs on Option 0 too, and names its failures there.

A verdict produced by one vendor is read inside another vendor’s product, by an analyst who owes their attention to the case, not to the agent. The agent is a guest. These are the obligations that come with being one, each traced to a row in the count or a criterion in section 01. The list itself is on the case study page.

A rule that only fits one pairing isn’t portable, so an AI agent checked all eight on paper against a different guest in a different kind of host: Dropzone AI writing into ServiceNow, where the AI polls the ticket queue, investigates in its own console, and posts its result back as a comment. By its check, seven of the eight apply as written. Rule 5 needed rewording, because in a ticketing tool most evidence lives outside the host, so “in the host’s own objects” became “and say where” — which the card already does. And rule 7 flipped: there, a comment is the only channel, so the text entry isn’t the fallback — it is the card. That’s why the freshness line is the first thing I’d ship. This tested whether the rules apply, not whether Dropzone follows them.

No analyst has used this. n = 0. The design rules stand as argued, not as tested.

The protocol is written — consent, three tasks, time to first correct action, five debrief questions, a scoring sheet. The prototype scores its own sessions and exports them, and a self-serve link needs no calendar and no facilitator. That is the next thing that happens, and whatever n it reaches gets printed first, in the findings.

What would make this wrong

Written before any data, so it cannot be adjusted afterwards.

• If analysts find the verdict just as fast with no card at all, the count overstated the problem and the card is solving something smaller than I claimed.
• If they catch the stale verdict without the card, freshness belongs in the host’s timeline, not in a guest’s widget, and rule 2 is aimed at the wrong surface.
• If the low-confidence card makes them slower without making them more accurate, withdrawing the recommendation is friction rather than safety, and it goes.
• If consoles start giving a guest’s verdict the treatment they already give their own AI — the landing view, a date, a history — the card becomes the host’s job. That would be the right outcome, and this study would have been an argument for it.

What I’d ship first

The freshness line and the claim-level checkability. Both are cheap, both work in a plain text entry as well as in a widget, and between them they carry the two failures the audit found: a verdict whose age nothing on screen states, and a claim you cannot follow.

What I’d cut

The preview-drawer density, until someone confirms a vendor widget renders in that drawer at all. The docs do not say, and I could not check without a tenant. It is drawn because rule 1 demands it, not because it is known to be buildable.

What breaks at scale

Claim-level checkability assumes the agent’s claims map onto objects the host holds. On a case with one alert that is easy. On a case at the host’s own documented ceiling, “checkable in this case” stops being one click and starts being a search, and the card would need to say which.

And the card only sees what lands in its case. The host groups a new alert into an open case when the two share a single entity, inside a window its admin sets. It opens a separate case if the window is shorter than 41 minutes, or if the case is already closed, because grouping never reopens one. That second path is the worst version of this whole problem: the analyst trusts the verdict and closes the case, and the evidence against it arrives somewhere else. A card inside one case cannot see that. Catching it needs something that looks across cases, and this study did not design it.

A clean narrative is not the same as a tidy process. The prose above reads forward; this is the order things actually happened in, and who decided each one.

All six options were machine-generated, and two AI scorers scored them; the margins above are theirs. An AI agent also ran the count and drafted the criteria, the gates and the eight rules. What is mine is the problem, the scope, the cut from seven criteria to six, the three additions no option produced, and the call to mix the top options rather than crown one. The page says which is which because concealing it is the actual red flag.