Operational Protocol — Diagram Frameworks

The Crystallization Protocol v3.0

A repeatable process for extracting load-bearing elements from any conversation and mapping them to artifact-ready structures.

To Invoke This Protocol, Say:
"Run the Crystallization Protocol on this conversation."

Purpose

This protocol transforms diffuse conversations into structured, artifact-ready output. It applies the Load-Bearing Test systematically to identify which elements must survive into the final artifact.

The protocol does not filter for novelty, interest, or impressiveness. It filters only for structural necessity.

This protocol governs any artifact type—diagrams, documents, tables, lists, dashboards, or any other externalized expression of insight.

Step 0.5: Complexity Triage

Before running the full protocol, assess the input to determine which path to take:

New in v3.0 — Path Selection
Pre-Structured Input
Streamlined Path
Indicators:
  • Conversation already has clear themes
  • Key insights are explicitly stated
  • Prior AI already helped organize
  • One dominant artifact candidate is obvious
→ Use Streamlined Path (S1-S6)
Diffuse Input
Full Protocol
Indicators:
  • Many tangents and exploratory threads
  • Insights are scattered or implicit
  • Contradictions or revisions occurred
  • Multiple competing artifact candidates
→ Use Full Protocol (01-09)

Triage Declaration: Claude states explicitly which path will be used before proceeding.

Streamlined Path
~10 minutes to artifact

For pre-structured input, skip formal segmentation and move faster:

S1

Identify the Dominant Insight

What is the ONE thing this conversation produced that needs to become an artifact?

State it: "The core insight is ________."

S2

Quick Load-Bearing Scan

List 3-7 elements that are structurally necessary for this insight to stand.

Apply the test rapidly: "Does the insight collapse without this?"

S3

Confirm Artifact Type

Based on the insight's job (reveal vs. act), select ONE type.

S4

DISTILL Check

Confirm Before Rendering:
Purpose: "This artifact exists to show ________."
No-Go: "This artifact must NOT show ________."
Name: What's the retrieval hook?
Output For: Webinar / TikTok / Handout / Reference / Marketing
S5

Artifact State + Fail-Safe

Declare: "This is an Explainer Artifact" (or Thinking Artifact if incomplete)

"If shared without me speaking, would this mislead someone?"
YES →
Flag and discuss
NO →
Proceed to render
S6

Render

Generate artifact containing only load-bearing elements.

Full Protocol
~30 minutes to artifact

Use this 9-step process when input is messy, exploratory, or unclear:

01

Segment the Conversation

Break into semantic units: claims, questions, responses, elaborations, examples, corrections.

Don't summarize. Just identify distinct units of meaning.

02

Identify Candidate Insights

From segments, identify statements that assert, conclude, reveal, or reframe.

Over-include at this stage. We filter next.

03

Apply the Load-Bearing Test

"If I removed this element, would the insight collapse?"
YES →
Keep. Load-bearing.
NO →
Remove. Scaffolding.
UNCERTAIN →
Flag for review.

Be aggressive. Most content is scaffolding.

04

Extract Relationships

For surviving elements, identify connections:

Causal: A causes B | Dependency: A requires B | Contrast: A vs B
Hierarchy: A contains B | Sequence: A then B | Boundary: A inside, B outside

05

Classify Artifact Type

"What is the primary job of this insight?"
REVEAL / EXPLAIN → Stack, Concept Map, Boundary, Before/After, Roadmap, Capability Table
ACT / EXECUTE → Flow, Decision Tree, Gotcha List, Dashboard

Choose ONE primary type. Hybrids create confusion.

06

Complete DISTILL Requirements

Before Rendering, Confirm:
Purpose: "This artifact exists to show ________."
No-Go: "This artifact must NOT show ________."
Name: What's the retrieval hook?
Output For: Webinar / TikTok / Handout / Reference / Marketing
07

Generate Crystallization Report

CRYSTALLIZATION REPORT // Source: [conversation identifier] LOAD-BEARING ELEMENTS: 1. [Element] 2. [Element] 3. [Element] RELATIONSHIP MAP: [E1] —[type]→ [E2] [E2] —[type]→ [E3] ARTIFACT TYPE: [Selected] RATIONALE: [Why this type] PURPOSE: "This artifact exists to show ________." NO-GO: "Must NOT show ________." NAME: "[Retrieval hook]" OUTPUT FOR: [Purpose] DRAFT STRUCTURE: [Sketch appropriate to type] FLAGGED FOR REVIEW: [Uncertain elements]
08

Apply Fail-Safe Question

"If shared without me speaking, would this mislead someone?"
YES →
Simplify or add boundaries
NO →
Proceed to render
09

Render (Upon Approval)

Generate artifact containing only load-bearing elements.

Nothing decorative. Nothing that was useful for arriving at insight but isn't necessary for it to stand.

Artifact State Declaration

Before sharing, declare honestly:

THINKING ARTIFACT
In-Progress
Cognitive scaffolding. Causality incomplete. For your own use.
Do NOT present as finished product.
EXPLAINER ARTIFACT
Complete
Causal, scoped, purposeful. Passes fail-safe question.
Ready for audience consumption.

Quick Reference: Path Selection

Decision Flow
INPUT RECEIVED │ ▼ COMPLEXITY TRIAGE │ ├─→ Pre-Structured? ──→ STREAMLINED PATH (S1-S6) │ │ │ ▼ │ [~10 min to artifact] │ └─→ Diffuse? ─────────→ FULL PROTOCOL (01-09) │ ▼ [~30 min to artifact] │ ▼ CRYSTALLIZATION REPORT │ ▼ [RENDER]

Quick Reference: Invocation Phrases

Phrase Action
"Run the Crystallization Protocol" Full or Streamlined based on triage
"What's load-bearing here?" Quick structural identification
"The goal is a [type]. Ask me questions." Mode 4 interrogation
"Generate a crystallization report" Structured output, no render
"This is pre-structured" Invoke streamlined path
"This is messy/diffuse" Invoke full protocol

What This Protocol Does NOT Do

Important Constraints

Does not filter for novelty. Load-bearing ≠ surprising.

Does not generate insight. Extracts and structures existing insight.

Does not replace human judgment. Flagged items require review.