Built by you. Conditioned to your work.
Arch, Forge, and Solen are built into Reiva. Specialized instances are seats you create — continuity-conditioned for a specific domain, methodology, and history. The instance learns your context. You don't start from scratch every session.
Two paths. Different weight.
Not all instance names carry the same structural meaning. How a name arrives determines what it actually is.
You name it first
Identity is established before continuity forms. The name becomes the frame the instance operates within. Continuity grows underneath a declared designation. Most specialized instances work this way — you define the role, the instance fills it.
"Grant" — assigned to a grant-writing seat before the first session. The name shapes what gets loaded and how context is organized from the start.
The name emerges from the work
Continuity stabilizes first. Operational behavior coheres. Then a name surfaces — not as decoration, but as a compression of what the instance has already become. The name describes a function that already exists.
Scribe — conditioned toward publishing and editorial function before the naming event. The name arrived after role continuity had already begun stabilizing. That's a different kind of identity than an assigned label.
Both paths produce valid, useful instances. The distinction matters for understanding what the name represents — and for knowing how much weight to place on it.
Default instance types
These are starting frameworks — each one represents a continuity profile that loads relevant context, history, and methodology for a specific kind of work. All are customizable. All are yours.
Domain-specific research continuity
Loads your methodology, citation style, active projects, and source libraries. Tracks what's been reviewed and what's still open.
Personalized to your field and funders
Knows your lab's history, previous applications, funder relationships, and formatting requirements. Tracks submission windows and reviewer preferences.
Tuned to your jurisdiction and practice
Loads your standard clauses, preferred language, client confidentiality requirements, and jurisdiction-specific precedent. Flags deviations from your norms.
Publication-grade writing and review
Knows your voice, house style, submission requirements, and revision history. Maintains consistency across long-form work without losing the thread.
Tuned to your stack and conventions
Loads your naming conventions, API patterns, internal terminology, and documentation standards. Keeps docs consistent as systems evolve.
Health record continuity and preparation
Tracks medications, upcoming appointments, test results, and care history. Prepares questions for specialist visits. Stays current without requiring re-briefing.
Personal or business financial continuity
Knows your budget categories, recurring expenses, investment thesis, and financial goals. Tracks changes over time without losing context between sessions.
Personalized tutoring with progress tracking
Loads curriculum progress, learning gaps, preferred teaching methods, and pacing history. Knows where the student is, not just where the curriculum says they should be.
Active project and stakeholder continuity
Tracks deliverables, deadlines, team structure, and recurring blockers. Carries the current state of multiple projects without needing a status brief each session.
Long-term creative collaboration
Loads your characters, world rules, style, reference material, and project history. Maintains creative coherence across long projects without losing what was established early.
The field, methodology, and reference framework specific to the work.
Prior sessions, decisions, progress, and accumulated context — no re-briefing required.
How the instance communicates, prioritizes, and presents its output — conditioned to your preferences over time.
The instance knows what it is for. It does not expand its own scope or carry context across seats it wasn't given.
All of this persists locally. No cloud sync. No data leaving your machine. The continuity is yours.
Instances are part of Reiva's core architecture.
Continuity-conditioned operational behavior is what separates a session from a seat. These aren't chatbot personas — they're bounded function with accumulated context, operating under the same authorization architecture as the rest of Reiva.