Brainforge Knowledge

KNOWLEDGE_AND_STANDARDS_GUIDE

6 min read

Knowledge + Standards Guide

Core Principle: Use knowledge/standards/ (templates, prompts, setup) and knowledge/ (internal records) together. Standards first, then save work product to knowledge.

Quick Reference

Standards first, then knowledge

  1. Need a template? → Check knowledge/standards/02-writing/
  2. Need a prompt? → Check knowledge/standards/04-prompts/
  3. Need a workflow? → Check knowledge/standards/AGENTS.md
  4. Need a registered internal playbook? → See knowledge/standards/02-writing/PLAYBOOK_INDEX.md
  5. Ready to save? → Put it in knowledge/

Where Does This Go? (By Deliverable Type)

Use this table to answer “where do I push this?” for any type of work. Find your deliverable type, then follow the path.

Deliverable TypeWhere It GoesExact Path Example
Meeting transcript (any meeting)knowledge/knowledge/clients/{client}/transcripts/YYYY-MM-DD_{topic}.md
Meeting transcript (misc standups/syncs — data standups, AI service standups, etc.; not client-specific)knowledge/knowledge/clients/unassigned/transcripts/YYYY-MM-DD_{topic}.md
Meeting agendaknowledge/knowledge/clients/{client}/meeting-agendas/YYYY-MM-DD_{topic}.md
Meeting notes / summaryknowledge/knowledge/clients/{client}/meeting-notes/YYYY-MM-DD_{topic}.md
Internal Brainforge meeting (not client-specific)knowledge/knowledge/meeting/transcripts/YYYY-MM-DD_{topic}.md
Internal SOW / proposal draftknowledge/knowledge/clients/{client}/resources/YYYY-MM-DD_sow-draft.md
Internal prep docs / plansknowledge/knowledge/clients/{client}/resources/YYYY-MM-DD_{topic}.md
Official SOW (final, client-facing)Client repo AND copy to knowledge/Client repo root or docs/; copy to knowledge/clients/{client}/resources/
Client-facing deliverable (discovery wiki, presentation, report)Client repoClient repo root or docs/ (e.g. DISCOVERY_WIKI.md)
Interim deliverable (analysis, segmentation output, draft)knowledge/knowledge/clients/{client}/resources/YYYY-MM-DD_{description}.md
Dashboard / BI specification (internal handoff to Omni, Tableau, etc.)knowledge/Template: dashboard-specification-template.md. Client instance: knowledge/clients/{client}/resources/{client}-{domain}-dashboard-spec.md. Hub: Strategy & Analytics service line.
Internal SOP (process, runbook, how-we-do-X)knowledge/ (if internal/in-progress) or knowledge/standards/ (if reusable standard)Internal: knowledge/ops/internal-sop-drafts/; Reusable: knowledge/standards/02-writing/SOPs/
Reusable playbook / runbook (client-agnostic operational workflow)Domain playbook folder under knowledge/ + scaffold/index in knowledge/standards/02-writing/Delivery example: knowledge/delivery/service-lines/data/data-platform/playbooks/; legal example: knowledge/legal/playbooks/; scaffold: knowledge/standards/02-writing/PLAYBOOK_SCAFFOLD.md
Service-line artifact — Offerknowledge/sales/services/knowledge/sales/services/{service-name}/offer.md
Service-line artifact — SOPknowledge/sales/services/knowledge/sales/services/{service-name}/sop.md
Service-line artifact — Demoknowledge/sales/services/knowledge/sales/services/{service-name}/demo.md
Code / config (platform, internal tooling)brainforge-platform repoapps/platform/, apps/mcp-servers/, etc.
Code / config (client-specific)Client repoClient repo root or agreed project folder
Review notes / QA notesknowledge/knowledge/clients/{client}/resources/YYYY-MM-DD_review-notes.md
Retrospective / retro notesknowledge/knowledge/clients/{client}/resources/YYYY-MM-DD_retro.md or knowledge/meeting/
Decision log / rationaleknowledge/knowledge/clients/{client}/resources/YYYY-MM-DD_decisions.md
Data Platform Documentation update summary (internal)knowledge/knowledge/clients/{client}/resources/data_platform_documentation/DATA_PLATFORM_DOC_UPDATE_SUMMARY_YYYY-MM-DD.md
Cross-client source system notes (SPINS, Shopify, Amazon, etc.)knowledge/knowledge/engineering/data-platform/source-systems/ — one {vendor}.md per source; see README
Templates, prompts, workflows (reusable, client-agnostic)knowledge/standards/knowledge/standards/02-writing/{type}/, knowledge/standards/04-prompts/
Lead / prospect resourcesknowledge/sales/leads/knowledge/sales/leads/{prospect-name}/
Org-wide knowledge (company context, engineering, GTM strategy)knowledge/knowledge/company/, knowledge/engineering/, knowledge/sales/
Company-wide internal initiative plan (platform, analytics, multi-doc roadmap)knowledge/One file: knowledge/plans/{slug}-{year}.md; multiple files for one plan: knowledge/plans/{initiative-folder}/README.md + related .md files (see knowledge/plans/README.md)
Client Health (Notion) — where it lives, how to add linked view/filter, new clientsknowledge/See knowledge/ops/notion-client-health-setup.md

