Glossary
The vocabulary that recurs across the product and these docs, defined in one place.
Cohort
One run of the first six weeks for one group of students, usually an intake. Each cohort has its own content, its own roster, and its own insights. Staff switch between cohorts; data never bleeds across them.
Week
A numbered step in the six-week arc. Content (events, briefings, to-dos, the check-in) is authored per week, and a cohort's weeks are marked as complete, current, or coming up.
Check-in
The weekly wellbeing question a student answers. A single response per week, rolled up into a cohort-level signal. Individual answers are never shown to staff.
Signal / Pulse
The aggregated read on how a cohort is travelling, derived from check-ins. Pulse is the view staff see: a distribution across the cohort, not a list of individuals.
Help request
A message a student raises through the help flow. Carries a priority (normal, urgent, or crisis) and routes to staff in the inbox.
Crisis
The danger threshold for a help request: the message tripped the crisis signal list (self-harm, suicide, or threats to others). Detected on the client and again on the server, and the only level that pages staff in real time.
Actor
An identity within an institution: a student or a staff record. A signed-in person
(auth_user_id) maps to exactly one actor per institution. See
the two apps.
Institution / tenant
One customer of First Six. Every row of data is scoped to an institution, and that scoping is the tenant boundary.
RLS (row-level security)
The database mechanism that enforces the tenant boundary. Policies attached to each table decide which rows a given caller can see, so isolation lives in the database rather than in application code.
Audience tags
The campus, program, and role labels used both to target content at the right students and to scope which content a staff member is allowed to author.
MIN_N
The small-cell suppression floor (five). A breakdown stays hidden until at least five students sit behind it, so no individual can be identified from an aggregate.
The fastest answer is usually one question away.