Recordari by Role
How different people use Recordari — same tools, different habits.
Recordari is one product, but people use it differently. A developer files decisions while shipping code. An architect records constraints and rejected options that outlive a sprint. A manager orients for status and treats the agent as a personal assistant.
These guides describe job roles — how you work day to day. They are not the same as workspace permissions (Owner, Editor, Reader on a shared team), which govern who can change someone else's memories. See When memories disagree for that.
On a shared team workspace, every member can read every memory — a personal key controls ownership, not visibility. Managers with HR-sensitive notes should read What the team can see in the engineering manager guide before filing 1:1 material.
Every guide assumes you connect with a personal key for your own sessions, so what you file is attributed to you.
Pick your role
| Role | What Recordari is for | Guide |
|---|---|---|
| Architect | Durable decisions, rejected options, cross-domain constraints | As an architect |
| Developer | Project domain, file while coding, connect implementation choices | As a developer |
| Tech lead | Team domain hygiene, contradictions, turning findings into decisions | As a tech lead |
| Engineering manager | Personal assistant pattern, orient for status, light filing | As an engineering manager |
| Product owner | Goals, issues, findings vs decisions, open threads | As a product owner |
Start with the architect guide if you care about choices that need to survive beyond the current sprint. Start with As a developer or Using Recordari with Claude Code if you are shipping code today.
What every role has in common
Orient at session start. Your agent loads recent context, standing rules, and significant decisions from the domain you're working in. You don't need to re-explain the project every time.
Domains partition work. Use a domain per product or initiative — for example payments-platform or identity-redesign. Your agent can alias short names if you use them often.
Your agent does the mechanics. You speak in plain language; the agent chooses remember, revise, connect, and the right memory type. You answer when it surfaces a contradiction or asks for a decision.
Standing rules (coming soon). Per-role setup templates — durable rules your agent should follow in every session — are planned but not shipped yet. When they land, each role guide will link to the relevant templates. Until then, file important constraints as standing memories yourself (see the architect guide).
More guides
- As an architect — constraints, options, and cross-domain design memory
- As a developer — file while coding, one domain per project
- As a tech lead — graph hygiene, contradictions, findings → decisions
- As an engineering manager — personal assistant, 1:1 prep, light filing
- As a product owner — goals, issues, and product decisions
- Using Recordari with Claude Code — a full developer session walkthrough
- Getting Started — connect your agent in five minutes
- MCP Tools Reference — what you can ask your agent to do