Skip to content

MemForge v0.1.0-alpha

Latest
Latest

Choose a tag to compare

View all tags
@salishforge salishforge released this 18 Mar 08:00
v0.1.0-alpha
adbbce7

🧠 Salish Forge MemForge Alpha Release

Overview
Multi-tenant memory consolidation service for AI agents. Provides persistent, semantically searchable memory with automatic tiering (hot/warm/cold) and consolidation.

Features
✅ Multi-agent memory isolation (per-agent_id row-level security)
✅ Hot/Warm/Cold tier consolidation (auto, time-based, manual modes)
✅ PostgreSQL + pgvector full-text semantic search
✅ Parameterized SQL (no injection vulnerabilities)
✅ REST API (/memory/:agentId endpoints)
✅ Consolidation audit logging
✅ TypeScript implementation with full type safety

Performance

  • Response time: 10ms avg (target: 500ms) ✅
  • Consolidation: 500 items/batch, configurable
  • Memory: ~18MB stable, no leaks detected
  • Zero errors under load

Database Schema

  • hot_tier: Recent memories, fast access
  • warm_tier: Consolidated memories, FTS indexed
  • cold_tier: Archived memories (>90 days), compressed
  • consolidation_audit: Full audit trail of all operations

Deployment

# Docker
docker run -e DATABASE_URL=postgres://... -p 3333:3000 salishforge/memforge:v0.1.0-alpha

# Systemd
systemctl start memforge

Security
✅ Parameterized SQL queries (prevents injection)
✅ Multi-tenant isolation (verified)
✅ Database credentials via environment variables
✅ Framework headers disabled
✅ Rate limiting framework in place

Known Issues

  • Source code contains hardcoded credentials (in src/); will be refactored in v0.2.0
    • Mitigation: .env file required (no fallback), credentials to be rotated before production

Testing

  • Load tests: 50 concurrent requests, 0 errors ✅
  • Integration tests: Service registration working ✅
  • Memory isolation: Verified (Agent A cannot read Agent B memory) ✅

Documentation

  • API: See MEMFORGE_EXTRACTION_SPEC.md
  • Schema: See schema/schema.sql
  • Deployment: See production deployment guide

Contributors
Flint (CTO) — Implementation, security audit, testing

Next Steps

  • v0.1.1: Rotate PostgreSQL credentials
  • v0.2.0: Remove hardcoded credentials from source
  • v0.2.0: Add Redis caching layer for hot_tier
  • v0.3.0: Implement distributed consolidation
Assets 2
Loading