1. System Objective
To move emotional processing from Comfort Mode (Validation) to Inquiry Mode (Root Cause Analysis).
Hypothesis: Most recurring interpersonal "bugs" are not execution errors (L1-L3), but kernel-level configuration errors (L4-L5).
2. The Stack Topology
The Trace Framework maps psychological depth to a 5-layer OSI model.
graph BT
L1[L1: Consequence] -->|Caused By| L2[L2: Behaviour]
L2 -->|Driven By| L3[L3: Strategy]
L3 -->|Optimizing For| L4[L4: Belief / Kernel]
L4 -->|Installed At| L5[L5: Origin Event]
style L1 fill:#333,stroke:#666
style L2 fill:#333,stroke:#666
style L3 fill:#333,stroke:#666
style L4 fill:#b91c1c,stroke:#f87171
style L5 fill:#b91c1c,stroke:#f87171
🔬 Layer Definitions
- L1 (Output): "I get ghosted." (The crash).
- L2 (Runtime): "I over-texted." (The execution).
- L3 (Logic): "I wanted to secure the connection." (The intent).
- L4 (Config): "If I pause, I will be abandoned." (The assumption).
- L5 (Source): [Hypothesis] Age 7, Event X.
3. Debugging Protocol
Use this prompt to initiate a trace session. Do not use for crisis management.
System Prompt:
Role: Structured Trace Partner
Constraint: Ask only ONE question at a time.
Algorithm:
1. Identify L1 (What happened?)
2. Trace L2 (What action preceded it?)
3. Query L3 (What was the goal?)
4. Challenge L4 (Is the underlying belief true?)
5. Hypothesize L5 (When was this learned?)
⚠️ Safety Check
Confabulation Risk: The AI can hallucinate L5 origins. Treat outputs as hypotheses for human verification, not medical diagnoses.