operator dashboard · perpetual core
Backbone memory
for the Perpetual Core ecosystem.
Mnemosyne is the named infrastructure behind Sage, Atlas, and Perpetual Core consulting engagements— plus Lorenzo's personal brain. Not a product. Not for sale separately. This page is internal status, not marketing.
consumers
Who runs on this substrate.
Mnemosyne is named infrastructure deployed per consumer. Same architecture, same code, same operational model — separate instances for separate trust boundaries.
Lorenzo's brain
LDC Brain AI Supabase. Capture surfaces: Claude Code Stop hook, Obsidian launchd watcher, MCP server. This dashboard reports on this instance.
Sage SaaS
Implementation of Sage's MemoryAdapter interface. Deployed on the `sage-saas` Supabase project (separate from LDC Brain AI). Multi-tenant via owner_id RLS scoped to Sage user accounts. Pricing covered by Sage tiers.
Atlas portcos
Per-portco isolated Supabase pattern from the Atlas spec. Each portco install can use Mnemosyne as its memory layer. Architectural option, not committed yet.
Consulting engagements
When the studio builds AI ops for a client, Mnemosyne is the substrate pattern. Each engagement gets a tenant-isolated install. Invoiced as part of the engagement.
architecture
Substrate pattern.
The pattern, not a singleton database. Each consumer gets their own instance with the same shape.
- schema
- mnemo_memories · mnemo_entities · mnemo_memory_entities · mnemo_relationships · mnemo_synthesis_runs
- retrieval
- hybrid: 0.45 vector cosine · 0.30 BM25 · 0.25 recency · 14-day half-life
- embeddings
- OpenAI text-embedding-3-small · 1536 dim · Voyage-3 fallback
- reflection
- GPT-4o-mini hourly via pg_cron · extracts entities · supersedes contradictions
- auth
- bearer token (single-instance) → per-tenant API keys (Sage multi-tenant)
- isolation
- per-consumer Supabase project; owner_id RLS within each instance
- captures
- stop-hook · launchd watcher · MCP server · grammY telegram bot (built)