Vanderbilt Owen Graduate School of Management
Session 7 · Monday, March 30, 2026

Pod Review &
Coordinated Teams Plan

★ MIDTERM ★

Pod progress review · Team dynamics assessment
Building a coordinated plan for the second half.

WHAT Layer Culmination
The Journey

The Story So Far

Six sessions from identity to intelligence

Session 1 — The Graph Is Everything

Graph theory fundamentals. Trinity Graph framework. VanderBot introduction. WHO

Session 2 — The Trinity Graph: Hands On

11 Inkwell Runes. The Omega Protocol. Kirk Progression stages. WHO

Session 3 — Week 1 Review & Team Assignment

Project showcase. Pod formation. The bridge from identity to knowledge. WHO → WHAT

Session 4 — Knowledge Graph Design

Entities, triples, Neo4j. The 100-Triple Challenge. Jeff Jonas on entity resolution. WHAT

Session 5 — Deep Research: The Intelligence Layer

7 Rights framework. AI-augmented research methodology. WHAT

Session 6 — AI Reliability Audit

Where AI gets it wrong. Domain risk assessment. Trust calibration. WHAT

Session 7 — MIDTERM: Persona Architecture & Context

Today. Integration day. All pods present. MILESTONE

Session 7

Today's Agenda

  1. 01
    Where We Are: The Midterm Checkpoint

    Framing what the first half has built and what the second half demands. 10 min

  2. 02
    Pod Reviews

    Each pod presents progress, blockers, and what they have built. ~60 min

  3. 03
    Team Dynamics Assessment

    Cross-pod strengths, gaps, and where teams can support each other. 15 min

  4. 04
    Coordinated Teams Plan

    Building the plan for how pods work together in the second half. 15 min

  5. 05
    The Bridge: WHAT → WHAT IF

    What changes when pods start building agents and generative systems. 5 min

Review Framework

Pod Review: What to Cover

Honest assessment, not performance

🏗

What You Have Built

Show the work. Graph structure, persona decisions, domain knowledge captured. Live demo if you have one.

✅

What Is Working

Where did the approach click? Which decisions are you confident about? What surprised you?

🚧

What Is Stuck

Blockers, open questions, areas where you are unsure. No penalty for honesty — this is how we help each other.

🤝

What You Need

Resources, feedback, expertise, or coordination from other pods. Name it specifically — this feeds the teams plan.

Listen actively during other pods' reviews. Your team plan depends on understanding where everyone stands.

The Three Layers

The Trinity Graph at Midterm

WHAT IF — Generative Graph Sessions 8-14 · Starts next week
★ WHAT — Knowledge Graph ★ Sessions 4-7 · Culminates TODAY
WHO — Social Graph Sessions 1-3 · Complete

You have mapped who your users are. You have structured what your domain knows. Today you demonstrate how those layers connect through persona.

Review Format

Pod Review Format

12 minutes per pod

7
Minutes

Pod Status Share

What you built, what is working, what is stuck, what you need. Demo if you have one. Be honest.

5
Minutes

Feedback & Questions

Class asks questions, offers insights. Focus on actionable feedback that helps the pod move forward.

📝
After Each Pod

Coordination Notes

Write down: one strength you noticed + one thing your team could offer this pod. These build the teams plan.

The reviews are not grades. They are inputs to the coordination plan. Listen with the question: how can our pods work together better?

Observation Guide

Team Dynamics

What to observe during pod reviews

🧩

Skill Distribution

Does every pod have the right mix? Domain knowledge, technical skill, design thinking. Where are the gaps?

🚀

Momentum

Which teams are accelerating? Which are plateauing or stuck? What is driving the difference?

🔗

Dependencies

Where do pods share data sources, domain overlap, or infrastructure needs? Hidden dependencies become blockers.

💬

Communication

How are teams communicating across pods? Who is using VanderBot effectively? Where is information siloed?

The WHAT IF layer requires cross-pod coordination. Individual pod strength is necessary but not sufficient.

The Shift

Why Coordination Matters Now

🏗

First Half: Build Within Pods

