Brainforge Knowledge

README

4 min read

Clients Directory

This directory contains internal project resources for Brainforge’s active client engagements. Resources are organized by client name with consistent subfolder structures.

Structure

Each active client has the following folder structure:

clients/{client-name}/
├── transcripts/          # Meeting transcripts
├── meeting-agendas/      # Meeting agendas and prep materials
├── meeting-notes/        # Internal meeting notes
├── sows/                 # Statements of Work (internal copies)
├── project-plans/        # Project planning documents
└── resources/            # Other internal resources (presentations, proposals, etc.)

Client Classification

Active/Confirmed Clients

Active clients get dedicated clients/{client-name}/ folders. These are clients with:

  • Signed contracts/SOWs
  • Active project work
  • Ongoing engagement

Current Active Clients (folder names are lowercase; see client-vault-mapping for canonical list):

  • abchomeandcommercial/ - ABC Home & Commercial
  • cta/ - Consumer Technology Association
  • eden/ - Eden / EdenOS
  • lmnt/ - LMNT (formerly also teamlmnt; merged into lmnt)

Leads/Prospects

Leads, prospects, and new logos go to knowledge/sales/leads/{slug}/ (see knowledge/sales/README.md) until they become active clients. When a lead becomes an active client, migrate resources from knowledge/sales/leads/… to knowledge/clients/{client}/.

Current Leads/Prospects:

  • knowledge/sales/leads/breezy/ - Breezy (not active client)

Archiving a client

When an engagement ends, move the client out of the active list so skills (weekly kick-off, meeting-prep, standup-deck, etc.) no longer treat them as active:

  1. Move folder: Move knowledge/clients/{client}/ to knowledge/clients/_archive/{client}/. Create _archive/ if it does not exist. Skills and canonical mapping should ignore _archive and anything under it.
  2. Update lists: Remove the client from the “Current Active Clients” list in this README. If standards/04-prompts/client-vault-mapping.md exists, remove or mark the client as archived there.
  3. No deletion: Keep the archived folder for reference; do not delete client history.

Use the Cursor command Archive client (or run the steps manually) when archiving.

Migration Rules

What Goes Here

  • Meeting transcripts (client-specific)
  • Meeting agendas and prep materials
  • Internal meeting notes
  • SOWs (internal copies for reference)
  • Project plans and timelines
  • Internal presentations and proposals
  • Slack notes and workflow summaries
  • Other internal project documentation

What Stays in Client Repos

  • Discovery wikis (DISCOVERY_WIKI.md) - client-facing deliverables
  • Active project code/configs
  • Client-specific policies/requirements
  • Official SOWs (but also copied here for internal reference)

What Goes Elsewhere

  • Internal Brainforge meetings → meeting/transcripts/ (not client-specific)
  • Lead/prospect resources → knowledge/sales/{client-name}/ (until client is active)

File Naming

  • Preserve original filenames when possible
  • Use consistent date formats (YYYY-MM-DD prefix preferred)
  • Add client prefix if needed for clarity: {client}-{original-name}.md

Purpose

This directory centralizes internal knowledge about client engagements while keeping client-facing deliverables in their respective client repositories. This creates a clear separation between:

  • Internal knowledge (vault) - for Brainforge team reference
  • Client-facing deliverables (client repos) - for client access

Adding a new client

  1. Create the folder under knowledge/clients/ with the intended name (lowercase recommended for consistency with existing folders and case-sensitive systems), e.g. knowledge/clients/newclient/.
  2. Add the client to the canonical client → vault path mapping: standards/04-prompts/client-vault-mapping.md (in the brainforge-platform repo). Add a row to the table and, if the client has a Linear team, note it in the Linear team column.
  3. Update any commands or skills that keep their own client list (e.g. weekly-kick-off-update command table) so the new client is included.

Skills that read or write under knowledge/clients/ (meeting-prep, standup-deck, weekly-kick-off, sync-granola-to-vault) use this mapping so paths stay consistent.

  • standards/04-prompts/client-vault-mapping.md (brainforge-platform) — Canonical client → knowledge/clients/ path mapping; single source of truth for skills and commands.
  • KNOWLEDGE_AND_STANDARDS_GUIDE.md — Complete guide on using knowledge/ + standards/ together
  • README.md — Overall knowledge/ structure and contribution guidelines
  • AGENTS.md - Agent guidance and repository map

Key Reminder

Always use standards/ + knowledge/ together:

  1. Check standards/ first for templates and standards
  2. Store internal knowledge in knowledge/
  3. Keep client repos minimal (only client-facing deliverables)

DO NOT put internal knowledge (transcripts, notes, resources) in client repos — use knowledge/ instead.

Graph View