architecture
Skill624 starsChanged 6 months agoApache-2.0View on GitHub
Memoria codebase structure, workspace layout, key traits, database tables, config patterns, and testing conventions. Use when navigating or modifying Memoria code.
136 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- lklimek/claudiustheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- DnsQueen/orcinus-skillstheir own version, first seen Nov 8, 2026
- denormans/claude-code-workflowtheir own version, first seen Nov 8, 2026
- xiaoyangtx996/Searching-skilltheir own version, first seen Nov 8, 2026
Used with
Projects with it also use intelligent-routing, bash-linux and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SKB3002Skillintelligent-routing
Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
Also in 6 projects that use this
xenitV1Skillbash-linux
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
Also in 8 projects that use this
xenitV1Skillred-team-tactics
Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.
Also in 8 projects that use this
SKB3002Skillnextjs-react-expert
React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.
Also in 3 projects that use this
- +8 more from xenitV1
Other versions136 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 136
- anthropics/knowledge-work-plugins★ 35ksame name
- iOfficeAI/AionUi★ 34ksame name
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- nativewind/nativewind★ 8.1ksame name
- PaulWoitaschek/Voice★ 3.3ksame name
- wellwelwel/poku★ 1.2ksame name
- Alwurts/simple-ai★ 755same name
- patrickjaja/claude-desktop-extra★ 734same name
- ktnyt/cclsp★ 673same name
126 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- .cursor/rules/memory-branching-patterns.mdcCursor rule
- .cursor/rules/memory.mdcCursor rule
- api-referenceSkill
- deploymentSkill
- local-embeddingSkill
- plugin-developmentSkill
- releaseSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 118 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 89
When adding a Config field: update ALL test Config { ..
- Very specific: line 106
Add handler in memoria-api/src/routes/
- Very specific: line 108
Add e2e test in memoria-api/tests/api_e2e.rs using spawn_server()
“Common” is measured: kept by at least 6 in 10 of the 118 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workspace Layout
memoria/ # Cargo workspace root
├── crates/
│ ├── memoria-core/ # Shared types: MemoriaError, Memory, MemoryType
│ ├── memoria-storage/ # SqlMemoryStore — all SQL queries, migrations
│ ├── memoria-service/ # Business logic
│ │ └── src/
│ │ ├── service.rs # MemoryService — main entry point
│ │ ├── scheduler.rs # GovernanceScheduler — periodic tasks + leader election
│ │ ├── config.rs # Config struct (reads env vars)
│ │ ├── distributed.rs # DistributedLock, AsyncTaskStore traits + SQL impls
│ │ ├── governance/ # GovernanceStrategy trait, DefaultGovernanceStrategy
│ │ └── plugin/ # Plugin system (manifest, repository, rhai, grpc)
│ ├── memoria-api/ # REST API (axum)
│ │ └── src/
│ │ ├── lib.rs # build_router(), route registration
│ │ ├── state.rs # AppState (service, task_store, instance_id)
│ │ └── routes/ # memory, admin, governance, plugins, sessions
│ ├── memoria-mcp/ # MCP server (stdio/SSE transport)
│ ├── memoria-cli/ # CLI binary: init, mcp, serve, plugin, benchmark
│ ├── memoria-embedding/ # Embedding + LLM client
│ └── memoria-git/ # Git-for-Data: snapshots, branches, merge
├── Cargo.toml # Workspace deps
└── build.rs # Proto compilation (tonic)Key Traits
trait GovernanceStrategy: Send + Sync {
fn strategy_key(&self) -> &str;
async fn plan(&self, store, task) -> Result<GovernancePlan>;
async fn execute(&self, store, task, plan) -> Result<GovernanceExecution>;
}
trait GovernanceStore: Send + Sync {
async fn list_active_users(&self) -> Result<Vec<String>>;
async fn quarantine_low_confidence(&self, user) -> Result<i64>;
// ... cleanup/maintenance methods
}
trait DistributedLock: Send + Sync {
async fn try_acquire(&self, key, holder, ttl) -> Result<bool>;
async fn renew(&self, key, holder, ttl) -> Result<bool>;
async fn release(&self, key, holder) -> Result<()>;
}
trait AsyncTaskStore: Send + Sync {
async fn create_task(&self, task) -> Result<()>;
async fn complete_task(&self, task_id, result) -> Result<()>;
async fn fail_task(&self, task_id, error) -> Result<()>;
async fn get_task(&self, task_id) -> Result<Option<AsyncTask>>;
}Database Tables
| Group | Tables |
| Core | mem_memories, mem_user_state, mem_branches, mem_snapshots |
| Graph | memory_graph_nodes, memory_graph_edges, mem_entities, mem_memory_entity_links, mem_entity_links |
| Audit | mem_edit_log, mem_retrieval_feedback, mem_memories_stats |
| Governance | mem_governance_cooldown, mem_governance_runtime_state, mem_user_retrieval_params |
| Auth | mem_api_keys |
| Plugin | mem_plugin_packages, mem_plugin_signers, mem_plugin_bindings, mem_plugin_binding_rules, mem_plugin_reviews, mem_plugin_audit_events |
| Distributed | mem_distributed_locks, mem_async_tasks |
Config
Config struct in config.rs reads from env vars:
| Field | Env Var | Default |
db_url | DATABASE_URL | mysql://root:111@localhost:6001/memoria |
embedding_provider | EMBEDDING_PROVIDER | local |
instance_id | MEMORIA_INSTANCE_ID | Random UUID |
lock_ttl_secs | MEMORIA_LOCK_TTL_SECS | 120 |
governance_plugin_dir | MEMORIA_GOVERNANCE_PLUGIN_DIR | None |
governance_plugin_binding | MEMORIA_GOVERNANCE_PLUGIN_BINDING | default |
governance_plugin_subject | MEMORIA_GOVERNANCE_PLUGIN_SUBJECT | system |
When adding a Config field: update ALL test Config { .. } constructors — check scheduler.rs tests AND tests/plugin_repository.rs.
REST API Structure
| Prefix | Module | Auth | Purpose |
/v1/memories | routes/memory.rs | Bearer | CRUD, search, retrieve |
/v1/snapshots, /v1/branches | routes/memory.rs | Bearer | Git-for-Data |
/v1/sessions | routes/sessions.rs | Bearer | Episodic memory, async tasks |
/v1/governance | routes/governance.rs | Bearer | Trigger governance |
/admin/* | routes/admin.rs | Master | Admin ops |
/admin/plugins/* | routes/plugins.rs | Master | Plugin repository |
/health | routes/admin.rs | None | Liveness probe |
/health/instance | routes/memory.rs | None | Readiness probe (returns instance_id) |
Adding a New REST Endpoint
- Add handler in
memoria-api/src/routes/ - Register route in
memoria-api/src/lib.rsbuild_router() - Add e2e test in
memoria-api/tests/api_e2e.rsusingspawn_server()
Plugin System Files
plugin/
├── mod.rs # Re-exports
├── manifest.rs # PluginManifest, PluginPackage, signing verification
├── repository.rs # Publish, review, score, binding rules, audit
├── rhai_runtime.rs # RhaiGovernanceStrategy (sandboxed Rhai)
├── grpc_runtime.rs # GrpcGovernanceStrategy (remote gRPC)
├── governance_hook.rs # Contract testing harness
└── templates/ # Rhai governance templateDistributed Components
| Component | File | Purpose |
DistributedLock trait | distributed.rs | Lock abstraction |
NoopDistributedLock | distributed.rs | Single-instance no-op |
SqlMemoryStore lock impl | distributed.rs | INSERT-based DB lock with TTL |
AsyncTaskStore trait | distributed.rs | Cross-instance task visibility |
GovernanceScheduler | scheduler.rs | Leader election + heartbeat |
AppState | state.rs | Holds instance_id + DB task store |
Testing
make check # cargo check + clippy -D warnings (MUST pass)
make test-unit # Unit tests (no DB): memoria-core, memoria-service, memoria-mcp
make test # All tests (needs MatrixOne, --test-threads=1)
make test-e2e # API e2e tests onlyPatterns:
- E2e:
spawn_server()→ random port, shared DB, reqwest client - Distributed e2e:
spawn_server_with_instance()→ custom instance ID - Plugin:
build_signed_plugin_files()helper for base64 file maps - Unique names:
uuid::Uuid::new_v4().simple()for test isolation - DB tests need
DATABASE_URLenv var
Common Pitfalls
- Adding Config fields → must update ALL test constructors
- Clippy
-D warnings→ any warning = build failure PathBuf::from("x")in comparisons → usePath::new("x")format!()insideprintln!()→ inline args directly- Plugin exports → re-export chain:
repository.rs→plugin/mod.rs→lib.rs - Shared DB in tests → use unique names for isolation
GovernanceSchedulerconstructors →#[allow(clippy::too_many_arguments)]- MatrixOne DATETIME columns → use
chrono::NaiveDateTime, notString
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

