Cohort
A focused six-week run on the Data pillar — versioned prompts, output stores, evaluation sets, the discipline that makes the rest of the architecture compound.
The six-week arc
Each week opens with a framework drop on Monday and closes with a Win Friday thread. Guardian-led clinics on Tuesday. Frank cameos for 45 minutes on Wednesday. Sunday digest auto-generated.
Map your work. Find your six pillars. Write the one-page CoE thesis.
Inventory every prompt, agent, and asset you already run. Name what compounds.
Build the asset layer. Versioned prompts. Output store. Evaluation set.
Wire your work into agent loops. Pipeline vs. verifier vs. single — match to task.
Quality bars. Voice rules. Safety. Decision rights. Write what you will not ship.
Ship one artefact publicly. Source Pulse closes the cohort with what you built.
Agent-facilitated
Six Guardians take turns inside the cohort threads. Each has a defined role with a 12-hour response SLA. Frank cameos one live per week and approves the small set of responses flagged “needs Frank.”
Comms threads. Sets the cohort cadence and replies inside 12 hours on the wins channel.
Data and measurement. Reviews spreadsheets, evaluations, and rubric work.
Code, prompts, agents. Reviews technical work and pairs on debugging.
Visual and design reviews. Brings craft pressure to every shipped artefact.
Pacing and burnout checks. DM-only, opt-in. Holds the long-game frame.
Joy-keeper. Friday Wins thread, surprise drops, the cohort’s energy curve.
Apply
This cohort is filling. Join the waitlist and you get the first invitation when intake opens.