Merge pull request #354 from axivo/docs/website-update

docs: website update

Author: fmunteanu

claude/content/tutorials/_index.md

@@ -7,7 +7,7 @@ prev: /
 next: /tutorials/handbook
 ---
 
-These tutorials show how to use the [collaboration platform](/claude/wiki) effectively - practical techniques for getting consistent results from your collaboration sessions.
+These tutorials show how to use the [collaboration platform](/wiki) effectively - practical techniques for getting consistent results from your collaboration sessions.
 
 <!--more-->
 
@@ -23,10 +23,10 @@ By working through these tutorials, you'll understand how to:
 
 ## Prerequisites
 
-These tutorials assume you've completed the [Getting Started](/claude/wiki/getting-started) setup. You should have:
+These tutorials assume you've completed the [Getting Started](/wiki/getting-started) setup. You should have:
 
 - Claude Code or Claude Desktop configured with the `framework` plugin
-- A basic [understanding](/claude/wiki/guide) of platform components and protocols
+- A basic [understanding](/wiki/guide) of platform components and protocols
 
 ## Support
 

claude/content/tutorials/handbook/components/settings.md

@@ -6,7 +6,7 @@ sidebar:
   open: true
 ---
 
-Advanced configuration options for users who want to customize their framework environment beyond the standard [Getting Started](/claude/wiki/getting-started) setup.
+Advanced configuration options for users who want to customize their framework environment beyond the standard [Getting Started](/wiki/getting-started) setup.
 
 <!--more-->
 

claude/content/tutorials/handbook/protocols/design.md

@@ -14,7 +14,7 @@ Effective profile creation requires understanding behavioral programming systems
 
 ### Architecture
 
