---
id: "action-choose-architecture-by-scale"
type: "action-item"
source_timestamps: ["00:45:53", "00:46:20"]
tags: ["system-design", "decision-making"]
related: ["claim-wiki-breaks-at-scale", "claim-wiki-better-solo-research"]
speakers: ["Nate B. Jones"]
action: "Choose a Wiki for solo research, but mandate a structured Database for team or multi-agent environments."
outcome: "Prevents system failure, race conditions, and data corruption at scale."
sources: ["s11-wiki-vs-open-brain"]
sourceVaultSlug: "s11-wiki-vs-open-brain"
originDay: 11
---
# Select Memory Architecture Based on Team Scale

# Action: Select Memory Architecture Based on Team Scale

**Action:** Choose a Wiki for solo research, but mandate a structured Database for team or multi-agent environments.
**Outcome:** Prevents system failure, race conditions, and data corruption at scale.

## Decision Rule

Evaluate your use case **before** building an AI context layer.

| Scenario | Recommendation |
|----------|----------------|
| Solo researcher, deep dives, no multi-agent need | [[concept-ai-wiki]] (markdown via [[entity-obsidian]]) |
| Team, multi-agent, or > ~10,000 documents | [[concept-openbrain-architecture]] (structured SQL DB) |
| Want both readability *and* scalability | [[concept-hybrid-memory-architecture]] |

## Why This Matters

- For solo deep research, the Wiki's [[concept-write-time-synthesis]] gives a uniquely readable evolving study guide ([[claim-wiki-better-solo-research]]).
- For multi-agent teams, the Wiki fails catastrophically due to [[concept-race-conditions-ai]] and lack of metadata filtering ([[claim-wiki-breaks-at-scale]], [[claim-db-better-multi-agent]]).

## See Also

[[action-build-hybrid-system]] for the recommended path when you need both.