INDB – 인식론적 엔진, 서명된 메모리, 영지식 저장

v0.7.0 · PRODUCTION READY · THE ONLY ONE INâDB Not a database. An Epistemological Engine designed to preserve truth in the age of manipulation. Modeled after human memory. Signed memory. Every fact. Every response. Every moment. No one else has this. "When everyone lies, INDB remembers what you saw." CORE PHILOSOPHY Inhale, exhale, axiom, hidden zones â like memory. 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 â Hidden zones 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. Like memories we store but cannot consciously access. 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 BLACK BOX CONTRACT You may hide what is inside. You may not hide that you were here. This is not a policy. It is an architectural law. When a blind_payload event is created, two fields become mandatory at the protocol level â and are enforced before the event reaches the storage layer. Every service that says "we protect your data" holds a key â for themselves, their lawyers, the government that comes with a request. "Protection" is a policy. Policies can be changed. Here the engine has no key. There is nothing to hand over. There is no backdoor because there is no door at all. The content is structurally unreachable â not by permission, but by design. Prevents replay attacks. The moment cannot be fabricated. The fact of presence must be spatially anchored. You may hide the contents â not the presence. the system has exactly one answer: "Something was here. This location. This time." What it was â unknown. Architecturally. That is their work to determine. Not ours. The system is not hiding a crime. It is a witness without access to the content. It confirms presence. Nothing more. 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 Paradox-aware Synthesis Transforms raw events into meaning. Returns competing readings, perception gap, has_unread_essence â paradox as signal. 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. Sherlock Holmes Thinking Infers conclusions from evidence chains. Given facts