Backed by: @pithy-sh/testers. Scopes: testers:roster:read · testers:roster:write · testers:nudge:send.
What it shows
Testers is the capability, and using it is the closed test it tracks. Roles and permissions is who may act here.
The index lists cohorts. The record is one cohort in full: the clock, Pithy’s forecast, the roster and each tester’s standing. The rail says Cohorts because the clock and the forecast are about the cohort, not about one tester.
Fetched live from your D1 and discarded. The roster, the daily pass that advances the clock and the invitations are all your Worker’s. Nothing about anybody’s roster is written down here.
The clock is read, never counted
The days held, the days remaining and the start of the window are your Worker’s, replayed from its own opt-in log. The dashboard subtracts nothing from today’s date, so two people in different timezones see the same day of the same window. The record says once which zone counts the days.
The count is Pithy’s, and it says so
Google’s opt-in count is the one that decides, and no API exposes it. Every figure here comes from the invitations and confirmations in your D1, and is labeled as Pithy’s count. The two can differ, most obviously when somebody opts out in the Play Store without telling the app, and the record lists each reason they can.
Managing testers
Invite a tester. Resend an invitation. Nudge a tester. Remove a tester. An invite names an address you type. A resend, a nudge and a remove name a tester from the roster this read carried, so nothing outside it can be sent. A Worker too old to send the roster says so, and so does every act that needs it.
A nudge mails a real person from your domain, so each tester is shown with what stands between them and one. A tester still cooling down is drawn with the moment it lifts and cannot be chosen. A tester whose address bounced or is suppressed is drawn with that reason and cannot be chosen either. A resend is held to the same two. Your Worker enforces the cooldown; the choice says so before you press, rather than a refusal after.
Removing a tester takes them off the cohort, and their history stays. A closed cohort takes none of the four.
All four are part of Solo, and each asks before it acts. Below Solo they are drawn locked and say what the plan buys; pithy testers does the same against your Worker on any plan.
Every action here is audited
In your trail, under the control-plane actor kind, carrying the connection id and the dashboard user’s own subject.