Five pillars. Two are shipped and already running in production in the underlying response engine. Three -- scored quizzes, the open self-serve teacher signup, and live billing -- are in development. Each is marked honestly.
An ungraded check today, a scored quiz once its shape ships
A pop quiz built here today is ungraded by construction: a single-choice question, a 1-to-5 scale check, or an open text prompt -- the three answer shapes the engine underneath already validates, enforced by a database wall, not just a client-side check. A right/wrong scored quiz needs an answer shape the engine does not yet enforce (a scoring shape). We say that plainly rather than badge grading available early: today this is a fast, informal read on the room, not a scored or standardized instrument.
Ungraded checks work on the shipped shapes -- scoring is in development
Sign up, create, share, read
The loop is short: sign up for early access, build a question or a short set, share a link or a code with the class, and read what comes back in a response feed. Today the authoring and share-link-mint surface is founder-only by design -- the founder-only posture lives in the UI gate, not the data model, which is exactly what lets a self-serve signup open the same surface to any teacher without a reshape. That opening is what this page is pitching: it is being built, not shipped.
Founder-only today -- self-serve teacher signup in development
A response with no identity column, by construction
There is no identity column in the response table at all -- no name, email, IP address, account, browser fingerprint, or session column. Not hidden, not masked, simply never created, so a future bug cannot fill in a column that does not exist. The stored submission time is coarsened to the hour before it is written, so even the moment a response landed cannot be lined up against the moment a link went out to work out who answered. This is a real, provable property of the data model, backed by the same response engine question.technology already proves in production today.
Shipped -- proven in production today
Moderation and abuse limits run before a response ever reaches your feed
Every incoming response passes a server-side moderation pass for likely foul language or spam before it lands anywhere -- a flagged response is labelled, never silently thrown away, so nothing disappears without a record. A salted, rotating rate limit bounds how many responses one source can send in a time window; the limiter key cannot be reversed back to a sender and is never written to the response table. Both checks are server-authoritative and already proven in production in the same engine today.
Shipped -- server-authoritative, already running
Early access, honestly: no live signup, no live billing yet
There is no open public signup form on this page and no live checkout. Requesting early access takes a teacher's own email address and nothing else; no student information is asked for, and no card is charged today. When self-serve signup and live billing are enabled, that will be a founder-gated decision announced plainly here, not a quiet flip.
Honest-off -- request early access, no card charged today