Writes reference cards for projects, concepts, or people in the wiki. Projects get 800-1500 words with architecture, benchmarks, limitations, and alternatives. Concepts get 1500-2500 words. People get 150-250 words. Use when writing wiki reference cards for specific entities.
Read config/domain.ts for domain context and taxonomy bucket definitions.
Write reference cards for projects, concepts, or people.
| Type | Words | Output path |
|---|---|---|
| Project | 800-1500 | wiki/projects/<slug>.md |
| Concept | 1500-2500 | wiki/concepts/<slug>.md |
| Person | 150-250 | wiki/people/<slug>.md |
raw/deep/repos/ and raw/deep/papers/Every card starts with <abstract></abstract> tags before any headings. One sentence, under 200 chars. State what it does plus the key differentiator. Not a generic description.
What It Does -- Concrete description. Not marketing copy. What problem it solves and the architectural approach that makes it different.
Architecture -- How it works. Name specific files, modules, algorithms from deep sources. Enough detail that a reader understands HOW, not just WHAT.
Core Mechanism -- The key algorithm or pattern with implementation detail from deep sources.
Key Numbers -- Benchmarks with credibility assessment: self-reported, peer-reviewed, or verified in code. If README claims cannot be verified, say so.
Strengths -- Each backed by evidence from a deep source.
Critical Limitations -- At minimum:
When NOT to Use It -- Operational conditions where this is the wrong choice.
Unresolved Questions -- 3-5 specific unknowns: governance, cost at scale, conflict resolution, architectural growth limits. What the documentation does not explain.
Alternatives -- Link to other project cards with guidance on when to pick each.
Definition -- What it is. Precise, no jargon layering.
Why It Matters -- The specific problem it solves for practitioners.
How It Works -- Implementation details from deep sources. Name projects that implement it and how their approaches differ.
Who Implements It -- Link to project cards with each project's specific approach noted.
Failure Modes -- When does this concept break down? Concrete scenarios.
Open Questions -- What remains unresolved.
Brief profile: who they are, key contributions to the field, notable work. Link to their projects and publications in the wiki.
[Source](../raw/type/file.md) or [Source](../raw/deep/type/file.md)[Mem0](../projects/mem0.md), [context graphs](../concepts/context-graphs.md)---
entity_id: <slug>