# Brain directory (`brain/`) brain **TiDB GTM knowledge, concentrated** — product facts, ICP, competitive set, messaging snapshot, benchmark standards. No executable skills here; load these files **with** [`skills`](../skills/README.md) so drafts stay aligned. ## Scope and evolution This knowledge layer is a **shared baseline** for org-wide external GTM — **not** a full substitute for account-specific truth, legal review, or what you already know from customers and deals. Content **updates on release, messaging, and competitive cadence** (see [Maintenance](#maintenance)). **Roadmap (in progress / planned):** expand coverage over time — e.g. **partner** motions, **integrations** and ecosystem narratives, and other surfaces as PMM and GTM prioritize them. Today’s five files are the core; expect **more files and deeper playbooks** as the program matures. **Source of truth: pingcap.com (and its subdomains — docs.pingcap.com, zero.tidbcloud.com, mem9.ai, drive9.ai) is the primary, authoritative source for every fact in this knowledge layer.** Internal GTM plans, positioning proposals, and drafts (e.g. `tidb-narratives/tidb_family/`) are useful *signal* for what may be coming, but they are never citable as fact until they are live on pingcap.com — no matter how final they read. When an authoritative source in your context disagrees with a brain file (signed-off quote, live SKU, regional nuance), **lead with that** and open a PR or issue to reconcile the brain — but "authoritative" means pingcap.com or an equivalent official/legal-approved source, not an internal draft. > **Skills directory:** [`skills`](../skills/README.md) — start with [`find-skill`](../skills/find-skill/SKILL.md). **Framework credits** live in the [skills README](../skills/README.md#credits-and-design-provenance). > **Version:** beta v0.13 · [Changelog](CHANGELOG.md) · [Repository](https://github.com/pingcap-inc/tidb-gtm-skills-n-brain) --- ## Quick start > **Workspace rule:** open the repository root (the folder containing both `skills/` and `brain/`) or use `tidb-gtm-pack.code-workspace`. Then follow [INSTALL.md](../INSTALL.md) for setup details. ```bash git clone https://github.com/pingcap-inc/tidb-gtm-skills-n-brain.git ``` ``` @skills/tidb-tech-story/SKILL.md @brain/knowledge/product.md @brain/playbooks/messaging.md ``` ```bash git pull ``` --- ## Knowledge index | File | When to load | |------|----------------| | [`knowledge/product.md`](knowledge/product.md) | Naming, tiers, capabilities, prohibited claims | | [`knowledge/icp.md`](knowledge/icp.md) | Segments, personas, buyer journey | | [`knowledge/competitors.md`](knowledge/competitors.md) | Comparisons, bake-offs, competitive copy | | [`knowledge/brand.md`](knowledge/brand.md) | Visual identity: colors, typography, logo, Cornerstone, layouts, asset library | | [`playbooks/messaging.md`](playbooks/messaging.md) | Approved messaging snapshot | | [`playbooks/benchmark-standards.md`](playbooks/benchmark-standards.md) | Performance / benchmark claims | | [`playbooks/seo-geo-standards.md`](playbooks/seo-geo-standards.md) | Universal SEO & GEO optimization principles for all published content | Full depth (examples, segment lists, competitor list) is **inside each file**. --- ## How this relates to skills ``` skills brain ──────────────────────── ────────────────────────────── HOW — 17 skills GTM knowledge (this repo) └──────── skills @ brain/... ───┘ ``` - **Skills** = workflow. **Brain** = reference content — update on different triggers. - **Default:** align org-wide naming and messaging to this repo; **override** when a verified local source is newer or contractually required. --- ## Skills → brain mapping | Skill | Brain files | |-------|-------------| | `find-skill` | *(routes to others)* | | `tidb-brand-voice` | `knowledge/product.md` | | `tidb-brand-visual` | `knowledge/brand.md` | | `tidb-icp-synthesis` | `knowledge/icp.md` | | `tidb-competitive-map` | `knowledge/competitors.md` | | `tidb-gtm-brief` | `knowledge/product.md`, `knowledge/icp.md` | | `tidb-strategy-review` | — | | `tidb-product-narrative` | `knowledge/product.md` | | `tidb-messaging-platform` | `knowledge/product.md`, `knowledge/icp.md`, `knowledge/competitors.md`, `playbooks/messaging.md` | | `tidb-benchmark-narrative` | `playbooks/benchmark-standards.md`, `knowledge/product.md` | | `tidb-messaging-review` | `playbooks/messaging.md`, `knowledge/product.md` | | `tidb-launch-brief` | `playbooks/messaging.md`, `knowledge/product.md` | | `tidb-field-brief` | `knowledge/icp.md`, `playbooks/messaging.md` | | `tidb-tech-story` | `knowledge/product.md`, `playbooks/messaging.md`, `playbooks/seo-geo-standards.md` | | `tidb-thought-leadership` | `knowledge/product.md`, `playbooks/messaging.md`, `playbooks/seo-geo-standards.md` | | `tidb-channel-copy` | `playbooks/messaging.md` | | `tidb-developer-story` | `knowledge/product.md` | | `tidb-case-study` | `knowledge/product.md`, `playbooks/messaging.md`, `playbooks/benchmark-standards.md`, `playbooks/seo-geo-standards.md` | | `tidb-content-review` | `playbooks/messaging.md`, `knowledge/product.md` | --- ## Maintenance | File | Owner | Trigger | |------|-------|---------| | `knowledge/brand.md` | PMM / Brand | Brand refresh; palette or design system change | | `knowledge/product.md` | PMM + PM | Major release; tier changes; new approved metrics | | `knowledge/icp.md` | GTM Strategy + PMM | Quarterly; pipeline shift; many new interviews | | `knowledge/competitors.md` | PMM | Material competitor / pricing change | | `playbooks/messaging.md` | PMM | After `tidb-messaging-review` PASS | | `playbooks/benchmark-standards.md` | PMM + Engineering | Benchmark or methodology change | Rules: no customer proof without approval; no unsourced metrics; don’t edit `playbooks/messaging.md` without messaging review; use `[TBD]` not invented data; date-stamp major edits in file headers. --- ## License MIT — see [LICENSE](LICENSE).