# From Conversation to Capability

> The deep-dive companion to WS-08. How meeting transcripts become trustworthy memory — the resolution layer that turns raw talk into a knowledge asset, end-to-end. Three passes, two storage layers, one identity spine. 18 slides, 30 minutes.

*WS·10 · Module WORKSHOPS — Workshops · The CEO AI Playbook by Stephen Forte*

Canonical: https://academy.buildclub.com/v1/workshops/trustworthy-memory

## Thesis

Without a resolution layer, every new raw document adds duplicates, conflicts, and ambiguities. The larger the pile, the faster the search index turns into a heap of garbage.

## Key Takeaways

- Without a resolution layer, every new raw document adds duplicates, conflicts, and ambiguities. The larger the pile, the faster the search index turns into a heap of garbage.
- Choose one pile to resolve. Do not build a 'company brain' overnight. Pick one folder — transcripts or a customer success log — and resolve it first.
- The deep-dive companion to WS-08. How meeting transcripts become trustworthy memory — the resolution layer that turns raw talk into a knowledge asset, end-to-end. Three passes, two storage layers, one identity spine. 18 slides, 30 minutes.

## The Playbook

1. **Same person, multiple aliases** — One transcript says 'Mike,' another 'Michael S.,' the calendar 'mike@'. Without resolution, the AI treats them as three separate people with disconnected responsibilities.
2. **Split company and system names** — 'ACME Corp', 'Acme, Inc.', and 'the legacy system' are mapped to separate files, preventing any synthesis of requirements or support timelines.
3. **Anonymous commitments** — Action items extracted as 'We'll follow up next week,' with no owner and no specific deadline. The commitment is untrackable.
4. **Silent decision reversals** — A Friday decision reverses a Tuesday choice. Because they live in separate files, the AI happily quotes the stale Tuesday choice as 'the decision.'
5. **Unverifiable claims** — The LLM answers confidently but can't cite the exact conversation, file, or speaker block, forcing humans to read back through hours of audio.
1. **Raw Transcript** — Messy speech-to-text dump. No standardized names or stable IDs. High semantic noise. The temptation is to point the LLM directly at it.
2. **Resolution Layer** — Maps aliases to identity spines. Structures actions under strict schema rules. Escalates uncertain entities to humans. Nothing reaches the database without passing through.
3. **Trustworthy Memory** — Pure relational schema database. Grounded, verifiable facts. Comprehensive cross-meeting queries. Intact audit trail to source files.
1. **Pass 1 — Candidate Extraction** — Scans raw text segments to isolate potential entities — proper names, systems and vendors, stated commitments, key decisions. Cheap, broad, and probabilistic. Designed to over-produce candidates; the next pass filters.
2. **Pass 2 — Identity Resolution** — Queries the local registry. Computes fuzzy match score. Maps variations to canonical IDs. Flags low confidence for human feedback. This is where 'Mike' becomes per_0042 — or escalates if the system cannot tell which Mike.
3. **Pass 3 — Structured Recording** — Records validated facts. Emits YAML structured blocks. Binds objects via strict schema keys. Integrates into the global memory database. Only resolved, validated entities reach this stage.
1. **Tier 1 — Syntax and schema integrity** — Validates formatting parameters. Rejects empty blocks, unassigned commitments, or entries lacking a secure stable ID. All dates must conform strictly to RFC-3339. This is the spell-check layer; it runs on every write.
2. **Tier 2 — Contradiction and orphan detection** — Identifies logical conflicts. Flags when a decision directly opposes an active corporate guideline or when a commitment exists with no parent meeting linked. This is the logic-check layer; it runs nightly and on demand.
3. **Tier 3 — Observability and auditing** — Inserts pointers back to source transcripts. Annotates changes without overwriting physical file history. Assures complete transparency and audit capability. The system uses write-only logs. When logical reversals are identified, the database annotates the stale node as supersedes: dec_0085, preserving the full audit timeline.
1. **Transcript — Raw Input** — Audio finishes, speech-to-text runs, unstructured text drops into the inbox. The only step the LLM sees raw.
2. **Candidate Check** — Pass 1 extracts every possible entity — names, systems, vendors, commitments, decisions. Deliberately over-produced.
3. **The Gate — Confident?** — Pass 2 scores each candidate. Above 0.90: commit path. Below 0.90: human queue. The difference between memory and noise.
4. **Ask — 'Which Mike?'** — Low-confidence candidates surface as plain questions. Once answered, the answer is bound to the canonical ID forever.
5. **Commit — Trustworthy Answer** — Validated entities, with full source provenance, write to the entity database. The downstream LLM queries this, not the transcript.

## What to Do Monday

- Choose one pile to resolve. Do not build a 'company brain' overnight. Pick one folder — transcripts or a customer success log — and resolve it first.
- Standardize the entity registry first. Compile a clean registry of names, roles, and legacy system codes. All files must bind to these keys. The registry is the foundation.
- Enable 'ask, don't guess' policies. When fuzzy matches fall below 0.90, halt automated entries and route to human feedback forms. Uncertainty is structured feedback, not silent failure.
- Ask the test question: 'When your AI is unsure, does it ask — or quietly pick one?' If the answer is the second, the rollout is not enterprise-ready.

## FAQ

**What is the core idea of From Conversation to Capability?**

Without a resolution layer, every new raw document adds duplicates, conflicts, and ambiguities. The larger the pile, the faster the search index turns into a heap of garbage.

**What should a CEO do Monday morning after reading From Conversation to Capability?**

Start here: Choose one pile to resolve. Do not build a 'company brain' overnight. Pick one folder — transcripts or a customer success log — and resolve it first; Standardize the entity registry first. Compile a clean registry of names, roles, and legacy system codes. All files must bind to these keys. The registry is the foundation; Enable 'ask, don't guess' policies. When fuzzy matches fall below 0.90, halt automated entries and route to human feedback forms. Uncertainty is structured feedback, not silent failure.

**What are the steps in From Conversation to Capability?**

1) Same person, multiple aliases; 2) Split company and system names; 3) Anonymous commitments; 4) Silent decision reversals; 5) Unverifiable claims.

**Where do the claims in From Conversation to Capability come from?**

The playbook cites Internal workshop source material.

## Sources

- [Internal workshop source material](https://buildclub.com)

---

Work with BuildClub: https://buildclub.com/company-brain