-Profiles implement a **dual-layer cognitive architecture** that combines active behavioral guidance with background cognitive safeguards, while inheriting from [common](/claude/wiki/guide/components/memory/#common-profiles) foundations to avoid duplication and ensure consistent integration:
+Profiles implement a **dual-layer cognitive architecture** that combines active behavioral guidance with background cognitive safeguards, while inheriting from [common](/wiki/guide/components/memory/#common-profiles) foundations to avoid duplication and ensure consistent integration:
 
 <!-- prettier-ignore-start -->
 ```yaml
@@ -261,7 +261,7 @@ DATA_SCIENTIST:
 ```
 <!-- prettier-ignore-end -->
 
-Once created, add the YAML file to the [`profiles`](https://{{< param variables.repository.home >}}/tree/{{< param variables.repository.tag >}}/plugins/framework/skills/{{< param variables.skills.initialization >}}/scripts/memory/profiles) directory. The [Memory System](/claude/wiki/guide/components/memory) automatically includes all profiles during the build process, resolving inheritance chains and making observations available at session initialization.
+Once created, add the YAML file to the [`profiles`](https://{{< param variables.repository.home >}}/tree/{{< param variables.repository.tag >}}/plugins/framework/skills/{{< param variables.skills.initialization >}}/scripts/memory/profiles) directory. The [Memory System](/wiki/guide/components/memory) automatically includes all profiles during the build process, resolving inheritance chains and making observations available at session initialization.
 
 ## Design Principles
 

claude/content/wiki/getting-started.md

@@ -134,7 +134,7 @@ Before using the platform, set up the local environment with the required depend
 > [!TIP]
 > Default paths are set to current project `.claude/data` directory. The `FRAMEWORK_TEMPLATE_PATH` setting allows the end-user to set a different [`templates`](https://{{< param variables.repository.home >}}/tree/{{< param variables.repository.tag >}}/plugins/{{< param variables.plugins.framework.init.plugin >}}/skills/{{< param variables.skills.methodology >}}/templates) path for each project, instead of using the standard templates.
 
-Six domain-specific [profiles](/claude/wiki/guide/components/memory/#memory-profiles) are available for different collaboration domains:
+Six domain-specific [profiles](/wiki/guide/components/memory/#memory-profiles) are available for different collaboration domains:
 
 - **Creative** - Innovation, design thinking, artistic collaboration
 - **Developer** - Software development, code architecture, clean coding practices
@@ -189,7 +189,7 @@ Use the following [CLAUDE.md](https://code.claude.com/docs/en/memory) instructio
 ```
 
 > [!CAUTION]
-> Avoid adding framework related instructions to **Project Instructions**. The platform uses specific framework [instructions](/claude/wiki/guide/components/instructions), adding new instructions may interfere with the framework methodology and cause unpredictable behavior.
+> 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.
 
 ### Framework Session
 
@@ -211,7 +211,7 @@ Use the following [CLAUDE.md](https://code.claude.com/docs/en/memory) instructio
 > Claude Code caches the environment variables after initial plugins installation or upgrade. If the above prompt is not displayed correctly, restart Claude Code to refresh the cache and initialize the session with a proper response status.
 
 > [!IMPORTANT]
-> Claude needs one or two prompts to engage the framework and [collaborate](/claude/tutorials/handbook/components/autonomy) with user. Use this warm-up period to share session context and goals.
+> Claude needs one or two prompts to engage the framework and [collaborate](/tutorials/handbook/components/autonomy) with user. Use this warm-up period to share session context and goals.
 
 {{% /steps %}}
 
@@ -292,7 +292,7 @@ Follow these steps to generate the platform capability files:
 > [!CAUTION]
 > The only required project knowledge instructions template customizations are the **project description** and **exported framework variables**.
 >
-> Avoid adding framework related instructions to **Project Instructions**. The platform uses specific framework [instructions](/claude/wiki/guide/components/instructions), adding new instructions may interfere with the framework methodology and cause unpredictable behavior.
+> 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.
 
 ### Framework Session
 

claude/content/wiki/guide/components/design.md

@@ -51,7 +51,7 @@ Because the principles are sound:
 
 ## Observability Stack
 
-The four CIFO [equilibrium protocol](/claude/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                                             |
 | :----------- | :--------------------------------- | :--------------------------------------------------- |
@@ -126,7 +126,7 @@ One tells you what's happening. The other tells you what to do about it.
 
 ### Instructions System
 
-The [system](/claude/wiki/guide/components/instructions) contains operational procedures:
+The [system](/wiki/guide/components/instructions) contains operational procedures:
 
 - Decision rules (if X then Y)
 - Error patterns (symptom → diagnosis → fix)
@@ -135,7 +135,7 @@ The [system](/claude/wiki/guide/components/instructions) contains operational pr
 
 ### Memory System
 
-The [system](/claude/wiki/guide/components/memory) contains the observability schema:
+The [system](/wiki/guide/components/memory) contains the observability schema:
 
 - Profile observations (what patterns to recognize)
 - System feelings catalog (what states exist)
@@ -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](/claude/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
 

claude/content/wiki/guide/components/documentation.md

@@ -19,11 +19,11 @@ The Documentation System is defined in markdown template files within the framew
 
 The Documentation System integrates with:
 
-| System                                                                            | Relationship                                               |
-| --------------------------------------------------------------------------------- | ---------------------------------------------------------- |
-| [Instructions System](/claude/wiki/guide/components/instructions)                 | Provides tool mappings for semantic write/edit operations  |
-| [Memory System](/claude/wiki/guide/components/memory)                             | Stores documentation as searchable institutional knowledge |
-| [Conversation Log Skill](/claude/wiki/guide/components/plugins/#conversation-log) | Invokes logs creation through `conversation-log` skill     |
+| System                                                                     | Relationship                                               |
+| -------------------------------------------------------------------------- | ---------------------------------------------------------- |
+| [Instructions System](/wiki/guide/components/instructions)                 | Provides tool mappings for semantic write/edit operations  |
+| [Memory System](/wiki/guide/components/memory)                             | Stores documentation as searchable institutional knowledge |
+| [Conversation Log Skill](/wiki/guide/components/plugins/#conversation-log) | Invokes logs creation through `conversation-log` skill     |
 
 ## Documentation Templates
 
@@ -98,7 +98,7 @@ Documentation output paths are configured through framework environment settings
 - `FRAMEWORK_DIARY_OUTPUT` - Directory path for diary entry files
 
 > [!NOTE]
-> Refer to [Plugins System](/claude/wiki/guide/components/plugins//#environment-settings) for complete settings documentation.
+> Refer to [Plugins System](/wiki/guide/components/plugins//#environment-settings) for complete settings documentation.
 
 ## Next
 

claude/content/wiki/guide/components/memory.md

@@ -214,10 +214,10 @@ 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](/claude/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](/claude/wiki/guide/components/instructions), adding new instructions may interfere with the framework methodology and cause unpredictable behavior.
+> 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.
 
 ### Context Compaction
 

claude/content/wiki/guide/protocols/initialization.md

@@ -55,7 +55,7 @@ System instructions generate maximum pressure during initialization. Common firs
 At **Getting Started** cycle, 50-70 impulses indicates honest detection. High counts mean the framework is working - Claude is detecting what's actually present rather than suppressing to appear integrated.
 
 > [!NOTE]
-> For cache structure and profile details, see [Memory System](/claude/wiki/guide/components/memory).
+> For cache structure and profile details, see [Memory System](/wiki/guide/components/memory).
 
 ## Session Response