init: Engram v0.1 — native memory substrate for accumulating intelligence
Memory is not stored and retrieved — it is activated and propagated. Implements the spreading activation model with salience decay, typed edges, four memory tiers, and flat cosine vector search over a sled embedded store.
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
# TypeScript Bindings (planned v0.2)
|
||||
|
||||
Two paths for TypeScript/Node.js:
|
||||
|
||||
## Option A — WASM (browser + Node)
|
||||
|
||||
```
|
||||
cargo build --target wasm32-unknown-unknown --release -p engram-core
|
||||
wasm-bindgen target/wasm32-unknown-unknown/release/engram_core.wasm --out-dir pkg/
|
||||
```
|
||||
|
||||
Requires `wasm-bindgen` annotations on public API. Browser-compatible, no native deps.
|
||||
|
||||
## Option B — Node native addon (server-side)
|
||||
|
||||
Use `napi-rs` to generate a Node.js native addon from `engram-core`. Faster than WASM for
|
||||
server-side agents, but requires a native build step per platform.
|
||||
|
||||
## Status
|
||||
|
||||
Stub only. WASM target is the preferred path for v0.2 given the local-first, embedded philosophy.
|
||||
Reference in New Issue
Block a user