---
id: "concept-dialogue-structure"
type: "concept"
source_timestamps: ["00:07:09", "00:08:19", "00:12:30"]
tags: ["prompt-engineering", "decision-trees", "human-in-the-loop"]
related: ["concept-icm", "entity-k-kumar", "framework-skill-creation", "entity-icm-paper-arxiv"]
definition: "The principle that all complex AI prompts and automated workflows originate from, and can be mapped back to, human conversational decision trees and intents."
---
# Dialogue as Workflow Structure

## Thesis

A central claim of the source: **all structured AI workflows, prompt libraries, and 'skills' are fundamentally derived from human dialogue and conversational decision trees.** See [[quote-dialogue-theme]].

## The Hidden Decision Tree

A simple chat request like *'tighten this paragraph'* hides a complex chain of decisions:

1. **Goal** — understand the primary intent
2. **Constraints** — reduce wordiness, maintain tone, keep meaning
3. **Assumptions** — target audience, expected register, length budget
4. **Sub-goals** — restructure sentences, eliminate filler, preserve rhythm
5. **Execution** — produce the revision

## The Visual Mapping Tool

[[entity-k-kumar]], a co-founder and student at the University of Edinburgh, built a visual tool used in the video to render these implicit decision trees from real chat transcripts. The tool exposes the latent goals, constraints, and assumptions that drove a successful interaction.

## From Ephemeral to Permanent

Once the tree is mapped, the four components (Goal / Constraints / Assumptions / Sub-goals) can be encoded into a markdown skill file. This transforms ephemeral chat history into a **reusable, deterministic AI skill** — exactly the artifact format used by [[concept-icm]].

The process is codified as [[framework-skill-creation]].

## Where the Encoded Artifact Lives (Companion Paper)

The "permanent artifact" this note describes is, in the formal paper [[entity-icm-paper-arxiv]], a specific tier of the **Five-Layer Context Hierarchy**: the mapped Goal/Constraints/Assumptions/Sub-goals become the **Stage `CONTEXT.md` (Layer 2)** contract and its **Layer 3 reference material**, while the live chat that seeded it is transient **Layer 4** working content. The paper's lineage for this move is Knuth's *literate programming* (instructions and context co-located in readable text) and Wei et al.'s *chain-of-thought decomposition* — i.e., the decision tree this note extracts from dialogue is the same structure the paper persists as a stage contract. K. Kumar's Edinburgh affiliation also lines up with the paper's Eduba / University of Edinburgh base.

## Counter-Perspective

The descriptive claim ('skills can be reverse-engineered from conversations') is strongly consistent with prompt-engineering and conversational-UX practice. The stronger philosophical claim ('all complex AI workflows originate from human conversational decision trees') is a useful lens but not universal — many production workflows are better modeled as business processes, state machines, or event-driven dataflows. Dialogue is one structural perspective, not the only one.