the community brain

A community brain you can see, and interns that go find what it doesn’t know yet.

Dispatch a long-running intern at a brief and leave it alone. It reads everything the community knows, does the work, and files what it learns back. Drafts stop and wait for you. Nothing goes out until you approve it, and then it goes from your own Gmail or Slack.

Try it with GitHub →a public test brain · everyone who signs in shares it
example · one onboarding briefsize = how much hangs off it
interna brief someone ranfactsomething the brain knowssourcewhere a fact came from
example · one intern
$spawn map every mention of the ramp pilot across slack, drive and the wiki
·int-01kx  queued
·int-01kx  recalled 3 facts from the brain
·int-01kx  reading #ramp-pilot — 34 messages
+int-01kx  filed note-118 “the pilot is Slack-first”
!int-01kx  drafted act-01hw → outbox, waiting on you
$_

why it isn’t a chat window

Nothing leaves without you

An intern that decides something should go out writes a draft and stops. You approve it, and it sends from your own connected account. Approval is the only way anything leaves.

Editing teaches it

The outbox keeps both halves: what the intern proposed and what you were actually willing to send. That difference becomes a fact the next intern reads first.

It never stalls

Missing details become [placeholders] you fill in before approving. There's no question to answer and no guess sent without you.

how it gets better

Four steps, and the fourth feeds the second. That loop is the whole product: the brain learns this community by being corrected, not by being configured.

  1. 1you brief

    One sentence, no workflow to configure. “Draft a Slack post introducing Intern.”

  2. 2it reads the brain

    Before thinking, the intern pulls the facts that bear on the task — including what people corrected last time.

    reads the brain
  3. 3it works, then stops

    It files what it learned as facts, and anything outbound becomes a draft. An intern can't send on its own.

    writes the brain
  4. 4you approve or edit

    Editing before approving is the training signal: the change is filed as a fact, so the next intern starts with it.

    teaches the brain
the brainone set of facts, shared by everyone who signs instep 4 writes what step 2 will read
Nobody writes a rule. A person rewrites a line before approving it, that rewrite becomes a fact, and the next brief retrieves it — so the brain gets more specific about this company every time somebody corrects it.

the community

Everyone who signs in joins one public Slack workspace. Connect your own Gmail or Slack and an intern’s approved draft goes out as you: an email from your address, a message under your name.

Point it at a brief and walk away.

It’s a public test brain — sign in with GitHub and everything you do joins what everyone else has taught it. Drafts stop and wait for you; nothing goes out until you approve it.

Try it with GitHub →