AI Team Development
Run shared bRRAIn memory for a team of people and AI assistants: structure, access, curation, attribution and hand-offs.
- Level
- Practitioner
- Learning time
- 18 hours
- Price
- $499
- Credential
- Valid 3 years
What changed in this edition.
- Memory layers replace v1's 'five zones', mapped to real vault structures: org and project canonical, session records, personal workspaces (Z2) and the access layer.
- Access for humans and agents taught on the real console: custom roles whose checklist replaces tier defaults, per-project Read/Add/Update/Delete grants, and purpose-issued agent credentials proven with a refused write.
- Hand-offs are MCP-first: start_brain_session, record_assistant_turn, record_decision with a human owner, and hand-off turns whose Depends on / Produced lines feed Nexus Memory Lineage. The git open/closure ritual is now the secondary variant.
- The Consolidator and Conflict Zone are taught as the product components they are: priorities, three-way merge, role-hierarchy auto-resolution and the 24-hour default escalation, with humans curating canonical.
- New team surfaces: console Projects with AI charter drafting, Nexus Plan epics and sprints, Nexus Memory and Meetings, and multi-client teams across Claude Desktop, VS Code, ChatGPT and Nexus.
- Labs and the capstone are AI role-plays scored against published rubrics; the exam is a per-candidate form with four AI-conducted performance tasks.
What you will be able to do.
- You will be able to design a team memory layout across memory layers, projects and charters for a mixed human-agent team.
- You will be able to configure least-privilege access for people and AI agents with custom roles, per-project permissions and proven boundaries.
- You will be able to run consolidation and curation of canonical memory and resolve collisions and conflicts without losing history.
- You will be able to attribute every decision to an accountable human across AI clients and hand off work between any combination of people and agents.
- You will be able to encode team standards so every assistant inherits them, and enforce the mechanical ones with recorded overrides.
- You will be able to run multi-actor work and blameless retros on Nexus Plan, Memory and Meetings.
- You will be able to onboard a new engineer or AI contributor into team memory in about 30 minutes.
Who it's for
- Tech leads and engineering managers running mixed human and AI teams
- Staff engineers responsible for shared memory and standards
- Project curators and maintainers coordinating contributors with AI assistance
- Founders moving from solo AI use to team AI use
Not covered here
- The personal session loop (see #13 AI Coding with bRRAIn; this course assumes it)
- Release-train design (see #15 AI SDLC & Release Train)
- System architecture (see #16 AI Augmented Systems Architect)
- People management; this is engineering practice
8 modules, 64 lessons.
About 18 hours of learning. Open a module to see every lesson.
-
Team memory structure
Why team memory differs from solo memory; the five memory layers mapped onto real vault structures; console Projects with AI-drafted 12-section charters; personal workspaces (Z2) and per-session records; designing a complete team memory layout. Lab 1 designs Northwind's layout with its engineering manager.
- Module 1 pretest
- Why solo memory and team memory are different
- Memory layers: mapping team memory onto the vault
- Projects and AI-drafted charters
- Personal workspaces and session records
- Designing a team memory layout end to end
- Lab 1: Design Northwind's team memory layout
- Retrieval: 8 questions across the module
-
Access for humans and agents
The seven canonical roles mapped to a team; custom roles whose checklist replaces tier defaults; per-project Read/Add/Update/Delete permissions; agent credentials, least privilege and refused-write proofs; an access review after a near miss. Lab 2 configures access with the security lead.
- Module 2 pretest
- The seven roles and team memory
- Custom roles that replace tier defaults
- Per-project permissions for team access
- Agent access: credentials, least privilege, proof
- Scenario: reviewing a team's access after a near miss
- Lab 2: Configure team access with the security lead
- Retrieval: 8 questions across the module
-
Consolidation and curation
The Consolidator pipeline at team scale and its read-only inspection commands; session records versus canonical; the curation protocol and its four dispositions; the Conflict Zone, role-hierarchy auto-resolution and escalation; consolidation and curation cadence; a worked weekly curation pass. Lab 3 curates a week of session records with the project curator.
- Module 3 pretest
- The Consolidator at team scale
- Session records vs canonical: the fundamental split
- The curation protocol: what survives, what doesn't
- Conflicts and the Conflict Zone
- Consolidation and curation cadence
- A weekly curation pass, worked
- Lab 3: Curate a week of team session records
- Retrieval: 8 questions across the module
-
Attribution and hand-offs
Attribution from credentials, record_decision owners and the first-turn convention; commit conventions for AI-touched work; multi-client teams across Claude Desktop, the VS Code extension, the ChatGPT app and Nexus; the MCP-first hand-off ritual with the git variant; AI-to-AI, human-to-AI and AI-to-human hand-offs. Lab 4 runs a six-step hand-off chain.
- Module 4 pretest
- The attribution model: who did what, with which assistant
- Commit conventions for AI-touched work
- Multi-client teams: Claude Desktop, VS Code, ChatGPT and Nexus
- The hand-off ritual: MCP-first
- AI-to-AI hand-offs: sub-agents and parallel sessions
- Human-to-AI hand-offs: resume my work
- AI-to-human hand-offs: review this
- Lab 4: Run a hand-off chain across two humans and two agents
- Retrieval: 8 questions across the module
-
Standards AI inherits
The four kinds of team standard and what makes one enforceable; encoding standards in canonical so every assistant inherits them through the session protocol and pointer rules; hooks and CI checks with recorded overrides; the 'AI says no' pattern; auditing standards drift. Lab 5 adds standards and enforcement for Northwind.
- Module 5 pretest
- The standards anatomy: style, review, decision quality, documentation
- Encoding standards so every assistant inherits them
- Pre-commit hooks and CI checks for AI-touched work
- The 'AI says no' pattern
- Auditing standards drift across a team, worked
- Lab 5: Add team standards and enforcement for Northwind
- Retrieval: 8 questions across the module
-
Multi-actor operations
The shape of a multi-actor session; team surfaces in Nexus Plan, Memory and Meetings; detecting the five collisions; lock-free coordination with append-only records and attribution-based merge; reviewing versus writing modes enforced by access; blameless retros that separate AI and human causes. Lab 6 runs a live session with injected collisions.
- Module 6 pretest
- The multi-actor session shape
- Team surfaces: Nexus Plan, Memory and Meetings
- Detecting collisions in real time
- Lock-free coordination: append-only records and attribution-based merge
- AI is reviewing vs AI is writing
- Blameless retros that separate AI and human causes
- Lab 6: Run a live multi-actor session with injected collisions
- Retrieval: 8 questions across the module
-
Onboarding and coaching
The 30-minute onboarding ritual for people; onboarding AI contributors with owner, credential, pointer instructions and a boundary proof; the coaching arc from personal loop to team fluency; common new-contributor failures. Lab 7 onboards a new engineer in 30 minutes.
- Module 7 pretest
- The 30-minute onboarding ritual
- Onboarding an AI contributor
- The coaching arc from solo to team fluency
- Common new-contributor failures and how to spot them
- Lab 7: Onboard a new engineer in 30 minutes
- Retrieval: 8 questions across the module
-
Capstone and exam readiness
The capstone brief, rubric and hard fails; exam structure, blueprint and pacing; the capstone role-play: stand up and run team memory for Harborline Logistics' Rate-Engine project and handle an incident.
- Module 8 pretest
- The capstone brief: what is given and what is required
- Exam readiness: blueprint, item types and timing
- Retrieval: 6 questions across the module
- Capstone: Stand up and run team memory for a mixed human-agent team
Practice against someone who pushes back.
Labs run in your browser as AI role-plays. An AI plays the person on the other side of the scenario — with their own goals and objections — and your work is scored against the published rubric. There is nothing to install.
-
Lab 1 · Team memory structure
AI role-play with Northwind's engineering manager: design the team memory layout for a mixed human-agent project
-
Lab 2 · Access for humans and agents
AI role-play with the security lead: configure roles, per-project grants and agent credentials for the team
-
Lab 3 · Consolidation and curation
AI role-play with the project curator: curate a week of team session records
-
Lab 4 · Attribution and hand-offs
AI role-play with a senior engineer arriving cold: run a six-step hand-off chain across two humans and two agents
-
Lab 5 · Standards AI inherits
AI role-play with a skeptical senior engineer: add team standards and enforcement that every assistant inherits
-
Lab 6 · Multi-actor operations
AI role-play with the engineering manager: run a live multi-actor session with five injected collisions
-
Lab 7 · Onboarding and coaching
AI role-play with a new engineer: run the 30-minute onboarding ritual
-
Lab 8 · Capstone and exam readiness
AI role-play with a VP Engineering and a curator: stand up team memory for a new project and handle an incident
Stand up and run team memory for a mixed human-agent team
AI role-play scored against the published rubric
Pass mark: 72%
Scored on
- Memory layout and project structure15%
- Access design for humans and agents20%
- Attribution and hand-off protocol20%
- Curation, consolidation and conflict handling20%
- Standards encoding and enforcement15%
- Onboarding and incident communication10%
One exam. A credential anyone can verify.
The exam
- Items per form
- 59
- Time allowed
- 120 min
- Pass mark
- 72%
- Performance tasks
- 4
- Attempts included
- 2
- Wait between attempts
- 7 days
- Online and timed, taken on learn.brrain.io.
- Your form is assembled for you from the course's item bank, so no two candidates sit the same paper.
- Performance tasks are conducted by an AI examiner: you work through a realistic scenario and are scored against a published rubric.
The credential
- A verifiable digital badge in your name.
- A public verification page at learn.brrain.io/verify, so an employer or client can confirm it.
- Valid for 3 years.
- Renewal: At 3 years, by passing the then-current exam; CE modules completed during the cycle keep the credential current
Where this course sits.
Stacks well with
Frequently asked.
Do I need to install anything for the labs?
No. Labs and the capstone run in your browser on learn.brrain.io as AI role-plays: an AI plays the person on the other side of the scenario, and your work is scored against the rubric published with the course.
How is the exam delivered?
Online and timed: 59 items in 120 minutes, on a form assembled for you from the course's item bank. 4 of the items are performance tasks conducted by an AI examiner: you do the work rather than pick an answer. The pass mark is 72%.
What if I don't pass first time?
You have 2 attempts, with a 7-day wait after an unsuccessful attempt. Further exam attempts can be bought for $299 each.
How long is the credential valid?
3 years. You receive a verifiable digital badge with a public verification page at learn.brrain.io/verify, so anyone can confirm it is genuine.
I hold the v1 credential. Is it still valid?
Yes. Credentials earned on v1 remain valid and verifiable at learn.brrain.io/verify. When you renew, you sit the then-current version of the exam.
Can my company enroll a team?
Yes. Firms can buy a certification bundle for $2,999 per firm per year — see the pricing page — or contact us to arrange enrollment for a larger group.
Related courses.
AI Team Development
Run shared bRRAIn memory for a team of people and AI assistants: structure, access, curation, attribution and hand-offs.