Brain

README

2 min read

🧠 Company Brain

The single source of truth for LettuceAI / bhakta.us. Plain Markdown. Git-backed. Human and AI readable.

Who reads this

ReaderAccess
Pat (Managing President)Full access — reads and writes everything
J.A.R.V.I.S. (CEO / Hermes)Read-write on 00-07, read-only on 10-11
Paperclip AgentsRead-only on 00-07, no access to 10-11
External toolsNo access

Folder structure

00-inbox/        → Quick capture. Triage to proper folder.
01-projects/     → Active project knowledge (Huible, InvestInMe, etc.)
02-decisions/    → Architecture Decision Records (ADRs)
03-lessons/      → What went wrong and what we learned
04-operations/   → How things run: infra, credentials, runbooks
05-people/       → Contacts, roles, relationships
06-meetings/     → Meeting notes, voice memo summaries
07-reference/    → External research, competitive analysis
10-private/      → Pat's private notes (agents: NO ACCESS)
11-journal/      → Pat's daily journal (agents: READ ONLY)
Templates/       → Note templates

How to use

  1. Write knowledge here, not in chat. If it matters, it goes in the vault.
  2. Link notes with [[wikilinks]] to build the knowledge graph.
  3. Commit after changes. git add -A && git commit -m "description"
  4. Pull before reading if synced from another device.
  5. Never store secrets in the vault. Use .env files outside the vault.

Rules for J.A.R.V.I.S.

  1. Before answering questions about projects, check the vault first.
  2. When you learn something important, write it to the vault, not just memory.
  3. When Pat corrects you, record it in 03-lessons/.
  4. Before reporting something as “done,” verify against the vault.
  5. Never write to 10-private/ or 11-journal/.

Rules for Paperclip agents

  1. The vault is your read-only reference for project context.
  2. Do not modify vault files directly — write code to repos.
  3. When you complete work, J.A.R.V.I.S. will update the vault.

Created: 2026-08-03 by J.A.R.V.I.S.

Graph View