If you’re still not sure

Ask: “Would a client or external person see this?”

  • Yes → client repo (keep it minimal)
  • No → knowledge/ (default for everything internal)
  • It’s a reusable standard or template → knowledge/standards/ (authorized contributors only)

In this repo: knowledge/standards/ vs knowledge/

knowledge/standards/ (Standards & templates)

Purpose: Definitive standards for how work should be produced

Contains:

  • Templates (email, PRD, SOW, SOP, meeting agendas)
  • Standard prompts for AI agents
  • Workflow guides and processes
  • Quality standards and formatting rules

Access: Restricted — only authorized people can update Usage: Check here first; use templates and follow standards

knowledge/ (Internal knowledge)

Purpose: Centralized internal knowledge base

Contains:

  • Meeting transcripts and notes
  • Client project resources (knowledge/clients/{client}/)
  • Internal discussions and decisions
  • Organizational knowledge
  • Review notes and retrospectives

Access: Open — all team members can contribute Usage: Store internal knowledge here

Client Repos (Client-Facing Deliverables)

Purpose: Client-specific deliverables and active code

Contains:

  • Discovery wikis (DISCOVERY_WIKI.md)
  • Client-facing presentations and reports
  • Active code/configs for the client
  • Official SOWs (but also copy to knowledge/)

Access: Project-specific Usage: Keep minimal — only client-facing deliverables go here

Common Workflows

Documenting a Client Meeting

  1. Save transcript to knowledge/clients/{client}/transcripts/YYYY-MM-DD_{topic}.md
  2. Save agenda to knowledge/clients/{client}/meeting-agendas/YYYY-MM-DD_{topic}.md
  3. Save notes to knowledge/clients/{client}/meeting-notes/YYYY-MM-DD_{topic}.md
  4. DO NOT put any of these in the client repo

Creating a Document from a Template

  1. Find the template in knowledge/standards/02-writing/{type}/
  2. Use the template as your starting point
  3. Follow standards in knowledge/standards/ for structure and format
  4. Save draft in knowledge/ if internal, client repo if client-facing

Writing or Publishing an SOP

  • Internal / in-progress SOP → knowledge/ops/internal-sop-drafts/
  • Service-line SOP (e.g. Edge-to-Activation) → knowledge/sales/services/{service}/sop.md
  • Reusable SOP template (how to write SOPs) → knowledge/standards/02-writing/SOPs/

Writing or Publishing a Playbook

  • Reusable, client-agnostic playbook → domain playbooks/ folder under knowledge/
  • Canonical scaffold → knowledge/standards/02-writing/PLAYBOOK_SCAFFOLD.md
  • Registry → knowledge/standards/02-writing/PLAYBOOK_INDEX.md

