Analyst
Evidence gathering
- Memory
- Sources, prior findings
- Scope
- Read-only research tools
Operators
An operator is a reusable template with a role, isolated persistent memory, explicit permissions, review requirements, and a budget. Operators are designed to cover distinct business functions — research, product, delivery, operations — and to coordinate as a company would. You configure the few your workflow needs; not every role is generally available yet.
Evidence gathering
Independent review
Governed action
Anatomy
What the operator is responsible for, and the boundary it may not cross.
Its own durable memory, separate from other operators and from shared org memory.
Tools, data, and actions granted explicitly — read-only by default.
What must be independently verified before it counts as done.
A spend ceiling per task and per workflow, enforced rather than advised.
Who is notified, and under what conditions, when the operator is blocked.
Collaboration
Operators work with each other inside Noria, where the interaction can be observed, constrained, and replayed. The direction: a small human team directs the work, and operators carry the coordination between functions.
An operator can ask another for an input it is not permitted to produce itself.
Handoffs carry context, constraints, and the reason for the transfer.
Decisions and their rationale persist beyond the session that produced them.
Findings become project or organization memory only through a governed step.
Setup
Standing up forty roles produces noise and cost. Noria's guided setup starts from one workflow and adds operators only where the work demands one.