Site Navigation

Download all pages
for Obsidian or LLMs.

Instructions for AI Assistant - Two-Person Call Wiki

These instructions are adapted from the group-call wiki process (see Instructions for AI Assistant) for a different format: a conversation between two friends. A two-person call has a fundamentally different shape than a group call — it's a dialogue, not a panel — and the wiki should reflect that.


Overview

You will receive artifacts from a two-person call (transcript, notes, links) and create a navigable markdown wiki / minipedia using [[Double Square Bracket Links]].

Key principles:


How a Two-Person Call Differs

Group Call (10-20 people) Two-Person Call
Many perspectives on shared themes Two people ranging across many topics
Theme pages synthesize across speakers Conversation threads follow natural flow
Participant pages are essential (who is this person?) Both participants are well-known; focus on what they discussed
150+ pages typical 30-60 pages typical
Hub pages needed for navigation Lighter navigation; fewer entry points needed
Formal structure Informal, conversational tone preserved

Phase 1: Analysis (Read Everything First)

CRITICAL: Read all source materials completely before creating any pages.

1.1 Read All Artifacts

1.2 Conversation Mapping

Map out the conversation's natural flow:

1.3 Depth Classification

Classify each topic into one of three tiers:

  1. Deep threads (multiple minutes of back-and-forth, substantive exchange) → Full wiki page with quotes and analysis
  2. Medium threads (a minute or two, some substance) → Wiki page with context and key points
  3. Brief mentions (a sentence, a name drop, a quick aside) → Stub page or mention within another page

This prevents the common error of inflating a 10-second mention into a full page that implies deep discussion.


Phase 2: Wiki Creation

2.1 Core Infrastructure Pages

  1. README.md — Homepage

    • Who spoke, when, what the call was about
    • The major conversation threads (not "themes" — these are threads in a dialogue)
    • Quick links to key pages
    • Tone: casual, reflecting that this is two friends talking
  2. Conversation Flow.md — The call's narrative arc

    • A guided walkthrough of how the conversation moved from topic to topic
    • This replaces "Themes Hub" — in a two-person call, the flow IS the structure
    • Brief description of each thread with links to deeper pages
    • Shows natural transitions ("...which led them to discuss...")
  3. Concept Index.md — Complete index of all pages

    • Organized by type: People, Projects, Topics, Concepts, Organizations, Media
    • Updated as pages are created
  4. Work Log.md — Process journal

2.2 Participant Pages

With only two people, participant pages serve a different purpose than in a group call. They're less "who is this person?" and more "what did they bring to this conversation?"

Template:

# First Last

**In this conversation:** One-sentence summary of their role/energy in this call.

## Topics They Introduced
- [[Topic 1]] — brief context for why they brought it up
- [[Topic 2]]

## Stories They Told
### [Story Title]
> "Key quote"

[Context and significance]

## Projects and Interests Discussed
- [[Project 1]] — their relationship to it
- [[Project 2]]

## People They Mentioned
- [[Person]] — context for the mention

## Follow-ups and Action Items
- What they said they'd do or share

2.3 Conversation Thread Pages

These are the heart of a two-person call wiki. Each substantive topic gets a page that captures the dialogue — not just extracted themes.

Template for deep threads:

# Topic Name

**Introduced by:** [[Person]] | **Depth:** Deep thread

[Overview: What this topic is about and why it came up in the conversation]

## The Conversation

[Narrative summary showing how the dialogue developed, with quotes from both participants woven in]

> **Sebastian:** "Quote"

> **Pete:** "Quote in response"

[Analysis of what emerged from the exchange]

## Key Points
- Point 1
- Point 2

## Related
- [[Related Topic]]
- [[Person or Project Mentioned]]

Template for medium threads:

# Topic Name

**Introduced by:** [[Person]] | **Depth:** Medium thread

[What was said, with key quotes, more concisely]

## Related
- [[Related links]]

Template for brief mentions / stubs:

# Topic Name

> **Note:** This topic was briefly mentioned during the call but not discussed in depth.

[What it is, who mentioned it, in what context]

**Mentioned by:** [[Person]]  
**Context:** Brief explanation of why it came up

2.4 Reference Pages

For people, organizations, projects, books, etc. that were mentioned:

# Name

[Brief description of what/who this is]

## In This Conversation

[How and why this came up, who mentioned it, what was said]

**Mentioned by:** [[Person]]

## Related
- [[Related pages]]

Phase 3: Orphan Resolution

3.1 Create Orphan-Finding Script

Create _bin/find-orphan-links.py to find all [[wiki links]] that don't have corresponding .md files.

3.2 Create Orphan Pages

For each orphan link:

3.3 Verify Zero Orphans

Run script to confirm all links resolve.


Phase 4: Enrichment

4.1 Re-read Transcript with Pages Open

Now that pages exist, re-read the transcript looking for:

4.2 Add Dialogue Texture

Two-person calls have a quality that group calls don't: genuine back-and-forth. Capture:

4.3 Quality Check

For thread pages:

For participant pages:

For reference pages:


Phase 5: Navigation

5.1 Lighter Navigation Structure

A two-person call wiki needs less navigation infrastructure than a group call. Create:

  1. Start Here.md (optional — README may suffice)

    • 2-3 suggested reading paths based on interest
    • "If you're interested in X, start with Page"
  2. Alphabetical Index.md

    • Complete A-Z of all pages
  3. Update README.md with clear navigation section

Skip the full hub-page treatment (Participants Hub, Themes Hub, Frameworks Hub) — overkill for a two-person call. The Conversation Flow page and README provide sufficient navigation.

5.2 Cross-Linking Pass

Ensure every page links to at least 3-5 related pages. In a smaller wiki, this keeps everything connected without requiring hub pages.


Phase 6: Process Documentation

6.1 Work Log

Document decisions, methodology, and any interesting observations about the process.

6.2 Wiki Creation Process Page

Document prompts, decisions, and lessons learned for future iterations.


Quality Principles

Dialogue Over Extraction

Honest Depth

Attribution in Dialogue

Preserve Voice

Appropriate Scale


File & Link Conventions

Files

Links

Structure

repo/
├── README.md
├── Conversation Flow.md
├── Concept Index.md
├── Alphabetical Index.md
├── Work Log.md
├── Wiki Creation Process.md
├── Details About This Wiki.md
├── [Participant 1].md
├── [Participant 2].md
├── [Conversation Thread].md (5-10 deep/medium threads)
├── [Reference Page].md (15-30 people, projects, concepts)
├── Call Artifacts/
│   └── meeting_saved_closed_caption.txt
└── _bin/
    └── find-orphan-links.py

Common Pitfalls for Two-Person Call Wikis

Don't

Do


Success Metrics

Completeness:

Quality:

Navigation:

Scale:


Adapted from Instructions for AI Assistant (group call version). Key adaptation: treating the conversation as a dialogue with natural flow rather than a panel discussion with extractable themes.