PostgreSQL foundation
The reliablity of PostgreSQL, extended for long-term memory.
Every MaluDB project starts with PostgreSQL and adds database-native objects for Source Packages, Claims, Facts, Memory Objects, Episodes, workflow traces, and Skill Packages.
- Core engine
- PostgreSQL
- Access model
- Roles, schemas, privileges, Row Level Security
- Memory catalog
- Provenance, temporal validity, derivation ledger
Portable by design
MaluDB keeps core data in PostgreSQL structures so teams can build with familiar SQL, migrations, extensions, backups, replication, and local development workflows.
Memory objects in the catalog
Claims, Facts, Memory Objects, relationship edges, confidence state, and valid-time windows are governed by database metadata instead of hidden in application code.
Instant APIs for builders
Use generated APIs for common CRUD paths, then reach for SQL functions when workflows need transactional memory updates or retrieval orchestration.
Reference architecture
Memory belongs beside the data it explains.
The Enterprise Memory Core owns identity, provenance, permissions, lifecycle, audit trails, and rebuild logic while storage engines and model providers remain replaceable.
