Most AI communities are feeds. Something happens, everyone reacts, and a week later nobody can find what was said. This one is built to do the opposite.
The programme is the onboarding. The community is the product.
A course gives you a concentrated burst of learning. But capability doesn’t come from the burst — it comes from sustained practice, from other people checking your reasoning, and from applying the work somewhere real and finding out where it breaks. That’s what this place is for.
What we actually mean by capability
The uncomfortable thing about AI is that it did not lower the bar. It raised it.
AI produces fluent output constantly, and fluent is not the same as correct. So the scarce skill has moved: it is no longer producing the work, it’s judging it. Can you tell when the model is confidently wrong? Can you supply the context it’s missing? Can you defend the decision afterwards, when it has already failed and someone is asking you why?
We call that last question Decision Survivability, and it’s the thing we actually assess. Not whether you can drive a tool — tools change. Whether you can own the outcome.
Two things to avoid
The Eloquence Trap — mistaking fluency for correctness. The model sounds certain because it always sounds certain. That tells you nothing.
Granting Epistemic Credit — accepting AI output as verified because it reads verified. The work of actually knowing whether it’s right is a real cost, and skipping it doesn’t remove the cost, it defers it to whoever finds the error later.
How this place is organised
- The Logic Pipe — the two protocols that make AI output verifiable: CAGE to set it up, ARCH to check its work.
- AI Adoption (ARGS) — the four domains an organisation has to get right: Architecture, Governance, Scaling, Agency.
- AI Guildhall Studio — bring a real problem, leave with a direction.
- Portfolio — evidence of capability. Not certificates. What you built and why you made those calls.
- Peer Groups, Certification Study Groups, Programme Discussion — the work in progress.
Four routes, not one ladder
Capability here is not a single ladder. Everyone shares a Floor, and above it the path forks into four routes defined by what you’re accountable for:
Build (make it work) · Operate (run it) · Assure (keep it defensible) · Direct (decide what’s worth doing)
They’re peers, not ranks. A senior builder and a senior leader are equals on different axes. Read Find your place to work out which buck you hold.
Topics are tagged by route and by depth (Floor, T1–T4), so you can filter to your seat rather than reading everything.
Membership
Explorer is free, and most of what’s here is readable without an account. Registration is open, but every application is reviewed before approval — that’s deliberate. A room worth being in is a room somebody is curating.
If you’re new: say hello in Introduce yourself, then read Find your level to work out where you’re starting from.
One thing worth saying plainly: most people belong at the Floor, and that is the design, not a failure. Nobody needs to be a Maestro. The point is knowing where you are and what the next rung asks of you.