Govern · Chapter 04

Trust and brand

How customers feel about dealing with agents, and how to earn it.

An assistant learns useful things about your voice when you correct a real draft. Perhaps a sentence promises more than you would promise, or a familiar phrase conceals what you mean. Keep the example and the reason for the correction. Those choices give the assistant something more precise than “sound like us.”

Personal context helps carry that learning between sessions. Record your goals, working constraints and a few representative examples in a place you control. Tiago Forte’s Building a Second Brain offers a useful principle: select and distill what helps future work. Saving everything makes the important choices harder to find.

Separate expression from what is true

A voice guide describes how you want to speak. Approved company facts establish what the business stands behind. A draft can sound right and still quote an old price, invent a benefit or reveal something private. Give each kind of context a clear home and preserve its source.

A small folder in an existing notes tool may be enough. Keep personal context, annotated voice examples and a dated session handoff. If dictation helps you explain your thinking, use the operating system’s dictation or a tool such as Wispr Flow after reviewing its permissions. The useful artifact is the corrected context, whatever captured it.

Test whether your correction travels

Ask the assistant to draft something you actually need. Correct it, save the reason and start a fresh session. Can the new session retrieve the preference and use it? That is a better test of continuity than being told the assistant remembers you.

Review the result for both expression and factual support before it reaches a customer. Keep private preferences out of shared company context unless you deliberately choose otherwise. Trust grows when the business can speak consistently and answer for what it says.

Tools and setup

Prior work: Tiago Forte's Building a Second Brain develops CODE: capture, organize, distill and express. Use it to select reusable context rather than collect indiscriminately.

  1. In Obsidian, create a vault in an agreed folder or open an existing folder. Add PERSONAL-CONTEXT.md, VOICE.md and SESSION-HANDOFF.md; begin with a few authorized samples and a private inbox.
  2. Optional voice input: install Wispr Flow from its official site, sign in, review data preferences and grant required microphone/input permissions. Complete a non-sensitive practice dictation into the inbox. OS dictation is a reasonable starting alternative.
  3. Give the assistant access only to the chosen folder or explicitly attached files. Ask it to cite a preference, draft a sample, then incorporate your correction. Do not claim cross-session memory until a fresh session retrieves the saved context.

Setup paths checked against linked documentation on 15 November 2026. Verify current account support during setup; reader integrations have not been tested here.

Work through this with your agent

Paste the request into your assistant. It will interview you and help produce the working artifact.

Interview me to build useful personal context and a voice guide. Ask at most three questions per turn; wait for answers. Ask how I decide, current goals, working preferences, examples of writing I like and dislike, and words or claims I avoid. Start with a few representative samples; request more only if needed. Identify private material and what must never enter shared business context. With permission, inspect existing notes before adding another store. Draft PERSONAL-CONTEXT.md, VOICE.md and SESSION-HANDOFF.md in an agreed location; keep source references, dates and editable assumptions. Separate preferences, tentative ideas and approved company claims. Test the guide on one real draft and ask me to correct it. Show how a fresh session retrieves the files; test that retrieval if supported. Do not claim persistent memory without proof or upload private samples without permission. Finish with artifacts, my corrections and any unverified retrieval step.

Use these documented setup paths as references; check current account support before acting:
https://fortelabs.com/blog/basboverview/
https://obsidian.md/help/vault
https://docs.wisprflow.ai/articles/3152211871

The Hypothesis Diff · weekly

Know when a hypothesis is stressed or changes.

One email a week: which hypotheses hold, which are stressed, which changed, and the tools worth trying. Nobody else publishes what stopped being true.