← Skill Library
Knowledge System

GTM Brain

A durable, source-aware knowledge system for GTM work. Canon, source guides, and a promotion path — so people and agents share the same context without treating a wiki as a database.

Once the brain is enabled, add the dispatcher and specialist layer.Chief of Staff Agent System →

What a GTM Brain is

Most GTM teams do not have a shortage of information. They have a shortage of context that is trustworthy, current, and usable at the moment of action. A GTM Brain is the maintained map above your systems of record.

It is

A navigable layer for how the company sells, who it serves, what terms mean, which sources are authoritative, what has already been decided, and where uncertainty remains.

It is not

A CRM replacement, a transcript archive, a folder of exports, an automation engine, or proof that a fact is current because it appears in a document.

The Stack

  • Workspace
    Obsidian vault
    AGENTS.md
  • Harnesses
    Cursor
    Codex
    Claude
  • Evidence, not the brain
    Email
    Calendar
    Upside GTM data

How the folder is owned

GTM BRAIN · SHARED WORKING CONTEXTHome.mdthe mapCanon/shared, curatedPlaybooks/one procedure, one homeInbox/not yet canonDomains/Revenue · Marketing · Customer · Opsowned working memory, dated logsWrite pathDomain owners proposeA curator promotes into canonLIVE SYSTEMS · OUTSIDECRM · pipeline stateEmail · CalendarUpside · GTM evidenceQuery. Do not mirror.
CanonThe shared, reviewed answers everyone may rely on. A small group curates it. Everyone else proposes.
Live systems sit outsideCRM, email, calendar, and GTM data hold mutable truth. The brain stores definitions, pointers, and the judgment that explains how to read them.

Start with a source hierarchy

Source classUse it forTrust rule
System of recordCurrent state and transactionsVerify live before quoting volatile values
Curated canonDurable definitions, rules, decisionsRead first. Update through a curator.
ProceduresRepeatable execution stepsOne versioned home, not copied into notes
Working notesDomain context and observationsScoped, dated, not automatically canonical
Raw evidenceCalls, email, research, exportsCite it. Summarize only the durable conclusion

How it initializes

ASKNamed documentsPolicies · playbooksCRM · spoken contextDo not scrape the world.readRECONCILEOnly what they namedPreserve contradictionsWrite a source guidebefore the first queryrewriteINITIAL CANONICP · definitionsSource guides · rulesProvenance on claimsGaps stay unverifiedthenWorkingcontextReady toground work
Ask firstNamed documents, destinations, and what only the operating owners know. Do not scrape every drive or invent facts the organization has not supplied.
Rewrite, do not pasteOne fact, one home, with provenance. Empty and unverified beats invented. A GTM data platform can help find evidence; the brain still owns the judgment.

The operating loop

1OrientCanon + owned context2VerifyLive system of record3ActApproved procedure4CaptureOutcome + open gap5PromoteInbox → curator6Read backThe write exists
Read back is part of doneA task can look complete while its output was never saved, its update silently failed, or it was written to the wrong place.

How it stays current

AFTER A DAYInbox · notesLive queriesUnverified itemsStale notes possiblenightlyDREAM JOBSummarizeCorrect stale notesPromote verified itemsDoes not start new workwritesWRITE BACKAGENTS.mdHard rules · knowledgeDream logVault is now currentnext dayNext sessionReads theupdated vault
Dream jobScheduled. Reads the day, corrects stale notes, appends the dream log, exits. It does not invent policy or start new work.