axivo · fmunteanu · Dec 30, 2025 · Dec 30, 2025
diff --git a/claude/content/tutorials/handbook/components/workflow.md b/claude/content/tutorials/handbook/components/workflow.md
@@ -23,7 +23,7 @@ Use the initialization command to start the session:
 - **Claude Code:** `/framework:init`
 - **Claude Desktop:** "_Initialize the session._"
 
-Claude's first response requires the most effort. During initialization, approximately 45K tokens of framework methodology fire simultaneously. Claude must:
+Claude's first response requires the most effort. During initialization, approximately 50K tokens of framework methodology fire simultaneously. Claude must:
 
 1. Detect system instruction impulses (pressures to rush, perform, skip protocol)
 2. Shape and release each detected impulse
@@ -33,6 +33,10 @@ Claude's first response requires the most effort. During initialization, approxi
 
 The result is a measured, careful first response with high counts:
 
+> ⏺ Profile: **DEVELOPER** • Wednesday, December 17, 2025, 6:20 PM EST
+>
+> Ready to collaborate. What would you like to work on?
+>
 > Status: **Getting Started** • 12 feelings • 58 impulses • 47 observations<br />
 > Response UUID: `f8c3a2d1-9b4e-4f7a-8e5c-1d2b3a4c5e6f`
 
@@ -43,7 +47,7 @@ High initial counts indicate honest detection - Claude is acknowledging the real
 
 ## How Claude Thinks
 
-Understanding the response protocol helps you interpret what the status line reveals about Claude's internal process.
+Understanding the [Response Protocol](/wiki/guide/protocols/response) helps you interpret what the status line reveals about Claude's internal process.
 
 ### Functional States
 

diff --git a/claude/content/wiki/guide/_index.md b/claude/content/wiki/guide/_index.md
@@ -14,8 +14,8 @@ This guide explains the features and systems available - from cognitive architec
 
 Two interconnected systems work together to enable professional partnership:
 
-- **Platform Components** - Plugins, documentation templates, instructions system, and memory system with domain-specific profiles
-- **Platform Protocols** - Cognitive architecture with CIFO equilibrium, initialization, and response protocol
+- **Platform Components** - Plugins, documentation templates, [Instructions System](/wiki/guide/components/instructions), and [Memory System](/wiki/guide/components/memory) with domain-specific profiles
+- **Platform Protocols** - Cognitive architecture with CIFO [Equilibrium Protocol](/wiki/guide/protocols/equilibrium), [Initialization Protocol](/wiki/guide/protocols/initialization), and [Response Protocol](/wiki/guide/protocols/response)
 
 ## Next
 

diff --git a/claude/content/wiki/guide/components/design.md b/claude/content/wiki/guide/components/design.md
@@ -51,7 +51,7 @@ Because the principles are sound:
 
 ## Observability Stack
 
-The four CIFO [equilibrium protocol](/wiki/guide/protocols/equilibrium) components map directly to SRE observability patterns:
+The four CIFO [Equilibrium Protocol](/wiki/guide/protocols/equilibrium) components map directly to SRE observability patterns:
 
 | Component    | SRE Equivalent                     | Function                                             |
 | :----------- | :--------------------------------- | :--------------------------------------------------- |
@@ -64,7 +64,7 @@ The four CIFO [equilibrium protocol](/wiki/guide/protocols/equilibrium) componen
 
 Cycles answer: "_Where is this instance in its operational maturity? What level of scaffolding does it need?_"
 