Each pod built its own graph, persona, and domain expertise. Individual depth was the goal. That work is solid.

🌐

Second Half: Coordinate Across Pods

Agents, RAG, and generative systems work across domains. Cross-pod knowledge makes every agent smarter.

An agent that draws on one pod's knowledge is useful. An agent that draws on all pods' knowledge is transformative. That requires coordination.

Framework

The Coordinated Teams Plan

Four components of cross-pod coordination

📦

Shared Resources

What can be pooled? Data sources, infrastructure, prompt patterns, design assets. Stop duplicating effort across pods.

🤝

Cross-Pod Pairs

Which pods should work more closely? Based on domain overlap, complementary skills, or shared stakeholders.

💡

Knowledge Exchange

How do teams share what they have learned? Graph patterns, persona insights, reliability findings, prompt engineering wins.

📅

Milestone Alignment

Sync pod timelines. Dependencies need to be handled in the right order for the WHAT IF phase. Who needs what, when?

We will build this plan together after the reviews, using what we learned from every pod's status.

🎤
Pod Reviews

Pod Reviews
Begin

12 minutes per pod — 7 status share / 5 feedback

What you built What is stuck What you need

Take coordination notes after each pod. These build the teams plan.

☕
Halfway

Intermission

Quick reset before the remaining reviews.

While you stretch, think about:

  • What patterns are emerging across pods?
  • Where are the natural cross-pod connections?
  • Which pod's needs could your team help with?
Workshop

Building the Plan

Coordinated Teams Plan

Shared Resources

What did multiple pods mention needing? Pool it. Data sources, tools, infrastructure, prompt patterns.

Cross-Pod Pairs

Which pods have complementary strengths or overlapping domains? Pair them for the second half.

Knowledge Exchange

What did one pod figure out that others need? Graph patterns, prompt wins, persona insights.

Second-Half Milestones

Given where each pod actually is, what are realistic checkpoints for Sessions 8-14?

This plan is not aspirational. It is built from real status observed today. Coordination is how individual pod strength becomes collective intelligence.

Looking Forward

The Bridge

WHAT → WHAT IF

You have built a structured knowledge base and designed a persona to make it useful. Starting next session, we ask: what can this system generate that did not exist before?

Session 8 Trinity Agent Design — RAG, context engineering, agent reasoning
Sessions 9-14 Generative Graph — agents that reason, create, and evolve

Everything you built in Weeks 1-4 was the foundation. The Generative Graph is where it comes alive.

Midterm Reflections

Key Takeaways

01

Individual depth is the foundation

Every pod built real domain expertise, graph structure, and persona design in the first half. That work is the substrate for everything that comes next.

02

Coordination is the multiplier

Working across pods makes every team stronger. The coordination plan transforms individual strength into collective capability.

03

Honesty beats polish

Knowing where you actually stand — including what is stuck — enables real planning. Today's honesty is tomorrow's progress.

04

Shared resources compound

Pooled knowledge, infrastructure, and patterns benefit everyone. The same prompt engineering win should not be discovered five times.

05

Dependencies are features

Cross-pod dependencies create opportunities for collaboration, not just blockers. Lean into them.

06

The second half is a team sport

The WHAT IF layer requires collective intelligence. Agents that draw on multiple pods' knowledge become genuinely powerful.

What Comes Next

Looking Ahead

8

Session 8: Trinity Agent Design

RAG · Agent Reasoning · Context Engineering

Your knowledge graph becomes the memory of an intelligent agent. Next session, we design how that agent thinks — how it retrieves, reasons, and generates.

Assignments for Wednesday, April 1

🗺
Agent Logic Map

How would an agent traverse your knowledge graph to answer a complex question? Draw the reasoning path from query to answer, showing which nodes and edges it uses.

📚
"Why Context Changes Everything" Analysis

1-2 pages. Same knowledge graph, different persona context — show how the answer changes. This is the bridge to generative reasoning.

"The foundation is built. Now we coordinate and teach it to think."

Session 7 · Pod Review & Coordinated Teams Plan — MIDTERM

Speaker Notes
1 / 15