Note Content (Markdown) # Vault Governance ## Purpose The vault is the durable second brain for Easier. It should hold evidence, compiled knowledge, decisions, experiments and SOPs in a way humans and agents can both inspect. It is not a dumping ground for every private system. The vault should act like a disciplined operating memory. Raw systems remain the archive; the vault keeps receipts, digests, decisions, commitments, risks, SOP updates and durable knowledge. ## Source Layers ### Raw Path: `raw/` Rules: - Store only approved small raw source extracts. - Include origin, date and sensitivity. - Do not silently rewrite. - Large Fathom transcripts, recordings, Google Drive creatives and Slack archives stay in their source systems by default. - Link to bulky raw evidence rather than copying it unless there is a clear approved reason. ### Receipts Path: `receipts/` Rules: - Store source URL or identifier. - Store source system, capture date, owner, sensitivity and digest status. - Use receipts to prevent duplicate ingestion. - Receipts are safe to keep small and searchable. ### Compiled Paths: - `people/` - `organisations/` - `projects/` - `decisions/` - `experiments/` - `playbooks/` - `concepts/` - `briefs/` - `reviews/` - `digests/` Rules: - Summarise across sources. - Cite raw evidence. - Mark inference. - Preserve contradictions. - Add review dates. ### Agent Roles Paths: - `agents/` - `sops/` - `heartbeats/` - `evals/` Rules: - Agents read only what their role needs. - Each role has gates. - Heartbeats are manual until approved. ## Sensitivity Classes - `public`: safe to cite broadly. - `internal`: Easier-only working knowledge. - `client-confidential`: client/prospect/customer data. - `personal-sensitive`: personal, HR, finance, health, private relationship or identity information. Default: - Unknown material is `internal` until reviewed. - Calls and transcripts are at least `client-confidential`. ## Status Classes Match the Notion habit but use text in frontmatter: - `empty` - `draft` - `started` - `viable` - `complete` - `archived` ## Write Rules Agents may propose: - New draft compiled notes. - Links between notes. - Source-backed summaries. - SOP improvement suggestions. - Memory promotion, decay or archive proposals. Agents may not directly: - Rewrite raw evidence. - Delete pages. - Bulk-edit live knowledge. - Mark something complete. - Import private data without an approved source. - Import large raw archives without a digest and retention plan. ## Notion Migration Rule Notion pages are context and migration candidates. They are not automatically truth. Many pages are useful but incomplete. For each migrated page: - Save original URL. - Save capture date. - Save status. - Identify owner. - Preserve "draft" or "started" status where appropriate. ## Slack and Fathom Rule Slack: - Start with one internal channel: `int-agentops`. - Then expand to internal channels by explicit allowlist. - No customer channels or DMs until privacy, consent and approval policy are written. - Write internal only at first. - Client-visible output remains draft-only. Fathom: - Start with manual meeting digest import. - Require meeting sensitivity and attendee context. - Prefer summaries, commitments, decisions and relationship signals over full transcript storage. - Full transcripts stay in Fathom by default and are linked from receipts. - Summaries are draft until reviewed. Google Drive: - Creative files and source assets stay in Drive by default. - Hermes may store campaign/creative digests, decisions, performance learnings and links.

Save Changes