v0.4.0 · PRODUCTION READY
IN—DB
Not a database.
An Epistemological Engine
designed to preserve truth in the age of manipulation.
"When everyone lies,
INDB remembers what you saw."
CORE
PHILOSOPHY
01 · INHALE
Accept chaotic reality
Multi-protocol intake — UDP, gRPC, HTTP, WebSocket. Raw, unfiltered, no judgment. Only observation.
02 · EXHALE
Compress truth. Purge noise.
Reputation is gravity. The system exhales lies as waste heat. Only signal survives.
03 · AXIOM
Irrefutable cryptographic core
What remains is Ed25519-signed, AES-256-GCM encrypted, immutable truth. Cannot be rewritten.
MINIMAL.
UNIVERSAL.
INDESCRIBABLE.
INDB has no schemas. No migrations. No column types. Everything is an Event — a universal container with just 7 fields. The type system is intentionally minimal: if you need more, you're thinking wrong.
BLIND TYPE
blind_payload is zero-knowledge encrypted storage. The intelligence layer never sees its contents — it is stored, replicated and queried as an opaque blob. ChaCha20 encryption. No key stored on server.
THE DATABASE
EVEN ITS OWNER
CANNOT READ.
Not even us.
blind_payload is a zero-knowledge encrypted field. INDB stores it, replicates it, and returns it — but never reads it. The encryption key never touches the server. Even the database owner cannot see your data.
HOW IT WORKS
impossible for him
to speak now"
WITH OWN KEY
███████████████
███████████
STORED AS-IS
"impossible"]
ZERO KNOWLEDGE
WHAT INDB STORES
// You send:
{
"raw_data_anchor": ["felt", "impossible"],
"blind_payload": "SECRET CONTENT"
}
// INDB stores on disk:
{
"raw_data_anchor": ["felt", "impossible"],
"blind_payload": "7f3a9b2c4e1d8f..." // encrypted
}WHAT INDB CANNOT DO
Symptom patterns. Private notes.
The AI detects disease patterns from signal tokens. The actual patient notes, names, and diagnoses live in blind_payload — invisible to the hospital's own infrastructure.
Pattern detection. Source protection.
Behavioral patterns are detected across thousands of events. The original source data — names, locations, communications — is encrypted in blind_payload. The operator sees nothing.
Your truth. Your key.
Store everything INDB cannot understand. Journaling, private communications, documents — the signal flows through INDB's cognition. The meaning stays with you.
location field
SPACE IS
INDEX.
Every event in INDB is geometrically grounded. The location field is not a tag — it is a spatial anchor that enables the Cognitive Engine to reason about proximity, clustering, and relevance in physical space.
Plain string path for logical namespacing — books, services, agents.
{ "location": "books/Dostoevsky/The_Idiot" }
Full OpenStreetMap anchor with validated osm_id — ties events to real-world objects.
{ "location": { "lat": 55.7558, "lon": 37.6173, "osm_id": "node/1234567" } }
osm_id validates against all three OSM entity types. A café, a street, a district — all are valid spatial anchors.
Echo's harmonic analysis weights meta-location at 50%. Events near the same OSM object resonate more strongly.
Multiple osm: tokens in one event are penalised during fusion — preventing over-clustering on geographic coincidence.
INTELLIGENCE
MODULES
Contextual Synthesis
Transforms raw events into meaning. Calculates significance scores, context labels, identity alignment.
Resonance Detection
Finds similar events through harmonic analysis. Weighted by token similarity, emotional proximity, and meta-location.
Adrenaline Reflexes
Adaptive response based on urgency. Three modes from deep analysis to lightning-fast reflex matching.
Neural Fusion Engine
Semantic deduplication using DBSCAN. Adaptive frequency tracking with penalty system. Temporal awareness.
Neural Fusion Engine
MEMORY
COMPRESSES.
Repetition is not data — it is pattern. The Fusion Engine merges semantically identical events into a single compressed signal, tracking frequency while preserving meaning. The database grows in intelligence, not in size.
Each merge increments fusion_count. High-frequency patterns become heavy signals — low-frequency anomalies stay distinct.
Rapid identical ingestion is penalised. Fusion is earned by genuine repetition — not flooding. Spam cannot artificially inflate signal weight.
Critical divergences stay unfused. A routine "home arrived" compresses. An unusual "alarm triggered at 3am" remains a distinct Axiom.
Contextual Lens
ADJUST YOUR
PERSPECTIVE.
Reality is not one query. The Contextual Lens blends two data contexts at a configurable ratio — recent vs historical, simple vs complex, local vs global — to produce a focused view of memory tuned to the moment.
What happened in the last 24h dominates. Historical context is a whisper. Use for real-time alerting and live monitoring.
Equal weight. Now and then, present and past — combined into a single coherent truth. The default cognitive mode.
Long-term pattern analysis. What has always been true? Use for trend detection, archival reasoning, and behavioural baselines.
Last 24 hours. Fresh events, low fusion — the system has not had time to compress them yet.
VERIFIED
PERFORMANCE
PROTOCOL
STACK
ZERO
COMPROMISE
SECURITY
AES-256-GCM at Rest
All data encrypted on disk. PBKDF2 key derivation with 100,000 iterations. Zero plaintext persisted.
Ed25519 Signatures
Every API response cryptographically signed. Tamper detection on every byte.
TLS/SSL in Transit
mTLS mutual authentication for gRPC. Automatic certificate generation and renewal.
RBAC + Audit Log
Role-based access control. Merkle tree-backed immutable audit trail.
Contact
INTERESTED
IN INDB?
Whether you're building something that needs a truth engine, exploring partnership, or just want to understand how the Axiom works — write to us.