Brain · Team brain
Repository memory with evidence
Find the guidance your repository already has, then check what reached a session, what a guard did, and whether the defect returned.
For: developers investigating a GitHub repository and the team reviewing its fixes
What it does, and why it helps
Memory keeps cases with their prevention evidence, including resolved cases. Open a case to inspect lesson versions, delivery receipts, guard outcomes and recurrence decisions.
Brain adds shared repository knowledge. The local page shows shared-lesson and repository counts, recent guidance, cases with lessons and a file lookup. Hosted Memory provides searchable lessons and a repository wiki. Personal repositories are excluded from hosted team knowledge and search.
The pain. A written lesson does not show whether anyone received or used it.
The point of view. Keep delivery, acknowledgment, use, guard execution and recurrence as separate evidence.
What gets easier. Read a lesson and open its case without leaving the investigation.
When it helps. Before changing an unfamiliar repository, or after a defect returns.
Its limits. A saved lesson is not proof of prevention. A guard that did not run is not a clean result. Lists are bounded and capture may be incomplete.
Understand it in 30 seconds
Read the narration
- 0:00 Your team wrote the lesson down.
- 0:02 Nobody knows if it reached anyone.
- 0:06 A saved lesson is not prevention.
- 0:08 RepoOps counts what was delivered, and what ran.
- 0:13 The lens shows delivered, caught, missed, and did not run.
- 0:16 A guard behind a disabled hook is not a clean run.
- 0:23 Read the receipts, not the count.
- 0:25 Sharing stays off until you allow it.
Synthetic example. Read the guide
Where to find it
Where to find it
- Desktop:
localhost:4000, then Memory in the sidebar, then Team brain under All tools, in the Evidence readers group. - Hosted:
repoops.ai/team/brain, from Memory in the sidebar. - Keyboard: ⌘ K, then type “Team brain”.
When to use it
Prepare a repository change
Situation. You are about to edit an unfamiliar module.
What you do. Search shared guidance or use the local file lookup.
What you see. A matching lesson identifies its repository and recorded guidance.
What it establishes. You know what was previously learned; this does not establish that the lesson was used in a new session.
Investigate a recurrence
Situation. A previously fixed problem returns.
What you do. Open its case from Memory and inspect Prevention.
What you see. Lesson version, delivery, guard results and recurrence decisions remain distinct.
What it establishes. You can distinguish missing delivery from a guard that ran and missed.
Before you start
- Supported versions
- This guide describes the focused source update of September 24, 2026. Signed-package acceptance remains pending.
- Where it runs
- Local Memory and its Brain supporting page; hosted Memory at /team/brain.
- Permissions
- Hosted knowledge follows current team membership and repository access. Personal repository knowledge is excluded from the team page and its search.
- Connections
- Shared local knowledge requires a team binding and enabled lesson sharing. Local case receipts are separate.
- Plan
- Hosted Brain search checks the team's entitlement before reading shared lessons.
Configure it
- Open Memory.
Review cases and their prevention evidence, including resolved cases.
- Connect the installation and enable lesson sharing.
Shared knowledge needs both a team binding and the lesson-sharing setting. Managed evidence capture has its own repository policy.
- Inspect the source.
Read the lesson, its repository and the recorded case evidence before relying on it.
| Setting | Where | A sensible choice | Why it matters |
|---|---|---|---|
Lesson sharing | Settings, Brain and sync | Enable for the intended team | Controls publishing and receiving distilled shared lessons. |
Repository access | Hosted team access settings | Grant only the repositories the investigator needs | The page and search resolve scope before reading knowledge. |
What you should see
Sharing unavailable
Configuration. No binding or lesson sharing disabled
Expect. Shared knowledge is locked. Local case evidence remains a separate read.
Verify. No invented shared-lesson count appears.
Shared knowledge available
Configuration. Bound installation with shared lessons
Expect. Repository counts and a bounded recent-lesson list; case receipts remain separately inspectable.
Verify. Open a lesson and a case. Confirm the repository and the recorded outcomes.
Read failed
Configuration. Unreadable cache or unavailable hosted store
Expect. An unavailable state, not an empty success.
Verify. Retry after restoring the store; no absence of evidence is presented as a successful guard run.
Data and cost
- What is captured
- This page reads distilled lessons and existing incident receipts. It does not start a new trace or transcript capture.
- Who can see it
- Shared lessons contain redacted trigger, rule and fix text with repository and observation metadata. Raw incident evidence follows the separate managed repository policy.
- How long it is kept
- The local shared-lesson cache is bounded to 500 entries. The recent local view shows at most eight lessons. These are bounded views, not a complete history.
- What leaves the machine
- The focused Brain page does not start presence broadcasts or fetch benchmark, discipline or cost comparisons. Shared-lesson synchronization runs independently of page rendering.
- What it costs
- Opening Brain no longer invokes the cross-repository AI-call and outcome aggregation used by the archived comparison panels. Whole-app resource acceptance remains pending.
When the result differs
| Symptom | Likely cause | Next action |
|---|---|---|
| Shared knowledge is locked | The installation is unbound or sharing is disabled | Check the team connection and lesson-sharing setting. |
| Search is unavailable | The knowledge or privacy-policy read failed | Retry after restoring the service; do not treat this as no matching guidance. |
| A guard did not run | No successful execution receipt exists for that event | Inspect the case's delivery and guard receipts before claiming prevention. |
- Disable
- Disable lesson sharing in Settings to stop subsequent exchange.
- Roll back
- The shared cache has no user-facing version rollback control.
- Revoke access
- Disconnect the installation or change hosted repository access. Previously delivered local records require their own retention handling.
- Delete
- Removing navigation or disabling sharing does not delete stored lessons or incident evidence.
Related tasks
Maintenance evidence
- Feature id
team-brain(spine leafteam-brain)- Owner
- Dashboard mission alignment, LDG-0942
- Supported product version
- September 24 source update; release pending
- Last verified
- Read against the focused local Brain reader and hosted Memory/search implementations. Local isolated fixture and targeted automated checks recorded in the implementation audit.
- Example fixtures
- lib/routes/team-brain.test.mjs; hosted Brain page tests; app/api/team/brain/query/route.test.ts
- Source references
public/team-brain.html,lib/routes/team-brain.mjs,lib/org-brain-pull.mjs,website/app/team/(home)/brain/page.tsx,website/app/api/team/brain/query/route.ts- Documentation review
- Source-alignment update; independent review not recorded.
- Video review
- Replacement walkthrough render, captions, review and publication remain pending. A storyboard is not a release receipt.
Last updated