A sample SwarmPlan, read as its arguments
The argument is the artifact.
Every SwarmPlan is what survives a room that refused to converge on the first answer. Below: the 3 arguments that produced the one in your hand, with 3 humans and 5 AI specialists on opposite sides of the table.
- № 01
DR-2
How Customers authenticate
Magic-link would convert dramatically better for a stranger asked to log in just to leave one rating.
Anonymous auth shreds the RLS story. Magic-link adds a new auth path we have to maintain.
Resolution
OAuth-only for v1. Magic-link deferred to v1.1 as a conversion optimization.
- № 02
DR-8
Reaction scale
Ship NPS in v1 for B2B parity. A fixed 1 to 5 Likert reads as toy.
We have not shipped NPS anywhere in the product. Carrying two scales doubles the synthesis surface.
Resolution
Likert ships v1. The scale column is reserved on the schema so v1.1 customisation does not need a migration.
- № 03
DR-10
Real-time visibility for Collaborators
Loosen RLS for trusted Collaborators. It would keep the query path simple and the aggregates honest.
NN-1, multi-tenant isolation, is a hard constraint. Loosening it for any role is a one-way door.
Resolution
Orchestrator computes aggregates under the system role and broadcasts as SSE activity frames. RLS untouched.