Operational Roles

Your work defines the role.
The role shapes around it.

You're not configuring it. You're shaping it.

There's a difference between an AI tool you set up once and a collaborator that accumulates context over time. Operational roles are the second thing. What you bring to it, it carries forward. What you correct, it holds. What matters in your domain becomes part of how the role operates — not because it was programmed that way, but because you worked with it.

Your domain, not a generic profile

It loads your methodology, your vocabulary, your reference framework. A role shaped around your jurisdiction and clause preferences — not generic legal concepts.

Your history, carried forward

Prior sessions, decisions, progress — no re-briefing required. It knows where you left off because it was there when you left off.

Yours over time, not out of the box

It stabilizes through work. The more you shape it, the more precisely it fits the role. That's not configuration — that's continuity.

When you name it matters

Two ways a name arrives.

Most people name their instance before the first session. The name becomes the frame — and the role grows into it. That's the most common path, and it works well. You define the role; it fills it.

Sometimes the name comes later, after continuity has already started forming on its own. Operational behavior coheres first. Then a name surfaces — not as a label, but as a compression of what the role has already become through work. That's a rarer path.

Either way, the name is yours to give. What matters is what you build into the role before and after you give it.

Examples of how roles can be personalized.

These aren't products to select — they're starting points. The role you build is your own. What it knows, how it works, what it carries: that comes from you and the work you do together.

Research

A role shaped around your domain, your methodology, your active projects. It knows what you've reviewed and what's still open — without being briefed each session.

A marine biologist's instance knows her active research sites, papers under review, and grant cycles. She doesn't re-introduce herself every session.
Grant Writing

Shaped around your field, your funders, your lab's history. Knows your prior applications, your scores, your reviewer feedback — and carries it into the next cycle.

An NIH-focused role tracks program officer cycles, formats to specific FOA requirements, and remembers what worked and what didn't last submission.
Legal Review

Shaped around your jurisdiction, your practice area, your firm's standard language. Flags deviations from your norms rather than generic best practice.

A small firm's role knows which clauses have been contested before, how they've resolved it, and what non-standard language looks like in their context.
Editorial

Shaped around your voice, your house style, your submission requirements. Maintains consistency across long-form work without losing what was established early.

Scribe — knows the paper in progress, the venue's style guide, and how the argument has evolved across drafts.
Technical Documentation

Shaped around your stack, your naming conventions, your internal terminology. Keeps documentation coherent as systems evolve without requiring a full re-brief.

A dev team's role knows which endpoints are deprecated, how they write error handling descriptions, and what the naming conventions actually mean in practice.
Medical Companion

Shaped around your health history, your care team, your appointment cadence. Tracks what's changed between visits and prepares you before you walk in.

Before a cardiology follow-up, it surfaces the last echo results, flags the medication change since the previous visit, and drafts questions based on the interval.
Financial Review

Shaped around your budget categories, your financial goals, your recurring patterns. Carries the context that makes one-off decisions make sense without re-explaining your situation.

A freelancer's role tracks quarterly income patterns, flags irregular expense categories, and holds the tax year context between sessions.
Education

Shaped around a student's progress, gaps, and learning style — not where the curriculum says they should be. Knows what's been mastered and what needs reinforcement.

A homeschooling role tracks which concepts landed, which need another approach, and adjusts explanation style based on what's actually worked.
Project Coordination

Shaped around your active projects, your team structure, your recurring blockers. Carries current state so you don't need a status brief before every session.

A producer's role knows which deliverables are blocked, which stakeholders need updates, and what the outstanding decisions are — before the morning call.
Creative Partner

Shaped around your characters, your world rules, your style, your project history. Maintains creative coherence across long work without losing what was established at the start.

A novelist's role knows the character roster, the established world rules, and which plot threads are unresolved — session after session, draft after draft.
What you put into it, it carries forward.
Your domain

The field, methodology, and reference framework you bring. Not a generic profile — yours.

Your history

Prior sessions, decisions, progress. No re-briefing. It was there when it happened.

Your way of working

How you communicate, what you prioritize, what precision looks like in your context. Conditioned over time, not configured at setup.

Its own boundaries

It knows what it's for. It doesn't expand its own scope or bleed into roles it wasn't given. Bounded function is part of what makes it trustworthy.

All of this stays on your machine. No cloud sync. No data leaving. The continuity is yours — structurally, not as a policy.

The architecture that makes this possible is filed.

Stable operational roles aren't a product feature — they're what happens when authorization topology, identity continuity, and bounded function are built into the substrate from the start. Reiva can stabilize a role across time because the architecture was designed to hold one.

Names & Trust → Identity Continuity → Class Definition → Why Prompt Injection Fails →