Founding cohort (illustrative)
0 of 10 places · Fictional preview. No one is enrolled.
Coordinator & sponsor demonstration
What the proposed cohort model would require
This is a planning destination, separate from the participant experience. Nothing here commits any organization, and no staff time has been assigned.
01
Prototype cohort administration
A protected demonstration of how authorized cohort records could be managed.
Checking your session…
02
Illustrative cohort preview
Fictional planning content so the shape of a cohort is visible without inventing real participants.
New Director circle (illustrative)
0 of 12 places · Fictional preview. Noncredit concept.
03
Proposed weekly rhythm
The facilitation shape a cohort session would follow.
1. Check-in · 10 minutes
Each director names one thing that went well and one thing that got stuck this week.
2. One practical dilemma · 25 minutes
A single anonymous leadership dilemma brought by a member; peers ask questions before offering advice.
3. Work studio · 35 minutes
Quiet, supported build time on the current course artifact, with a facilitator circulating.
4. Next-step commitment · 10 minutes
Each director writes one action, an owner role, and a review date before leaving.
04
Who would need to do what
Roles, not named people. No organization has agreed to any of this.
| Role | Scope |
|---|---|
| College / program team | Course approval, academic sequencing, and any credit-bearing decisions. |
| Community coalition | Director recruitment, local context, and connection to existing early learning efforts. |
| Funding partner | Scholarship support decisions and reporting expectations. |
| Cohort facilitator | Weekly rhythm, dilemma facilitation, and artifact support. |
| Director participants | Attendance, artifact completion, and trying one change in their own center. |
Secure coordinator bootstrap
There is no way to become a coordinator from inside this app, by design. The first coordinator must be granted by an owner-authorised database action: the person creates an ordinary account, the owner looks up that verified account's user id, and inserts a single coordinator row into the roles table using an administrative connection. The roles table has no write rule for members at all, so the first person to sign up gains nothing, no email address is hardcoded anywhere, and no service key is exposed to the browser.
Proposed educational model only. No active collaborative, sponsor, staffing commitment, schedule, funding, or partnership is confirmed.