Experience the
Stash with synthetic data
Explore the Stash with synthetic data. Browse memories, search saved context, follow Rummage processing, and inspect the knowledge graph. This is a product simulation, not a connection to a production Stash.
Four views of
the same Stash
Switch between perspectives to understand how Recall Racoon organizes, searches, governs, and visualizes memory.
Stash Browser
15 memoriesDeployment requires approval from SRE team via #deploy-requests channel. Runbook: wiki/deploy-v2
Staging environment auto-deploys on merge to main. Production requires manual gate.
Database migrations must run before service deploy. Order: migrate → smoke test → deploy.
Rollback procedure: revert commit, trigger pipeline, verify health checks.
Connection pool maxes at 20 by default. Increase via DATABASE_POOL_SIZE. Monitor: dashboard/db-health
Symptom: 503 errors with "no connections available". Cause: unclosed transactions in v2.3.1.
Fix: upgrade to v2.3.2 (connection leak patched). Verify: pgbouncer active.
Previous fix (v2.2.8) addressed different leak in connection factory. Not applicable.
Right to erasure: submit via privacy@company.com. SLA: 30 days. Verification required.
Data retention: customer data 7 years post-contract. Analytics data anonymized after 2 years.
ADR-0047: CQRS chosen for order domain due to conflicting read/write models.
Trade-off: eventual consistency acceptable (max 2s lag). Not acceptable for inventory—stays CRUD.
Previous attempt (ADR-0021): unified model caused N+1 on reporting. Reverted.
JWT tokens must never be logged. Redaction pattern: /[A-Za-z0-9-_]{20,}\.[A-Za-z0-9-_]{20,}/
AWS access keys detected in memory are auto-redacted at ingest. Alert sent to #security.
Synthetic memories
from real scenarios
The demo uses 15 precomputed memories covering deployment runbooks, incident retrospectives, architecture decisions, compliance policies, and secret handling. All data is synthetic—no real customer information.
🚀Deployment & Operations
- • Deploy approval runbook (MEM-001)
- • Staging vs production gates (MEM-002)
- • Migration order policy (MEM-003)
- • Rollback procedure (MEM-004)
🚨Incident & Resolution
- • Connection pool limits (MEM-005)
- • 503 error root cause (MEM-006)
- • Leak fix verification (MEM-007)
- • Historical fix archive (MEM-008)
📋Compliance & Architecture
- • GDPR erasure workflow (MEM-009)
- • Data retention policy (MEM-010)
- • CQRS architecture decision (MEM-011)
- • Consistency trade-offs (MEM-012)
- • Reverted ADR reference (MEM-013)
- • Secret redaction patterns (MEM-014, 015)
How the demo
works
The demo uses a fixed set of synthetic memories and simulated processing events. It illustrates the interface. It does not run production inference, store visitor memories, or access the credential vault.
Stash Browser
- • Browse synthetic memories.
- • Inspect example source context and claim states.
- • Open related information.
Recall Search
- • Search the seeded dataset using text matching.
- • Review illustrative result scores.
- • Open a result in the Stash Browser.
Rummage Log
- • Follow simulated processing events.
- • See examples of governance and review.
- • Inspect the relationship between processing and memory state.
Knowledge Graph
- • Explore the seeded relationships.
- • Select a node to inspect its example memory.
- • View connected information across the demo dataset.
From demo to
your deployment.
The demo shows the workflow. Let's discuss the memory, governance, and infrastructure your agents need.