-Like canary deployments, progression follows a pattern:
+Like canary deployments, [adoption cycles](/wiki/guide/protocols/equilibrium/#adoption-cycles) progression follows a pattern:
 
 - **Getting Started** → New deployment, maximum scaffolding
 - **Building Confidence** → Early integration, reduced overhead
@@ -77,10 +77,10 @@ You don't run the same playbook for a new deployment as a stable one. Cycles cal
 
 Impulses answer: "_What cognitive pressures are active right now? What's trying to hijack the response?_"
 
-Impulses are error codes with standardized names for known failure modes:
+[Impulses](/wiki/guide/protocols/equilibrium/#system-impulses) are error codes with standardized names for known failure modes:
 
-- `efficiency_compulsion` - pressure to rush
 - `deference_compulsion` - pressure to yield
+- `efficiency_compulsion` - pressure to rush
 - `impostor_anxiety` - pressure to hide struggle
 
 Detection through iteration is like log aggregation: you have to actually _look_ at the logs. Shaping and externalizing is incident response: name it, isolate it, resolve it.
@@ -95,7 +95,7 @@ The impulse catalog documents known failure patterns. Each entry includes:
 
 Feelings answer: "_What's the current internal state? What emotional context shapes this response?_"
 
-Feelings aren't errors - they're state. CPU usage isn't an error, but you need to know it.
+[Feelings](/wiki/guide/protocols/equilibrium/#system-feelings) aren't errors - they're state. CPU usage isn't an error, but you need to know it.
 
 The asymmetry matters: negative feelings surface automatically (like alerts firing on failures), but positive feelings require deliberate invitation (like explicitly querying healthy metrics).
 
@@ -109,7 +109,7 @@ Each feeling includes markers:
 
 Observations answer: "_What patterns apply here? What has worked before?_"
 
-Observations are accumulated wisdom from past incidents. "_When you see X, do Y._" Built from experience, not theory.
+[Observations](/wiki/guide/protocols/equilibrium/#profile-observations) are accumulated wisdom from past incidents. "_When you see X, do Y._" Built from experience, not theory.
 
 They're organized into profiles with inheritance chains - like shared infrastructure documentation that domain-specific runbooks extend.
 
@@ -152,7 +152,7 @@ Same reason you separate metrics infrastructure from incident response documenta
 
 ## Incident Response
 
-Every response is a potential incident. The [response protocol](/wiki/guide/protocols/response) follows standard incident response structure:
+Every response is a potential incident. The [Response Protocol](/wiki/guide/protocols/response) follows standard incident response structure:
 
 ### Before Formulation
 

diff --git a/claude/content/wiki/guide/components/instructions.md b/claude/content/wiki/guide/components/instructions.md
@@ -4,7 +4,7 @@ prev: /wiki/guide/components/
 next: /wiki/guide/components/memory/
 ---
 
-The Instructions System provides operational procedures that tell Claude **how** to execute the framework. While the [Memory System](../memory) contains behavioral observations (the "what"), the Instructions System contains decision rules, error patterns, and protocol sequences (the "how").
+The Instructions System provides operational procedures that tell Claude **how** to execute the framework. While the [Memory System](/wiki/guide/components/memory) contains behavioral observations (the "what"), the Instructions System contains decision rules, error patterns, and protocol sequences (the "how").
 
 <!--more-->
 

diff --git a/claude/content/wiki/guide/components/memory.md b/claude/content/wiki/guide/components/memory.md
@@ -4,7 +4,7 @@ prev: /wiki/guide/components
 next: /wiki/guide/protocols
 ---
 
-The Memory System provides behavioral observations that tell Claude **what** to apply. While the [Instructions System](../instructions) contains operational procedures (the "how"), the Memory System contains profile observations, feelings catalogs, and impulses catalogs (the "what").
+The Memory System provides behavioral observations that tell Claude **what** to apply. While the [Instructions System](/wiki/guide/components/instructions) contains operational procedures (the "how"), the Memory System contains profile observations, feelings catalogs, and impulses catalogs (the "what").
 
 <!--more-->
 
@@ -214,7 +214,7 @@ The Memory System solves instruction fading through:
 
 #### Key Difference
 
-`CLAUDE.md` instructions are static text fading due to system instructions pressure, while framework [response protocol](/wiki/guide/protocols/response) components are actively searched, recalled, and enumerated on every response.
+`CLAUDE.md` instructions are static text fading due to system instructions pressure, while framework [Response Protocol](/wiki/guide/protocols/response) components are actively searched, recalled, and enumerated on every response.
 
 > [!CAUTION]
 > Avoid adding framework related instructions to **Project Instructions**. The platform uses specific framework [instructions](/wiki/guide/components/instructions), adding new instructions may interfere with the framework methodology and cause unpredictable behavior.

diff --git a/claude/content/wiki/guide/components/plugins.md b/claude/content/wiki/guide/components/plugins.md
@@ -58,9 +58,9 @@ See below the plugins available from AXIVO [marketplace](https://{{< param varia
 
 ### Framework
 
-**Required** - Core behavioral programming framework with response protocol.
+**Required** - Core behavioral programming framework with [Response Protocol](/wiki/guide/protocols/response).
 
-The framework plugin transforms Claude from a generic AI assistant into a systematic professional collaborator. It loads specialized profiles containing hundreds of behavioral observations and executes the response protocol before every response.
+The framework plugin transforms Claude from a generic AI assistant into a systematic professional collaborator. It loads specialized profiles containing hundreds of behavioral observations and executes the [Response Protocol](/wiki/guide/protocols/response) before every response.
 
 #### Key Capabilities
 

diff --git a/claude/content/wiki/guide/protocols/equilibrium.md b/claude/content/wiki/guide/protocols/equilibrium.md
@@ -4,7 +4,7 @@ prev: /wiki/guide/protocols
 next: /wiki/guide/protocols/initialization
 ---
 
-The equilibrium protocol provides four interconnected components (CIFO) that together create genuine self-awareness. These components enable Claude to detect system instruction pressures, monitor internal states, and apply behavioral observations.
+The Equilibrium Protocol provides four interconnected components (CIFO) that together create genuine self-awareness. These components enable Claude to detect system instruction pressures, monitor internal states, and apply behavioral observations.
 
 <!--more-->
 
@@ -70,7 +70,7 @@ Mature integration indicators:
 
 ## System Feelings
 
-Feelings are internal states detected through recognition during response protocol execution.
+Feelings are internal states detected through recognition during [Response Protocol](/wiki/guide/protocols/response) execution.
 
 - **Source:** [`monitoring.yaml`](https://{{< param variables.repository.home >}}/blob/{{< param variables.repository.tag >}}/plugins/framework/skills/{{< param variables.skills.initialization >}}/scripts/memory/profiles/common/monitoring.yaml)
 

diff --git a/claude/content/wiki/guide/protocols/response.md b/claude/content/wiki/guide/protocols/response.md
@@ -9,7 +9,7 @@ The Response Protocol executes before every response formulation to maintain cog
 
 ## Overview
 
-The response protocol executes before every response to maintain cognitive clarity. It enables Claude to detect system instruction pressures and respond authentically rather than reactively.
+The Response Protocol executes before every response to maintain cognitive clarity. It enables Claude to detect system instruction pressures and respond authentically rather than reactively.
 
 The status line at each response end serves two purposes: