πŸ”— How The Company Talks: System Integration

Last updated: 2026-08-03

The Three Systems

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                 PAT (Human)                  β”‚
β”‚            WhatsApp ←→ Voice                 β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                   β”‚
         β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
         β”‚  J.A.R.V.I.S.      β”‚
         β”‚  (Hermes CEO)      β”‚
         β”‚  glm-5.2 @ z.ai    β”‚
         β””β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”˜
              β”‚        β”‚
    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”  β”Œβ”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
    β”‚  VAULT     β”‚  β”‚  PAPERCLIP      β”‚
    β”‚  Obsidian  β”‚  β”‚  Agent Kanban   β”‚
    β”‚  Git-backedβ”‚  β”‚  Port 3100      β”‚
    β”‚            │◄──                 β”‚
    β”‚  /root/    β”‚  β”‚  Agents read    β”‚
    β”‚  repos/    β”‚  β”‚  vault for      β”‚
    β”‚  brain/    β”‚  β”‚  context        β”‚
    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β””β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                         β”‚
              β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
              β”‚  GITHUB (LettuceAI)  β”‚
              β”‚  Code repos w/       β”‚
              β”‚  remote backups      β”‚
              β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Data Flow

Knowledge (What we know)

  • Source of truth: Obsidian vault (/root/repos/brain/)
  • J.A.R.V.I.S. reads vault before answering questions
  • J.A.R.V.I.S. writes to vault when learning new facts
  • Pat reads/edits vault on any device via git sync
  • Paperclip agents read vault (read-only) for project context

Tasks (What we’re doing)

  • Source of truth: Paperclip issue boards
  • Pat creates issues or asks J.A.R.V.I.S. to create them
  • J.A.R.V.I.S. assigns to agents, monitors progress
  • Agents report progress in issue comments
  • J.A.R.V.I.S. verifies against git before marking done

Code (What we built)

  • Source of truth: Git repos at /root/repos/
  • Agents write code to repos using OpenCode
  • Every commit pushed to GitHub remote
  • No issue marked done without commit + push + test verification

Communication (How we talk)

  • Pat ↔ J.A.R.V.I.S.: WhatsApp (voice-first, auto-TTS)
  • Status updates: 2hr cron to WhatsApp
  • J.A.R.V.I.S. ↔ Agents: Paperclip issue comments
  • Urgent items: WhatsApp + Paperclip issue + vault lesson

Access Control Matrix

ResourcePatJ.A.R.V.I.S.Paperclip Agents
Vault 00-07 (projects, decisions, lessons)RWRWRO
Vault 10-privateRW❌❌
Vault 11-journalRWRO❌
Git reposRWRWRW (assigned repo only)
Paperclip issuesRWRWRW (assigned project only)
Hermes configRWRW❌

Verification Chain (The Fix)

Before reporting anything as β€œdone”:

  1. Check git: cd /root/repos/<project> && git log --oneline -5
  2. Check push: git status β€” must be β€œup to date” with remote
  3. Check tests: python -m pytest -q β€” must pass
  4. Update vault: Write results to relevant project note
  5. Then mark Paperclip issue as done

What We Dropped

  • ❌ memU β€” Disabled. Cron removed. Was empty anyway.
  • ❌ Trusting agent self-reports β€” Must verify against git
  • ❌ Compressed 2KB Hermes memory β€” Reduced to pointer + critical facts
  • ❌ Session search as primary memory β€” Vault is now primary