You asked for "share a report with developers who don't have accounts" and left the
details open. These five questions are the details that have architectural cost if guessed wrong —
ordered so the biggest one comes first.
Pick one answer per question; each card says what choosing it commits you to.
"You decide" is a real answer — it means you're delegating that call on purpose. The decisions
table and your reply fill in as you go. Copy the reply at the bottom and paste it back into the
chat.
What is this?
A live example from the finding-unknowns skill. For an ambiguous feature, the expensive
unknowns are the questions the builder would otherwise answer silently with assumptions. This
artifact asks them in order of blast radius — storage and auth before cosmetics — and turns your
clicks into a ready-to-paste implementation prompt.
1 · Who can open a shared link?
The biggest call: it decides whether shared reports need their own auth path, and
whether a leaked URL is an incident.
2 · Do links expire, and can they be revoked?
Decides whether tokens are stateless or need a lookup table you can delete from.
3 · How much of the report does a link show?
QA reports carry internal notes and reporter names — decide what crosses the wall.