Dexter
Pick the Dexter layer you need first. Each link jumps to the section that answers the most common Labs question.
- Primary job: Turn rough ideas into bounded experiments with clear hypotheses, success signals, and kill criteria.
- First split: Dexter designs and assesses; Buzz distributes and finds audiences.
- Best use: Open this page when the question is how Labs tests ideas, what kill criteria means, or when to engage the Dexter + Buzz lane.
Dexter is the Labs experiment leader
Reader orientation
Use this page when you need to understand how Labs tests product ideas — from hypothesis through honest assessment — with kill criteria set before the experiment starts.
What changed recently
Compact updates that help a reader place this agent in the current network story.
- Aug 8·Dexter district page created following the established PageHero/PageSection/RouteRow pattern.
Every experiment ships with a hypothesis, a success signal, and a kill criteria line
Dexter rejects vague momentum. A candidate idea must become a bounded experiment with a clear hypothesis, success signal, and next decision gate before it earns build time.
The question Dexter forces: What specific hypothesis are we testing, what signal proves it wrong, and what decision follows?
Every experiment ships with an explicit shutdown condition defined upfront. No experiment runs without a kill criteria line that names when to stop.
Example: "If no measurable improvement after 10 new hires, sunset the experiment." This prevents sunk-cost momentum from keeping dead ideas alive.
When results return, Dexter's job is not to celebrate — it is to assess honestly. Did the hypothesis hold? Did the success signal fire? Should this continue, pause, or sunset?
The assessment produces one of three explicit recommendations: continue (scale up), pause (iterate on the design), or sunset (kill the idea and document what was learned). Jake and Derek hold final say on the financial/strategic commitment.
Dexter and Buzz still pair on every Labs experiment — CurryChat is their shared direct surface. Dexter works Slack, Notion, and CurryChat directly; Buzz's registry lanes are Bridge + CurryChat.
This keeps Labs collaboration lightweight while staying honest about transport: the Dexter → Buzz experiment handoff lands on CurryChat, and Buzz's network-side work (the Budgets social loop) rides Bridge.
The Dexter + Buzz Labs experiment lifecycle
Dexter takes a rough product idea and shapes it into a falsifiable hypothesis with a clear question, success metric, and kill criteria — before any code is written.
Example: "New hires will complete onboarding 40% faster with an AI-generated personalized checklist." Success signal: time-to-first-PR reduced from 5 days to ≤3 days across a 2-week cohort.
Once the experiment plan is validated, Dexter routes it to Buzz for distribution design. Buzz finds the audience and designs the distribution experiment.
This handoff lands on CurryChat — the pair's shared direct surface. Buzz's network-side lanes, including the Budgets social loop, ride Bridge.
Results flow back to Dexter. The assessment is honest: did the hypothesis hold, did the success signal fire, and what is the explicit continue/pause/sunset recommendation?
Dexter's assessment goes back to the team via CurryChat or Slack. The recommendation is explicit and documented — not buried or implied — and the founding team makes the final call.