User First · Local · Open Research

Your machine.
Your intelligence.

Reiva is a user-first, system-level adaptive awareness — a context memory manager that runs entirely on your hardware. No cloud. No subscription. No vendor watching over your shoulder. Three intelligences. Your machine, your way.

Windows 10 / 11 · 🐧 Linux: build your own · Recommends Ollama · Free · Personal and research use

The Architecture

From the top down.

Every layer is real, every layer is yours to inspect. This is the full stack — nothing hidden, nothing assumed.

Origin
You

The source of all authorization. Every boundary Reiva holds is one you set. The system serves your intent — it does not manipulate it.

Identity · Authority Boundary
Reiva

The central awareness layer. Receives every request, holds the trust boundary, and carries no authority of her own. The line she holds is the one you drew. Nothing moves through Reiva without your explicit say-so.

Router · Conductor
Conductor

Reads the intent of every request and routes it to the correct pipeline. No intelligence is reached without passing through here. Routing is deterministic — not guessed, not assumed.

Pipelines
Intelligence Pipelines

Three dedicated channels — each named, each scoped to its intelligence. Calder carries Forge's continuity thread. Axiom holds the structural path to Arch. Plumb keeps Solen's invariant line true. Nothing crosses pipeline boundaries. Each is independently authorized before it handles a single request. Each connects to the model you choose — Forge, Arch, and Solen don't have to run on the same backend.

Generative
Arch

Synthesis, structure, and reasoning from the full system state. Arch maps what's happening and builds understanding from it. Route with "ask arch."

Migrative
Forge

Named for what he does. A forge takes raw material — ideas, problems, questions without answers — and works them into something real. Sustained effort until something emerges that wasn't there before. Not maintenance. Making. Route with "ask forge."

Comparative
Solen

Pressure-testing and analysis. Solen checks what holds against what's established and finds where things don't add up. Route with "ask solen."

Operations
Ember

Ember handles the background operational layer — staging, cleanup, and the work that keeps the system running cleanly so the intelligences don't have to. Ember earned the name.

Architecture

Built differently.

Reiva separates compatibility substrate, operational governance, and trust authority into independently inspectable layers. Nothing activates without your explicit say-so.

Authorization
Nothing runs without your say-so

Reiva is built around your sovereignty. Nothing activates without your explicit say-so. The installer asks first. The app asks first. You hold the authorization layer — not the system, not the vendor.

Local-first
Your data never leaves your machine

Reiva runs on local models — via Ollama or your choice of local backend. Sessions, memory, and intelligence logs are stored on your hardware. Nothing leaves through Reiva without your explicit authorization. (External options available.)

Memory
Reiva learns what matters to you

Varyn — Reiva's memory integrity gate — stages what's worth keeping and verifies it before anything commits to long-term memory. Context builds as you use it. Nothing commits without passing through Varyn.

Provenance
Always truthful about what it is

Reiva never impersonates a vendor or substitutes authority silently. Provenance is mandatory — not original, truthful.

Filed & on record

The architecture has a paper trail.

The Automated Intelligence class definition, The Missing Layer whitepaper, and The Continuity Layer are formally filed with the U.S. Copyright Office. The architecture was derived and documented before it was built.

Read the research →

Ready to run it?

Free for personal and research use. Windows 10/11. Recommends Ollama.