The system does not understand. It contains only the structure of the signals it has processed.
Why Kremis
| Problem | How Kremis addresses it |
|---|---|
| Hallucination | No fabricated data. Every result traces back to real ingested signals. Explicit “not found” for missing data. |
| Opacity | Fully inspectable state. No hidden layers, no black box. Every result traces back to a graph path. |
| Lack of grounding | Zero pre-loaded knowledge. All structure emerges from real signals, not assumptions. |
| Non-determinism | Same input, same output. No randomness, no floating-point arithmetic in core. |
| Data loss | ACID transactions via redb embedded database. Crash-safe by design. |
Architecture Overview
| Component | Description |
|---|---|
| kremis-core | Deterministic graph engine (pure Rust, no async) |
| apps/kremis | HTTP server + CLI (tokio, axum, clap) |
| apps/kremis-mcp | MCP server bridge for AI assistants (rmcp, stdio) |
Quick Start
Get running in 2 minutes
API Reference
REST API endpoints
CLI Reference
Command-line interface