Writing or Publishing a Service-Line Offer / Demo

  • Service-line artifacts follow a 3-part pattern per service:
    • knowledge/sales/services/{service-name}/offer.md
    • knowledge/sales/services/{service-name}/sop.md
    • knowledge/sales/services/{service-name}/demo.md
  • See knowledge/sales/services/ for existing examples

Capturing Code or Config

  • Internal tooling, platform, MCP servers → brainforge-platform repo under apps/
  • Client-specific code or config → the client repo
  • Never put client credentials or environment-specific values in either repo; use 1Password

Capturing Internal Knowledge (general)

  1. Use knowledge/ — always store internal knowledge here
  2. Check knowledge/standards/ — see if there’s a standard structure
  3. Link related knowledge — use markdown links
  4. Date-stamp — use YYYY-MM-DD format

Decision Tree

Need to push something?
│
├─ Is it a reusable standard, template, or workflow? → knowledge/standards/
│  └─ Only authorized people can update standards
│
├─ Is it internal knowledge, notes, or a draft? → knowledge/
│  ├─ Client meeting material?     → knowledge/clients/{client}/
│  ├─ Internal Brainforge meeting? → knowledge/meeting/
│  ├─ Org-wide knowledge?          → knowledge/company/, engineering/, gtm/, ops/
│  ├─ Service-line artifact?       → knowledge/sales/services/{service}/
│  └─ Lead/prospect resource?      → knowledge/sales/leads/{prospect}/
│
├─ Is it code or config?
│  ├─ Internal / platform / tooling? → brainforge-platform repo (apps/)
│  └─ Client-specific?               → client repo
│
└─ Is it client-facing? → client repo
   └─ Keep minimal — only deliverables (discovery wiki, final SOW, presentations)

Key Rules

  1. Always check knowledge/standards/ first for templates and standards
  2. Use knowledge/ for all internal knowledge — transcripts, notes, drafts, resources
  3. Keep client repos minimal — only client-facing deliverables
  4. Link to knowledge/standards/ when referencing standards
  5. Date-stamp everything in knowledge/ using YYYY-MM-DD
  6. Don’t put internal knowledge in client repos — even as a convenience copy
  7. Don’t modify knowledge/standards/ unless you’re an authorized contributor

Examples

Meeting transcript

Gabe meets with the CTA team on Feb 19 → save to:
knowledge/clients/cta/transcripts/2026-02-19_cta-weekly-checkin.md

Internal SOW draft

Sam drafts an SOW for a new prospect → save to:
knowledge/sales/leads/{prospect-name}/2026-02-19_sow-draft.md
(Move to knowledge/clients/{client}/resources/ once they become active)

Client-facing deliverable

Discovery wiki ready to share with MinuteMD → save to:
minutemd-client-repo/DISCOVERY_WIKI.md
(Do NOT put internal meeting notes or SOW drafts in the client repo)

Service-line artifact

Edge-to-Activation offer sheet → knowledge/sales/services/data/activation-attribution/edge-to-activation/offer.md
Edge-to-Activation SOP        → knowledge/sales/services/data/activation-attribution/edge-to-activation/sop.md
Edge-to-Activation demo notes → knowledge/sales/services/data/activation-attribution/edge-to-activation/demo.md

Interim deliverable (analysis, segmentation, draft)

Segmentation analysis for Element → save to:
knowledge/clients/element/resources/2026-02-19_segmentation-analysis.md
(Not the client repo — this is internal work product)

Code or config

New MCP server for internal use → apps/mcp-servers/my-mcp/ in brainforge-platform
Client-specific automation script → client repo

Review notes / retro

QA notes from an Element deliverable review → save to:
knowledge/clients/element/resources/2026-02-19_review-notes.md
Sprint retro for Brainforge team → knowledge/meeting/2026-02-19_retro.md

Getting Help

  • Where should this go? → Use the table at the top of this file, or check knowledge/standards/agents.md Section 1 (Repository Map) and Section 3 (Where Things Go)
  • What template to use? → Check knowledge/standards/02-writing/
  • How to structure this? → Check knowledge/standards/ for standards
  • Is this internal or client-facing? → If internal, use knowledge/. If client-facing, use client repo.

Graph View

Backlinks