RTT‑1 Teaching Capture Worksheet

Beginner‑friendly worksheet for capturing processes in IPD‑12#

This worksheet teaches students how to perform Capture, the first step in IPD‑12.
It uses RTT‑1 surface‑regime language: simple, clear, structural, non‑substrate.

SECTION 1 — Process Identity#

Process Name
Write a short, canonical name (lowercase, underscores, no spaces).
Example: human_notes

Purpose
One sentence describing what the process is for.
Example: capture information manually

SECTION 2 — Boundaries (Constraints)#

List the limits or constraints of the process.

Examples:

• time
• attention
• input quality
• model constraints

Write at least two boundaries.

1.
2.

SECTION 3 — Structural Layers#

List the main components of the process.
Use nouns (input, processing, output, etc.).

Examples:

• input
• interpretation
• output

Write at least three layers.

1.
2.
3.

SECTION 4 — Operational Flow#

List the steps in the order they occur.
Use verbs (input → process → output).

Examples:

• listen
• interpret
• write

Write at least three steps.

1.
2.
3.

SECTION 5 — Coherence Baseline#

Write what “working correctly” means for this process.

Examples:

• clear notes
• accurate transcription
• stable output

One sentence:

Coherence baseline:

SECTION 6 — Domain & Regime Level#

Domain
One domain only (workflow, music, physics, mythology, etc.).

Regime Level
Choose one:

surface | mid | deep

SECTION 7 — Drift‑Ready Checklist#

Before running drift(), confirm:

• boundaries are filled
• structural_layers are filled
• operational_flow is filled
• coherence_baseline is declared
• domain is set
• regime_level ≤ deep

This checklist ensures the capture object is ready for drift, tensor, coherence, and paradox operators.

SECTION 8 — Compare Two Processes (RTT‑1)#

Use this section when capturing two processes for drift comparison.

Process A Name:
Process B Name:

Shared Structure#

List what both processes share.

1.
2.
3.

Shared Boundaries#

1.
2.

Shared Coherence Baseline#

baseline:

This unlocks compare_process() and prepares for drift analysis.

SECTION 9 — Student Exercise Template#

Process Name:
Purpose:

Boundaries:
- 
- 

Structural Layers:
- 
- 
- 

Operational Flow:
- 
- 
- 

Coherence Baseline:

Domain:
Regime Level:

Shared Structure (if comparing):
Shared Boundaries:
Shared Coherence:

SECTION 10 — Teacher Notes (RTT‑1)#

• Keep language simple.
• Avoid substrate, inversion, dimensional, or infinite‑regime concepts.
• Declare coherence explicitly.
• Bound drift to structural differences only.
• Treat paradoxes as tensions, not contradictions.
• Use everyday examples (notes, workflows, tools, music, etc.).