Skip to main content
Master Vault is the workspace file system for GTM knowledge. It stores strategy docs, account docs, and agent-maintained notes that should outlive any one conversation.
Yuzu Master Vault showing drafted strategy docs including Sales process and ICP

​
Strategy docs

Strategy docs are living workspace references. Teams use them for:
  • ICP and positioning
  • Buying committee patterns
  • Objection playbooks
  • Pricing rules
  • TLDR style guidance
  • Tone of voice
  • Win and loss themes
  • Sales process
  • USPs
  • Industries
  • Fundraising, when investor evidence exists
The master agent can review these docs against recent workspace signal and write versioned updates when the evidence has materially changed. Workspaces with enough classified customer calls can bootstrap drafted docs such as ICP, Sales process, Buying committee patterns, Positioning, Objection playbook, Pricing rules, Win themes, USPs, and Industries. Some docs intentionally remain placeholders until Yuzu has enough evidence. For example, Tone of voice, TLDR style guide, Loss themes, and Competitive stance should not be filled with generic guesses just because the file exists.

​
Evidence boundaries

Vault docs should stay honest about where their evidence came from. Buyer, customer, and prospect conversations can update GTM docs such as ICP, positioning, pricing rules, win themes, and objection playbooks. Fundraising, investor diligence, board updates, and capital strategy belong in fundraising or investor context. They should not rewrite buyer-facing GTM docs unless the same fact is also supported by customer or prospect evidence.

​
Zu’s notes

Zu’s notes is a system document written by the chat agent. It is read-only for humans and exists so Zu can preserve durable workspace facts it learns through conversations. Humans can:
  • Read the doc.
  • Open the version rail.
  • See which agent wrote each revision.
  • Duplicate content into a normal editable doc when needed.
Humans cannot directly edit the system doc. That keeps agent memory auditable and prevents accidental manual edits from being treated as agent-authored memory.

​
Version rail

The version rail shows each saved change, author type, timestamp, and summary. Prior system versions are visible for inspection, while restore actions are disabled on protected agent-memory documents.

​
Accounts

Account docs let the workspace keep durable context outside the deal page. Use them for account-level notes that should apply across multiple conversations or opportunities.