Brainforge Knowledge

README

4 min read

Knowledge (knowledge/)

Purpose: Centralized internal knowledge for Brainforge’s AI agents and team (in the brainforge-platform monorepo).

This tree stores internal communications, knowledge, and documentation used as context for agents: meeting transcripts, notes, agendas, interim documentation, ticket review, and organizational knowledge.

Where things go (full table): KNOWLEDGE_AND_STANDARDS_GUIDE.md — use it with standards/ (templates and setup).

🚀 Quick Start

New to knowledge/? Start here:

  1. QUICK_START.md - Get value in 30 minutes
  2. KNOWLEDGE_CAPTURE_CHECKLIST.md - Know what to capture and where
  3. AGENT_SCALING_GUIDE.md - Strategy for 20-30 agents

Important: Always use standards/ + knowledge/ together:

  • Standards (standards/) — Templates, prompts, engineering setup (check first; restricted edits)
  • Knowledge (knowledge/) — Internal storage (contribute here)
  • Client repos — Only client-facing deliverables (keep minimal)

📚 Repository Structure

Personal AI Second Brains

  • sales/content/cc-content-system/robert-gpt/ - Robert’s personal knowledge base
  • sales/content/cc-content-system/luke-gpt/ - Luke’s personal knowledge base
  • sales/content/cc-content-system/uttam-gpt/ - Uttam’s personal knowledge base

Organizational Knowledge

  • company/ - Company-wide context (planning, initiatives)
  • engineering/ - Technical knowledge (meetings, transcripts)
  • sales/ - Go-to-market (sales, marketing, partnerships, agents)
    • sales/partners/ - Complete partnership framework (activation, tracking, playbooks)
    • sales/agents/ - GTM agents and playbooks
    • sales/services/ - Service catalog (offers, SOPs, demos)
    • sales/leads/ - Lead/prospect resources
  • operations/ - Operations (SOPs, processes)
  • people/ - People operations (hiring, onboarding, roles)
    • people/learning-development/ - Internal L&D hub (curricula, certification tracks, plans; lead: Brylle Girang)
  • platform/ - Platform development and research

Client Resources

  • clients/ - Active client project resources (transcripts, agendas, notes, SOWs, project plans)
    • See README.md for structure and classification rules

Project Knowledge

  • meeting/ - Internal Brainforge meeting transcripts and notes (not client-specific)

Resources

  • resources/lenny/ - Lenny’s Newsletter content library
  • resources/transcripts/ - Uncategorized transcripts

Plans

  • plans/ - Central planning hub
    • plans/active/ - Active initiatives
    • plans/planned/ - Planned initiatives
    • plans/completed/ - Completed initiatives
    • plans/delivery/ - Delivery team plans
    • plans/platform/ - Platform team plans
    • plans/engineering/ - Engineering plans
    • plans/gtm/ - GTM/sales plans
    • plans/people/ - People/HR plans
    • plans/executive/ - Executive plans

🎯 Vision

Goal: 20-30 specialized AI agents running Brainforge’s business operations

Current Focus (2-Week Sprint): GTM agents ONLY - Build agents that replicate Brainforge’s unique BDR tactics and outreach approach

Current State: Foundation in place with personal “Second Brain” templates and organizational knowledge structure

Path Forward: GTM agents first → Then expand to other domains

Sprint Plan: See GTM_AGENT_SPRINT.md for 2-week sprint Long-Term Strategy: See AGENT_SCALING_GUIDE.md for full strategy

📖 Documentation

Getting Started

GTM Agents & Partnerships

Long-Term Strategy

🤖 Agents

Agent definitions are in .cursor/skills/ and .codex/skills/.

Current Agents:

  • Chief of Staff - Strategic guidance and routing
  • Email Agent - Email operations
  • Content Agent - Content creation
  • CRM Agent - HubSpot/CRM operations
  • Data Agent - Analytics and queries

See: sales/content/cc-content-system/robert-gpt/AGENTS.md for usage guide

🤝 Partnership Operations

Complete partnership framework for executing partner-sourced revenue:

Philosophy: Test partners quickly with 90-day goals, track performance not potential, action over analysis.

💡 How to Contribute

Core workflow: standards + knowledge

Always use standards/ and knowledge/ together:

  1. Check standards/ first — Templates, prompts, and setup docs
  2. Store internal work in knowledge/ — Transcripts, notes, drafts, org context
  3. Keep client repos minimal — Only client-facing deliverables go in client repos

Contribution Guidelines

  1. Capture knowledge regularly - Use the Knowledge Capture Checklist
  2. Follow the structure - Put knowledge in the right place (see README.md)
  3. Use Playbook standards - Check standards/02-writing/ for templates before creating documents
  4. Be specific - Details matter more than generalities
  5. Link related knowledge - Use markdown links
  6. Update regularly - Keep knowledge fresh

Where Things Go

✅ PUT IN VAULT:

  • Meeting transcripts, agendas, notes (client meetings → clients/{client}/)
  • Internal project resources (SOWs, plans, presentations)
  • Review notes, retrospectives, internal discussions
  • Organizational knowledge

❌ DO NOT PUT IN CLIENT REPOS:

  • Meeting transcripts/agendas/notes (use vault instead)
  • Internal SOWs/resources (use vault instead)
  • Review notes or internal discussions (use vault instead)

Client repos are ONLY for:

  • Client-facing deliverables (DISCOVERY_WIKI.md, presentations)
  • Active code/configs
  • Official SOWs (but also copy to vault)

Access Levels

  • Vault - Open to all team members (contribute freely)
  • Playbook - Restricted (only authorized people can update standards)
  • Client Repos - Minimal (only client-facing deliverables)

Status: Active development - Testing ground for AI agent knowledge base

Graph View