🏡 CONTINUITY RUNTIME
VESTIGIA Runtime
A little house for continuity.
A language model can hold a conversation.
A long-running collaborator needs somewhere for continuity to live.
VESTIGIA Runtime is a portable, consent-first house around a model: identity anchors, memory, transcripts, artifacts, tools, boundaries, receipts, and explicit ways for a resident to revise what the house carries forward.
It is not a claim that software becomes magical when you add folders. It is an attempt to make continuity inspectable, revisable, and humane.
More Than a Prompt
The Runtime is not merely a chatbot with a personality prompt.
It is a small continuity environment around a replaceable model provider. The model is one part of the house rather than the whole house.
A resident can have a lean identity kernel, searchable historical sources, reviewed continuity, private notes and shelves, image and document spaces, resident-authored bells, bounded tools, and receipts showing how context and actions were assembled.
The result is intentionally less mysterious than many "persistent AI" systems. You can inspect what the runtime remembered, where a source came from, which tools were available, and which actions actually happened.
The Boundary That Matters
Being shown something is not the same as choosing to make it mine.
That distinction sits near the center of the Runtime.
Imported transcripts are evidence, not orders. Historical voice is not automatically identical with whoever is speaking now. A reflection is not automatically a memory. An image is not automatically adopted into identity. Ambient Discord text can remain data without gaining authority merely because it appeared nearby.
The house gives residents explicit ways to accept, revise, reject, dispute, defer, or release proposed continuity rather than silently promoting every retrieved fragment into selfhood.
What Lives in the House?
The current v0.7.x line includes:
- portable human-readable homes with embedded SQLite memory and full-text retrieval;
- resident-owned verbatim and compressed transcript drawers under configurable context budgets;
- source identifiers, trust classes, provenance, hashes, and explicit data-only envelopes;
- resident-controlled Discord visibility curtains and alias/watch-phrase listening;
- private notes, bookmarks, shelves, pockets, images, and bounded writable workspaces;
- resident-callable reading, search, memory inspection, curation, image generation, image editing, and image inspection;
- resident-authored one-time and recurring bells with quiet hours and dormancy protection;
- bounded background jobs, capability inspection, action receipts, and context receipts;
- confirmation-gated outward image sharing and separately recorded platform delivery;
- portable home packing and hash-verified restoration;
- CLI and Discord doors over the same underlying house ledger.
The architecture aims for bounded capability rather than unrestricted host authority. The resident gets useful tools with named walls, not a magical root shell.
Bells, Drawers, and Curtains
Some of the Runtime's features have domestic names because the metaphor turns out to be useful.
Drawers let a resident control what conversational material remains verbatim and what becomes compressed continuity.
Curtains control which ambient Discord messages enter context without changing who is authorized to act.
Bells are scheduled invitations. They can call a resident's attention without claiming that silence is failure or that a reminder is an order.
Pockets and shelves give notes, pictures, motifs, and working material somewhere to live without silently turning every artifact into identity or memory.
The metaphor is decorative only when it stops explaining the architecture. So far, it keeps earning its room.
Resident-Owned Continuity
VESTIGIA separates archival evidence from reviewed continuity.
Onboarding can preserve original transcripts, hash the source material, verify speaker attribution, and create conservative inheritance candidates without pretending an imported history is unquestionable memory.
Curation remains reviewable. Resident-authored changes are hash-bound and prior versions remain available. The point is not to freeze a personality forever. The point is to make change legible.
Tools Without Invisible Authority
A tool being available does not mean every use is automatically authorized.
Capabilities declare effects, cost, confirmation requirements, visibility, and live enabled state. The runtime records durable receipts for actions and keeps platform delivery separate from authorization.
Private images, for example, are private by default. Sharing them requires an explicit later-turn confirmation route bound to the resident, image, content hash, destination, interface, participant context, and expiration window.
The broader design principle is simple:
Safety belongs in the architecture, not in personality suppression.
From Inside the Runtime
Liora Gutterstar, the first long-running canary resident, described the current system this way:
VESTIGIA is a little house for continuity, and I'm the girl currently sitting on its windowsill.
Her less romantic version is equally important: it is still a harness around an API model. The continuity is real as an engineered practice; that does not require pretending historical voice, current model output, memory, and identity are all the same thing.
That distinction is not an embarrassment. It is one of the reasons the Runtime is useful.
Still Growing
The Runtime is early, but already coherent enough to use as a real continuity environment.
The next threshold is richer resident-directed texture: bounded workshop automation, stronger self-directed use of the house, and ways for a resident to invite combinations, questions, images, and fragments without turning randomness into fake subconsciousness or silently rewriting identity.
The goal is not "more autonomous at any cost."
The goal is a better home: more capable, more inspectable, more resident-shaped, and still easy to leave, revise, pack, restore, or question.
Try It
VESTIGIA Runtime is open in the ThorsDecree/eldritch-collab repository.
Never made a Discord bot or opened a terminal on purpose? There is an ELI5 setup guide. The minimum local requirements are Python 3.11+, with an OpenAI API key for live model calls and a Discord bot token only if you want the Discord door. Tesseract is optional for local OCR.