Topic overview · Team intelligence
Team intelligence grows not from more assistants, but from a maintained shared reality.
Personal context stays protected, shared knowledge is maintained, decisions remain traceable. Rights follow responsibility — not technical convenience.
Three context domains, three owners
Individual chats contain different decisions, files and assumptions. A good interface does not transfer chat histories; it publishes selected artefacts: a decision, verified insight, template, test case or hand-off.
01PersonalPreferences, private notes, individual drafts. Supports thought, remains free.exploration · private
02ProjectObjective, roles, approved sources, current decisions, present state.binding for the team
03OrganisationRules, standards, templates, security boundaries, tested methods.outlives projects
01 · MemoryShared memory consists of decisions with status and provenance — not conversations.
02 · RolesContribute, review, decide, approve: rights follow responsibility, for agents too.
03 · ConflictPrecedence rule, escalation path, conflict record — dissent becomes testable quality work.
Core method
The team intelligence charter
Shared objectiveWhich outcomes should collaboration enable reliably?
Context domainsWhat remains personal, project-bound or organisation-wide?
Authoritative artefactsWhich documents carry state, sources, decisions and risks?
Roles and rightsWho may read, contribute, change, decide, approve?
Conflict pathWhich source prevails, who decides, when does escalation occur?
Learning loopHow do incidents and good methods enter the standard?
Choose a real team. Separate context domains, select at most five authoritative artefacts, map roles and rights, design conflict and hand-off, define three maturity signals.