Module 2: Lesson 8 of 16

Module 2 · Lesson 8 – The Execution Loop

Run the system without drift.

The Execution Loop (Before / During / After)

The Execution Loop replaces habit with procedure. If you follow it exactly, alignment compounds. If you skip steps, drift is guaranteed.

BEFORE Every Session:

Define the problem in one sentence. If you cannot, you are not ready.
Select the minimum mode(s) needed. Do not stack modes by default.
Load Framing Density: Identity, Constraints, Format, Verification.
Assign adversarial roles if stakes are high. Resistance is not optional when stakes are real.

DURING the Session:

Run execution. Let AI generate. Do not negotiate tone.
Interrupt performance. If output becomes inspirational or vague, pause and tighten framing.
Decide what mattered: decisions, rules, constraints, non-negotiables only.

AFTER the Session (NON-NEGOTIABLE):

Execute in reality. If nothing is executed, the session failed.
Copy → Store → Re-inject (Memory Stacking).
Discard the rest. Unused output is noise.

Memory Handoff Sentence

Every serious session ends with you writing one sentence:

"What must be remembered for this to work again?"

If you cannot answer that, you did not run the system.

Failure Signals (Stop Conditions)

Stop immediately if any of these appear:

Output feels inspirational rather than precise
Decisions reappear as negotiable
Rules soften without discussion
You stop documenting
You trust continuity without checking memory
You feel the urge to "just push through"

These are not edge cases. They are warning lights. Continuing past them compounds error.

Reset Protocol

When failure signals appear, execute the following in order:

Reload Framing Density. Restate identity, constraints, format, verification.
Re-inject Memory Stack. Load only relevant decisions, rules, constraints.
Run Adversarial Stress Test. Attack the plan.
Discard anything that cannot survive pressure.

If reliability does not return quickly, disengage AI from that problem. Pausing is not failure. Continuing blindly is.

Interactive Exercise

Run ONE real work session using the full Execution Loop:

We are going to run ONE real work session using the full Execution Loop. 1. Define your current problem in ONE sentence. 2. Choose the minimum mode(s) you will use (Framing Density, Memory Stacking, Adversarial Stress Test, Ghost Protocol, Temporal Hierarchy) and explain why. 3. Run the AI execution step. 4. Identify only: - Decisions - Rules - Constraints - Non-negotiables 5. Write your memory handoff sentence: 'What must be remembered for this to work again?' and answer it.

Checkpoint: Proof of Understanding

Describe one real session where you used the complete Execution Loop. Include: (1) The one-sentence problem you defined, (2) Which mode(s) you used and why, (3) What you actually executed in reality afterward, (4) Your memory handoff sentence. Be specific. This is proof you ran the system, not theory.

0 / 100 characters minimum

Continue to Module 3 →