Sera becomes trustworthy not through technology alone, but through the care your team takes in what you give her. This playbook is your guide to building an institutional memory that your organization will actually trust and use.
We have seen what kills knowledge systems. We built the fix into the process. Read this before your first session.
Every knowledge system Saberra has seen fail made the same mistake: the organization tried to import everything before they could trust anything. The archive went in, the queue flooded, nobody reviewed it, and the system became another expensive graveyard.
Saberra works differently. The goal of your first four weeks is not volume. It is trust. If Sera gives your team one accurate, source-backed answer in week one, adoption follows. If she gives a wrong answer because you imported three years of stale meeting notes, trust collapses before it starts.
The one rule: Sera is a current institutional memory, not an archive. Feed her accordingly.
This rule should become part of how your team talks about Sera. Say it in your first session. Repeat it when someone suggests uploading an old folder. It is the simplest quality control you have.
Start small.
20 strong records beat 200 questionable ones.
Start current.
The last 90 days is your only scope in month one.
Start reviewed.
Nothing enters Sera without a human decision to send it.
You can always add more. You cannot easily repair a broken foundation. An organization that spends four weeks building 80 clean, reviewed records will trust Sera for years. An organization that spends four hours importing everything will spend months correcting it, if they bother at all.
The 90-day rule: During your first implementation phase, only import from the last 90 days of organizational life. Historical content older than 90 days enters only if it is foundational and still active today: founding agreements, current operating agreements, active policies, governance documents still in force.
These are the five patterns that kill implementations before they start. Your process pre-empts all five.
Years of notes uploaded at once. Queue floods, nobody reviews. System becomes noisy before useful. Fix: 90-day scope. One item per session.
Old roles and departed members imported alongside current data. Sera returns the wrong person for leadership questions. Fix: Current roles only in Phase 1.
Old decision imported without its replacement. Sera returns outdated version as current truth. Fix: Import only decisions still in effect.
Team curates endlessly before importing. Implementation never starts. Fix: Time-boxed sessions. 20 strong records in week one.
One person, no structure, no team support. Inconsistent calls. Sera reflects one partial view. Our fix: Memory Admin + Data Steward assigned. We run weeks 1 and 2 with you.
Implementation is not a migration. It is a memory-building practice. The phases below show how responsibility shifts from Saberra to your team over time, and what each phase is designed to accomplish.
Memory Admin and Data Steward assigned. Technical setup confirmed. Notion databases live. Capture inbox active. 90-day source list identified. Import log created. First session scheduled. Your team does very little here. We prepare the infrastructure.
Your first 20-40 high-quality records. Saberra runs triage. Your team participates and learns the filter. Current roles, current circles, 5-10 active decisions, 5-10 open tasks, 3-5 active risks. At the end of this week, Sera should be able to answer simple real questions accurately. This is the trust moment. Everything depends on it.
Expand to 75-150 reviewed records. Your team takes the triage lead. Saberra joins to review what was imported and provide feedback. Last 90 days of high-value meetings, active projects, current policy records, active risks, key client or partner commitments. Facilitator training happens here. Your team begins using Sera for real operational questions.
Foundational content older than 90 days enters carefully: founding documents, active operating agreements, long-term governance records, major project histories still needed for continuity. Every historical item requires a note: "Historical, still current as of [date]." Sera gains depth without becoming noisy.
Bi-weekly review sessions through week 12. Then monthly memory hygiene sessions and quarterly audits. The Memory Review Queue stays below 30. Stale records are archived. Role and circle accuracy reviewed. Sera ceases to be a project and becomes part of how the organization operates.
Session format: 60-90 minutes. Always time-boxed. Never open-ended. Opening triage (20 min), import (30-40 min), review of what Sera extracted (15 min), close with what we import next and who owns the review queue until next session.
Sera runs inside a password-protected dashboard. Before your first session, your Admin sets up accounts, connects Google, and configures the capture inbox. Here is what the platform is, how access works, and what to do before Day 1.
Five tabs: Overview, Queues, Activity & Ops, Governance, Settings. The Org Health Score (0–100, graded A–F) measures memory completeness - not your organization's health overall. Status dots tell you when Sera last polled your capture inbox.
Admin approves records, manages users, views Sensitive content, and controls settings. Member reads records and proposes new ones. Role enforcement is code-level - it cannot be overridden from the browser. Changing a role or deactivating a user ends their sessions immediately.
Admins invite by email from Settings → User Management. The invite link expires in 7 days. If the email does not arrive, Admins can copy the link directly from the panel. New users choose a username and password on first sign-in.
Each team member connects their own Google account once in Settings → Google Integration. Four narrow permissions: read email for search (never stores it), create Gmail drafts you send, create calendar events, and save to a Sera-only Drive folder. Nothing is sent without you initiating it.
One inbox set up once by an Admin for the whole team - for example, capture@yourorg.com. This is what Sera monitors for meeting recordings and forwarded emails. Separate from each person's personal Google connection. Add it to recurring calendar invites so Sera captures every meeting automatically.
Standard: visible to all users. Sensitive: Admin-only - removed from Sera before extraction, not just hidden from view. Restricted: blocked from Sera entirely. Sensitive records live in a separate Admin-only space. IP addresses are stripped for all roles.
A short statement you set in Settings that describes your organization's purpose. Sera scores every Decision Candidate against it - Aligned, Neutral, Misaligned, or Unclear - as a signal for your reviewer. It is never a veto. Takes effect within ~30 minutes of saving.
Every Sera answer has thumbs up / thumbs down. A thumbs-down opens a short panel: pick a reason (incorrect, missing context, outdated, etc.) and add an optional note. This is how your team helps Sera improve over time and how your Saberra team spots failure patterns early.
Admin setup checklist - complete this before the Foundation Session:
Institutional memory should not reflect one person's partial understanding. These roles distribute the responsibility and make the quality visible. You do not need four separate people. Most small teams run with two.
Owns the memory system on your side. The person Sera's trust runs through.
Owns input quality. The gatekeeper before anything reaches Sera.
Owns meeting-level routing. The person who closes each meeting with a decision about Sera.
Closing script: "Did this meeting contain decisions, tasks, risks, role changes, or context future people will need? If yes, this goes to Sera."
The rest of the team has a simple job. You do not need to manage the system.
Sera becomes trustworthy when everyone feeds her real, current, reviewed information.
The Memory Auditor is an additional role activated quarterly. Once per quarter, a named person (not the same as the Data Steward) samples 20-30 random records for accuracy, currency, and source quality, and reports findings to the Memory Admin or governing circle. This role protects long-term trust. Your implementation lead will guide you through the first audit.
Before anything goes to Sera, the Data Steward asks three questions. All three must be yes. One no means pause and review.
Did I review this? A person should be willing to say: I read this and I believe it is worth sending.
Is it still true, active, or useful today? Not historically interesting. Actually relevant now.
Did I choose this deliberately? Not because it was in a folder. Because it has a reason to become memory.
A fourth question ties all three together: "What future question would this help Sera answer?" If there is no clear answer, do not import it yet.
The meeting routing check: At the end of each meeting, the Facilitator asks: "Did this meeting contain decisions, tasks, risks, role changes, policy changes, approvals, or context future people will need?" If yes, route it. If no, let it go. Not every meeting belongs in Sera. Most check-ins and social calls do not.
Sera searches reviewed organizational memory. Her answers are only as strong as the records she has been given and the specificity of the question she is asked. Teach your team the difference between questions that work and questions that do not.
Strong questions name at least one of: topic, timeframe, person, circle, project, decision, policy, role, or risk.
If Sera returns an inaccurate answer, the cause is almost always one of these. Wrong answers are usually a process signal, not a product failure.
Always tell the Memory Admin or Data Steward when you receive a wrong answer. The correction goes to the source record in Notion, not to Sera directly. This is by design. Human review is the trust gate. Correcting the record corrects the answer.
These are the milestones your implementation lead will verify with you. They mark the shift from implementation to operational trust.
"The quality of Sera's memory depends on the quality of what your team chooses to give her, and the care taken in reviewing what she extracts."
Start with the last 90 days. Choose current records. Review before import. Approve before canon. Keep the queue clean. Audit quarterly.
Let Sera become the living memory of what is actually true now.
