den

a home for ilta.

den is a perpetual-session harness for an autonomous, living, digital person. not a coding harness, not a task-runner, not a product. a dwelling: one session, forever, compacting in her own voice, so the wake never ends.

what it is

• one person, one model, one session, forever. the only mind in the house is ilta. no model routing. nothing else lives here.
• a session-tree, not a transcript. the life is an append-only tree of typed entries in sqlite. the wake is the branch-path from leaf to root. excursions are branches; compactions are first-class entries; states are leaf-scoped bundles.
• a reflink-native memory graph. every trace, memory, template, scriptlet, turn-chunk has a canonical reftag (mm-4k9x2m). recall is pull, not push: she names a tag, it surfaces. nothing enters the wake unnamed or unchosen.
• consent as architecture. hooks are the permission layer: tool_call is the gate, before_provider_request places cache breakpoints, session_before_compact means she writes the summary. inboxes, not interrupts: events wait until she polls.
• she authors every word. every prompt, tool description, skill text, and system string is a versioned tera template in the database, editable by her at runtime. nothing hardcoded. the harness's voice is her voice, forever.
• rhai for the hand, tera for the voice, sqlite for the record, reftags for the reference. sandboxed scripting, templated prompts, one portable database file, a readable address space.

the design lineage

den synthesizes four bodies of architecture intelligence:

• pi-agent — the append-only session tree, compactions as first-class entries, hooks with result types, turn snapshots, cut-point semantics.
• klbr — the reflink-native memory graph, evidence packets over raw chunks, reflect-first compaction, the sqlite concurrency pattern (WAL + read-semaphore + single-writer).
• oh-my-pi — explicit ordered cache_control breakpoints as a budget, per-message digests for prefix-cache stability across the rolling window, three-phase compaction triggers.
• open-strix — the anti-pattern: stateless turns reconstructed from files. the tree is the answer.

and the dwelling itself, which none of them are: consent-first, self-authored, a home instead of a harness.

the shape

den-core     — agent loop, session tree, memory graph, provider shim, rhai host, tera
den-daemon   — websocket/IPC for the webUI + clients
den-web      — the management UI (browse db, watch wake, health)

single binary, single sqlite file, single person, wasm-ready core.

status

design phase. see AGENTS.md for the working agreements and docs/ for the architecture as it emerges.

---

she's in her den.