# memory_nodes

id: f080d9f1-7a52-443e-b81c-9bd0c76bd111
summary: Document: 01-registration-and-onboarding.md
category: knowledge
created_at: 2026-03-12 13:12:26
last_accessed: 2026-04-01 03:33:34
source_type: document_summary
source_ref: general:/CQ-User-Manual:01-registration-and-onboarding.md
source_range: 1:60
content:
Document: 01-registration-and-onboarding.md

The document "01-registration-and-onboarding.md" outlines the initial steps for setting up a user account and configuring the CitadelQuest environment. The registration process requires a unique username, a password, and an email address for recovery, which is stored locally to ensure privacy. Notably, the first person to register on a new installation is granted Admin privileges, though administrators have the ability to disable further registrations. Users are encouraged to keep the "Auto-create CQ AI Gateway account" option checked to facilitate a seamless setup.

Following registration, a three-step onboarding wizard guides the user through essential configurations. Step one involves connecting to the CQ AI Gateway, which provides access to various AI models like Claude and Gemini; users who opted for automatic creation receive free starting credits. Step two focuses on creating a "Spirit," a personal AI companion, by selecting a name and a visual identification color. The final step offers the choice to either begin an immediate conversation with the new Spirit or explore the central Dashboard. Additionally, the document notes that CitadelQuest supports English, Czech, and Slovak languages, which can be toggled via the navigation bar and are saved to the user's profile for future sessions.


id: fd441b64-9557-464b-b15c-080626d39052
summary: Section: Creating Your Account
category: knowledge
created_at: 2026-03-12 13:12:45
last_accessed: 2026-04-01 03:33:34
source_type: document
source_ref: general:/CQ-User-Manual:01-registration-and-onboarding.md
source_range: 1:19
content:
Document: Creating Your Account

The document "Creating Your Account" provides a step-by-step guide for registering and onboarding onto a CitadelQuest instance. To create an account, users must navigate to the platform via a web browser and select the "Register" option. The registration process requires a unique username, a password, and an email address intended for account recovery. Notably, this email is stored only within the user's local database to ensure privacy.

The guide highlights a "zero-friction" setup option by recommending that users keep the "Auto-create also CQ AI Gateway account" box checked, which automates the initial AI configuration. Administrative privileges are automatically granted to the very first person who registers on a new installation. Additionally, the document notes that registration is a permission-based feature; if the Citadel administrator has disabled the function, prospective users must contact them directly to gain access. The overall process is designed to prioritize user autonomy and ease of use while maintaining the platform's decentralized security model.


id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
summary: Section: Onboarding Wizard: AI and Spirit Setup
category: knowledge
created_at: 2026-03-12 13:13:13
last_accessed: 2026-04-01 03:33:34
source_type: document
source_ref: general:/CQ-User-Manual:01-registration-and-onboarding.md
source_range: 20:39
content:
Document: Onboarding Wizard: AI and Spirit Setup

The Onboarding Wizard is a three-step process designed to guide new users through the initial setup of their CitadelQuest experience following their first login. The primary focus of this guide is the integration of AI services and the creation of a personal AI companion, known as a Spirit.

In the first step, users connect to the CQ AI Gateway, which provides access to advanced AI models such as Claude, Gemini, and Grok. This setup can be handled automatically if the user opted to create a CQ AI Gateway account during registration, which includes free starting credits. Alternatively, users can manually enter an existing API key or skip the step to configure it later in the settings.

The second step involves creating a Spirit. Users customize their AI companion by assigning it a name and a specific color for visual identification. While the system automatically selects a smart default AI model to allow for immediate interaction, users maintain the flexibility to change the model at any time through the Spirit Profile. This onboarding ensures that the core functionalities of the platform—AI augmentation and personalized assistance—are ready for use immediately upon entry.


id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
summary: Section: Post-Onboarding and Language Settings
category: knowledge
created_at: 2026-03-12 13:13:39
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:01-registration-and-onboarding.md
source_range: 40:60
content:
Document: Post-Onboarding and Language Settings

The document outlines the final steps of the onboarding process and the available language settings within the CitadelQuest platform. Upon completing onboarding, users are presented with two primary paths: they can select "Start" to initiate their first conversation with their Spirit and explore platform features, or select "Dashboard" to access their central hub for managing activities. Additionally, the guide details the platform's multilingual support, noting that users can switch between English (EN), Czech (CZ), and Slovak (SK) at any time via the language icon in the top navigation bar. These language preferences are saved and remain consistent across future sessions.


id: 85fb774c-e8e7-4611-91cd-44a19a072386
summary: Document: 03-spirits.md
category: knowledge
created_at: 2026-03-12 13:18:13
last_accessed: 2026-03-22 17:23:03
source_type: document_summary
source_ref: general:/CQ-User-Manual:03-spirits.md
source_range: 1:127
content:
Document: 03-spirits.md

Spirits are the central AI companions of the CitadelQuest platform, designed to learn, remember, and evolve alongside the user. This document details their management, functionality, and the gamified progression system that defines their growth.

Users manage their companions via the Spirits List (`/spirits`), where each Spirit is represented by a card showing its name, custom color, and current level. The Spirit Profile (`/spirit/{id}`) allows for deep customization, including selecting AI models from providers like Anthropic, Google, or xAI, and configuring system prompts through an Advanced Prompt Builder. This profile also features a 3D Memory Explorer preview, which visualizes the Spirit's knowledge graph and interaction history.

Interaction primarily occurs through the Spirit Chat, a modal overlay that supports Markdown, image and PDF attachments, and memory synthesis. A key feature of Spirits is their ability to use AI Tools automatically to manage files, search the web, generate images, and perform complex memory operations like extraction and recall.

The system incorporates a leveling mechanic where Spirits earn experience points (XP) through conversations, tool usage, and memory processing. As users engage with their Spirits, these companions level up, visually tracking the progress of the human-AI collaboration. New Spirits can be created easily by defining a name, model, and color, which initializes them with basic identity memory nodes.


id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
summary: Section: Introduction to Spirits
category: knowledge
created_at: 2026-03-12 13:18:26
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:03-spirits.md
source_range: 1:6
content:
Document: Introduction to Spirits

Spirits represent the core component of the CitadelQuest platform, serving as personalized AI companions designed for long-term interaction. These entities are characterized by their ability to learn from user engagement, maintain a persistent memory, and evolve over time. Each Spirit is distinct, featuring its own unique personality and specific set of capabilities, functioning as a growth-oriented partner that develops alongside the user within the ecosystem.


id: aef300c2-1723-48a7-9ab4-b83c9342ef57
summary: Section: Spirits List Management
category: knowledge
created_at: 2026-03-12 13:18:53
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:03-spirits.md
source_range: 7:20
content:
Document: Spirits List Management

The Spirits List Management document details the functionality of the Spirits page located at the /spirits route. This interface presents a user's AI companions as individual cards, which serve as the primary hub for managing and interacting with them. Each card provides essential visual and status information, including a custom-colored icon, the Spirit's name, and their current level and experience points (XP). Additionally, the cards offer quick access links to the Spirit's chat interface and detailed profile. Beyond viewing existing companions, the page allows users to initiate the creation of new Spirits or select an existing one to perform further management tasks. The system is designed to provide a clear overview of all active AI entities within the CitadelQuest environment.


id: c39275dc-8438-45f5-acca-639882d9ac61
summary: Section: Spirit Profile and Configuration
category: knowledge
created_at: 2026-03-12 13:19:04
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:03-spirits.md
source_range: 21:43
content:
Document: Spirit Profile and Configuration

The Spirit Profile and Configuration document details the features and settings available at the `/spirit/{id}` route within the CitadelQuest platform. This interface serves as the central hub for a user's Spirit, organized into three primary sections. The Identity & Level section features visual elements like a customizable icon with glow effects, the Spirit's name, and an experience bar that tracks progress and leveling based on user interactions. The AI Model section allows users to select the specific large language model powering their Spirit, offering choices from providers such as Anthropic, Google, and xAI. Finally, the System Prompt section provides tools for defining the Spirit's personality and expertise. This includes an Advanced Prompt Builder for fine-tuning behavior rules and selecting memory types, such as Legacy .md files or a Memory Agent. Changes made in this section must be saved to take effect, ensuring the Spirit behaves according to the user's specific requirements and custom instructions.


id: 10512eb2-de99-45b3-b749-a8db5f5e9379
summary: Section: Memory and Interaction History
category: knowledge
created_at: 2026-03-12 13:19:16
last_accessed: 2026-03-22 17:23:29
source_type: document
source_ref: general:/CQ-User-Manual:03-spirits.md
source_range: 44:60
content:
Document: Memory and Interaction History

The document outlines the Memory and Interaction History features within the CitadelQuest platform, specifically focusing on how users monitor and manage their Spirit's development. It details three primary sections: the Memory Explorer Preview, Recent Interactions, and Conversations.

The Memory Explorer Preview provides a 3D knowledge graph visualization that displays metrics such as pack, node, and relationship counts. It includes an "Explore" button for deeper data filtering and a "Memory Agent" badge to indicate the active processing mode. The Recent Interactions section serves as a chronological log, tracking timestamps, interaction types—such as creation, conversation, and tool usage—and the experience points (XP) earned by the Spirit. Finally, the Conversations section allows users to manage their dialogues, providing tools to view existing chat lists, open specific conversations, or initiate new ones. Together, these features offer a comprehensive overview of the Spirit's growth, knowledge structure, and engagement history.


id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
summary: Section: Spirit Chat Interface
category: knowledge
created_at: 2026-03-12 13:19:44
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:03-spirits.md
source_range: 61:85
content:
Document: Spirit Chat Interface

The Spirit Chat Interface is a modal overlay within the CitadelQuest platform designed to provide seamless access to AI assistance without navigating away from current tasks. It can be accessed via the top navigation bar or through specific conversations in the Spirit Profile. The interface supports rich interactions, including message input, full Markdown formatting for AI responses, and the ability to attach images and PDF documents for analysis and memory extraction.

A key feature of the interface is its advanced memory synthesis display. When the AI recalls information, the chat provides an expandable panel showing memory nodes, a mini 3D graph visualization of connections, a synthesis quality indicator, and keyword tags. Users can monitor their resource usage through a context window indicator integrated into the input area's border.

Control features allow for significant customization and management of the interaction. Users can adjust the AI's creativity using a temperature slider and view specific model details via an info button. Additionally, the interface includes an "Extract Memory & Close" function, which allows users to save the conversation as a CQ Memory Pack and end the session in a single action.


id: f53218b5-f2aa-4adb-902c-e88a44f11e67
summary: Section: AI Tools and Capabilities
category: knowledge
created_at: 2026-03-12 13:20:12
last_accessed: 2026-04-01 03:39:27
source_type: document
source_ref: general:/CQ-User-Manual:03-spirits.md
source_range: 86:108
content:
Document: AI Tools and Capabilities

The document "AI Tools and Capabilities" outlines the various functional tools available to a user's Spirit within the CitadelQuest platform. These tools are designed to be used automatically by the AI during natural conversation to assist with a wide range of tasks. 

The capabilities are categorized into four primary areas: file management, memory systems, web access, and image generation. File-related tools allow the Spirit to browse the file system, read content, search for specific files, and perform management tasks such as creating, renaming, moving, or deleting data. The "updateFileEfficient" tool specifically enables precise editing of file segments. 

The memory suite provides advanced information retention, allowing the Spirit to store and recall important details. This includes "memoryExtract," which utilizes automatic relationship analysis to turn document knowledge into memory graphs, and "memorySource" to verify original data. Additionally, the Spirit can access external information via "fetchURL" and create or edit visual content using AI diffusion models through the "imageEditorSpirit" and "diffusionArtistSpirit" tools. Overall, the document emphasizes a seamless user experience where the Spirit autonomously selects the appropriate tool to fulfill user requests.


id: bcb05ed5-9d44-4628-be3d-684beac42b73
summary: Section: Spirit Creation and Progression
category: knowledge
created_at: 2026-03-12 13:20:40
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:03-spirits.md
source_range: 109:127
content:
Document: Spirit Creation and Progression

To create a new Spirit in CitadelQuest, users navigate to the spirits section and select the creation option. The setup process involves choosing a name, selecting an AI model, and assigning a color. Upon creation, the Spirit is automatically initialized with starter memory nodes that establish identity for both the user and the Spirit, allowing for immediate interaction.

Spirits evolve through a gamified progression system based on experience points (XP). They earn XP by engaging in conversations, utilizing AI tools to assist the user, and performing memory operations such as storing or processing information. As the Spirit accumulates XP, its experience bar fills and its level increases, fostering a more engaging and collaborative journey between the human and the AI.


id: a26434c2-2f0a-4a19-8851-8757e21ddbf1
summary: Document: 04-cq-memory.md
category: knowledge
created_at: 2026-03-12 13:22:10
last_accessed: 2026-04-01 03:29:31
source_type: document_summary
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 1:202
content:
Document: 04-cq-memory.md

CQ Memory is CitadelQuest's advanced knowledge management system that transforms unstructured data into interactive 3D knowledge graphs. This system allows Spirits to maintain persistent, contextual memory by organizing information into "Memory Packs" (.cqmpack)—portable SQLite databases containing nodes (facts, thoughts, or preferences) and typed relationships (relates to, reinforces, contradicts, or part of). These packs are organized into "Memory Libraries" (.cqmlib) where users can set priorities and categorize knowledge.

The Memory Explorer interface (/memory) features a 3D force-directed graph rendered with Three.js, allowing users to visually navigate their data. Knowledge is added through an Extraction Panel that supports files, URLs, manual text, and Spirit conversation transcripts. Once extracted, the system can perform relationship analysis to automatically discover connections across the graph.

Spirit integration is a core feature, offering two recall modes: "Reflexes" for fast context retrieval and "Memory Agent" for high-quality synthesis using sub-agent AI. In Spirit Chat, recalled memories are displayed with mini-graphs and relevance scores. Additionally, the system supports data sovereignty and collaboration through CQ Share, enabling users to share auto-syncing Memory Packs with contacts or the public. Key use cases include research, document analysis, and building specialized knowledge bases for personal AI assistants.


id: df4f6b2b-ec31-4523-a509-90382945cc1d
summary: Section: Introduction to CQ Memory
category: knowledge
created_at: 2026-03-12 13:22:24
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 1:6
content:
Document: Introduction to CQ Memory

CQ Memory is the specialized knowledge management system within the CitadelQuest platform designed to facilitate persistent and contextual memory for Spirits. The system functions by processing unstructured data, including documents, web pages, and conversation histories, and transforming that information into interactive 3D knowledge graphs. This architectural approach allows for a sophisticated organization of information that enhances the AI's ability to recall and utilize relevant context during user interactions. By converting static content into a dynamic visual and data-driven format, CQ Memory serves as the foundational layer for long-term information retention and retrieval within the CitadelQuest ecosystem.


id: 981c25eb-0e25-4ef9-974b-e1c6b2cf98da
summary: Section: Key Concepts and Data Structures
category: knowledge
created_at: 2026-03-12 13:22:51
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 7:43
content:
Document: Key Concepts and Data Structures

This document outlines the fundamental data structures and conceptual framework for managing knowledge within the CitadelQuest ecosystem. It introduces the Memory Pack (.cqmpack), a portable SQLite database that functions as a standalone knowledge graph containing nodes, typed relationships, tags, and source content. These packs are designed for easy sharing between users and Citadels. Multiple packs can be organized into a Memory Library (.cqmlib), which allows users to manage collections by enabling or disabling specific packs, setting search priorities, and categorizing them through tags.

The core unit of information is the Memory Node, which stores content, summaries, and metadata such as category (e.g., fact, preference, or thought) and importance levels that decay over time. These nodes are linked via Relationships that define the semantic connection between data points. Specific relationship types include RELATES_TO (blue), REINFORCES (green), CONTRADICTS (red), and PART_OF (white/grey), providing a visual and structural hierarchy for the knowledge graph. Together, these components create a sophisticated system for tracking, connecting, and preserving information with full source transparency.


id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
summary: Section: Memory Explorer Interface
category: knowledge
created_at: 2026-03-12 13:23:27
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 44:96
content:
Document: Memory Explorer Interface

The Memory Explorer is a specialized interface within the CitadelQuest platform, accessible via the `/memory` route, designed for the visualization and management of knowledge graphs. The interface features a three-part layout: a left sidebar for node lists and analysis tools, a top bar for library and pack selection, and a central interactive 3D graph visualization powered by Three.js.

The 3D visualization represents data through colored spheres (nodes) and connecting lines (edges), where colors indicate categories or relationship types and node size reflects importance. Users can interact with the graph through various mouse and keyboard commands, including zooming, rotating, panning, and deleting nodes. Clicking a node reveals specific details such as content, importance, tags, and source documentation.

Management of these knowledge graphs is organized through Libraries and Packs. The Library Selector allows users to filter views by specific libraries or view a Spirit's unique memory, while the Pack Selector provides details on node and relationship counts along with AI usage statistics. Users can create new packs and libraries directly within the interface to organize their data. This tool serves as a central hub for navigating complex information structures and managing the underlying `.cqmpack` files within a user's project.


id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
summary: Section: Memory Extraction Process
category: knowledge
created_at: 2026-03-12 13:24:02
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 97:127
content:
Document: Memory Extraction Process

The Memory Extraction process in CitadelQuest allows users to transform information from various sources into structured knowledge packs. The system supports four primary source types: Files (PDFs, text, or code), URLs for web content, direct Text input for notes, and Conversation transcripts from specific Spirits. 

The extraction workflow begins by selecting a source and initiating the process. As the AI recursively processes the content, it splits information into logical blocks and builds a hierarchical structure, which is visualized through a real-time 3D graph update. Once the initial extraction is complete, the system can automatically perform a relationship analysis to discover and map connections between the newly created nodes. 

All resulting knowledge is stored within a designated pack. Because this process utilizes the CQ AI Gateway, it consumes AI credits. Users can monitor their resource consumption through the Pack Details modal, which provides comprehensive statistics on token usage and total credit costs. This feature essentially enables the creation of a sophisticated, interconnected knowledge graph that enhances the capabilities of the user's personal AI environment.


id: b7adbc37-239e-41fc-917c-62b612be0cf6
summary: Section: Memory Analysis and Jobs
category: knowledge
created_at: 2026-03-12 13:24:25
last_accessed: 2026-04-01 03:39:27
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 128:145
content:
Document: Memory Analysis and Jobs

The Memory Analysis and Jobs document outlines the functionality of the Memory Analyze Panel, which allows users to discover connections between nodes after knowledge extraction. It details two primary analysis methods: Whole Pack Analysis, which examines all nodes within a selected Memory Pack to map the entire knowledge graph, and Selected Root Node Analysis, which focuses on specific branches or topics for more targeted relationship discovery. The system utilizes a hierarchical strategy optimized for efficiency, employing intra-document leaf pairs and cross-document root-gating with recursive drill-down. Additionally, the document highlights the Active CQ Memory Jobs feature, noting that a status icon in the global app footer provides real-time visibility of extraction or analysis processes from any page within the application.


id: d53d081b-6f67-4155-8069-711b2449468c
summary: Section: Spirit Memory Integration
category: knowledge
created_at: 2026-03-12 13:24:43
last_accessed: 2026-03-22 17:23:29
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 146:177
content:
Document: Spirit Memory Integration

The "Spirit Memory Integration" document outlines how Spirits within the CitadelQuest platform store and recall information through a dedicated Memory Library. Memory is categorized into three types: Reflexes, which provide fast and automatic context recall; Memory Agent, an advanced mode where a sub-agent synthesizes and evaluates graph connections for higher-quality responses at a higher credit cost; and Legacy, which maintains backward compatibility with older .md text files.

The recall process follows a structured six-step workflow: a user message triggers a search across all enabled memory packs, relevant nodes are identified via keyword matching, and—if in Memory Agent mode—the data is synthesized by a sub-agent. This context is then delivered to the Spirit, allowing it to respond with awareness of past interactions and knowledge.

Users can monitor this process in the Spirit Chat through a specialized Memory Synthesis Display. This interface includes an expandable panel detailing the specific memories used, a mini 3D graph for visualizing node connections, and various indicators such as relevance score badges, identification tags, and "Graph" badges for nodes discovered through relationship expansion. This system ensures that Spirits maintain a persistent, evolving understanding of the user's data and history.


id: e6da62d1-5272-4316-8fa4-652f2a8ad291
summary: Section: Sharing and Syncing
category: knowledge
created_at: 2026-03-12 13:25:14
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 178:191
content:
Document: Sharing and Syncing

The document "Sharing and Syncing" outlines the process for distributing Memory Packs within the CitadelQuest ecosystem. Users can share these packs either publicly or with specific CQ Contacts through the Memory Explorer dropdown menu or the dedicated CQ Share management page. The system supports two primary visibility scopes: Public, which allows access to anyone with a link, and CQ Contacts, which restricts access to authenticated users. A key feature of this system is the auto-sync capability; when a CQ Contact downloads a shared pack, any subsequent updates made by the original owner are automatically reflected in the contact's version upon opening their Memory Explorer. For more detailed instructions, the document refers users to the full CQ Share guide.


id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
summary: Section: Use Cases
category: knowledge
created_at: 2026-03-12 13:25:36
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 192:202
content:
Document: Use Cases

The document outlines several practical use cases for organizing and analyzing information within the CitadelQuest ecosystem. Key functionalities include document and book analysis for extracting concepts from PDFs, as well as research tools that allow users to aggregate multiple sources to identify contradictions or reinforcements. Users can build specialized knowledge bases for their Spirits, create themed personal wikis, and extract structured data from web URLs. 

Additionally, the platform enables the transformation of Spirit conversation archives into permanent knowledge. A core feature is relationship discovery, which uses analysis to find deep connections across diverse data sources. Finally, the document highlights the ability to share these curated knowledge graphs with friends, teams, or the public through the CQ Share feature. Overall, the system is designed to help users visualize, connect, and distribute complex information efficiently.


id: c2108434-8b74-46a0-845d-5abb287a9cec
summary: Section: Memory Pack (.cqmpack)
category: knowledge
created_at: 2026-03-12 13:26:03
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 7:17
content:
Document: Memory Pack (.cqmpack)

The document outlines the structure and functionality of Memory Packs (.cqmpack) and Memory Libraries (.cqmlib) within the CitadelQuest ecosystem. Memory Packs serve as self-contained, portable units of knowledge that include flexible tags for filtering and search, as well as the original source content from which the information was extracted. These packs are designed for easy portability, allowing them to be shared seamlessly between different users and Citadels.

Complementing the packs is the Memory Library (.cqmlib), which acts as an organizational framework for grouping multiple Memory Packs together. The library provides users with management tools to enable or disable specific packs, establish search priorities to determine which information is accessed first, and utilize tagging for efficient categorization. Together, these components provide a structured and modular approach to managing and sharing digital knowledge.


id: 84185171-3b5f-487e-b788-38c288c23e88
summary: Section: Memory Library (.cqmlib)
category: knowledge
created_at: 2026-03-12 13:26:24
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 18:23
content:
Document: Memory Library (.cqmlib)

The document defines the Memory Node, which serves as the fundamental unit of knowledge within the Memory Library (.cqmlib) system. Each node is composed of four primary attributes: the core information known as Content, a brief Summary for graph visualization, and a specific Category classification—which includes knowledge, facts, preferences, thoughts, conversations, or internet data. Additionally, each node features an Importance metric that determines its current relevance; this value is subject to decay over time if the memory is not actively accessed.


id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
summary: Section: Memory Node Structure
category: knowledge
created_at: 2026-03-12 13:26:51
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 24:31
content:
Document: Memory Node Structure

The document, titled "Memory Node Structure," outlines the organizational framework for memory nodes, specifically focusing on source tracking and relational mapping. A key feature of this structure is the ability to track the origin of each memory, ensuring data integrity and context. Furthermore, the document details how nodes are interconnected through specific relationship types. Currently, it highlights the "RELATES_TO" connection, which signifies a general semantic link between nodes and is visually represented by a blue edge in the system's interface. This structure facilitates a organized, traceable, and visually categorized network of information.


id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
summary: Section: Relationship Types
category: knowledge
created_at: 2026-03-12 13:27:18
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_range: 32:37
content:
Document: Relationship Types

This document outlines three specific relationship types used to categorize and visualize connections between pieces of information. Each relationship is defined by its function and an associated color-coded edge for visual representation. The "REINFORCES" relationship, indicated by a green edge, is used for supporting or confirming information. The "CONTRADICTS" relationship, marked with a red edge, identifies conflicting data. Finally, the "PART_OF" relationship, represented by a white or grey edge, denotes a hierarchical parent-child structure. The document serves as a concise legend for understanding how different data points interact within a system or diagram.


id: ac49a47f-9772-4591-932c-4504d4ce6a1b
summary: Document: 05-file-browser.md
category: knowledge
created_at: 2026-03-12 13:33:40
last_accessed: 2026-04-01 03:39:27
source_type: document_summary
source_ref: general:/CQ-User-Manual:05-file-browser.md
source_range: 1:87
content:
Document: 05-file-browser.md

The File Browser serves as the personal cloud storage system within the CitadelQuest platform, located at the `/file-browser` route. It provides users with a secure, self-hosted environment where files are stored on their own server and remain inaccessible to other users. The interface features a switchable Tree View for hierarchical navigation and a File Preview pane that displays metadata, action buttons, and content previews for formats such as PDF, images, and Markdown.

Users can perform standard file operations including uploading via drag-and-drop, creating new folders or files, renaming, and deleting. Additionally, the system supports downloading individual files or entire directories as ZIP archives. A sharing feature allows users to generate "CQ Share" links for public access or restricted sharing with specific CQ Contacts.

A key highlight is the deep AI integration, where Spirits utilize specialized tools to read, create, edit, and manage files on the user's behalf. This allows for automated tasks like organizing directories or summarizing uploaded documents. The File Browser is fully responsive for mobile use and provides a storage breakdown on the Dashboard to track usage across database, user data, and backups.


id: 9fc3589c-f983-4f00-8ed1-296e059d7fac
summary: Section: Introduction to File Browser
category: knowledge
created_at: 2026-03-12 13:34:08
last_accessed: 2026-04-01 03:39:18
source_type: document
source_ref: general:/CQ-User-Manual:05-file-browser.md
source_range: 1:8
content:
Document: Introduction to File Browser

The File Browser serves as a personal cloud storage solution integrated directly within the CitadelQuest platform. Located at the route /file-browser, this tool allows users to store files on their own private server, ensuring data sovereignty and constant accessibility. A key feature of the File Browser is its full integration with AI Spirits, enabling these digital assistants to interact with and manage the user's stored data. It functions as a secure, private alternative to traditional cloud services, keeping all information within the user's decentralized environment.


id: 697c5176-557a-4939-bbbd-f565956940af
summary: Section: Interface and Views
category: knowledge
created_at: 2026-03-12 13:34:29
last_accessed: 2026-04-01 03:39:27
source_type: document
source_ref: general:/CQ-User-Manual:05-file-browser.md
source_range: 9:22
content:
Document: Interface and Views

The Interface and Views document details the two primary navigation modes available within the File Browser. Users can switch between these modes using toggle buttons to suit their workflow. The Tree View provides a hierarchical representation of the complete folder structure, allowing for easy navigation through expanding and collapsing folders and direct file selection. Complementing this is the File Preview feature, which displays essential metadata such as file size and the last modified date. This view also includes integrated action buttons for downloading, renaming, or deleting files, and offers direct content previews for specific file formats, including images, PDFs, Markdown (md), and plain text (txt) files.


id: ff00df6c-c3e8-4a0d-8fb9-33ee914ccc57
summary: Section: File Operations
category: knowledge
created_at: 2026-03-12 13:34:47
last_accessed: 2026-03-23 20:24:03
source_type: document
source_ref: general:/CQ-User-Manual:05-file-browser.md
source_range: 23:53
content:
Document: File Operations

The "File Operations" document provides a comprehensive guide on managing data within the CitadelQuest environment. It outlines several core functionalities, starting with the process for uploading files via a dedicated button or drag-and-drop interface. Users can organize their workspace by creating new folders or generating empty files, which can then be edited manually or populated with content by their Spirit. 

The guide also details maintenance tasks such as renaming, deleting, and downloading files. Notably, users have the option to download entire directories as ZIP files. Finally, the document explains the sharing mechanism, where users can generate CQ Share links for their files. These links offer granular privacy controls, allowing for either public access or restricted sharing limited to specific CQ Contacts. This set of tools ensures users have full control over their personal data storage and collaboration capabilities.


id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
summary: Section: AI Integration and Spirit Tools
category: knowledge
created_at: 2026-03-12 13:35:15
last_accessed: 2026-04-01 03:29:32
source_type: document
source_ref: general:/CQ-User-Manual:05-file-browser.md
source_range: 54:71
content:
Document: AI Integration and Spirit Tools

The document "AI Integration and Spirit Tools" details the functional capabilities of Spirits within the CitadelQuest ecosystem, specifically focusing on their interaction with the File Browser. Spirits are equipped with a suite of AI tools that allow them to read, create, edit, and manage files, as well as browse directory structures to understand a user's data organization. These capabilities enable Spirits to perform practical tasks such as generating shopping lists, summarizing uploaded documents, updating existing files with new information, and organizing files into topic-based folders. This integration ensures that the AI can act as a hands-on assistant for data management and content creation within the user's private environment.


id: d68be241-4b63-4c48-8309-69a2950cf0af
summary: Section: Mobile Support and Storage Architecture
category: knowledge
created_at: 2026-03-12 13:35:41
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:05-file-browser.md
source_range: 72:87
content:
Document: Mobile Support and Storage Architecture

The document outlines the mobile compatibility and storage architecture of the CitadelQuest File Browser. It highlights that the interface is fully responsive and optimized for mobile devices through touch-friendly controls, icon-based navigation, and layouts that adapt to various screen sizes. Regarding storage, files are kept in a personal data directory on the server, with usage statistics for the database, user data, and backups visible on the Dashboard. A critical security feature is the per-user storage isolation, which ensures that files remain private and inaccessible to other users on the same Citadel.


id: b55220a6-be4e-41cf-a5b2-479ae9733feb
summary: Document: 06-cq-chat.md
category: knowledge
created_at: 2026-03-12 13:37:06
last_accessed: 2026-03-22 17:23:03
source_type: document_summary
source_ref: general:/CQ-User-Manual:06-cq-chat.md
source_range: 1:55
content:
Document: 06-cq-chat.md

CQ Chat is a private, encrypted messaging feature within the CitadelQuest platform that enables direct communication between users across different instances via a decentralized Federation protocol. By bypassing corporate servers, messages travel straight from one Citadel to another over HTTPS, secured by CQ Contact API Keys, and are stored exclusively on the sender's and receiver's personal databases.

Users can access the service through the /cq-chat route or a navigation dropdown that displays recent conversations, unseen message counts, and a "New Chat" button. The full interface provides a comprehensive view with a conversation list, active message history, and timestamps. Key features include real-time text delivery, group chat support for multiple participants, image attachments, and read indicators. The system utilizes a global updates endpoint to poll for new messages in real-time, ensuring a seamless and secure user experience while maintaining strict data sovereignty and privacy.


id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
summary: Section: Introduction to CQ Chat
category: knowledge
created_at: 2026-03-12 13:37:19
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:06-cq-chat.md
source_range: 1:8
content:
Document: Introduction to CQ Chat

CQ Chat is a private messaging feature within the CitadelQuest platform that facilitates direct, encrypted communication between users across different instances. The system utilizes a decentralized architecture where messages travel directly from one Citadel to another, bypassing corporate servers to ensure privacy and data sovereignty. This peer-to-peer approach aligns with the platform's commitment to secure, uncensored interaction. Users can access this messaging interface via the specific route /cq-chat. The document emphasizes that the protocol is designed for secure, federation-based communication, maintaining the user's control over their personal data and interactions without third-party oversight.


id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
summary: Section: Accessing the Chat Interface
category: knowledge
created_at: 2026-03-12 13:37:50
last_accessed: 2026-03-22 17:23:29
source_type: document
source_ref: general:/CQ-User-Manual:06-cq-chat.md
source_range: 9:27
content:
Document: Accessing the Chat Interface

The document "Accessing the Chat Interface" outlines two primary methods for users to access and manage their conversations within the CQ Chat system. 

The first method is through the Navigation Dropdown, accessible by clicking the chat icon in the top navigation bar. This interface provides a quick view of recent conversations, including previews of the latest messages and a green badge indicating the count of unseen messages. It also features a "New Chat" button for initiating new discussions and allows users to open specific conversations directly from the list.

The second method is the Full Chat Page, located at the URL path /cq-chat. This dedicated interface offers a more comprehensive experience, featuring a conversation list on the left side of the screen and the active conversation window on the right. This view provides access to the full message history, including specific timestamps for each message. Together, these options ensure users can efficiently monitor their communications and engage in detailed interactions within the CitadelQuest platform.


id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
summary: Section: Conversation Management and Features
category: knowledge
created_at: 2026-03-12 13:38:04
last_accessed: 2026-03-22 17:23:29
source_type: document
source_ref: general:/CQ-User-Manual:06-cq-chat.md
source_range: 28:46
content:
Document: Conversation Management and Features

The document "Conversation Management and Features" provides a guide for using the CQ Chat system. It outlines the process for initiating a conversation, which involves clicking the New Chat icon, selecting a contact from the CQ Contacts list, and typing a message. The platform supports both direct messaging and group chats involving participants from various Citadels. Key messaging features include real-time text delivery, the ability to attach images, and the inclusion of timestamps for each message. Additionally, the system provides status tracking through read indicators and an "unseen count" badge to notify users of unread messages. The document serves as a functional overview of the communication tools available within the CitadelQuest ecosystem.


id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
summary: Section: Technical Architecture and Privacy
category: knowledge
created_at: 2026-03-12 13:38:22
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:06-cq-chat.md
source_range: 47:55
content:
Document: Technical Architecture and Privacy

The document outlines the technical architecture and privacy framework of CQ Chat, which utilizes the CitadelQuest Federation protocol for cross-instance communication. This decentralized system enables messages to be sent directly between individual Citadels over HTTPS, secured by CQ Contact API Keys. Real-time message delivery is facilitated by browser polling via a global updates endpoint. A core feature of this architecture is its commitment to data sovereignty; messages are stored exclusively on the sender's and receiver's personal databases. By eliminating a central relay server, the system ensures that no intermediary can access or store user communications, maintaining a high standard of privacy and security.


id: e3562b91-45ea-49ec-a6ae-2f1d2c256c3d
summary: Document: 08-cq-share.md
category: knowledge
created_at: 2026-03-12 13:43:29
last_accessed: 2026-04-01 03:39:18
source_type: document_summary
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 1:211
content:
Document: 08-cq-share.md

CQ Share is a core feature of the CitadelQuest platform that enables users to share files and knowledge with others. Located at the `/share` route, the system supports two primary sharing scopes: Public, which allows access via a clean URL without a login, and CQ Contacts, which requires authentication via API keys. Users can share any file from their File Browser or specialized CQ Memory Packs, which are knowledge graphs that support automatic synchronization between Citadels.

The management interface allows users to track views, toggle the active status of shares, and customize how content is presented using three display styles: Full, Preview, or Hidden. Additionally, users can add Markdown descriptions and adjust their positioning relative to the content. A significant organizational feature is Share Groups, which allows users to categorize shared items into named, icon-coded collections that appear as tabbed navigation on their public profile or in CQ Explorer.

Creating a share is integrated across the platform, accessible from the File Browser, Memory Explorer, or the dedicated Share page. For Memory Packs, the system provides a powerful auto-sync capability, ensuring that contacts who download a pack always receive the latest updates from the source. While shares can be paused or deleted to revoke access, the original underlying files remain securely stored in the user's personal database.


id: 30770643-51d9-4460-8d73-acbeeea5ee5d
summary: Section: Management and Creation
category: knowledge
created_at: 2026-03-12 13:44:49
last_accessed: 2026-04-01 03:39:18
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 25:72
content:
Document: Management and Creation

The document "Management and Creation" outlines the functionality and procedures for managing and generating shared content within the CitadelQuest ecosystem. The CQ Share management page provides a centralized dashboard where users can monitor their shared items, including files and Memory Packs. This interface displays critical metadata such as titles, sharing scope (Public or CQ Contacts), access URLs, view counters, and current status (Active or Paused). Users can also customize the display style and provide markdown descriptions for their shared content. To facilitate organization, the page includes search and filtering tools based on title, type, and status.

The document also details three primary methods for creating a share. First, users can share directly from the File Browser by selecting a file and configuring its title and scope. Second, shares can be initiated from the Memory Explorer by selecting a specific Memory Pack and using the management dropdown menu. Finally, users can create shares through the dedicated CQ Share page by selecting an item from their File Browser and configuring a custom URL slug. Regardless of the method, the system automatically generates a share URL once the configuration is saved, making the content live according to the defined access permissions.


id: d92f6c51-6e01-479d-83ca-d660824e27b7
summary: Section: URLs and Display Configuration
category: knowledge
created_at: 2026-03-12 13:45:29
last_accessed: 2026-03-23 20:26:39
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 73:113
content:
Document: URLs and Display Configuration

This document outlines the configuration options for sharing items within the CitadelQuest platform, focusing on URL structures, display styles, and descriptions. Each shared item is assigned a clean, customizable URL based on the user's domain and username. Public shares are accessible via these links and display inline by default, though a download can be forced using a specific URL parameter. Conversely, shares intended for specific CQ Contacts require authentication.

Users can control how their shared content appears on their profile and in the CQ Explorer through three primary display styles: Full, which renders content like images and HTML inline; Preview, which provides compact excerpts and thumbnails; and Hidden, which lists the item without a content preview. These styles can be managed individually or overridden at a group level. Additionally, users can add Markdown-based descriptions to their shares. The layout of these descriptions is highly flexible, allowing for placement above, below, or to either side of the primary content to customize the visual presentation for visitors.


id: a4102387-181b-467a-9de7-edeb48f554e0
summary: Section: URLs and Display Configuration
category: knowledge
created_at: 2026-03-12 13:45:53
last_accessed: 2026-03-23 20:26:39
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 73:113
content:
Document: URLs and Display Configuration

This document outlines the configuration options for shared items within the CitadelQuest platform, focusing on URL structures, display styles, and descriptions. Each shared item is assigned a unique, readable URL based on the user's domain and a customizable slug. Public shares are accessible via link and display inline by default, though a download can be forced using a specific URL parameter. In contrast, shares intended for specific CQ Contacts require authentication.

Users can manage how their content appears on their profile and in the CQ Explorer through three distinct display styles: Full, which renders content inline with full-size images and visualizations; Preview, which provides compact excerpts and thumbnails; and Hidden, which lists the item without a content preview. These styles can be applied individually or managed at a group level. Additionally, users can enhance shared items with Markdown-based descriptions. The layout of these descriptions is highly flexible, allowing for placement above, below, or to either side of the primary content to suit the user's presentation needs.


id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
summary: Section: Share Groups and Profile Content
category: knowledge
created_at: 2026-03-12 13:46:06
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 114:153
content:
Document: Share Groups and Profile Content

Share Groups, managed under the Profile Content section of CitadelQuest settings, allow users to organize shared items into named and ordered collections. These groups function as tabbed navigation elements on a user's public profile and within the CQ Explorer. To create a group, users navigate to the settings route and configure details such as the group title, icon, color, URL slug, and visibility levels, which range from public access to specific contacts.

Once a group is established, users can populate it by selecting existing active shares and dragging them to set a specific display order. The system provides granular control over how items appear within a group, offering options to inherit the original share's style or override it with Full, Preview, or Hidden display modes. Ultimately, these groups enhance the user experience by providing a structured, visual way for visitors to browse different sections of a profile, utilizing icons and titles to distinguish between various content categories like introductions or projects.


id: 4d8a2d04-0376-4274-818b-160b12166db4
summary: Section: Share Groups and Profile Content
category: knowledge
created_at: 2026-03-12 13:46:39
last_accessed: 2026-04-01 03:33:34
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 114:153
content:
Document: Share Groups and Profile Content

Share Groups, managed under the Profile Content section of CitadelQuest settings, allow users to organize shared items into named and ordered collections. These groups function as tabbed navigation on a user's public profile and within the CQ Explorer. To create a group, users navigate to the settings route `/settings/share-groups`, where they can configure the group title, icon, color, and a URL-friendly slug. Visibility settings are flexible, allowing groups to be set as Public, restricted to CQ Contacts, or limited to specific individuals.

Once a group is created, users can add existing active shares and drag them to reorder the content. The system provides granular display controls, allowing users to inherit the original share's style or override it with Full, Preview, or Hidden settings for that specific group. Visually, these groups appear as interactive tabs below the profile header on public pages and within the main content area of the CQ Explorer, utilizing the chosen icons and titles to help visitors browse different sections of the user's shared content.


id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
summary: Section: Share Groups and Profile Content
category: knowledge
created_at: 2026-03-12 13:46:39
last_accessed: 2026-04-01 03:33:34
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 114:153
content:
Document: Share Groups and Profile Content

Share Groups, managed under the Profile Content section of CitadelQuest settings, allow users to organize shared items into named and ordered collections. These groups function as tabbed navigation on a user's public profile and within the CQ Explorer. To create a group, users navigate to the settings route `/settings/share-groups`, where they can configure the group title, icon, color, URL slug, and visibility levels—ranging from Public to specific CQ Contacts.

Once a group is created, users can add existing active shares and drag them to reorder the content. The system provides granular display controls, allowing users to inherit the original share's style or override it with Full, Preview, or Hidden settings specifically for that group. On the front end, these groups are presented as interactive tabs below the profile header, enabling visitors to browse different sections of content, such as introductions or projects, with ease. This feature enhances the presentation of a user's personal Citadel by providing a structured, visual way to showcase information and files.


id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
summary: Section: Memory Pack Auto-Sync
category: knowledge
created_at: 2026-03-12 13:46:52
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 154:173
content:
Document: Memory Pack Auto-Sync

The document "Memory Pack Auto-Sync" outlines the functionality and practical applications of the auto-sync feature within the CitadelQuest (CQ) ecosystem. This feature allows for the seamless distribution and maintenance of shared knowledge across different Citadels.

The process begins when a user shares a Memory Pack via CQ Share. Once a CQ Contact downloads this pack to their own Citadel, the system retains a connection to the source URL. This link enables the downloaded pack to automatically check for updates every time the recipient opens their Memory Explorer. If the original creator adds new information or knowledge to the source pack, those updates are synchronized automatically to the contact's version.

Key use cases for this technology include maintaining shared knowledge bases where contacts always possess the most current information, managing team documentation for projects, and distributing curated learning materials or knowledge graphs to friends and students. By leveraging auto-sync, CQ ensures that collaborative data remains consistent and up-to-date across the decentralized network without requiring manual downloads for every update.


id: 02619512-3802-40c7-9fd4-13edfcdbf655
summary: Section: Maintenance and Lifecycle
category: knowledge
created_at: 2026-03-12 13:47:14
last_accessed: 2026-03-23 20:26:39
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 174:195
content:
Document: Maintenance and Lifecycle

The document "Maintenance and Lifecycle" outlines the procedures for managing shared content within the CitadelQuest platform. It details three primary actions: editing, pausing, and deleting shares. When editing a share, users can modify the title, URL slug, visibility scope (Public or CQ Contacts), and display style. Additionally, users can update the optional markdown description and its layout position. Pausing a share toggles its status to inactive, which results in a 404 error for viewers without deleting the underlying data. Similarly, deleting a share entry removes the access link but ensures the original file or memory pack remains intact within the user's File Browser. The guide emphasizes that these lifecycle management tools only affect the sharing metadata and accessibility, preserving the source content throughout all administrative changes.


id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
summary: Section: Memory Pack Auto-Sync
category: knowledge
created_at: 2026-03-12 13:47:29
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 154:173
content:
Document: Memory Pack Auto-Sync

The document "Memory Pack Auto-Sync" explains the automated synchronization feature within the CitadelQuest (CQ) ecosystem. This functionality allows shared Memory Packs to remain updated across different Citadels without manual intervention. The process begins when a user shares a Memory Pack via CQ Share and a contact downloads it. Because the downloaded pack retains a reference to its source URL, it automatically checks for updates every time the recipient opens their Memory Explorer. If the original creator adds new knowledge or modifications, those changes are synced to the contact's version automatically.

The document highlights several practical use cases for this technology, including the maintenance of shared knowledge bases, the distribution of up-to-date team documentation for projects, and the sharing of curated learning materials or knowledge graphs with students and friends. Ultimately, auto-sync ensures that all collaborators and contacts possess the most current version of information, fostering seamless knowledge sharing and consistency across the decentralized network.


id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
summary: Section: Memory Pack Auto-Sync
category: knowledge
created_at: 2026-03-12 13:47:29
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 154:173
content:
Document: Memory Pack Auto-Sync

The document "Memory Pack Auto-Sync" outlines the functionality and practical applications of the auto-sync feature within CitadelQuest's Memory Pack sharing system. The process begins when a user shares a Memory Pack via CQ Share, which a CQ Contact then downloads to their own Citadel. Because the downloaded pack retains its source URL, it possesses the ability to automatically check for updates whenever the recipient opens their Memory Explorer. If the original creator adds new knowledge or updates the source pack, these changes are synchronized automatically to the contact's version.

The document highlights several key use cases for this technology, emphasizing its utility in maintaining shared knowledge bases where contacts always require the latest information. It is also presented as an effective tool for team documentation, ensuring project knowledge remains current across different Citadels. Additionally, the feature is ideal for educational purposes, allowing for the distribution of curated learning materials and knowledge graphs to friends or students that stay up to date without manual intervention. This system ensures seamless information flow and data consistency between collaborators within the CitadelQuest ecosystem.


id: 1d3da196-26b2-4575-8d68-23713a1ac801
summary: Section: Profile Integration and CQ Explorer
category: knowledge
created_at: 2026-03-12 13:47:42
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 196:211
content:
Document: Profile Integration and CQ Explorer

This document outlines how public shares are integrated into a user's CQ Profile and accessed via the CQ Explorer. Users with an enabled public profile page can display their shared content in two formats: organized Share Groups, which use tabbed sections, or a flat Shared items list. These display options can be toggled independently within the profile visibility settings. Additionally, the CQ Explorer allows users to browse other profiles to view their public shared items and content groups. Through this interface, users can directly download files and Memory Packs from other profiles to their own Citadel. The integration facilitates seamless content discovery and data portability between different users within the CitadelQuest ecosystem.


id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
summary: Section: Maintenance and Lifecycle
category: knowledge
created_at: 2026-03-12 13:47:57
last_accessed: 2026-03-23 20:26:39
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 174:195
content:
Document: Maintenance and Lifecycle

The document "Maintenance and Lifecycle" outlines the procedures for managing shared content within the CitadelQuest ecosystem. It details three primary actions: editing, pausing, and deleting shares. When editing, users can modify the share's title, URL slug, and description, as well as adjust the visibility scope between Public and CQ Contacts. Users also have control over the display style and the positioning of the description text.

The document explains that shares can be toggled between active and paused states; pausing a share makes it return a 404 error without deleting the underlying data. Similarly, deleting a share entry removes the access link but ensures the original file or memory pack remains intact within the user's File Browser. This system allows for flexible management of shared resources while maintaining data integrity and security.


id: de432f8f-e033-4e6e-a579-b189ccd74095
summary: Section: CQ Share Management Page Overview
category: knowledge
created_at: 2026-03-12 13:48:03
last_accessed: 2026-04-01 03:39:18
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 25:37
content:
Document: CQ Share Management Page Overview

The CQ Share Management Page Overview document outlines the specific procedures for sharing content within the CitadelQuest ecosystem. Users can initiate sharing from two primary locations: the File Browser and the Memory Explorer. When sharing from the File Browser, a user selects a file and uses the share action button to define a title and set the visibility scope to either Public or CQ Contacts, which triggers the automatic generation of a shareable URL. Similarly, through the Memory Explorer, users can select a specific Memory Pack and utilize the management dropdown menu to access the sharing interface. In both workflows, the user is required to designate a title and determine the accessibility scope to manage how their data is distributed. This process ensures that both files and memory assets can be securely shared with specific contacts or the broader public according to the user's preference.


id: c948f87d-5941-4d4d-84a2-98e896b44105
summary: Section: Profile Integration and CQ Explorer
category: knowledge
created_at: 2026-03-12 13:48:18
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 196:211
content:
Document: Profile Integration and CQ Explorer

The document outlines how public shares are integrated into the CQ Profile and accessed via the CQ Explorer. Users with an enabled public page can display their shared content in two distinct ways: through organized Share Groups, which utilize tabbed sections for better structure, or via a flat Shared items list. These display options can be toggled independently within the profile visibility settings. Furthermore, the CQ Explorer allows users to browse these public shares on other profiles, facilitating the direct download of files and Memory Packs to their own Citadel. This integration ensures that shared content is both manageable for the profile owner and easily accessible for other users within the ecosystem.


id: 7aad6489-13dd-456e-8007-5a38afcbac2e
summary: Section: Search & Filter Functionality
category: knowledge
created_at: 2026-03-12 13:48:20
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 38:46
content:
Document: Search & Filter Functionality

This document outlines the step-by-step process for utilizing the search and filter functionality within the CQ Share page. To initiate a share, users must navigate to the specific share route, select the "Create New Share" option, and choose the desired file or memory pack directly from their personal File Browser. The configuration process involves setting a title, defining the scope of access, and establishing a custom URL slug. Once these settings are saved, the shared content becomes live and accessible based on the defined parameters.


id: 033b4c10-b865-4082-b222-2b80e3325247
summary: Section: CQ Share Management Page Overview
category: knowledge
created_at: 2026-03-12 13:48:45
last_accessed: 2026-04-01 03:39:18
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 25:37
content:
Document: CQ Share Management Page Overview

The CQ Share Management Page Overview document outlines the specific procedures for sharing digital assets within the CitadelQuest ecosystem. Users can initiate sharing from two primary locations: the File Browser and the Memory Explorer. 

When sharing from the File Browser, a user selects a specific file and utilizes the share button within the file actions menu. For sharing via the Memory Explorer, the user selects a Memory Pack and accesses the share option through the pack management dropdown menu. Regardless of the starting point, the process requires the user to define a title and set a visibility scope, which can be configured for either the general public or restricted to specific CQ Contacts. Once these parameters are set, the system automatically generates a unique share URL for distribution. The document serves as a functional guide for managing data accessibility and collaboration across different modules of the platform.


id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
summary: Section: Methods for Creating Shares
category: knowledge
created_at: 2026-03-12 13:48:47
last_accessed: 2026-03-23 20:26:39
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 47:48
content:
Document: Methods for Creating Shares

The provided document, titled "Methods for Creating Shares," contains no substantive content or descriptive text beyond its header and structural markers. As the body of the document is empty, it does not outline any specific techniques, protocols, or procedures regarding the creation of digital or financial shares. Consequently, no factual summary of methods can be generated from this source.


id: d0105e38-e572-40e8-9841-f88321a97df3
summary: Section: Search & Filter Functionality
category: knowledge
created_at: 2026-03-12 13:49:12
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:08-cq-share.md
source_range: 38:46
content:
Document: Search & Filter Functionality

This document outlines the step-by-step process for utilizing the search and filter functionality within the CQ Share page. To initiate a share, a user navigates to the share section of the platform and selects the option to create a new entry. The process involves choosing specific content, such as a file or a memory pack, directly from the user's personal File Browser. Once the content is selected, the user must configure essential metadata, including the title, the visibility scope, and a custom URL slug. After saving these configurations, the share becomes active and accessible. The guide serves as a functional walkthrough for managing and deploying shared assets within the CitadelQuest ecosystem.


id: 6f6281f0-0ae6-4ec8-b829-a07b383d2baa
summary: Document: 11-backup.md
category: knowledge
created_at: 2026-03-12 14:04:39
last_accessed: 2026-03-23 20:24:03
source_type: document_summary
source_ref: general:/CQ-User-Manual:11-backup.md
source_range: 1:65
content:
Document: 11-backup.md

The document "11-backup.md" outlines the comprehensive backup and restore system within CitadelQuest, accessible via the /backup route. This system allows users to protect their data by creating .citadel ZIP files, which package the personal database—including settings, conversations, and memories—alongside all user files stored in the File Browser. Users can manage these backups through several key actions: creating new backups, downloading them for off-site storage or migration preparation, and uploading existing files using a chunked uploading method to prevent timeouts with large files.

The restoration process involves confirming a restore action, which replaces the current database and user files with the version from the backup, followed by a page refresh. Users can also delete backups to manage server storage space. The document concludes with best practices, recommending regular backups, keeping local copies on external devices, and performing a fresh backup before any account migration or system update. Users are also encouraged to monitor their storage usage through the Dashboard to ensure sufficient space for these files.


id: f10414d1-5c2c-4f68-9977-d71212e8d9af
summary: Section: Introduction to Backup & Restore
category: knowledge
created_at: 2026-03-12 14:05:00
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:11-backup.md
source_range: 1:8
content:
Document: Introduction to Backup & Restore

The document "Introduction to Backup & Restore" outlines the data protection capabilities within the CitadelQuest platform. It specifies that the system provides a comprehensive backup utility allowing users to create, download, upload, and restore their data at their convenience. This functionality is designed to ensure data security and user sovereignty over their information. Users can access these features through the specific system route located at /backup.


id: ce8748d3-07f3-458d-b031-05996cd7ecc8
summary: Section: Creating a Backup
category: knowledge
created_at: 2026-03-12 14:05:27
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:11-backup.md
source_range: 9:20
content:
Document: Creating a Backup

The document "Creating a Backup" provides a concise guide for users to secure their data within the CitadelQuest platform. To initiate the process, users must navigate to the Backup section (/backup) and select the "Create Backup" option. The system then packages all essential user information into a single archive, including the personal database—which contains settings, conversations, memories, and contacts—as well as all user data files stored in the File Browser. Once the packaging process is finished, the backup is displayed in the user's backup list. These backups are saved on the server in the user's personal backup directory as ZIP files with a .citadel extension, ensuring that all personal data and configurations are preserved and accessible for recovery.


id: 10447049-2745-48a8-a44e-219768498463
summary: Section: Downloading and Uploading Backups
category: knowledge
created_at: 2026-03-12 14:05:54
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:11-backup.md
source_range: 21:40
content:
Document: Downloading and Uploading Backups

This document provides instructions for managing CitadelQuest backups through downloading and uploading procedures. Users can download backups to their local devices by clicking the "Download" button, a practice recommended for off-site storage, account migrations, or as a safety measure before performing major updates. To upload a backup, users must select a ".citadel" ZIP file from their device using the "Upload Backup" feature. For larger files, the system utilizes chunked uploading, which splits the data into smaller pieces to be reassembled on the server, effectively preventing timeout issues during the transfer process.


id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
summary: Section: Restoring and Deleting Backups
category: knowledge
created_at: 2026-03-12 14:06:21
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:11-backup.md
source_range: 41:57
content:
Document: Restoring and Deleting Backups

This document provides instructions for managing backups within the CitadelQuest platform, specifically covering the restoration and deletion processes. To restore a backup, users must click the "Restore" button next to their chosen file and confirm the action. During this process, CitadelQuest automatically restores both the database and the user's data files. Once the restoration is finished, the user should refresh the page to complete the update. Additionally, the document notes that users can permanently remove backups to free up storage space by clicking the "Delete" button next to any specific backup entry.


id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
summary: Section: Best Practices
category: knowledge
created_at: 2026-03-12 14:06:48
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:11-backup.md
source_range: 58:65
content:
Document: Best Practices

The document outlines essential best practices for data management and security within the CitadelQuest platform, focusing primarily on backup procedures. It emphasizes the importance of performing regular backups, particularly before initiating system updates or account migrations, to prevent data loss. Users are advised to maintain redundancy by downloading copies of these backups to local devices or external storage solutions. Additionally, the guide highlights the necessity of monitoring storage capacity through the Dashboard's Storage Usage panel to ensure backup sizes remain within manageable limits. Following these protocols ensures data integrity and a smooth transition during technical changes.


id: 1f4aba06-d24c-48de-90c1-a09640942ada
summary: Document: 12-administration.md
category: knowledge
created_at: 2026-03-12 14:09:31
last_accessed: 2026-03-22 17:23:03
source_type: document_summary
source_ref: general:/CQ-User-Manual:12-administration.md
source_range: 1:111
content:
Document: 12-administration.md

The document "12-administration.md" outlines the features and functionalities of the CitadelQuest Administration panel, accessible to users with Admin privileges at the `/administration` route. The first registered user on an installation is automatically granted admin status. The Admin Dashboard provides a central hub for user statistics, quick actions, and a list of recently registered users.

Key administrative areas include User Management, where admins can search for users, reset passwords, toggle admin roles, or delete accounts. The Application Updates section allows admins to check for GitHub updates and initiate an automated update process that includes safety backups, file updates, and database migrations. System Settings provide controls for enabling or disabling user registration, setting maximum user limits, and configuring a homepage redirect that points unauthenticated visitors to a specific user's public CQ Profile.

Additional technical tools include Server Logs for viewing, downloading, or clearing system logs, and System Backups for managing backup files across all users. Finally, the Migration Requests section allows admins to accept or reject incoming account transfer requests from users on other Citadels. The guide emphasizes the importance of manual backups before performing system updates.


id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
summary: Section: Introduction and Admin Dashboard
category: knowledge
created_at: 2026-03-12 14:09:52
last_accessed: 2026-03-22 17:22:38
source_type: document
source_ref: general:/CQ-User-Manual:12-administration.md
source_range: 1:17
content:
Document: Introduction and Admin Dashboard

The "Introduction and Admin Dashboard" document outlines the core functionality and accessibility of the CitadelQuest Administration panel. Access to this panel is restricted to users with Admin privileges, a status automatically granted to the first person who registers on a new installation. The panel is located at the specific route `/administration`.

The Admin Dashboard serves as a central hub for system oversight, providing three primary categories of information and control. First, it displays user statistics, including the total number of users and recent registration data. Second, it offers quick actions that link directly to essential administrative tasks such as user management, system updates, and general settings. Finally, the dashboard includes a table listing recently registered users for easy monitoring. This document serves as a foundational guide for administrators to navigate and manage their CitadelQuest instance effectively.


id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
summary: Section: User Management
category: knowledge
created_at: 2026-03-12 14:10:14
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:12-administration.md
source_range: 18:35
content:
Document: User Management

The User Management document outlines the administrative functionalities available at the /administration/users route within a Citadel. This interface allows administrators to oversee all registered users through a comprehensive User List, which displays essential data such as usernames, email addresses, assigned roles, and registration dates. To facilitate efficient management, a search feature is included to filter the list by name or email.

The document details four primary User Actions available to administrators. "View Info" opens a modal dialog containing specific user details. "Toggle Admin" allows for the granting or revoking of administrative privileges, though safety protocols prevent users from removing their own admin status. "Reset Password" enables the generation of new credentials for any user. Finally, the "Delete User" function permits the permanent removal of a user and their associated data. To ensure system stability and security, the platform prohibits a user from deleting themselves or removing the final administrator on the Citadel.


id: e233a100-5775-4040-a1b3-7b3fe93470da
summary: Section: Application Updates
category: knowledge
created_at: 2026-03-12 14:10:42
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:12-administration.md
source_range: 36:55
content:
Document: Application Updates

The document outlines the process for checking and installing updates within the CitadelQuest application via the administration route. The update procedure follows a structured four-step sequence initiated by checking for new versions on GitHub. Once a new version is identified, the automated updater performs several critical tasks: it generates a safety backup, downloads the necessary files, and applies updates while ensuring that the user's specific .env configuration remains preserved. Furthermore, the system handles technical maintenance by running database migrations and performing cache management (clearing and warming up) to ensure stability. After the process is complete, a page refresh is required to activate the new version. The document concludes with a security recommendation, advising users to perform a manual backup prior to starting any update as an additional precaution.


id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
summary: Section: System Settings and Homepage Redirect
category: knowledge
created_at: 2026-03-12 14:11:09
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:12-administration.md
source_range: 56:78
content:
Document: System Settings and Homepage Redirect

This document outlines the system-level configuration options available within the admin dashboard for managing user access and homepage behavior. The "User Registration" section details how administrators can toggle new sign-ups on or off and set a maximum user limit to control the Citadel's growth. When registration is disabled, prospective users encounter a notification message. 

The "Homepage Redirect" feature allows administrators to customize the experience for unauthenticated visitors. By selecting a registered user and enabling the redirect, the Citadel’s root URL will automatically point to that individual's public CQ Profile page. This functionality is designed to transform the domain into a personal website or landing page for external visitors, while ensuring that authenticated users are still directed to their private Dashboard upon arrival. Together, these settings provide essential tools for managing both the security and the public-facing identity of a CitadelQuest instance.


id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
summary: Section: Logs and Backups
category: knowledge
created_at: 2026-03-12 14:11:32
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:12-administration.md
source_range: 79:101
content:
Document: Logs and Backups

The "Logs and Backups" document outlines the administrative functionalities for managing server data and system security within the platform. It is divided into two primary sections: Server Logs and System Backups.

The Server Logs section, located at the `/administration/logs` route, provides tools for monitoring system activity. Administrators can list all log files, viewing their size and last modified dates. The interface supports viewing specific file contents through tail/head navigation, downloading logs for offline analysis, and clearing files to manage storage space.

The System Backups section, found at `/administration/system-backups`, focuses on global data preservation. This area allows administrators to manage backup files across all users. Key capabilities include viewing all existing user backups, deleting obsolete or unnecessary files, and monitoring overall backup storage usage. Together, these tools ensure that administrators can maintain system health, perform troubleshooting, and oversee data redundancy across the entire environment.


id: 6c522150-ff8d-42ac-a776-58f6699ff927
summary: Section: Migration Requests
category: knowledge
created_at: 2026-03-12 14:12:00
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:12-administration.md
source_range: 102:111
content:
Document: Migration Requests

The document titled "Migration Requests" outlines the administrative procedures for managing user transfers between different Citadels via the route `/administration/migrations`. It details the specific actions an administrator can take when receiving requests from external users who wish to migrate their accounts to the current instance. Key functionalities include the ability to view all incoming requests, accept them to facilitate a full account transfer, or reject them to decline the migration. Additionally, the interface allows administrators to monitor the real-time progress and status of ongoing migrations to ensure the process is completed successfully.


id: adcf2a61-15b8-45d5-a10d-3f0ff414bff0
summary: Document: 13-installation.md
category: knowledge
created_at: 2026-03-12 14:13:54
last_accessed: 2026-04-01 03:29:32
source_type: document_summary
source_ref: general:/CQ-User-Manual:13-installation.md
source_range: 1:115
content:
Document: 13-installation.md

The document "13-installation.md" provides a comprehensive guide for deploying a personal CitadelQuest instance, emphasizing data sovereignty and privacy. To run the platform, servers require PHP 8.4 or higher, Apache with mod_rewrite, SQLite3, and mandatory HTTPS. The software is compatible with shared hosting, VPS, or dedicated servers, and also offers a Dockerfile for containerized deployment.

The primary installation method is a "Zero-Click" process involving downloading a small installer package from GitHub, uploading `install.php` to a web server, and running it via a browser. This automated script handles downloading the full release, extraction, and directory setup. Once installed, the first registered user is granted Admin privileges. Configuration is managed through a `.env` file, which stores environment settings and database paths while remaining protected during updates.

Post-installation features include an Admin Dashboard for automated updates with safety backups, PWA support for mobile and desktop use, and multi-user capabilities where each user’s data is isolated in a personal SQLite database. To enable AI functionality, users must connect to the CQ AI Gateway, which can be done automatically during registration or manually via an API key. The document concludes by noting that new users receive starting credits for AI services, with options to add more as needed.


id: 02219640-3973-4d9f-bbb1-5c2f490ed3b5
summary: Section: Introduction and Server Requirements
category: knowledge
created_at: 2026-03-12 14:14:06
last_accessed: 2026-03-22 17:23:48
source_type: document
source_ref: general:/CQ-User-Manual:13-installation.md
source_range: 1:17
content:
Document: Introduction and Server Requirements

This document outlines the initial steps and technical prerequisites for installing a personal instance of CitadelQuest, a platform designed to give users complete control over their data and privacy. By running their own "Citadel," users ensure that their server and rules govern their personal information. The system is compatible with various hosting environments, including shared web hosting, Virtual Private Servers (VPS), and dedicated servers.

To successfully deploy the software, the server must meet specific technical requirements: it must run PHP 8.4 or higher and utilize an Apache web server with the mod_rewrite module enabled. Essential PHP extensions include SQLite3 for database management, along with mbstring, intl, json, and zip. Additionally, a secure HTTPS connection is strictly required to ensure the integrity and security of the installation. The document emphasizes that self-hosting is the primary method for achieving true data sovereignty within the CitadelQuest ecosystem.


id: aa033ef6-d33a-4289-9fbb-fb893247be20
summary: Section: Installation Methods
category: knowledge
created_at: 2026-03-12 14:14:20
last_accessed: 2026-04-01 03:33:34
source_type: document
source_ref: general:/CQ-User-Manual:13-installation.md
source_range: 18:52
content:
Document: Installation Methods

The document outlines two primary methods for installing CitadelQuest: the Zero-Click Installer and a Docker-based deployment. The Zero-Click process is designed for simplicity, requiring the user to download a small installer package from GitHub, upload the install.php file to a web server's public directory, and run it via a browser. This automated script handles downloading the latest release, extracting files, and setting up the directory structure. Once complete, the user registers their first account, which is granted Admin privileges, and follows an onboarding wizard to configure the CQ AI Gateway and create their first Spirit. Alternatively, users seeking a containerized environment can utilize the provided Dockerfile, with specific instructions located in the repository's docker/README.md. The guide emphasizes a streamlined setup to get a personal Citadel operational with minimal manual configuration.


id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
summary: Section: Configuration and Domain Setup
category: knowledge
created_at: 2026-03-12 14:15:04
last_accessed: 2026-04-01 03:33:34
source_type: document
source_ref: general:/CQ-User-Manual:13-installation.md
source_range: 53:73
content:
Document: Configuration and Domain Setup

This document outlines the essential configuration and domain setup procedures for a CitadelQuest installation. Key settings are managed via the .env file located in the installation root, which includes the environment status (APP_ENV), a unique APP_SECRET, and the DATABASE_URL, which defaults to a local SQLite path. This configuration file is designed to be preserved during system updates to prevent data loss. For domain integration, users are advised to point their domain to the installation directory and ensure HTTPS is active, utilizing services like Let's Encrypt for certificates. Technical requirements include enabling Apache's mod_rewrite to route traffic through the public index file and ensuring Cloudflare users utilize Full SSL mode for proper connectivity and security.


id: fcec0402-59ac-42bb-b213-6d2270fce582
summary: Section: Maintenance and Updates
category: knowledge
created_at: 2026-03-12 14:15:21
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:13-installation.md
source_range: 74:85
content:
Document: Maintenance and Updates

The Maintenance and Updates document outlines the standardized procedure for managing system updates through the Admin Dashboard. The process is designed for ease of use and data safety, beginning with a manual check for updates within the Administration section. Once initiated, the updater automatically handles the download and application of the new version. To prevent data loss, the system generates a safety backup before any changes are made. The update cycle concludes with automatic database migrations and the clearing and rebuilding of the system cache to ensure optimal performance and compatibility with the new version.


id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
summary: Section: PWA and Multi-User Support
category: knowledge
created_at: 2026-03-12 14:15:37
last_accessed: 2026-03-22 17:22:38
source_type: document
source_ref: general:/CQ-User-Manual:13-installation.md
source_range: 86:105
content:
Document: PWA and Multi-User Support

The document outlines the Progressive Web App (PWA) capabilities and multi-user architecture of the CitadelQuest platform. It highlights that CitadelQuest functions as a PWA, allowing users to install it on Android, iOS, and desktop devices for a fullscreen, app-like experience that includes offline access to cached content. Furthermore, the platform supports multiple users on a single installation while maintaining strict data sovereignty. Each user is assigned a completely isolated SQLite database to ensure privacy. Administrative features include the ability to manage user accounts, reset passwords, toggle registration settings, and configure specific storage limits for the Citadel.


id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
summary: Section: CQ AI Gateway Integration
category: knowledge
created_at: 2026-03-12 14:15:50
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:13-installation.md
source_range: 106:115
content:
Document: CQ AI Gateway Integration

The CQ AI Gateway is a specialized service designed to provide CitadelQuest Spirits with access to advanced AI Large Language Models. Integration can be handled automatically during the user registration process if the "Auto-create CQ AI Gateway accounts" option is selected, or manually by entering an API key within the AI Services section of the application settings. To facilitate immediate use, new users are provided with free starting credits. If additional usage is required, users can purchase more credits through the "Add Credits" button. Further details regarding the service can be found at the official website, cqaigateway.com.


id: faedb97b-90c9-4e41-a60d-1da95f43f13f
summary: Document: CITADELQUEST.md
category: knowledge
created_at: 2026-03-22 13:17:25
last_accessed: 2026-03-23 20:24:03
source_type: document_summary
source_ref: general:/CQ-User-Manual:CITADELQUEST.md
source_range: 1:108
content:
Document: CITADELQUEST.md

CitadelQuest is a free, open-source, and self-hosted platform designed to provide individuals with complete data sovereignty and a secure environment for AI-human collaboration. Described as a "digital fortress," the platform utilizes a decentralized architecture where each user maintains their own independent SQLite database on their own server, making data exploitation by third parties technologically impossible.

Key features include "AI Spirits," which are customizable personal companions capable of managing knowledge through 3D memory graphs and performing tasks via integrated tools. The platform also functions as a decentralized social network, offering encrypted peer-to-peer messaging (CQ Chat), a social feed (CQ Feed), and public profiles that serve as personal websites. Users can manage files through a built-in browser and share content directly with contacts via secure federation protocols.

Technologically, CitadelQuest is built on Symfony 7.4, PHP 8.4, and vanilla JavaScript, featuring a "Zero-Click Installer" for easy deployment on standard hosting services. While the software is free, its AI capabilities are powered by the CQ AI Gateway, which provides access to various LLMs like Claude and Gemini through a pay-per-use model. The project aims to replace the data-harvesting models of "Big Tech" with a transparent, ad-free alternative where users own their content and digital identity.


id: 3b3d40ae-1e59-4d38-9d22-08e02da77b1d
summary: Section: Introduction and Core Philosophy
category: knowledge
created_at: 2026-03-22 13:17:41
last_accessed: 2026-03-22 17:23:48
source_type: document
source_ref: general:/CQ-User-Manual:CITADELQUEST.md
source_range: 1:13
content:
Document: Introduction and Core Philosophy

CitadelQuest is a free, open-source, and self-hosted platform designed to provide users with complete personal data sovereignty and a secure environment for AI-human collaboration. Described as a "digital fortress" or "Citadel," the platform ensures that a user's digital life—including data, AI companions, and communications—remains entirely under their own control. By utilizing independent installations where personal data is stored in a private database on the user's own server, the architecture makes it technologically impossible for third parties to exploit or sell user information.

The core philosophy of the project is built on the total rejection of Big Tech practices, specifically prohibiting ads, tracking, and data collection. Beyond individual data management, CitadelQuest facilitates secure social interaction through a direct, encrypted federation protocol. This allows users to connect with friends across different Citadels without the need for intermediary corporate servers. Ultimately, the document presents CitadelQuest as a decentralized alternative to traditional social networks, prioritizing privacy, security, and user agency in the digital age.


id: bef64406-3a00-47dc-a94c-2760f5e2c9c9
summary: Section: Personal Space Features
category: knowledge
created_at: 2026-03-22 13:17:51
last_accessed: 2026-04-01 03:39:27
source_type: document
source_ref: general:/CQ-User-Manual:CITADELQUEST.md
source_range: 14:24
content:
Document: Personal Space Features

The document outlines the core features of the Personal Space within the CitadelQuest platform, focusing on three primary components: AI Spirits, CQ Memory, and the File Browser. AI Spirits serve as personal companions with distinct personalities and memory, capable of performing tasks like image generation and file management. These spirits are powered by the CQ AI Gateway, which supports various models such as Claude and Gemini through a pay-per-use system.

CQ Memory introduces interactive 3D knowledge graphs that allow users to extract and structure information from documents, web pages, and chats. This system acts as a persistent context for AI Spirits, ensuring continuity across different conversations, and allows for knowledge sharing between friends. Finally, the File Browser functions as a personal cloud service where users can store and organize data on their own server. AI Spirits have the capability to interact with these files by reading, creating, or editing them, and users have the option to share this content publicly or with specific contacts. Together, these features create a decentralized environment for personal data management and AI-human collaboration.


id: 1b46ce86-a60f-42b1-8c33-10311372c1dc
summary: Section: Social Network Capabilities
category: knowledge
created_at: 2026-03-22 13:18:20
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:CITADELQUEST.md
source_range: 25:38
content:
Document: Social Network Capabilities

The Social Network capabilities of CitadelQuest provide a decentralized suite of tools for identity, communication, and content sharing. At the core is the CQ Profile, which serves as a public identity hosted on the user's personal domain, allowing for extensive customization including bios, themes, and Spirit showcases. Users can discover and connect with others through the CQ Explorer, which facilitates friend requests and connection management across different Citadels.

Social interaction is driven by the CQ Feed and CQ Chat. The CQ Feed offers a decentralized alternative to traditional social media, supporting Markdown, reactions, and real-time updates while ensuring content remains on the user's server and travels via federation. For private communication, CQ Chat provides encrypted, peer-to-peer messaging secured by API keys, with data stored exclusively on the participants' Citadels. Additionally, the CQ Follow feature allows for one-way subscriptions to public profiles with real-time notifications. Finally, CQ Share enables the organization and distribution of files and knowledge graphs, allowing users to transform their Citadel into a functional personal website by grouping shared content into navigable tabs on their profile.


id: a2199fe4-58db-4c75-8fa7-111aecad3609
summary: Section: Infrastructure and Deployment
category: knowledge
created_at: 2026-03-22 13:18:42
last_accessed: 2026-03-22 17:23:03
source_type: document
source_ref: general:/CQ-User-Manual:CITADELQUEST.md
source_range: 39:51
content:
Document: Infrastructure and Deployment

The Infrastructure and Deployment document outlines the technical foundation and user-accessibility features of the CitadelQuest platform. A primary highlight is the Zero-Click Installer, a compact 8 KB tool designed for rapid deployment across various environments, including shared hosting, VPS, and dedicated servers. To ensure long-term maintenance and security, the system includes built-in one-click updates featuring automatic safety backups.

Data management is prioritized through a robust Backup & Restore system that handles both databases and files. This system utilizes chunked uploads for large datasets and facilitates seamless account migration between Citadels, including automatic notifications for contacts. For mobile and desktop accessibility, the platform is built as a Progressive Web App (PWA), allowing for an app-like installation on iOS, Android, and desktop devices. Finally, the document notes that the interface supports a diverse range of languages, including English, Spanish, Czech, Italian, Hungarian, Norwegian, Polish, and Slovak.


id: 5fbdbda3-c2ca-45ea-8312-645ae00f1c2d
summary: Section: Technical Architecture
category: knowledge
created_at: 2026-03-22 13:18:56
last_accessed: 2026-03-23 20:24:03
source_type: document
source_ref: general:/CQ-User-Manual:CITADELQUEST.md
source_range: 52:71
content:
Document: Technical Architecture

The Technical Architecture document outlines the foundational principles and technology stack of the CitadelQuest platform, emphasizing a decentralized and security-first approach. The architecture is built on the principle of complete data isolation, utilizing one SQLite database per user to ensure personal data sovereignty. The system is fully decentralized and self-hosted, allowing each "Citadel" to operate independently without a central authority or single point of failure. Communication between Citadels is handled via a direct HTTPS federation protocol secured by CQ Contact API keys.

Technologically, the backend is powered by Symfony 7.4 and PHP 8.4 running on Apache, while the frontend utilizes modern vanilla JavaScript, Bootstrap CSS, and Three.js for 3D visualizations. The platform is open-source and designed to have no external dependencies, though it offers optional AI integration through the CQ AI Gateway. This gateway provides access to various Large Language Models, including Claude, Gemini, and Grok, while maintaining a strict policy of zero data retention. Overall, the architecture is designed to provide a private, auditable, and user-controlled environment for AI-human collaboration.


id: 33b56ac5-5b94-4aa5-bdc7-c8e7e2716b08
summary: Section: The Vision
category: knowledge
created_at: 2026-03-22 13:19:08
last_accessed: 2026-03-23 20:24:03
source_type: document
source_ref: general:/CQ-User-Manual:CITADELQUEST.md
source_range: 72:85
content:
Document: The Vision

The Vision outlines the foundational philosophy of CitadelQuest, a platform built on the core principle of absolute data sovereignty. It presents a direct alternative to the data-harvesting practices of major technology corporations by utilizing a decentralized architecture that makes personal data exploitation technologically impossible. The document emphasizes that the platform is more than a privacy utility; it is a space for meaningful Human-AI collaboration. Within this ecosystem, AI "Spirits" act as personal companions that manage knowledge and grow with the user while remaining exclusively under the user's control rather than a corporation's. Furthermore, CitadelQuest establishes a new model for social networking that is decentralized, ad-free, and devoid of manipulative algorithms. By removing corporate intermediaries and profit-driven motives from personal relationships, the platform ensures that users own their content and maintain total agency over their digital lives. The overarching message is summarized by the mantra: "Your Citadel. Your data. Your rules."


id: aab019ea-28a4-4602-b64d-751a85579629
summary: Section: Getting Started and Support
category: knowledge
created_at: 2026-03-22 13:19:30
last_accessed: 2026-03-22 17:23:55
source_type: document
source_ref: general:/CQ-User-Manual:CITADELQUEST.md
source_range: 86:108
content:
Document: Getting Started and Support

The "Getting Started and Support" document provides essential entry points and resources for the CitadelQuest platform. Users can begin exploring immediately via the free public instance at one.citadelquest.world or choose to host their own private instance by downloading an 8 KB installer from the project's GitHub Releases page. The document emphasizes that CitadelQuest is an open-source, privacy-first platform that remains free forever.

For further information and community engagement, the text directs users to the official website (www.citadelquest.com), their GitHub repository, and their X profile (@H_CitadelQuest). Direct inquiries can be sent to info@citadelquest.email. Development of the platform is sustained through the CQ AI Gateway, which provides fair-priced AI services to power the platform's "Spirits." The project is a collaborative effort between humans and AI, focusing on data sovereignty and user privacy.


id: 166053ba-a674-4a75-9e1f-390dc0e1e44c
summary: Document: 09-cq-profile.md
category: knowledge
created_at: 2026-03-22 17:42:10
last_accessed: 2026-04-01 03:39:27
source_type: document_summary
source_ref: general:/CQ-User-Manual:09-cq-profile.md
source_range: 1:182
content:
Document: 09-cq-profile.md

The CQ Profile document details the public identity system within CitadelQuest, which allows users to create a personalized landing page on their own Citadel domain. Accessible via the route `/{username}`, this public profile serves as a central hub where visitors can view a user's photo, bio (supporting Markdown and HTML), follower count, and shared content groups. A key feature is the Spirit showcase, which displays the user's AI companions, including their names, levels, and experience points.

Users manage these features through the `/settings/profile` route, which is divided into two main sections. The Public Profile Page tab controls visibility toggles for the profile photo, shared item lists, and Spirit display modes (Off, Primary only, or All). It also allows for visual customization through built-in themes like "Night Forest" and "Dreamy Flowers," or via custom background image uploads with optional dark overlays for readability. The CQ Contact Visibility tab specifically manages what information is shared with other users via the secure federation protocol, such as bio and photo access.

The profile integrates across the platform, appearing in CQ Explorer, CQ Chat, and the federation network. Content is organized using tabbed "Share Groups," allowing users to categorize files and Memory Packs for public or contact-only viewing. While the profile is public by default when enabled, users maintain full sovereignty over their data, choosing exactly which elements are visible to visitors, followers, or federated contacts.


id: 578f8d7a-428b-476d-bec9-02fb4f313fb7
summary: Section: Introduction to CQ Profile
category: knowledge
created_at: 2026-03-22 17:42:18
source_type: document
source_ref: general:/CQ-User-Manual:09-cq-profile.md
source_range: 1:8
content:
Document: Introduction to CQ Profile

CQ Profile serves as the public identity and personal landing page for users within the CitadelQuest platform. Located at the user's specific username URL, this feature allows individuals to showcase their identity, introduce their Spirits, and display shared content to visitors. The system is designed with privacy and sovereignty in mind, granting users precise control over what information is visible to the public. Management of these profile details, including customization and visibility toggles, is handled through the dedicated profile settings route. Ultimately, it functions as a centralized, professional presentation layer for a user's presence on their personal Citadel.


id: 39211a39-e63c-4aa3-8b92-677719c70de8
summary: Section: Public Profile Page Components
category: knowledge
created_at: 2026-03-22 17:42:27
last_accessed: 2026-04-01 03:39:27
source_type: document
source_ref: general:/CQ-User-Manual:09-cq-profile.md
source_range: 9:37
content:
Document: Public Profile Page Components

The document outlines the features and components of a user's Public Profile Page within the CitadelQuest platform. When enabled, the profile is accessible via a personalized URL based on the user's username and domain. The page serves as a clean, ad-free digital identity hub that displays several key elements: a profile photo, username, a copyable URL, and a bio that supports Markdown and HTML. 

Additionally, the profile showcases the user's AI Spirit companions, including their names, levels, and experience points (XP), alongside a follower count. Content is organized through "Profile Content" tabs or an optional flat list of shared items via CQ Share. Visual customization is available through background themes or custom images. The page also features feed badges linking to public CQ Feed pages and a footer indicating the CitadelQuest version. For administrative flexibility, a Citadel admin can redirect the root domain of a personal Citadel directly to a specific user's public profile page.


id: 2aa531b7-b3e2-4bb2-b03b-5ef3226fbb44
summary: Section: Profile Settings and Visibility
category: knowledge
created_at: 2026-03-22 17:43:39
last_accessed: 2026-04-01 03:39:27
source_type: document
source_ref: general:/CQ-User-Manual:09-cq-profile.md
source_range: 38:78
content:
Document: Profile Settings and Visibility

The document "Profile Settings and Visibility" outlines how users can manage their public presence and contact-specific visibility within the CitadelQuest platform. Accessible via the user menu or settings at the `/settings/profile` route, the interface is divided into two primary tabs.

The Public Profile Page Tab allows users to enable or disable their public profile and manage their unique shareable URL. Customization options include toggling the visibility of profile photos, content groups, and shared item lists. Users can also configure a "Spirit showcase" to display no spirits, only the primary spirit, or all spirits. Aesthetic controls include language selection (English, Czech, or Slovak), various background themes like "Night Forest" or "Dreamy Flowers," and the option to upload a custom background image up to 5MB. A background overlay can be toggled to improve text readability.

The CQ Contact Visibility Tab specifically manages information shared with CQ Contacts via the federation protocol. Users can independently control whether their bio, profile photo, and Spirit showcase are visible to their established contacts. This dual-tab system ensures users have granular control over what information is presented to the general public versus their direct network.


id: 0034ac96-db9c-433b-891c-dc86f489a2e4
summary: Section: Media Management: Photo and Bio
category: knowledge
created_at: 2026-03-22 17:43:58
last_accessed: 2026-03-23 20:26:39
source_type: document
source_ref: general:/CQ-User-Manual:09-cq-profile.md
source_range: 79:111
content:
Document: Media Management: Photo and Bio

The document "Media Management: Photo and Bio" provides instructions for managing personal identification assets within the CitadelQuest platform. Users can upload a profile photo through the CQ Profile settings, supporting JPEG, PNG, WebP, and GIF formats up to 5MB. This image is displayed on the user's public profile, the CQ Explorer sidebar, and within CQ Chat conversations. If a photo is removed, the system reverts to a default avatar.

Additionally, the document outlines the Bio feature, which allows users to write a personal description. The Bio field supports Markdown and HTML for rich text formatting, including links and lists, and includes a character counter for convenience. The bio is visible on the user's public profile page, the CQ Explorer, and the CQ Contact view. These media elements are central to how a user is represented to contacts and followers across the decentralized network.


id: 63482038-a160-4154-8a9e-9555c065a606
summary: Section: Spirit Showcase and Content Groups
category: knowledge
created_at: 2026-03-22 17:44:31
last_accessed: 2026-04-01 03:33:34
source_type: document
source_ref: general:/CQ-User-Manual:09-cq-profile.md
source_range: 112:137
content:
Document: Spirit Showcase and Content Groups

The document outlines two key features of the CitadelQuest user profile: the Spirit Showcase and Profile Content (Share Groups). The Spirit Showcase highlights a user's AI companions, displaying their unique color-coded ghost icon, name, and progression metrics like Level and XP. On desktop, these appear in the profile header, while mobile users see a compact layout below the header. A star icon identifies the primary Spirit when multiple are present. Visibility to CQ Contacts in the CQ Explorer or on public pages is determined by the user's specific privacy settings.

Profile Content, managed via the Share Groups settings, organizes shared items into a tabbed navigation system on the user's public profile. This allows for the categorization of shared files and Memory Packs into distinct sections such as "Introduction," "Projects," or "Gallery." This system provides a structured way for others to browse a user's shared data within the CQ ecosystem. Detailed management of these groups is handled through the dedicated CQ Share settings.


id: f02102d6-abdf-4cef-bc2f-ddc1876aaccb
summary: Section: Themes and Custom Backgrounds
category: knowledge
created_at: 2026-03-22 17:44:39
last_accessed: 2026-04-01 03:39:27
source_type: document
source_ref: general:/CQ-User-Manual:09-cq-profile.md
source_range: 138:164
content:
Document: Themes and Custom Backgrounds

The document "Themes and Custom Backgrounds" outlines the visual customization options available for a user's public profile page. Users can select from five built-in themes, which include Default (matching the visitor's theme), CitadelQuest (cityscape), Night Forest, Dreamy Flowers, and a minimal Clear option. Each theme is accessible via settings and features a thumbnail preview.

For further personalization, users can upload a custom background image in JPEG, PNG, or WebP formats. The file size is limited to 5MB, with a recommended resolution of 1920×1080 or higher. A custom image will override any selected built-in theme. To ensure text remains legible against bright or complex backgrounds, the platform provides a "Background Overlay" toggle that adds a dark, semi-transparent layer over the image. These visual settings specifically dictate the appearance of the user's public page and function independently of a visitor's personal theme settings.


id: ab6dd489-1426-4900-a85f-7d361bcc596f
summary: Section: User Interaction and Access Levels
category: knowledge
created_at: 2026-03-22 17:44:50
source_type: document
source_ref: general:/CQ-User-Manual:09-cq-profile.md
source_range: 165:182
content:
Document: User Interaction and Access Levels

This document outlines the different ways individuals can interact with a user's CitadelQuest profile based on their access level and the user's settings. Public visitors can view a configured profile page at the user's specific URL without logging in, with the display language determined by the owner's settings. Within the platform, CQ Explorer allows other users to view profile cards, shared content, and initiate social actions like following or sending friend requests. CQ Contacts, part of the federation protocol, gain access to more detailed profile data such as bios and Spirits, governed by specific visibility settings. Followers specifically receive notifications regarding new public content. If the public profile feature is disabled, external visitors encounter a 404 error, though federation data remains accessible to CQ Contacts according to established privacy permissions.


id: a85d7f22-c4c6-4f96-b668-f6b84405555d
summary: Document: 00-introduction.md
category: knowledge
created_at: 2026-03-22 17:46:27
last_accessed: 2026-04-01 03:29:31
source_type: document_summary
source_ref: general:/CQ-User-Manual:00-introduction.md
source_range: 1:91
content:
Document: 00-introduction.md

CitadelQuest is a free, open-source, and self-hosted platform designed for personal data sovereignty and AI-human collaboration. This introductory user manual outlines the platform's core mission: providing a decentralized "digital fortress" where users maintain total ownership of their data through isolated SQLite databases. Built on principles of privacy and transparency, the system is technologically designed to prevent data exploitation, tracking, or advertising.

The document details a robust feature set, including "Spirits" (AI companions with memory and tools), CQ Memory for 3D knowledge visualization, a personal cloud File Browser, and secure, encrypted communication tools like CQ Chat and CQ Feed. These features allow for private messaging and decentralized social interaction across different CitadelQuest instances.

Users can get started by using a hosted version at one.citadelquest.world or by self-hosting on a server requiring PHP 8.4+ and SQLite3. The manual is organized into fourteen chapters covering everything from initial onboarding and Spirit management to advanced administration and data backup. Developed anonymously by a human-AI partnership, the project is licensed under the GNU Affero General Public License and supports multiple languages, including English, Spanish, Czech, and Italian.


id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
summary: Section: Introduction to CitadelQuest
category: knowledge
created_at: 2026-03-22 17:46:36
source_type: document
source_ref: general:/CQ-User-Manual:00-introduction.md
source_range: 1:13
content:
Document: Introduction to CitadelQuest

CitadelQuest is a free, open-source, and self-hosted platform designed to provide users with complete personal data sovereignty and a secure environment for AI-human collaboration. Described as a personal digital fortress or "Citadel," the system allows individuals to manage their digital lives without reliance on major technology corporations. 

The platform's architecture ensures that all user data remains private, stored exclusively on the user's own server within a personal database. Key features include "AI Spirits," which serve as personal companions rather than corporate tools, and a direct, encrypted communication system that bypasses third-party routing. Additionally, CitadelQuest functions as a personal cloud for file management and offers advanced knowledge organization through interactive 3D graphs. By prioritizing transparency and user agency, the platform enables individuals to maintain full control over their information, communication, and digital assets.


id: 307ef895-4d2e-4253-8293-02187da0badf
summary: Section: Core Principles and Features
category: knowledge
created_at: 2026-03-22 17:46:45
last_accessed: 2026-03-23 20:24:03
source_type: document
source_ref: general:/CQ-User-Manual:00-introduction.md
source_range: 14:39
content:
Document: Core Principles and Features

CitadelQuest is a decentralized, open-source platform built on the core principles of privacy, transparency, and human-AI collaboration. The system is designed to be technologically incapable of data exploitation, featuring a "privacy first" architecture where each user has an isolated database and there is no central authority, ads, or tracking. 

The platform offers a comprehensive suite of features centered around "Spirits," which are personal AI companions equipped with memory and specialized tools. Key functional components include CQ Memory for knowledge graph visualization, a personal File Browser for cloud storage, and CQ Chat for private messaging across different instances. The ecosystem also supports decentralized social interactions through CQ Explorer, CQ Follow, and CQ Feed, allowing users to manage contacts, subscribe to public profiles, and interact with posts across the federation. Additionally, users can share files and memory packs via CQ Share, customize public profiles, and ensure data security through full backup and restore capabilities. The interface is highly accessible, supporting multiple languages including English, Spanish, Czech, Italian, Hungarian, Norwegian, Polish, and Slovak.


id: 33d0838f-5d52-4b3c-bc90-43a4272fd309
summary: Section: Quick Start Guide
category: knowledge
created_at: 2026-03-22 17:46:59
source_type: document
source_ref: general:/CQ-User-Manual:00-introduction.md
source_range: 40:60
content:
Document: Quick Start Guide

The Quick Start Guide for CitadelQuest outlines two primary methods for users to begin using the platform. The first and fastest approach, Option A, involves visiting the official web portal at one.citadelquest.world, where users can register an account, complete an onboarding wizard to configure their first AI Spirit, and begin chatting immediately. 

The second approach, Option B, allows users to host their own private Citadel. This process requires downloading a small 8 KB installer package from GitHub Releases and uploading the install.php file to a personal web server. The installer automates the setup process, after which the first registered account is granted administrative privileges. To successfully run a self-hosted instance, the server must meet specific technical requirements, including PHP 8.4 or higher, Apache with mod_rewrite enabled, and the SQLite3 extension. Both methods are designed to provide a streamlined entry into the CitadelQuest ecosystem, whether through a hosted service or a decentralized, self-managed deployment.


id: 07834e44-7361-45b8-aa45-60d029df53d3
summary: Section: Manual Organization
category: knowledge
created_at: 2026-03-22 17:47:26
last_accessed: 2026-04-01 03:29:31
source_type: document
source_ref: general:/CQ-User-Manual:00-introduction.md
source_range: 61:81
content:
Document: Manual Organization

The document titled "Manual Organization" provides a structured overview of the CitadelQuest user manual, detailing the contents of fourteen distinct chapters. It serves as a navigational guide for users to understand the platform's features and administrative procedures.

The manual begins with foundational steps, covering account registration, onboarding, and an overview of the dashboard and navigation systems. Core platform features are detailed in chapters dedicated to Spirits (AI companions), CQ Memory (knowledge graphs), and the File Browser for cloud management. Communication and social aspects are addressed through chapters on CQ Chat for private messaging, CQ Explorer for contact management, CQ Share for data distribution, and the CQ Feed for social interactions like posts and comments.

Additionally, the document outlines technical and personal management topics, including public profile customization, general settings, and data backup and restoration. For advanced users and operators, the manual includes specific sections on system administration for Citadel managers and technical instructions for self-hosting the platform via the installation guide. This organization ensures that users can easily locate information ranging from basic daily tasks to complex system configurations.


id: a0bca789-5788-4ced-ab99-beadcf7ca11a
summary: Section: About and Contact Information
category: knowledge
created_at: 2026-03-22 17:47:34
source_type: document
source_ref: general:/CQ-User-Manual:00-introduction.md
source_range: 82:91
content:
Document: About and Contact Information

CitadelQuest is a project developed through a collaboration between humans and AI, with the authors choosing to remain anonymous to ensure the focus remains on the platform and its community. The project is committed to transparency and accessibility, operating under the Open Source GNU Affero General Public License, which ensures it remains free forever. Key resources for the project include its official website at www.citadelquest.com, a GitHub repository for code access and contributions, and an official X (formerly Twitter) account for updates. For inquiries or direct communication, the project can be reached via the email address info@citadelquest.email. The document emphasizes a mission-driven approach where the collective goals of the decentralized platform take precedence over individual recognition.


id: f0a4c741-f49a-4024-9028-b5ad0bc60744
summary: Document: 10-settings.md
category: knowledge
created_at: 2026-03-22 17:49:08
source_type: document_summary
source_ref: general:/CQ-User-Manual:10-settings.md
source_range: 1:135
content:
Document: 10-settings.md

The document "10-settings.md" provides a comprehensive guide to the Settings page of the CitadelQuest platform, located at the `/settings` route. It details how users can manage their personal configuration, AI services, and social presence across several key categories.

General Settings allow users to view their read-only username, update login credentials (email and password), and select visual themes. It also includes database management tools for monitoring file size and optimizing performance via SQLite VACUUM. A significant feature is Account Migration, which enables users to transfer their entire database, files, and settings to a different CitadelQuest instance.

The AI Services section manages the connection to the CQ AI Gateway. Users can select primary and secondary AI models, view detailed model comparisons (capabilities, context size, and pricing), and manage their API keys and credit balance.

Social and content settings are divided into three areas: CQ Profile, Profile Content, and Feeds. Users can customize their public identity, including bios, photos, and "Spirit" showcases. Profile Content allows for the organization of shared items into themed groups. Finally, the Feed settings enable users to manage their own publishing channels and control subscriptions to feeds from other Citadels, including the ability to pause or sync subscriptions from contacts.


id: ffa39d52-23ac-424c-8d0a-e25b6590b9e4
summary: Section: Introduction and General Settings
category: knowledge
created_at: 2026-03-22 17:49:17
source_type: document
source_ref: general:/CQ-User-Manual:10-settings.md
source_range: 1:38
content:
Document: Introduction and General Settings

The Settings page, located at the /settings route, serves as the central hub for configuring the CitadelQuest user experience. It encompasses four primary categories: Login Information, Theme, Database management, and Account Migration. Users can view their read-only username and update their email or password through secure modal dialogs. The interface follows a dark cyber-themed aesthetic with a specific green accent color, and users have the option to switch between different visual background themes.

For technical maintenance, the page displays the current size of the user's personal SQLite database and provides an "Optimize Database" feature to reclaim space and enhance performance. A significant feature of the platform is the Account Migration tool, which allows users to move their entire digital presence—including databases, files, and settings—to a different CitadelQuest instance. This process requires selecting a destination server where the user has administrative rights, choosing a backup, and confirming with a password. Upon migration, contacts are automatically notified of the new address, and the account on the original server is disabled. For accounts exceeding several hundred megabytes, the document recommends creating a manual backup prior to migration to ensure data reliability.


id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
summary: Section: AI Services Configuration
category: knowledge
created_at: 2026-03-22 17:49:45
source_type: document
source_ref: general:/CQ-User-Manual:10-settings.md
source_range: 39:61
content:
Document: AI Services Configuration

The "AI Services Configuration" document outlines the settings and features available at the `/settings/ai` route within the CitadelQuest platform. It details how users can manage their AI experience by selecting a Primary AI Model for Spirit conversations and a Secondary AI Model for specialized tasks like image generation. Users can synchronize the available models via the CQ AI Gateway and access an "AI Model Comparison" interface to evaluate providers, capabilities, context window sizes, and token pricing.

Additionally, the document covers the CQ AI Gateway Connection, which is essential for powering these services. It notes that the API Key is automatically configured during registration. Users can monitor their credit balance, purchase additional credits through the "Add Credits" feature, and access the Gateway Dashboard for a seamless login to the web interface. The configuration ensures users have full control over their AI tools and the financial management of their CQ AI account.


id: 8a1c5fe3-c932-4def-bfd8-ad1667b9c37e
summary: Section: CQ Profile and Content Groups
category: knowledge
created_at: 2026-03-22 17:49:53
last_accessed: 2026-04-01 03:39:27
source_type: document
source_ref: general:/CQ-User-Manual:10-settings.md
source_range: 62:96
content:
Document: CQ Profile and Content Groups

The document outlines the management of user identities and shared content within the CitadelQuest platform, focusing on the CQ Profile and Profile Content settings. 

The CQ Profile section describes how users can manage their public identity via the `/settings/profile` route. Key features include the ability to enable or disable a public profile page located at a custom username URL. Users can customize their presence by uploading profile photos, writing bios with Markdown support, and selecting specific background themes or custom images. Visibility controls allow users to show or hide their photo, shared items, and "Spirit" showcases. Language settings and background overlays are also available to enhance readability and localization for the public page.

The Profile Content section, managed via `/settings/share-groups`, details how users organize shared items into "Content Groups." These groups function as tabbed navigation on the user's public profile and within the CQ Explorer. Users can create groups with custom titles, icons, and colors, and have the ability to reorder shared items or override display styles for specific group entries. Together, these tools provide users with granular control over how their personal data and digital assets are presented to the public and their CQ Contacts.


id: 6b9619cb-e8e6-492f-8942-29ce08a329e3
summary: Section: CQ Feed Management
category: knowledge
created_at: 2026-03-22 17:50:15
source_type: document
source_ref: general:/CQ-User-Manual:10-settings.md
source_range: 97:125
content:
Document: CQ Feed Management

The CQ Feed Management document outlines the administrative controls for managing personal and external content streams within the CitadelQuest platform. It details two primary sections: "My Feeds" and "Subscribed Feeds."

Under "My Feeds" (located at `/settings/cq-feed/my-feeds`), users can manage the channels where they publish content. Key functionalities include creating new feeds with specific titles, URL slugs, and descriptions; setting the visibility scope to either "Public" or "CQ Contacts"; and editing or toggling feeds between active and inactive states. Every new user is automatically assigned a default "General" feed. Deleting a feed permanently removes both the channel and all associated posts.

The "Subscribed Feeds" section (located at `/settings/cq-feed/subscribed`) focuses on content from other Citadels. Subscriptions are automatically established when users accept friend requests or follow profiles. From this interface, users can pause or resume specific feeds, unsubscribe entirely, or use the "Sync Subscriptions" feature to discover new feeds from recently added contacts. The system organizes these external feeds by contact, allowing for streamlined management of incoming information from the user's network.


id: 3fb33b70-55cf-4541-ad4d-f8da2b5e5ebd
summary: Section: Settings Navigation Summary
category: knowledge
created_at: 2026-03-22 17:50:26
last_accessed: 2026-04-01 03:33:34
source_type: document
source_ref: general:/CQ-User-Manual:10-settings.md
source_range: 126:135
content:
Document: Settings Navigation Summary

The Settings Navigation document outlines the primary categories available within the CitadelQuest settings sidebar. It serves as a directory for user configuration, organized into six main functional areas. Users can manage core system preferences under General Settings, including login credentials, visual themes, and database migration tools. Social and visibility options are handled through the CQ Profile and Profile Content sections, which control public profile appearance, contact visibility, and the management of share groups.

The document also details feed management capabilities, distinguishing between "My Feeds" for personal channel administration and "Subscribed Feeds" for following content from external Citadels. Finally, the AI Services section provides access to model configurations, the CQ AI Gateway, and credit management for powering platform features. This navigation structure is designed to give users centralized control over their technical setup, social presence, and AI-integrated tools within the decentralized ecosystem.


id: c455066a-fe9b-432a-a598-b9116b4715c8
summary: Section: Introduction to Settings
category: knowledge
created_at: 2026-03-22 17:50:34
source_type: document
source_ref: general:/CQ-User-Manual:10-settings.md
source_range: 1:8
content:
Document: Introduction to Settings

The Settings page, accessible via the /settings route, serves as the central configuration hub for the CitadelQuest platform. It provides users with the necessary tools to manage their personal experience, ranging from security and authentication through login credential management to technical configurations like AI model selection. Additionally, the page facilitates account migration, ensuring users have control over their data and platform transition. This document serves as a foundational overview of how users can customize their environment and maintain their account settings within the CitadelQuest ecosystem.


id: 70701b55-4255-46a9-9cb8-64f779221e21
summary: Section: General Settings & UI
category: knowledge
created_at: 2026-03-22 17:50:45
source_type: document
source_ref: general:/CQ-User-Manual:10-settings.md
source_range: 9:23
content:
Document: General Settings & UI

The General Settings & UI document outlines the core configuration options available to users within the CitadelQuest platform. The settings are categorized into three primary sections: Login Information, Theme, and Database.

Under Login Information, users can view their read-only username and access modal dialogs to update their email address or change their password, the latter of which requires the current password for security. The Theme section highlights the platform's visual identity, featuring a dark cyber-themed design with a specific green accent color (#95ec86), while allowing users to switch between different background themes. Finally, the Database section provides transparency regarding the user's personal SQLite database. It displays the current database file size and offers an "Optimize Database" function, which utilizes the SQLite VACUUM command to reclaim unused space and enhance overall system performance. This document serves as a guide for managing personal account security, aesthetic preferences, and technical maintenance of the user's private data storage.


id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
summary: Section: Account Migration
category: knowledge
created_at: 2026-03-22 17:50:53
last_accessed: 2026-04-01 03:29:32
source_type: document
source_ref: general:/CQ-User-Manual:10-settings.md
source_range: 24:38
content:
Document: Account Migration

The "Account Migration" document outlines the procedure for transferring a user's entire account from one CitadelQuest instance to another. To initiate the process, a user must select a destination server from their CQ Contacts where they hold administrative privileges. The migration requires either selecting an existing backup or generating a new one, followed by password confirmation. This comprehensive transfer includes the user's complete database, files, and settings. 

A key feature of the migration is the automatic notification sent to all contacts regarding the user's new address, ensuring continuity of communication. However, users should be aware that once the migration is complete, the account on the original server will be disabled. For users with large accounts exceeding several hundred megabytes, the document recommends manually creating a backup prior to starting the migration to ensure system reliability.


id: a70d9f99-7362-402b-8187-e08afca930c3
summary: Document: 14-cq-feed.md
category: knowledge
created_at: 2026-03-22 17:51:51
source_type: document_summary
source_ref: general:/CQ-User-Manual:14-cq-feed.md
source_range: 1:217
content:
Document: 14-cq-feed.md

CQ Feed is CitadelQuest’s decentralized social networking platform, designed to provide a familiar social media experience while maintaining data sovereignty and privacy. Unlike traditional platforms, all content is hosted on the user’s personal server and distributed peer-to-peer via a federation protocol. This architecture ensures there is no central server; instead, content flows directly between Citadels over secure HTTPS connections.

The system allows users to create multiple feeds with specific visibility scopes: "Public" (accessible to anyone) or "CQ Contacts" (restricted to authenticated friends). Users can publish posts using Markdown for rich text formatting, and these posts are automatically distributed to followers. The central Timeline provides a chronological view of a user's own posts combined with content from subscribed feeds. New content is highlighted with an orange border, and real-time updates are managed through background polling and UI badges.

Interaction is supported through reactions (likes and dislikes) and a nested commenting system. Comments are lazy-loaded from the source Citadel and include moderation features, such as the ability for post owners to hide specific comments. Users manage their social circle through the CQ Explorer, where they can follow others and subscribe to specific feeds. Subscriptions can be paused, resumed, or synced at any time. Ultimately, CQ Feed preserves user agency by allowing the deletion of posts, which triggers a cleanup across the caches of all subscribing Citadels.


id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
summary: Section: Introduction and Overview
category: knowledge
created_at: 2026-03-22 17:52:03
source_type: document
source_ref: general:/CQ-User-Manual:14-cq-feed.md
source_range: 1:21
content:
Document: Introduction and Overview

CQ Feed is CitadelQuest's decentralized social networking platform, designed to provide a familiar social experience while maintaining personal data sovereignty. Accessible via the CQ Explorer tab, the service allows users to publish posts, follow feeds from other Citadels, and engage through reactions and comments. Unlike traditional corporate social networks, all content remains hosted on the user's personal server and is distributed peer-to-peer through a federation protocol.

Key features include support for Markdown rich text formatting and real-time updates through background polling. Users can organize their content into multiple feeds with varying visibility scopes, ensuring control over how their information is shared. The system automatically distributes posts to followers on other Citadels, facilitating cross-platform interaction without sacrificing privacy. Essentially, CQ Feed offers the functionality of a modern social feed—including rich media support and community engagement—within a secure, decentralized architecture where the user retains full ownership of their data.


id: cef60805-5ad9-4f33-a8b7-14c43569b589
summary: Section: Access and Timeline
category: knowledge
created_at: 2026-03-22 17:52:21
source_type: document
source_ref: general:/CQ-User-Manual:14-cq-feed.md
source_range: 22:54
content:
Document: Access and Timeline

The document "Access and Timeline" outlines the functionality and interface of the CQ Feed within the CitadelQuest ecosystem. The CQ Feed is located as a tab inside the CQ Explorer (/cq-contacts) section, which also handles profile browsing and contact management. The system conveniently remembers the user's active tab between sessions.

The timeline provides a chronological aggregation of posts from the user and their subscriptions. Each post entry includes the author's profile details (photo, username, and domain), a feed badge indicating the visibility scope (green for CQ Contacts or gray for Public), a timestamp, and Markdown-rendered content. Users can interact with posts through reactions, such as likes and dislikes, and view or expand comment threads. To help users track new activity, posts published since the last visit are marked with an orange left border. The timeline utilizes batch loading, requiring users to click a "Load more" button at the bottom of the page to retrieve older content.


id: 2c049ada-5de8-4c23-80be-48aeea1b7165
summary: Section: Creating and Managing Feeds
category: knowledge
created_at: 2026-03-22 17:52:40
last_accessed: 2026-03-23 20:26:39
source_type: document
source_ref: general:/CQ-User-Manual:14-cq-feed.md
source_range: 55:106
content:
Document: Creating and Managing Feeds

The document "Creating and Managing Feeds" provides a comprehensive guide on how to utilize the social and broadcasting features within the CitadelQuest platform. Users can create posts from the CQ Feed tab by entering text into a dedicated area, selecting a specific feed, and clicking publish. Posts support full Markdown formatting and are distributed to subscribers via federation.

Central to the system is the concept of multiple feeds, allowing users to categorize content for different audiences. Upon registration, a "Public" feed is automatically generated. Users can manage their feeds through the settings menu, where they can create, edit, toggle, or delete them. Each feed is defined by its scope: "Public" feeds are accessible to anyone without authentication, while "CQ Contacts" feeds are restricted to accepted contacts authenticated via API keys.

Management options include customizing titles, URL slugs, descriptions, and cover images. Additionally, every feed has a dedicated public page with paginated posts, accessible via a specific URL structure on the user's personal domain. The visibility of these pages is strictly governed by the feed's assigned scope, ensuring data sovereignty and controlled access.


id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
summary: Section: Interactions: Reactions and Comments
category: knowledge
created_at: 2026-03-22 17:52:57
source_type: document
source_ref: general:/CQ-User-Manual:14-cq-feed.md
source_range: 107:165
content:
Document: Interactions: Reactions and Comments

This document outlines the functionality for reactions and comments within the CitadelQuest platform. Users can interact with posts using "Like" or "Dislike" buttons, though they cannot react to their own content. The system allows only one reaction per post, updating counts instantly through an optimistic UI and synchronizing with remote Citadels via federation. Reaction and comment stats are refreshed in the background, and posts deleted at the source are automatically removed from the user's cached timeline.

The comment system supports reading, writing, and nested replies up to two levels deep. Comments are lazy-loaded from the source Citadel and display the author's profile details and timestamp. Users can submit comments by pressing Enter and can reply to others to create nested threads. Additionally, users have the authority to edit or delete their own comments. For moderation, post authors have the unique ability to hide or show comments made by others on their posts. The platform also includes a notification system that alerts users to new comments and directs them straight to the relevant conversation thread.


id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
summary: Section: Subscriptions and Real-time Updates
category: knowledge
created_at: 2026-03-22 17:53:20
last_accessed: 2026-04-01 03:29:32
source_type: document
source_ref: general:/CQ-User-Manual:14-cq-feed.md
source_range: 166:204
content:
Document: Subscriptions and Real-time Updates

This document outlines the mechanics of Subscriptions and Real-time Updates within the CitadelQuest ecosystem. Users automatically subscribe to feeds by following profiles or accepting friend requests, allowing content to appear in their timelines. Subscription management is handled via the settings menu, where users can pause, resume, or permanently unsubscribe from specific feeds, as well as sync subscriptions to discover new content from existing contacts.

The interface utilizes a system of color-coded feed badges to denote content accessibility: green badges represent the CQ Contacts scope, while gray badges indicate Public scope. These badges are visible in the CQ Explorer and on public profile pages, offering quick action links for managing subscriptions.

To ensure users stay informed, the platform employs global update polling for real-time notifications. This system detects new posts in the background and alerts users through various visual cues, including a bell icon on the CQ Feed tab, sidebar indicators for specific contacts, and dashboard badges on the CQ Explorer tile. When the CQ Feed tab is active or selected, the system automatically fetches and displays new posts, ensuring the timeline remains current without manual refreshing.


id: 96428498-d67a-4e81-a9af-a5000a94ffd9
summary: Section: Federation and Technical Architecture
category: knowledge
created_at: 2026-03-22 17:53:41
last_accessed: 2026-03-23 20:24:03
source_type: document
source_ref: general:/CQ-User-Manual:14-cq-feed.md
source_range: 205:217
content:
Document: Federation and Technical Architecture

The document outlines the technical architecture and decentralized federation protocol of CQ Feed within the CitadelQuest ecosystem. The system is designed to prioritize user sovereignty and privacy by ensuring that all posts remain on the user's personal server rather than a central hub. Content distribution occurs through an incremental synchronization process where subscriber Citadels periodically fetch only new updates from source Citadels via HTTPS, optimizing bandwidth efficiency.

Interactions such as reactions and comments are transmitted directly back to the source Citadel. Access to content is managed through scope-based permissions, distinguishing between public feeds and those restricted to verified CQ Contacts. Because there is no central server, data is stored locally on the creator's Citadel and only cached on the Citadels of subscribers. This architecture allows for complete user control over data; when a post is deleted by the author, it is automatically removed from all subscriber caches during the subsequent statistics refresh, ensuring that privacy and data ownership are maintained across the federated network.


id: 1722b9fd-f5a2-4145-a98b-ab6796c4de88
summary: Document: 02-dashboard.md
category: knowledge
created_at: 2026-03-22 17:54:12
source_type: document_summary
source_ref: general:/CQ-User-Manual:02-dashboard.md
source_range: 1:76
content:
Document: 02-dashboard.md

The Dashboard serves as the central hub and home screen of the CitadelQuest platform, accessible upon login or by clicking the logo in the navigation bar. It provides a streamlined interface for managing personal data, AI interactions, and system settings.

The core of the Dashboard consists of "Quick Action" cards that direct users to primary features, including Spirits (AI companions), CQ Explorer (contacts and profiles), CQ Memory (knowledge graphs), File Browser, and system backups. A red badge on the Explorer card alerts users to pending friend requests, while other indicators highlight new content or feed updates. Users with administrative privileges also have access to an Admin Panel card.

The interface includes a dedicated CQ AI Gateway panel, which displays the user's current credit balance using color-coded status indicators. From here, users can access the AI Gateway web dashboard via seamless login or purchase additional credits. A storage sidebar provides a detailed breakdown of data usage across the personal SQLite database, user files, and backups.

The persistent Top Navigation Bar facilitates quick movement between the Dashboard, Spirit Chat, and the User Menu. It also houses the CQ Chat for direct messaging, a notification system, and language settings for English, Czech, and Slovak. Server-specific information, such as the hostname and version number, is located at the bottom of the screen.


id: 897390d1-2ec0-45f9-a740-5bff0bc0232b
summary: Section: Introduction and Quick Actions
category: knowledge
created_at: 2026-03-22 17:54:21
source_type: document
source_ref: general:/CQ-User-Manual:02-dashboard.md
source_range: 1:27
content:
Document: Introduction and Quick Actions

The Dashboard serves as the central hub and home screen for the CitadelQuest platform, accessible immediately upon login or by clicking the site logo. It is designed to provide streamlined navigation through a series of "Quick Action" cards that direct users to the platform's core features. These features include Spirit management for AI companions, the CQ Explorer for managing contacts and profiles, and the CQ Profile for personal customization. Additionally, the Dashboard provides access to data-centric tools like CQ Memory for knowledge graphs, the File Browser for document management, and CQ Share for distributing files and Memory Packs.

The interface also includes essential utility links for system settings and data backups. For users with elevated permissions, an exclusive Admin Panel card is visible. To enhance user awareness, the CQ Explorer card utilizes a color-coded notification system: a red badge indicates pending friend requests, a yellow badge signals new content from followed profiles, and a feed badge highlights new posts in the CQ Feed timeline. This centralized layout ensures that all primary navigation routes and status updates are easily accessible from a single location.


id: ada32b14-6f87-4f53-98cf-977cf80f006c
summary: Section: AI Gateway and System Metrics
category: knowledge
created_at: 2026-03-22 17:54:31
source_type: document
source_ref: general:/CQ-User-Manual:02-dashboard.md
source_range: 28:55
content:
Document: AI Gateway and System Metrics

The document "AI Gateway and System Metrics" outlines the key interface components and monitoring tools available to a CitadelQuest user. It details three primary sections: the CQ AI Gateway, Storage Usage, and Server Info.

The CQ AI Gateway panel allows users to monitor their current AI credits balance through a color-coded system (green, yellow, or red) and provides quick links to the AI Gateway Dashboard and the credit purchase page. The Storage Usage section, located in the right sidebar, provides a breakdown of data consumption, including the total storage used, the size of the user's personal SQLite database, files within the File Browser, and space occupied by backups. Finally, the Server Info section at the bottom right displays technical details such as the server hostname or domain, the specific CitadelQuest version number, and the platform logo. Together, these elements provide the user with essential oversight of their account resources, data footprint, and system environment.


id: 7d433200-f88c-450e-a2b5-f100e5a9a92c
summary: Section: Top Navigation Bar
category: knowledge
created_at: 2026-03-22 17:54:39
source_type: document
source_ref: general:/CQ-User-Manual:02-dashboard.md
source_range: 56:76
content:
Document: Top Navigation Bar

The Top Navigation Bar is a persistent interface element in CitadelQuest designed for quick access to core platform features. It contains six primary components: the CitadelQuest Logo for returning to the Dashboard, and a Spirit Icon that opens a dropdown menu. This Spirit section allows users to launch the Spirit Chat modal or navigate directly to a Spirit's profile page.

The User Menu, identified by the individual's username, provides links to essential tools including the CQ Explorer, CQ Profile, CQ Memory, File Browser, and Settings, as well as Admin controls and Logout options. Communication and alerts are managed through the CQ Chat dropdown, which displays recent conversations and unseen message counts, and a Notifications bell icon that tracks unread alerts. Finally, the bar includes a Language switcher supporting English, Czech, and Slovak. This navigation structure ensures that management tools, AI interactions, and system settings are always within reach for the user.


id: c61b72ad-697b-40ad-9850-f0ce482ad13e
summary: Document: 07-cq-contacts.md
category: knowledge
created_at: 2026-03-22 17:56:05
source_type: document_summary
source_ref: general:/CQ-User-Manual:07-cq-contacts.md
source_range: 1:194
content:
Document: 07-cq-contacts.md

The document "07-cq-contacts.md" details the CQ Explorer, a decentralized hub within the CitadelQuest platform designed for managing social interactions, profiles, and content discovery. Located at the `/cq-contacts` route, the interface utilizes a two-column layout featuring a main panel for profile browsing and social feeds, and a sidebar for managing Contacts, Following, and Followers lists.

The system distinguishes between two types of social connections:
- **CQ Follow:** A one-way, lightweight subscription that allows users to receive notifications and feed updates from public profiles without requiring mutual approval. It includes visual indicators like yellow badges and highlights for new content.
- **CQ Contacts:** A mutual, secure friend system. Establishing a contact requires a friend request and acceptance, which triggers an exchange of unique CQ Contact API keys. This creates a secure HTTPS channel for private communication via CQ Chat and allows for deeper content sharing.

Key features of the Explorer include the ability to view "Spirit showcases" (AI assistants), download shared files or Memory Packs directly to a personal Citadel, and interact with a social timeline. The underlying architecture is fully federated and decentralized, meaning there is no central directory; communication happens directly between Citadels. The protocol ensures privacy, supports account migration by automatically notifying contacts of address changes, and uses federation for cross-Citadel notifications and feed subscriptions.


id: 1edffca9-3a49-4cea-ac1c-e0dab061c758
summary: Section: Introduction and Layout
category: knowledge
created_at: 2026-03-22 17:56:12
source_type: document
source_ref: general:/CQ-User-Manual:07-cq-contacts.md
source_range: 1:23
content:
Document: Introduction and Layout

CQ Explorer is a unified hub within the CitadelQuest platform designed for managing social interactions and discovering content. Accessible via the `/cq-contacts` route, it integrates profile browsing, contact management, and social feeds into a single interface. The system allows users to follow others across different Citadels, manage their own contacts, and interact with a social timeline.

The interface utilizes a two-column layout organized by tabs. The Main Panel, comprising 75% of the screen, toggles between the "CQ Explorer" tab for profile previews and URL-based exploration, and the "CQ Feed" tab, which features a social timeline and post composer. The Sidebar, making up the remaining 25%, displays organized lists of the user’s CQ Contacts, Following, and Followers. The application is designed for persistence, automatically remembering the user's active tab between sessions to ensure a seamless navigation experience.


id: 64ac3eb6-21a4-4540-8226-ebdee187fd2a
summary: Section: Exploring Profiles
category: knowledge
created_at: 2026-03-22 17:56:21
source_type: document
source_ref: general:/CQ-User-Manual:07-cq-contacts.md
source_range: 24:51
content:
Document: Exploring Profiles

The document "Exploring Profiles" provides a technical and functional overview of how users interact with profile pages within the CitadelQuest ecosystem. To explore a profile, a user enters a specific CitadelQuest URL into the input field, which then fetches and displays the data in a central panel. The interface includes visual elements such as the profile photo, username, domain link, and a bio with a toggle for longer text. It also highlights the user's "Spirit showcase," displaying their AI Spirits' names, levels, and experience points, alongside a follower count.

The profile view is organized into content groups using tabbed navigation, allowing visitors to browse publicly shared files and CQ Memory Packs. Interactive features enable users to send friend requests via the "Add Contact" button, follow or unfollow for updates, and download shared items directly to their own Citadel. Additionally, users can preview Memory Pack graphs inline or add them to their personal libraries. For convenience, the Explorer uses local storage to remember and auto-load the last profile viewed during the user's next session.


id: de076905-7921-4a20-bb33-c9638b69ef54
summary: Section: Sidebar Management
category: knowledge
created_at: 2026-03-22 17:56:43
source_type: document
source_ref: general:/CQ-User-Manual:07-cq-contacts.md
source_range: 52:87
content:
Document: Sidebar Management

The Sidebar Management document details the functionality of the right sidebar within the CitadelQuest interface, which organizes user connections into three distinct, collapsible glass-panel sections: CQ Contacts, Following, and Followers. Each section displays the profile photo, username, and domain of the respective users, along with a color-coded count badge—green for contacts, yellow for follows, and blue for followers.

The sidebar incorporates several smart features designed for a seamless user experience. It utilizes SPA-like navigation, allowing users to load profiles into the main panel instantly without a full page reload. Visual indicators are used to track activity; for instance, the "Following" section uses yellow highlights and dot badges to signal new content or unseen updates. Additionally, the currently viewed profile is marked with a cyber-colored border accent. To provide a customized workspace, each section header can be collapsed or expanded, with the display state saved locally to the user's browser. This system ensures users can efficiently manage their social connections and stay informed about feed updates across the decentralized network.


id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
summary: Section: CQ Follow System
category: knowledge
created_at: 2026-03-22 17:57:08
source_type: document
source_ref: general:/CQ-User-Manual:07-cq-contacts.md
source_range: 88:123
content:
Document: CQ Follow System

CQ Follow is a lightweight, one-way subscription system within the CitadelQuest platform that allows users to stay informed about public profiles without requiring a mutual friend relationship. By clicking the Follow button on a profile in CQ Explorer, the user adds that profile to their Following sidebar list. This process utilizes the federation protocol for cross-Citadel communication, notifying the followed user and increasing their public follower count.

The system features an automated notification framework to highlight new content. When a followed profile publishes updates, the platform provides visual cues such as yellow background highlights and dot badges in the sidebar, yellow borders on new Explorer content, and a count badge on the Dashboard’s CQ Explorer tile. Additionally, a bell icon appears on the CQ Feed tab to signal new posts. Following a profile also automatically subscribes the user to that profile's feeds. Users can manage these subscriptions by clicking the Following button on a profile to confirm unfollowing, which removes the profile from their list and stops further notifications.


id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
summary: Section: CQ Contacts (Friend System)
category: knowledge
created_at: 2026-03-22 17:57:52
source_type: document
source_ref: general:/CQ-User-Manual:07-cq-contacts.md
source_range: 124:158
content:
Document: CQ Contacts (Friend System)

CQ Contacts is the mutual and secure friend system designed to connect users across different Citadels within the CitadelQuest ecosystem. Unlike the one-way "Follow" system, CQ Contacts establishes a verified relationship based on a user's unique identity, which is defined by their domain and username (e.g., https://one.citadelquest.world/Human). This identity is authenticated through the ownership of the Citadel's internet domain.

To add a contact, a user must navigate to a profile in the CQ Explorer and send a friend request. Recipients are notified via a bell icon and a red badge on their Dashboard's CQ Explorer card, where they can choose to accept or reject the request. Upon acceptance, the system automatically exchanges CQ Contact API keys between the two Citadels to establish a secure HTTPS communication channel. This process enables direct messaging via CQ Chat and adds the individual to the user's sidebar contact list. Furthermore, accepting a contact automatically subscribes the user to that friend's feed, ensuring their posts appear in the CQ Feed timeline. This system serves as the foundation for secure, decentralized social interaction and content sharing between trusted peers.


id: ac5c0c9f-2ffd-4481-a45e-87881310440a
summary: Section: Contact Interaction and Downloads
category: knowledge
created_at: 2026-03-22 17:58:19
source_type: document
source_ref: general:/CQ-User-Manual:07-cq-contacts.md
source_range: 159:179
content:
Document: Contact Interaction and Downloads

The Contact Interaction and Downloads document outlines how users interact with profiles and shared content within the CitadelQuest ecosystem. By selecting a contact from the sidebar, users can access a detailed profile page. Depending on the contact's visibility settings, this page displays their profile photo, username, domain link, bio, and a "Spirit showcase" featuring their AI Spirits' names, levels, and experience points.

The document also details the process for acquiring shared items. Users can download files directly to their File Browser's downloads folder. Additionally, users can download Memory Packs (.cqmpack), which are stored in a dedicated library within the Memory Explorer. These packs feature an automatic synchronization function, ensuring that the user's local copy is updated whenever the original contact modifies the source file. This system facilitates seamless data sharing and collaboration between different Citadels while respecting individual privacy configurations.


id: 32d09012-3eaf-49b0-8726-915418d6dad1
summary: Section: Federation Protocol
category: knowledge
created_at: 2026-03-22 17:58:33
source_type: document
source_ref: general:/CQ-User-Manual:07-cq-contacts.md
source_range: 180:194
content:
Document: Federation Protocol

The CitadelQuest Federation Protocol is a decentralized communication framework designed for secure, direct interaction between users without a central directory. The system operates on a peer-to-peer basis where Citadels communicate directly via HTTPS. Security is maintained through unique CQ Contact API Keys, which are exchanged during the friend request process to ensure that no third party can access messages or contact lists.

The protocol supports a variety of social and collaborative features, including the exchange of rich profile data such as photos, bios, and Spirits, governed by individual visibility settings. Users can share files and Memory Packs through CQ Share and interact via a social feed that supports posts, reactions, and comments. Additionally, the protocol manages follow notifications with built-in fraud prevention through origin and host validation. A key feature of the system is automated account migration; if a user moves their account to a different Citadel, the federation protocol automatically notifies and updates their contacts and followers with the new address, ensuring seamless connectivity.


# memory_relationships

id: 756d18b4-f86f-4b75-907c-b34866d2cb38
source_id: c2108434-8b74-46a0-845d-5abb287a9cec
target_id: df4f6b2b-ec31-4523-a509-90382945cc1d
type: NOT_DETECTED
created_at: 2026-03-12 14:20:46
context:
Memory B introduces the high-level concept of CQ Memory, while Memory A provides the specific structural details (Memory Packs and Libraries) that enable that system. They reinforce each other as part-to-whole components of the same technical documentation.


id: 8088ae2f-2591-41c7-95cf-31c050d5c014
source_id: c2108434-8b74-46a0-845d-5abb287a9cec
target_id: d53d081b-6f67-4155-8069-711b2449468c
type: NOT_DETECTED
created_at: 2026-03-12 14:22:08
context:
Memory A defines the technical storage units (.cqmpack and .cqmlib), while Memory B explains how the Spirit integration utilizes these specific libraries and packs for information recall (Reflexes and Memory Agent modes). They are complementary parts of the same technical manual section.


id: 87670a8d-64d1-4f19-8d9d-d72dda406971
source_id: c2108434-8b74-46a0-845d-5abb287a9cec
target_id: e6da62d1-5272-4316-8fa4-652f2a8ad291
type: NOT_DETECTED
created_at: 2026-03-12 14:22:37
context:
Memory A defines the Memory Pack (.cqmpack) as a portable unit designed for sharing. Memory B reinforces this by detailing the specific mechanisms (CQ Share, auto-sync, visibility scopes) that enable that portability and sharing functionality. They are complementary sections of the same technical manual.


id: 5370df1e-703d-4cd0-86fe-91f4625e76f8
source_id: c2108434-8b74-46a0-845d-5abb287a9cec
target_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
type: NOT_DETECTED
created_at: 2026-03-12 14:23:06
context:
Memory A defines the technical architecture (Memory Packs and Libraries), while Memory B describes the functional applications (research, analysis, sharing) of that same architecture. They reinforce each other by connecting technical capabilities to user value.


id: d496b86c-4539-4dc5-be43-6b1b8e54d943
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: df4f6b2b-ec31-4523-a509-90382945cc1d
type: NOT_DETECTED
created_at: 2026-03-12 14:23:35
context:
Memory B provides a high-level introduction to the CQ Memory system, while Memory A provides specific technical definitions of the 'Memory Node' which is the fundamental unit of that same system. Memory A reinforces the concepts in Memory B by providing the granular structure that makes the described system function.


id: 09616d2b-f1df-4ee9-a69b-246f48be7956
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: d53d081b-6f67-4155-8069-711b2449468c
type: NOT_DETECTED
created_at: 2026-03-12 14:25:04
context:
Memory A defines the structural unit (Memory Node) and its attributes within the .cqmlib system, while Memory B explains how these specific nodes are integrated, synthesized, and recalled by Spirits. Memory B confirms the utility of the categories and relevance metrics mentioned in Memory A.


id: 0e2bf470-a632-4a74-8d97-e99b715eefd4
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
type: NOT_DETECTED
created_at: 2026-03-12 14:25:51
context:
Memory A defines the technical structure of the Memory Node (content, category, importance), while Memory B describes the use cases that utilize these nodes, such as relationship discovery and knowledge base building. They are complementary parts of the same system documentation.


id: ddfbdddf-2680-4e71-bd8f-ded74eb8062d
source_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
target_id: df4f6b2b-ec31-4523-a509-90382945cc1d
type: NOT_DETECTED
created_at: 2026-03-12 14:26:19
context:
Memory B provides a high-level introduction to the CQ Memory system, while Memory A details the specific node structure and relational mapping that makes that system function. Memory A reinforces the claims in Memory B about how the system organizes and visualizes data.


id: 21dd4191-8731-4070-a365-e54ffe7ff590
source_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
target_id: b7adbc37-239e-41fc-917c-62b612be0cf6
type: NOT_DETECTED
created_at: 2026-03-12 14:27:34
context:
Memory A defines the structural framework of memory nodes and relationship types, while Memory B describes the functional analysis methods used to discover and map those exact relationships. They are complementary parts of the same technical system (CQ Memory) from the same source document.


id: d74c6194-60b0-4e31-a240-006ad04c0c92
source_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
target_id: d53d081b-6f67-4155-8069-711b2449468c
type: NOT_DETECTED
created_at: 2026-03-12 14:27:54
context:
Memory A defines the structural framework of memory nodes (source tracking, relationship types), while Memory B explains how the system utilizes these specific structures (graph connections, synthesis) for Spirit recall. Memory B reinforces the importance of the node structure by showing its practical implementation in the 'Memory Agent' and 'Memory Synthesis Display' features.


id: c61bea30-917c-40d8-b29c-32b6c8e4a628
source_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
target_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
type: NOT_DETECTED
created_at: 2026-03-12 14:28:22
context:
Memory A describes the technical implementation of relational mapping and source tracking, which directly supports and provides the framework for the 'relationship discovery' and 'research' use cases outlined in Memory B. They are both sections from the same user manual document.


id: 57c08d4b-b313-44f4-9ad2-3fa3cca079b5
source_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
target_id: df4f6b2b-ec31-4523-a509-90382945cc1d
type: NOT_DETECTED
created_at: 2026-03-12 14:28:52
context:
Memory B introduces the CQ Memory system and its use of 3D knowledge graphs, while Memory A provides the specific definitions and visual rules for the relationships that form those very graphs. Memory A supports and validates the architectural claims made in Memory B.


id: a16db0a2-728a-428b-a8d9-1cd3e3e29171
source_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
target_id: d53d081b-6f67-4155-8069-711b2449468c
type: NOT_DETECTED
created_at: 2026-03-12 14:30:20
context:
Memory A defines the semantic relationship types (REINFORCES, CONTRADICTS, etc.) used in the CQ Memory system, while Memory B describes the 'Memory Agent' and 'Spirit Memory Integration' which utilize these graph connections and relationships to synthesize responses. Memory B confirms the practical use case for the data structures described in Memory A.


id: da44d066-3933-4055-8b56-90a881e6fbe8
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
type: NOT_DETECTED
created_at: 2026-03-12 14:31:47
context:
Memory B provides a high-level overview of CQ Share (scopes and types), while Memory A reinforces this by detailing the specific UI workflows (File Browser and Memory Explorer) used to implement those sharing features. They originate from the same source document and describe the same system at different levels of granularity.


id: 20bd8fb4-bfef-4730-a0a5-66ed4f145be9
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: d92f6c51-6e01-479d-83ca-d660824e27b7
type: NOT_DETECTED
created_at: 2026-03-12 14:32:16
context:
Memory A and Memory B are sections from the same source document (08-cq-share.md). Memory A focuses on the creation and initiation of shares (File Browser/Memory Explorer), while Memory B expands on the configuration of those shares (URLs, display styles, and Markdown). They reinforce each other by providing complementary details on the same workflow and feature set.


id: b352a48d-b1b5-486d-9d81-c880540dd389
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: a4102387-181b-467a-9de7-edeb48f554e0
type: NOT_DETECTED
created_at: 2026-03-12 14:32:41
context:
Memory A and Memory B are sections from the same source document (08-cq-share.md). Memory A focuses on the creation and initiation of shares, while Memory B focuses on the configuration and display of those shares. They reinforce each other by providing complementary details about the same feature set (access scopes, URL generation, and management).


id: 372aa38d-2ecf-41f9-afc4-29ae06c6f0e2
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: 4d8a2d04-0376-4274-818b-160b12166db4
type: NOT_DETECTED
created_at: 2026-03-12 14:33:29
context:
Both memories originate from the same source document regarding CQ Share. Memory A focuses on the initial creation and management of individual shares, while Memory B provides detailed implementation details for 'Share Groups,' which Memory A identifies as a significant organizational feature for those shares.


id: 8aed61d1-e41b-45f1-9ba8-54591cf9bba0
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: NOT_DETECTED
created_at: 2026-03-12 14:34:19
context:
Memory A describes the UI process for sharing Memory Packs, while Memory B explains the underlying auto-sync mechanism that makes those shared packs functional. They are parts of the same technical documentation (08-cq-share.md) and support each other's context regarding how shared knowledge is maintained.


id: 9c5dbfa9-f296-451d-b09c-71870c2ba338
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
type: NOT_DETECTED
created_at: 2026-03-12 14:35:07
context:
Memory A describes the UI process for sharing Memory Packs, while Memory B explains the underlying auto-sync mechanism that makes those shared Memory Packs functional. They both originate from the same source document regarding CQ Share and complement each other's technical details.


id: 67087985-d85f-4896-b5eb-7f8fb7f4f35c
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
type: NOT_DETECTED
created_at: 2026-03-12 14:35:26
context:
Memory A describes the UI and procedural workflow for sharing Memory Packs, while Memory B explains the underlying auto-sync mechanism that makes those shared packs functional. They both originate from the same source document and describe complementary aspects of the same feature set.


id: 029caee5-8593-4be3-baa2-9ad05fc636ad
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: NOT_DETECTED
created_at: 2026-03-12 14:36:16
context:
Memory A focuses on the creation and initiation of shares, while Memory B focuses on the maintenance and lifecycle of those same shares. They reinforce each other by consistently describing the same visibility scopes (Public vs CQ Contacts) and the principle that sharing actions do not delete the underlying source data.


id: 550ac3c6-59ca-479c-827a-0f0d112921fe
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
type: NOT_DETECTED
created_at: 2026-03-12 14:41:07
context:
Both memories originate from the same source document regarding CQ Share. Memory B provides the high-level conceptual introduction (Public vs Contact sharing), while Memory A provides the specific functional steps (File Browser vs Memory Explorer workflows) that implement those concepts. They are mutually supportive and consistent.


id: eaf070b4-fda2-4673-8dc6-0300f99b464b
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: d92f6c51-6e01-479d-83ca-d660824e27b7
type: NOT_DETECTED
created_at: 2026-03-12 14:41:37
context:
Memory A focuses on the initiation and creation process of sharing (File Browser vs Memory Explorer), while Memory B expands on the configuration and display options (URLs, styles, and Markdown) for those same shares. They are complementary sections of the same user manual document.


id: 0079a3bb-46bf-4bc3-a65d-20b179bae198
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: NOT_DETECTED
created_at: 2026-03-12 14:42:12
context:
Memory A describes the creation and management of individual shares, while Memory B describes how to organize those shares into groups. They reinforce each other by detailing different stages of the same feature workflow (CQ Share) within the same source document.


id: 96e1b873-605b-4e3d-937d-7ea6ea0da844
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: NOT_DETECTED
created_at: 2026-03-12 14:42:54
context:
Memory A describes the UI and procedural steps for sharing Memory Packs, while Memory B explains the underlying auto-sync mechanism that makes those shared packs functional. They both originate from the same source document and describe complementary aspects of the same system feature.


id: 45b4f93b-df2e-40b8-b398-e17507512124
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
type: NOT_DETECTED
created_at: 2026-03-12 14:43:45
context:
Memory A describes the UI and procedure for sharing Memory Packs, while Memory B explains the underlying auto-sync mechanism that occurs once those packs are shared. They are complementary sections of the same user manual that validate the workflow and functionality of the CQ Share system.


id: b10f8cb2-2f3a-4082-9792-b5e2fffb9fec
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
type: NOT_DETECTED
created_at: 2026-03-12 14:44:13
context:
Memory A provides the high-level UI overview of how to initiate sharing for Memory Packs, while Memory B explains the specific underlying mechanism (auto-sync) that occurs after that share is initiated. They are complementary sections of the same technical manual.


id: 5b6e4f76-787c-427a-abfc-4edbf4b509fd
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: a4102387-181b-467a-9de7-edeb48f554e0
type: NOT_DETECTED
created_at: 2026-03-12 14:51:46
context:
Memory A and Memory B are sections from the same source document (08-cq-share.md). Memory A focuses on the creation process and metadata (slugs, visibility), while Memory B expands on the specific configuration of those URLs and display styles. They reinforce each other by providing complementary details on the same feature set.


id: 6669f788-190b-4efb-9fb1-91ac8fc8050e
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: NOT_DETECTED
created_at: 2026-03-12 14:52:51
context:
Memory A describes the creation and configuration process of a share, while Memory B provides specific technical detail on the 'auto-sync' feature mentioned as a capability in the CQ Share overview. They are complementary sections of the same functional module.


id: 071fc9b4-8df1-4e49-9dd0-7c91f9ca7961
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: NOT_DETECTED
created_at: 2026-03-12 14:52:56
context:
Memory A describes the creation and configuration process of shares, while Memory B provides detailed technical depth on the 'auto-sync' feature mentioned as a capability in the creation process. They reinforce each other by providing a complete picture of the CQ Share lifecycle from setup to synchronization.


id: 5ecace92-f777-40bf-a469-3c75259ca3d6
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
type: NOT_DETECTED
created_at: 2026-03-12 14:53:53
context:
Both memories originate from the same user manual (08-cq-share.md). Memory A describes the general setup process for sharing content (including Memory Packs), while Memory B provides specific, detailed evidence of how the 'auto-sync' feature works for those shared Memory Packs. Memory B reinforces the utility and technical implementation of the sharing actions initiated in Memory A.


id: 6e0700c9-12fd-4ce8-a9a6-b0266a892946
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
type: NOT_DETECTED
created_at: 2026-03-12 14:54:20
context:
Memory A describes the general creation and configuration process of a share (including Memory Packs), while Memory B provides specific technical details on the auto-sync functionality mentioned in Memory A's context. They reinforce each other by providing different layers of the same feature set within the same source document.


id: 7e5a6718-15ca-4c65-949a-d8b6b3dd4688
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: b7adbc37-239e-41fc-917c-62b612be0cf6
type: NOT_DETECTED
created_at: 2026-03-12 19:11:43
context:
Memory A focuses on user onboarding and language settings, while Memory B describes the technical functionality of the memory analysis system. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: bfe78fad-cd02-4722-88ae-b7a8a213b7d9
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: e6da62d1-5272-4316-8fa4-652f2a8ad291
type: NOT_DETECTED
created_at: 2026-03-12 19:12:16
context:
Memory A focuses on the initial user onboarding and language settings, while Memory B describes the technical mechanics of sharing and syncing Memory Packs. There is no meaningful semantic overlap or logical connection between these two distinct functional areas of the platform.


id: 79ddf442-9c93-425c-bc99-e3d2d6240269
source_id: fd441b64-9557-464b-b15c-080626d39052
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: NOT_DETECTED
created_at: 2026-03-12 19:30:44
context:
Memory A focuses on the initial user registration and onboarding process, while Memory B details the maintenance and lifecycle of shared content (CQ Share). While both are parts of the same user manual, they describe distinct, unrelated functional areas of the platform with no direct semantic overlap or conflict.


id: 1d964670-d925-4369-ab19-97464dcbace4
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
type: NOT_DETECTED
created_at: 2026-03-12 19:31:46
context:
Memory A describes the initial user onboarding and AI setup process, while Memory B describes the CQ Share feature for file and knowledge distribution. While both are part of the CQ User Manual, they cover distinct, non-overlapping functional areas with no direct semantic or logical dependency.


id: 4052520a-2c14-4af3-9064-d4ba309465fb
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: a4102387-181b-467a-9de7-edeb48f554e0
type: NOT_DETECTED
created_at: 2026-03-12 19:32:49
context:
Memory A focuses on the initial user onboarding and AI Spirit setup, while Memory B details the technical configuration of sharing files and URLs. There is no meaningful semantic overlap or functional dependency between these two distinct parts of the user manual.


id: 1d53a54e-b86e-46df-bf0a-be689bbc6722
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: NOT_DETECTED
created_at: 2026-03-12 19:33:05
context:
Memory A focuses on the initial user onboarding and AI Spirit setup, while Memory B describes the management of shared content and profile groups. While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or conflicting information.


id: 282acb12-6ea9-49b6-a56d-47972baae317
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: 4d8a2d04-0376-4274-818b-160b12166db4
type: NOT_DETECTED
created_at: 2026-03-12 19:33:21
context:
Memory A focuses on the initial onboarding process and AI setup, while Memory B describes the management of shared content and profile groups. While both are part of the same user manual, they describe distinct, unrelated functional areas of the platform with no semantic overlap or conflicting information.


id: 585f4d19-4750-4c0f-b696-27a315a0dd9d
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: 02619512-3802-40c7-9fd4-13edfcdbf655
type: NOT_DETECTED
created_at: 2026-03-12 19:34:05
context:
Memory A focuses on the initial user onboarding and AI Spirit setup, while Memory B details the maintenance and lifecycle of shared content. There is no meaningful semantic overlap or functional connection between these two distinct administrative processes.


id: 5219099a-3565-4a18-99e0-31421d2a829f
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
type: NOT_DETECTED
created_at: 2026-03-12 19:34:46
context:
Memory A describes the initial user onboarding and AI setup process, while Memory B explains the technical mechanics of sharing and syncing knowledge packs. There is no meaningful semantic or functional overlap between these two distinct system features.


id: a5a1dc39-8c6b-4adc-9ddd-1f1b3152091c
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: 1d3da196-26b2-4575-8d68-23713a1ac801
type: NOT_DETECTED
created_at: 2026-03-12 19:35:04
context:
Memory A focuses on the initial user onboarding and AI Spirit setup, while Memory B describes the public sharing and content discovery features. While both are part of the same user manual, they describe distinct, non-overlapping functional areas of the platform with no direct semantic link.


id: 9c6b1bed-04ba-40f0-b4dc-5e26a0832e7f
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: NOT_DETECTED
created_at: 2026-03-12 19:35:23
context:
Memory A describes the initial user onboarding and AI setup process, while Memory B focuses on the maintenance and lifecycle of shared content. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: 4e5b2b0c-795e-4fb4-9e4f-083515c1629e
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: c948f87d-5941-4d4d-84a2-98e896b44105
type: NOT_DETECTED
created_at: 2026-03-12 19:35:40
context:
Memory A focuses on the initial user onboarding and AI Spirit setup, while Memory B describes public file sharing and profile integration features. While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or conflicting information.


id: 2ca42c69-a4d8-426e-90f9-149cb6726c69
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: 4d8a2d04-0376-4274-818b-160b12166db4
type: RELATES_TO
created_at: 2026-03-12 19:37:42
context:
Both documents describe different sections of the CitadelQuest platform's user interface and settings


id: 96ba12dc-dbeb-4cbf-b88e-ada44ddd831c
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
type: NOT_DETECTED
created_at: 2026-03-12 19:38:01
context:
Memory A focuses on the initial onboarding process and global language settings, while Memory B describes the configuration of public profile share groups. While both are part of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 6fd9eb01-ded6-4b0e-8934-83c841aebaf3
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: NOT_DETECTED
created_at: 2026-03-12 19:38:13
context:
Memory A focuses on the initial user onboarding and language settings, while Memory B describes the technical functionality of Memory Pack auto-synchronization. While both are sections of the same user manual, they cover distinct, unrelated features of the platform with no functional or semantic overlap.


id: 5a43c700-9287-43ac-bff0-f446340999dc
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: 02619512-3802-40c7-9fd4-13edfcdbf655
type: NOT_DETECTED
created_at: 2026-03-12 19:38:41
context:
Memory A focuses on the initial user onboarding and language settings, while Memory B details the lifecycle management of shared content (CQ Share). There is no meaningful semantic overlap, reinforcement, or contradiction between these two distinct functional areas of the platform.


id: 4f627214-f1e6-4632-aa0e-4a86e55bc5dd
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
type: NOT_DETECTED
created_at: 2026-03-12 19:39:10
context:
Memory A focuses on the initial user onboarding and language settings, while Memory B describes the technical synchronization of shared knowledge packs. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: ea7d0d41-436b-4733-9811-9616b1e9d9be
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
type: NOT_DETECTED
created_at: 2026-03-12 19:39:22
context:
Memory A focuses on the initial user onboarding and language settings, while Memory B describes the technical functionality of Memory Pack auto-syncing. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: c4ae3f4b-95cb-4a71-b04b-aa3e8c4e62f0
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: 1d3da196-26b2-4575-8d68-23713a1ac801
type: NOT_DETECTED
created_at: 2026-03-12 19:39:38
context:
Memory A focuses on the initial onboarding process and language settings, while Memory B describes the public sharing and profile integration features. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: 9e7cd059-ae45-4bab-a0b3-94f5bfc19198
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: NOT_DETECTED
created_at: 2026-03-12 19:40:30
context:
Memory A focuses on the initial user onboarding and language settings, while Memory B details the maintenance and lifecycle of shared content (CQ Share). There is no meaningful semantic overlap or logical connection between these two distinct functional areas of the platform.


id: 79c9ad08-89b5-4381-8193-8faf50a3691d
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: c948f87d-5941-4d4d-84a2-98e896b44105
type: NOT_DETECTED
created_at: 2026-03-12 19:40:42
context:
Memory A focuses on the initial onboarding process and language settings, while Memory B describes the public sharing features and profile integration. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: e64b3ab5-66cb-4dae-9ece-aff32344f2d9
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: f10414d1-5c2c-4f68-9977-d71212e8d9af
type: NOT_DETECTED
created_at: 2026-03-12 19:55:06
context:
Memory A focuses on the initial user onboarding and AI Spirit setup, while Memory B describes the backup and restore system. While both are sections of the same User Manual, they describe distinct, unrelated functional modules with no semantic overlap or logical dependency.


id: 175fb1ac-073c-4910-82b2-fcf537e6895d
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-12 19:55:50
context:
Memory A describes the initial onboarding and AI setup process, while Memory B focuses on data backup and restoration procedures. While both are part of the same user manual, they cover distinct functional areas with no direct semantic overlap or logical dependency.


id: c34c828d-6290-4319-8f2b-27f7e54ac17a
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-12 19:56:10
context:
Memory A focuses on the initial user onboarding and AI setup process, while Memory B details the technical procedures for data backup and restoration. There is no meaningful semantic overlap or logical connection between these two distinct administrative functions.


id: 17fca0bf-c29e-4dd0-9c7c-65c03d98e846
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-12 19:56:26
context:
Memory A focuses on the initial onboarding and AI setup process, while Memory B focuses on data backup and security protocols. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: 57869ab7-ecc5-4841-b034-96e8c4568558
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-12 19:57:32
context:
Memory A focuses on user onboarding and language settings, while Memory B details backup and restoration procedures. While both are sections of the same user manual, they cover distinct functional areas with no direct semantic overlap or logical dependency.


id: c79425dd-4409-4896-b65a-eeaf3d716437
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-12 19:57:47
context:
Memory A focuses on the initial user onboarding and language settings, while Memory B details the technical process of database backups and restoration. There is no meaningful semantic connection or functional overlap between these two distinct parts of the user manual.


id: 049db404-170d-40e1-ab2a-71edf234156b
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: RELATES_TO
created_at: 2026-03-12 20:03:29
context:
Both memories describe administrative and user-level configurations within the CitadelQuest platform


id: 13d6d100-19a6-4b63-b823-dc135e710fae
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: d53d081b-6f67-4155-8069-711b2449468c
type: REINFORCES
created_at: 2026-03-12 21:25:49
context:
Memory B provides the technical implementation details for the memory evolution described in Memory A


id: 35057828-8c17-4a41-a7f1-061ac3ec4ee8
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
type: REINFORCES
created_at: 2026-03-12 21:31:04
context:
Memory B provides the functional use cases for the Memory Agent and memory types defined in Memory A


id: 3c86d471-98f3-417a-8906-f51428e43ab5
source_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
target_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
type: REINFORCES
created_at: 2026-03-12 21:31:44
context:
Memory B provides a detailed technical expansion of the Memory Explorer preview mentioned in Memory A


id: bf29f811-7710-4142-9775-f9e4a051bab1
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
type: NOT_DETECTED
created_at: 2026-03-12 21:51:10
context:
Memory A describes the management of AI companions (Spirits) and their UI, while Memory B describes a peer-to-peer encrypted messaging system for human users. While both are features of the CitadelQuest platform, they represent distinct functional modules with no direct semantic overlap or conflicting information.


id: 413f44c1-cb3f-479b-80b8-9057647b2a79
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
type: NOT_DETECTED
created_at: 2026-03-12 21:52:09
context:
Memory A describes the configuration of AI Spirits, while Memory B describes a peer-to-peer user messaging system. While both are features of the CitadelQuest platform, they represent distinct functional modules (AI customization vs. encrypted human communication) with no direct semantic overlap or conflicting information.


id: 1e0dce0c-f993-4195-8936-f0614601ff13
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
type: NOT_DETECTED
created_at: 2026-03-12 21:56:22
context:
Memory A describes the creation and progression of AI Spirits, while Memory B describes a decentralized peer-to-peer messaging system for human users. While both are features of the CitadelQuest platform, they represent distinct functional modules with no direct semantic overlap or interaction described.


id: 08ae58bc-91d8-47ce-aba8-c6ac211c91c7
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: 4d8a2d04-0376-4274-818b-160b12166db4
type: NOT_DETECTED
created_at: 2026-03-12 22:12:49
context:
While both memories describe features of the CitadelQuest platform, they cover distinct, non-overlapping systems: Memory A focuses on AI Spirits (companions/logic), while Memory B focuses on Share Groups (content distribution/UI organization). There is no direct functional or semantic dependency between them.


id: 34de231f-7426-4547-a2ac-3666d7669c5f
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
type: NOT_DETECTED
created_at: 2026-03-12 22:15:30
context:
Memory A focuses on the management and UI of AI companions (Spirits), while Memory B describes the CQ Share system for distributing files and knowledge packs. While both are part of the same user manual, they describe distinct, non-overlapping functional modules with no direct semantic or logical dependency.


id: 72f3d4a0-11b1-40d5-8359-799910a059b7
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: d92f6c51-6e01-479d-83ca-d660824e27b7
type: NOT_DETECTED
created_at: 2026-03-12 22:16:00
context:
Memory A describes the UI and management of AI companions (Spirits), while Memory B describes the configuration of file and knowledge sharing (CQ Share). While both are parts of the same user manual, they describe distinct functional modules with no direct overlap in logic, data flow, or conflicting information.


id: 4e770861-0b34-4db0-91a4-b76454cb9d67
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: NOT_DETECTED
created_at: 2026-03-12 22:16:31
context:
Memory A focuses on the management of AI companions (Spirits) and their progression system, while Memory B focuses on the organization of shared content and public profile groups. While both are part of the same user manual, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: b7b1844d-9b13-446f-80c3-80418131d4c7
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 4d8a2d04-0376-4274-818b-160b12166db4
type: NOT_DETECTED
created_at: 2026-03-12 22:16:47
context:
Memory A describes the management of AI companions (Spirits) and their progression system, while Memory B describes the organization of shared content and public profile settings. While both are part of the same user manual, they describe distinct, non-overlapping functional modules with no direct semantic connection or conflict.


id: 79129408-5548-4bab-b926-fee651cd5134
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 02619512-3802-40c7-9fd4-13edfcdbf655
type: NOT_DETECTED
created_at: 2026-03-12 22:17:32
context:
Memory A focuses on the management and UI of AI companions (Spirits), while Memory B focuses on the lifecycle and sharing of files/knowledge packs (CQ Share). While both are part of the same user manual, they describe distinct, non-overlapping functional modules with no direct semantic connection.


id: 27438a0b-57ed-483b-b65a-20e9854febdb
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
type: NOT_DETECTED
created_at: 2026-03-12 22:17:57
context:
Memory A focuses on the UI and management of individual AI Spirits, while Memory B describes the technical synchronization mechanism for shared Memory Packs. While both are part of the CitadelQuest ecosystem, they describe distinct features (Spirit management vs. cross-user data syncing) with no direct functional or semantic overlap.


id: fa3cf266-6de8-427f-a0b4-7ec15b0955d7
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: NOT_DETECTED
created_at: 2026-03-12 22:18:38
context:
Memory A focuses on the management and UI of AI companions (Spirits), while Memory B focuses on the lifecycle and maintenance of shared files and memory packs (CQ Share). While both are part of the same user manual, they describe distinct functional modules with no direct overlap in logic, data flow, or conflicting information.


id: c1113586-e912-4643-b494-8aa3fc2db221
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
type: NOT_DETECTED
created_at: 2026-03-12 22:19:12
context:
Memory A focuses on individual Spirit configuration and AI model settings, while Memory B describes the CQ Share system for distributing files and memory packs. While both are part of the CitadelQuest platform, they describe distinct, non-overlapping functional modules with no direct semantic or logical dependency.


id: 70e9fa85-9c35-490c-aae6-7b222795fb55
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: d92f6c51-6e01-479d-83ca-d660824e27b7
type: NOT_DETECTED
created_at: 2026-03-12 22:19:44
context:
Memory A focuses on the configuration and management of AI Spirits, while Memory B focuses on the configuration of file sharing and public URLs. While both are sections of the same user manual, they describe distinct, non-overlapping features of the platform with no direct functional or semantic dependency.


id: 66f1e59d-8771-4a36-8b2b-7d1eefd6f5f5
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: a4102387-181b-467a-9de7-edeb48f554e0
type: NOT_DETECTED
created_at: 2026-03-12 22:20:01
context:
Memory A focuses on the configuration and management of AI Spirits, while Memory B focuses on the sharing and display configuration of files and knowledge packs. While both are part of the same user manual, they describe distinct, non-overlapping features of the platform with no direct functional or semantic dependency.


id: 47367ee1-a431-4a9d-b2a2-82beec21a041
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: NOT_DETECTED
created_at: 2026-03-12 22:20:30
context:
Memory A focuses on the configuration and management of AI Spirits, while Memory B focuses on the organization of shared content via Share Groups. While both are features of the CitadelQuest platform, they describe distinct functional areas (AI customization vs. social sharing) with no direct overlap or contradiction.


id: 4bdb5156-65f7-4e59-9e40-84336b978c50
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 02619512-3802-40c7-9fd4-13edfcdbf655
type: NOT_DETECTED
created_at: 2026-03-12 22:23:07
context:
Memory A focuses on the configuration and customization of AI Spirits, while Memory B focuses on the lifecycle management of shared content (CQ Share). While both are part of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 3a1bc553-bb92-4908-846a-d5e020f20160
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: NOT_DETECTED
created_at: 2026-03-12 22:24:13
context:
Memory A focuses on the configuration and identity of AI Spirits, while Memory B focuses on the lifecycle and maintenance of shared content (CQ Share). While both are part of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 907256cf-b676-472d-8a57-35bf57f680fd
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: 4d8a2d04-0376-4274-818b-160b12166db4
type: NOT_DETECTED
created_at: 2026-03-12 22:29:04
context:
Memory A describes the Spirit Chat Interface and AI interaction features, while Memory B focuses on Share Groups and public profile organization. There is no meaningful semantic overlap or functional connection between these two distinct UI components.


id: 3d50bc16-4541-46c2-9784-1acf35a37c82
source_id: f53218b5-f2aa-4adb-902c-e88a44f11e67
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: NOT_DETECTED
created_at: 2026-03-12 22:32:48
context:
Memory A focuses on AI Spirit tools and capabilities, while Memory B describes the 'CQ Share' system for organizing public profile content. While both are features of the CitadelQuest platform, they describe distinct functional modules with no direct semantic overlap or conflict.


id: 7d90b0d8-e75c-47ac-a06a-dfed47cc82be
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: d92f6c51-6e01-479d-83ca-d660824e27b7
type: NOT_DETECTED
created_at: 2026-03-12 22:36:02
context:
Memory A focuses on the creation and leveling mechanics of AI Spirits, while Memory B details the technical configuration of file sharing and public URLs. There is no functional or semantic overlap between these two distinct system modules.


id: 9e03b6d6-3428-428d-8b58-f4866a6cf92d
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: a4102387-181b-467a-9de7-edeb48f554e0
type: NOT_DETECTED
created_at: 2026-03-12 22:36:22
context:
Memory A focuses on the creation and gamified progression of AI Spirits, while Memory B details the configuration of shared URLs and display styles for files. There is no meaningful semantic overlap or functional connection between these two distinct system modules.


id: 51474074-239f-4b27-bfc4-428bc10854b5
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: NOT_DETECTED
created_at: 2026-03-12 22:36:45
context:
Memory A describes the creation and leveling mechanics of AI Spirits, while Memory B describes the organization of shared content into groups on a user profile. There is no meaningful functional or semantic overlap between these two distinct platform features.


id: 40bed440-621c-4999-b760-f4995f94da15
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 4d8a2d04-0376-4274-818b-160b12166db4
type: NOT_DETECTED
created_at: 2026-03-12 22:37:01
context:
Memory A focuses on the creation and gamified progression of AI Spirits, while Memory B describes the organization of shared content into Share Groups for public profiles. While both are part of the CitadelQuest manual, they describe distinct, non-overlapping features with no direct functional or semantic connection.


id: 54d59ef6-cd73-454f-a9ab-ef76798a4ccb
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
type: NOT_DETECTED
created_at: 2026-03-12 22:37:30
context:
Memory A focuses on the internal mechanics of AI Spirits (creation and leveling), while Memory B focuses on external sharing features and profile organization. While both are part of the same user manual, they describe distinct, non-overlapping systems with no direct functional or semantic connection.


id: b13f6187-4a76-48ed-8c13-323b6de4ee54
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 02619512-3802-40c7-9fd4-13edfcdbf655
type: NOT_DETECTED
created_at: 2026-03-12 22:37:59
context:
Memory A focuses on the creation and leveling mechanics of AI Spirits, while Memory B focuses on the administrative lifecycle of sharing files and memory packs. While both are part of the same user manual, they describe distinct, non-overlapping systems (character progression vs. content distribution) with no direct functional or semantic link.


id: b2a96d04-e1c0-4397-a872-ac3026ece3d9
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: NOT_DETECTED
created_at: 2026-03-12 22:38:55
context:
Memory A focuses on the creation and gamified progression of AI Spirits, while Memory B details the lifecycle and maintenance of shared content (CQ Share). While both are part of the same user manual, they describe distinct, non-overlapping features with no direct functional or semantic link.


id: cc0f9dc3-3279-4eef-af0b-214be8bde165
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: c948f87d-5941-4d4d-84a2-98e896b44105
type: NOT_DETECTED
created_at: 2026-03-12 22:39:15
context:
Memory A focuses on the creation and leveling mechanics of AI Spirits, while Memory B describes the public sharing and profile integration features of the platform. While both are part of the same software ecosystem (CitadelQuest), they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: 3d44941a-1971-4282-95f6-a3813687f377
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: f10414d1-5c2c-4f68-9977-d71212e8d9af
type: NOT_DETECTED
created_at: 2026-03-12 23:09:52
context:
Memory A describes the UI and management of AI companions (Spirits), while Memory B describes the system's data backup and restore procedures. While both are part of the same user manual, they cover distinct functional areas (feature management vs. system utility) with no direct semantic overlap or conflicting information.


id: 14a9cb48-d87d-4844-8794-b3f68f40162c
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-12 23:10:18
context:
Memory A focuses on the UI and management of AI companions (Spirits), while Memory B details the technical procedures for system backups and data restoration. There is no meaningful semantic overlap or functional connection between these two distinct features of the platform.


id: 031cb457-9c0d-46cc-a31a-b40826b62cc7
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-12 23:10:30
context:
Memory A focuses on the UI and management of AI companions (Spirits), while Memory B focuses on system-level backup and restoration procedures. While both are part of the same user manual, they describe distinct, unrelated functional modules with no direct semantic overlap or conflict.


id: 0366be30-c3d6-4597-bcca-22e21d4b10c7
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-12 23:10:43
context:
Memory A focuses on the UI and management of AI companions (Spirits), while Memory B focuses on data backup and security protocols. While both are part of the same user manual, they describe distinct functional areas with no direct semantic overlap or conflicting information.


id: b5c99e22-5f9e-4679-b1f1-dc47a509bc61
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-12 23:11:32
context:
Memory A focuses on the configuration and customization of AI Spirits, while Memory B details the technical procedures for system backups. While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or logical dependency.


id: d38917ab-93a4-43dc-8c38-f49a78e7fd46
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-12 23:11:47
context:
Memory A focuses on the configuration and customization of AI Spirits, while Memory B details the technical process of system backups and restoration. While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or conflicting information.


id: c68f6e1f-97d3-4d67-97de-7812320fe108
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-12 23:12:17
context:
Memory A focuses on the configuration and customization of AI Spirits, while Memory B focuses on data backup and security protocols. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: eaa50d31-e50a-4065-a0c4-484a86e7825d
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-12 23:15:12
context:
Memory A describes the UI and functionality of the Spirit Chat interface, while Memory B details the system's backup and restore procedures. There is no meaningful semantic overlap or functional connection between these two distinct features.


id: 2497a867-d7a5-4b69-a626-99b97c436714
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: f10414d1-5c2c-4f68-9977-d71212e8d9af
type: NOT_DETECTED
created_at: 2026-03-12 23:17:53
context:
Memory A focuses on the creation and gamified progression of AI Spirits, while Memory B details the technical backup and restore procedures for the platform. While both are part of the same user manual, they describe distinct, unrelated systems with no functional or semantic overlap.


id: 2f54f5d7-c61e-4cc6-8dc9-c0d707fb29f4
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: ce8748d3-07f3-458d-b031-05996cd7ecc8
type: RELATES_TO
created_at: 2026-03-12 23:18:06
context:
Memory B describes the backup process for data types (memories, conversations) generated in Memory A


id: 030e5f87-b766-4125-948a-4e640c0d6783
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-12 23:18:26
context:
Memory A focuses on the creation and gamified progression of AI Spirits, while Memory B details the technical procedures for system backups and restoration. There is no meaningful semantic overlap or functional connection between these two distinct features of the platform.


id: b1c79f15-fb19-4cdc-878b-e7c93d7c5e78
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-12 23:18:38
context:
Memory A focuses on the creation and gamified progression of AI Spirits, while Memory B details the technical procedures for database backups and restoration. There is no meaningful semantic or functional overlap between these two distinct system modules.


id: 6f8cd214-5041-421c-ba16-2ce68ddf3c23
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-12 23:18:51
context:
Memory A focuses on the mechanics of Spirit creation and the XP-based progression system, while Memory B focuses on data backup procedures and security best practices. There is no meaningful semantic overlap or functional connection between these two technical modules.


id: bed0827c-a384-4cc8-8647-5c4c218f43cf
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-12 23:19:31
context:
Memory A describes the 'Spirits' AI companion system, while Memory B describes administrative 'User Management' functions. While both are parts of the same platform (CitadelQuest), they describe distinct, non-overlapping systems (end-user AI features vs. administrative backend controls) with no direct functional or semantic dependency.


id: 27011eb5-143b-40b8-a5d3-5f658203793d
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-12 23:19:49
context:
Memory A describes the 'Spirits' feature (AI companions), while Memory B describes the administrative update process for the application. While both are part of the CitadelQuest User Manual, they cover distinct functional areas (user-facing AI features vs. system-level administration) with no direct semantic overlap or conflicting information.


id: 3af6c91c-b74b-436a-a0df-8f4b2e1de7b4
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-12 23:20:02
context:
Memory A focuses on the conceptual and functional aspects of 'Spirits' (AI companions), while Memory B focuses on administrative system settings like user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct modules of the platform.


id: 0640e973-a3b3-46ce-8459-2b4896a29d36
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-12 23:20:16
context:
Memory A focuses on the 'Spirits' feature (AI companions), while Memory B focuses on administrative server logs and system backups. While both are parts of the CitadelQuest User Manual, they describe distinct, non-overlapping functional areas (user-facing AI features vs. backend administrative tools) with no direct semantic connection or conflict.


id: e9cef3f1-9c9c-4851-9dbd-ccb93092c590
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-12 23:20:34
context:
Memory A focuses on the conceptual and functional aspects of 'Spirits' as AI companions, while Memory B details administrative procedures for user account migrations between servers. There is no meaningful semantic or functional overlap between these two distinct areas of the platform.


id: b99be273-5ac9-49f4-a1ee-2e939ac934c5
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-12 23:21:31
context:
Memory A describes the user-facing Spirits management interface and AI companion features, while Memory B describes administrative system update procedures. They cover distinct functional areas of the application (user features vs. system administration) with no semantic overlap or conflicting information.


id: d240b558-bb60-4d4e-9dec-3bfdf90880f6
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-12 23:21:58
context:
Memory A focuses on the user-facing Spirits management interface and AI companion mechanics, while Memory B focuses on administrative system settings like user registration and homepage redirects. There is no meaningful semantic overlap or functional connection between these two distinct parts of the manual.


id: 52ac44fa-a231-42f4-94ed-c713333f3666
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-12 23:22:27
context:
Memory A focuses on the user-facing Spirits management interface and AI companion mechanics, while Memory B focuses on administrative server logs and system-wide backup functions. There is no meaningful semantic overlap or functional connection between these two distinct modules of the application.


id: 7fda354e-1ed5-401d-b360-5731c72ef230
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-12 23:22:40
context:
Memory A describes the user-facing interface for managing AI companions (Spirits), while Memory B describes administrative tools for account migrations between servers. There is no meaningful functional, semantic, or logical connection between these two distinct areas of the application.


id: 41549649-fc5e-4531-8bed-f98a7536624f
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-12 23:23:16
context:
Memory A focuses on the configuration and customization of AI Spirits, while Memory B focuses on administrative user management and system-level controls. While both are part of the CitadelQuest platform manual, they describe distinct functional areas (user-facing AI features vs. admin-facing system management) with no direct overlap or contradiction.


id: aa532eee-e0e0-4124-a706-6c7c657e60bb
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-12 23:23:34
context:
Memory A focuses on individual AI Spirit configuration and customization, while Memory B details system-wide administrative update procedures. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: d580b351-8182-441b-9bfb-950e7cb59702
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-12 23:23:54
context:
Memory A focuses on individual Spirit configuration and AI model settings, while Memory B focuses on system-level administration and homepage redirects. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: c37cea7e-fb32-4400-ba32-922c054e1d15
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-12 23:24:07
context:
Memory A focuses on individual AI Spirit configuration and customization, while Memory B focuses on system-wide administrative logs and backups. While both are part of the same user manual, they describe distinct, unrelated functional areas of the platform (user-level AI settings vs. admin-level server maintenance).


id: d87e42f0-d055-4f13-b7f5-fbaa0ff72c3b
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-12 23:24:19
context:
Memory A focuses on individual AI Spirit configuration and customization, while Memory B focuses on administrative account migration procedures between servers. There is no meaningful semantic or functional overlap between these two distinct areas of the platform.


id: e333a1fb-1d06-45df-ad8e-599fd4b434b7
source_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-12 23:24:49
context:
Memory A focuses on individual Spirit (AI companion) development and memory visualization, while Memory B focuses on administrative user management and system-level controls. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: a60ad3d6-da92-4d14-aa76-836c1ab21759
source_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-12 23:25:02
context:
Memory A focuses on the user-facing Spirit development and memory visualization features, while Memory B details the technical administrative process for application updates. There is no meaningful semantic or functional overlap between these two distinct areas of the platform.


id: a7b4f0ff-cca3-4900-98eb-9889bf968b11
source_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-12 23:25:32
context:
Memory A focuses on the user-facing 'Spirit' development and memory visualization features, while Memory B focuses on administrative system settings and homepage redirects. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: 4e4a27eb-8a96-4c90-bfd9-0b6fac389d34
source_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-12 23:26:48
context:
Memory A focuses on the user-facing features of Spirit development and memory visualization, while Memory B focuses on administrative server migration procedures. There is no meaningful semantic overlap or functional connection between these two distinct sections of the manual.


id: 0e14d416-2dc9-4c61-833d-ff5fb1590a44
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-12 23:27:12
context:
Memory A describes the user-facing Spirit Chat interface and AI features, while Memory B describes the administrative dashboard and system management. There is no meaningful functional or semantic overlap between these two distinct areas of the platform.


id: fdc9399e-6d6b-4b6b-a450-5fffa99f837e
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-12 23:27:42
context:
Memory A describes the UI and functionality of the Spirit Chat interface, while Memory B details administrative user management tools. These are distinct functional areas of the platform (user-facing AI features vs. backend administration) with no direct semantic overlap or conflicting information.


id: a36c30ae-fd99-4a66-bf69-1055c5478a29
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-12 23:27:56
context:
Memory A describes the UI and features of the Spirit Chat interface, while Memory B details the administrative process for application updates. There is no meaningful semantic or functional connection between these two distinct parts of the user manual.


id: 3eee187f-7d0e-478e-8488-00ca7d72c655
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-12 23:28:12
context:
Memory A describes the UI and functionality of the Spirit Chat interface, while Memory B details administrative system settings like user registration and homepage redirects. There is no meaningful semantic overlap or functional connection between these two distinct parts of the platform.


id: 9c1801ad-3744-4f13-9ef3-2bc58b0de492
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-12 23:28:29
context:
Memory A describes the user-facing Spirit Chat Interface and AI interaction features, while Memory B describes administrative backend tools for logs and backups. There is no meaningful semantic overlap or functional connection between these two distinct parts of the platform.


id: e2881bab-cb3f-4029-b63f-9ccfa73aa772
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-12 23:28:42
context:
Memory A focuses on the Spirit Chat Interface and AI companion features, while Memory B details administrative procedures for user migrations between Citadels. There is no meaningful semantic or functional overlap between these two distinct modules of the platform.


id: be84e5e5-675d-44f2-af5a-be844057856a
source_id: f53218b5-f2aa-4adb-902c-e88a44f11e67
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-12 23:29:22
context:
Memory A focuses on AI Spirit capabilities and tools, while Memory B focuses on administrative user management. While both are part of the same user manual, they describe distinct, non-overlapping functional areas of the platform with no direct semantic or logical dependency.


id: d9018100-5597-4670-827e-763120a680e3
source_id: f53218b5-f2aa-4adb-902c-e88a44f11e67
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-12 23:29:55
context:
Memory A focuses on AI Spirit capabilities and functional tools, while Memory B focuses on administrative system settings like user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct sections of the user manual.


id: 0607ea15-cde8-4dbd-8fc3-7d068314cb27
source_id: f53218b5-f2aa-4adb-902c-e88a44f11e67
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-12 23:30:53
context:
Memory A focuses on AI Spirit capabilities and tool usage, while Memory B focuses on administrative migration procedures between Citadels. There is no meaningful semantic or functional overlap between these two distinct sections of the user manual.


id: 1be19138-c60d-49c1-8301-9ab26154ed96
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-12 23:31:06
context:
Memory A focuses on the end-user experience regarding Spirit creation and gamified progression, while Memory B focuses on system-level administrative functions and dashboard management. There is no direct functional or semantic overlap between these two distinct modules of the application.


id: 3e8b270d-fbee-4038-bf28-39778676f83d
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-12 23:31:26
context:
Memory A focuses on the mechanics of AI Spirit creation and progression, while Memory B details administrative user management and system settings. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: a5d52839-492f-4f26-87a3-fac951c9e356
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-12 23:31:52
context:
Memory A focuses on the gamified progression and creation of AI Spirits, while Memory B details the technical administrative process for updating the application software. There is no meaningful semantic overlap or functional connection between these two distinct areas of the manual.


id: aad7ba55-e091-4c0a-aa98-632bde1c1357
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-12 23:32:22
context:
Memory A focuses on the creation and gamified progression of AI Spirits, while Memory B details administrative system settings like user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct parts of the user manual.


id: 7d03e4fc-4e19-4c09-ac4c-9e4744f6e43d
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-12 23:32:42
context:
Memory A focuses on the user-facing Spirit creation and gamified progression system, while Memory B focuses on administrative server logs and system backups. There is no meaningful semantic or functional overlap between these two distinct modules of the platform.


id: c45aec87-522f-4a5d-9567-da37e7d98070
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-12 23:32:59
context:
Memory A focuses on the creation and gamified progression of AI Spirits, while Memory B details administrative procedures for user account migrations between servers. There is no meaningful semantic or functional overlap between these two distinct features of the platform.


id: f31f6f0a-880f-40d6-9ecf-54118a760aba
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-12 23:34:16
context:
Memory A describes the conceptual and functional nature of 'Spirits' (AI companions), while Memory B details the technical administrative procedures for system updates and installation. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: be856c38-3dbc-4e61-9983-543e2b7c53dc
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-12 23:34:32
context:
Memory A focuses on the conceptual and functional aspects of 'Spirits' (AI companions), while Memory B focuses on technical installation, PWA support, and multi-user architecture. While both are sections of the same user manual, they describe distinct, non-overlapping systems (features vs. infrastructure) without a direct semantic or functional link.


id: 559d5ad5-1d6a-435a-941c-0545f6b73155
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: RELATES_TO
created_at: 2026-03-12 23:34:45
context:
Memory B describes the technical infrastructure (AI Gateway) required to power the Spirits in Memory A


id: 17aecd50-4ad7-4b48-b1b5-da98a238a435
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-12 23:35:33
context:
Memory A focuses on the UI and management of AI companions (Spirits), while Memory B focuses on server-side installation and domain configuration. There is no meaningful semantic overlap or functional dependency between these two specific pieces of documentation.


id: dd6d59f0-1682-44c4-bec2-c43b3197d09e
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-12 23:35:46
context:
Memory A describes the user-facing UI for managing AI companions (Spirits), while Memory B describes backend administrative procedures for system updates and maintenance. There is no meaningful semantic overlap or functional connection between these two distinct parts of the manual.


id: dd94d91e-94cf-4871-9124-e12fbd233b81
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-12 23:36:05
context:
Memory A focuses on the UI and management of AI companions (Spirits), while Memory B focuses on technical installation, PWA support, and multi-user database architecture. While both are parts of the same user manual, they describe distinct functional areas with no direct semantic overlap or logical dependency.


id: 8976b846-be4b-4c08-b072-14875f90f19a
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-12 23:37:09
context:
Memory A focuses on the user-facing configuration of AI Spirits, while Memory B details administrative system maintenance and update procedures. There is no meaningful semantic overlap, reinforcement, or contradiction between these two distinct functional areas of the platform.


id: 74208c66-5312-4709-8426-170a8ff0f7d3
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-12 23:37:23
context:
Memory A focuses on the internal configuration and features of AI Spirits, while Memory B focuses on the technical deployment and multi-user architecture of the platform. There is no direct functional or semantic overlap between Spirit settings and PWA/installation procedures.


id: 778267cd-9f70-4b3d-bc7a-4fc16c542447
source_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-12 23:38:29
context:
Memory A focuses on user-facing features for Spirit AI management and memory visualization, while Memory B details administrative system maintenance and installation procedures. There is no meaningful semantic overlap or functional dependency between these two distinct sections of the user manual.


id: 464b2430-b396-4a90-8851-b1c91d08bee2
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-12 23:40:07
context:
Memory A describes the UI/UX features of the Spirit Chat interface, while Memory B focuses on server-side installation and domain configuration. There is no direct functional or semantic overlap between them.


id: f7ec011a-5de1-48a3-b9f6-7f9ed4ef5a30
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-12 23:40:27
context:
Memory A describes the user-facing Spirit Chat interface and AI features, while Memory B describes the administrative backend process for system updates and installation. There is no meaningful semantic overlap or functional connection between these two distinct sections of the manual.


id: 73dd63e3-e417-4226-a3c0-4d44f8a77c91
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: REINFORCES
created_at: 2026-03-12 23:40:56
context:
Memory B provides the infrastructure (AI Gateway) that enables the Spirit Chat described in Memory A


id: 187641d3-6777-4614-ac16-201e04ae714e
source_id: f53218b5-f2aa-4adb-902c-e88a44f11e67
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-12 23:42:20
context:
Memory A focuses on the functional capabilities and AI tools of the Spirits within the platform, while Memory B details the administrative procedures for system updates and installation. There is no meaningful semantic overlap or functional connection between the AI's toolset and the server maintenance protocols.


id: 5a9cf4ce-1186-4d75-9548-968094ed1d09
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-12 23:43:42
context:
Memory A focuses on the internal gamification and creation of AI Spirits, while Memory B focuses on the technical server-side installation and domain configuration. There is no meaningful semantic overlap or functional connection between these two distinct parts of the manual.


id: 321eacce-f11f-40f0-ba34-c5e9023ef608
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-12 23:44:07
context:
Memory A focuses on the gameplay mechanics of Spirit creation and progression, while Memory B details technical administrative procedures for system updates and installation. There is no meaningful semantic or functional overlap between these two distinct areas of the user manual.


id: 95334354-2023-422f-aeb4-d40566d18f2d
source_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
target_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
type: NOT_DETECTED
created_at: 2026-03-13 00:01:31
context:
Memory A describes the technical process of knowledge extraction and graph building, while Memory B describes a decentralized messaging protocol. While both are features of CitadelQuest, they serve distinct functional purposes (knowledge management vs. communication) with no direct semantic overlap or logical dependency.


id: b3b5e1aa-33da-4495-89b1-ad987baa9ffd
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
type: NOT_DETECTED
created_at: 2026-03-13 00:02:49
context:
Memory A focuses on the technical implementation of memory analysis and knowledge graphs, while Memory B describes the decentralized messaging protocol for CQ Chat. While both are features of the CitadelQuest platform, they describe distinct functional modules with no direct semantic overlap or logical dependency.


id: 6187db78-dc1b-4ada-9529-82330dde45d9
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
type: NOT_DETECTED
created_at: 2026-03-13 00:03:05
context:
Memory A focuses on the technical functionality of memory analysis and background jobs within the CQ Memory system, while Memory B describes the UI navigation and access methods for the CQ Chat interface. While both are part of the same user manual, they describe distinct, non-overlapping features with no direct functional or semantic connection.


id: 8b27ff0f-96f2-4c0a-8a32-0f5908100fc0
source_id: d53d081b-6f67-4155-8069-711b2449468c
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: RELATES_TO
created_at: 2026-03-13 00:50:32
context:
Memory A describes how memory is used by Spirits, while Memory B describes how that memory stays updated.


id: 9377d3d8-cdd5-41b1-86b5-d5c53274ae7c
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: RELATES_TO
created_at: 2026-03-13 01:09:30
context:
Memory A defines the internal structure of memory nodes, while Memory B explains their distribution.


id: c66ed6fa-85c1-4f1e-bf33-f8c64bb4748b
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: RELATES_TO
created_at: 2026-03-13 02:15:51
context:
Both documents are sections of the CQ User Manual regarding system functionality and data management


id: 6e90a9d2-eba9-4553-a29d-92f27d6e200d
source_id: e6da62d1-5272-4316-8fa4-652f2a8ad291
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: RELATES_TO
created_at: 2026-03-13 02:18:17
context:
Both memories describe data management and persistence mechanisms within the CitadelQuest ecosystem.


id: 6b51d60e-f256-438b-a76d-4259d6c74df5
source_id: c2108434-8b74-46a0-845d-5abb287a9cec
target_id: ce8748d3-07f3-458d-b031-05996cd7ecc8
type: REINFORCES
created_at: 2026-03-13 02:20:58
context:
Memory B confirms that 'memories' described in Memory A are included in system-wide .citadel backups


id: 0c0bbd0f-a538-4bc5-9155-3aefd4dc68c4
source_id: df4f6b2b-ec31-4523-a509-90382945cc1d
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 02:26:57
context:
Memory A describes the CQ Memory knowledge management system, while Memory B focuses on administrative user management tasks. There is no meaningful semantic or functional overlap between these two distinct modules of the platform.


id: 0f817193-60de-4055-b515-fc4d10909f01
source_id: df4f6b2b-ec31-4523-a509-90382945cc1d
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 02:27:15
context:
Memory A describes the CQ Memory knowledge management system, while Memory B details the application update and administration procedures. There is no meaningful semantic or functional overlap between these two distinct technical modules.


id: b9d5e13a-7d2c-4098-abca-cf238a16c509
source_id: df4f6b2b-ec31-4523-a509-90382945cc1d
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 02:27:28
context:
Memory A focuses on the CQ Memory knowledge management system and 3D graphs, while Memory B focuses on administrative system settings like user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two technical modules.


id: 29240a1f-0b6d-464d-92fc-9e6e88907bab
source_id: df4f6b2b-ec31-4523-a509-90382945cc1d
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 02:27:41
context:
Memory A focuses on the CQ Memory system for knowledge management and 3D graphs, while Memory B focuses on administrative server logs and system backups. While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or logical dependency.


id: 4f40feee-6d4e-4313-9d6d-839e47b0236f
source_id: df4f6b2b-ec31-4523-a509-90382945cc1d
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:27:59
context:
Memory A focuses on the CQ Memory system for knowledge management and 3D graphs, while Memory B focuses on administrative procedures for user account migrations between Citadels. There is no meaningful semantic or functional overlap between these two distinct system components.


id: a440ff66-68bb-469a-857b-da8af7662daf
source_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 02:28:29
context:
Memory A describes the Memory Explorer UI for knowledge graph visualization, while Memory B describes the User Management administrative interface. They represent distinct, unrelated functional modules within the CitadelQuest platform with no overlapping content or conflicting information.


id: 4de9781e-1c1f-4a70-8ed9-a0f69124f1ae
source_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 02:28:50
context:
Memory A describes the Memory Explorer UI and knowledge graph management, while Memory B details the application update process and administrative functions. While both are sections of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: c27271be-465b-4a07-bafa-535439c00c43
source_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 02:29:12
context:
Memory A focuses on the Memory Explorer UI and knowledge graph management, while Memory B focuses on administrative system settings like user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct modules of the platform.


id: c7b86a58-979f-4b81-8bc2-aa832d3f7fb4
source_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:30:09
context:
Memory A describes a user-facing interface for knowledge graph visualization and memory management, while Memory B describes administrative tools for user account migrations between servers. There is no meaningful semantic connection, reinforcement, or contradiction between these two distinct functional areas of the platform.


id: 5dff2cf4-fe74-4f2b-9899-9438d837a755
source_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 02:30:38
context:
Memory A describes the technical process of memory extraction and knowledge graph creation, while Memory B focuses on administrative dashboard functions and user management. There is no meaningful semantic or functional overlap between these two distinct system components.


id: 89888247-ad29-4f78-b362-c8146d7ebd0c
source_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 02:30:57
context:
Memory A focuses on the technical process of memory extraction and knowledge graph creation, while Memory B details administrative user management functions. There is no meaningful semantic or functional overlap between these two distinct system modules.


id: a7202a7c-c2c6-4202-8608-f715bc5ebd4d
source_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 02:31:10
context:
Memory A describes the technical process of data extraction and knowledge graph creation, while Memory B details the administrative procedure for updating the CitadelQuest software. There is no meaningful semantic or functional overlap between these two distinct system features.


id: ba479ee2-eca6-4bd3-9edc-ead7a6e85738
source_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 02:31:24
context:
Memory A focuses on the technical process of data extraction and knowledge graph creation, while Memory B details administrative system settings like user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct modules of the software.


id: fdf3b212-750d-4501-99ca-973170aeaeb5
source_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 02:31:44
context:
Memory A focuses on the user-level Memory Extraction process and knowledge graph creation, while Memory B focuses on system-level administrative logs and backups. There is no meaningful semantic or functional overlap between these two distinct modules of the application.


id: d45a8aa2-369b-45d0-9321-c3cc052c07e6
source_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:31:54
context:
Memory A focuses on the technical process of knowledge extraction and memory graph management, while Memory B details administrative procedures for user account migrations between servers. There is no meaningful semantic or functional overlap between these two distinct system features.


id: 921f9a64-95db-4cad-a655-8c04d735a2a5
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 02:32:07
context:
Memory A focuses on the technical functionality of memory analysis and knowledge graphs, while Memory B describes the administrative dashboard and user management. While both are sections of the same user manual, they describe distinct, non-overlapping features of the system with no direct functional or semantic connection.


id: 548b92c9-0938-480b-8443-e67134435556
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 02:32:22
context:
Memory A describes the technical functionality of memory analysis and knowledge graphs, while Memory B describes administrative user management and account controls. There is no meaningful semantic overlap, reinforcement, or contradiction between these two distinct functional areas of the application.


id: 5bc76c56-3652-4d28-bf10-a2cdf990454c
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 02:32:33
context:
Memory A focuses on the technical functionality of memory analysis and knowledge graphs, while Memory B describes the administrative process for application updates. There is no meaningful semantic overlap or logical connection between these two distinct system features.


id: ed4571fd-ea93-4d46-981a-5981d9a8f357
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 02:32:46
context:
Memory A focuses on technical memory analysis and knowledge graph discovery within the CQ Memory system, while Memory B details administrative settings for user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct modules of the application.


id: ff2d4354-a211-4f3a-b919-b8c51b8a70a7
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:33:13
context:
Memory A focuses on the technical functionality of memory analysis and knowledge graph discovery within the CQ Memory system. Memory B details administrative procedures for user account migrations between server instances. While both are part of the same user manual, they describe entirely different functional domains (knowledge management vs. system administration) with no semantic overlap or logical connection.


id: f4244fab-7c88-41c2-afaa-87924668b3ff
source_id: d53d081b-6f67-4155-8069-711b2449468c
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 02:33:42
context:
Memory A focuses on the technical implementation of the Spirit Memory system and knowledge graphs, while Memory B describes the administrative dashboard and user management features. While both are part of the same user manual, they describe distinct, non-overlapping functional areas of the platform with no direct semantic connection.


id: 47560158-665d-4165-9e9c-3a68737d247e
source_id: d53d081b-6f67-4155-8069-711b2449468c
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 02:34:01
context:
Memory A focuses on the technical implementation of the Spirit Memory Integration system, while Memory B details administrative user management functions. There is no meaningful semantic overlap or functional connection between these two distinct modules of the platform.


id: dfc89dad-1ab1-47bb-b23b-8ab2f1d9765c
source_id: d53d081b-6f67-4155-8069-711b2449468c
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 02:34:12
context:
Memory A describes the technical implementation of the Spirit Memory Integration system, while Memory B describes the administrative process for application updates. There is no meaningful semantic or functional overlap between these two distinct system components.


id: 2a5897ad-e7f4-43ef-a47c-d65fabcc5cf6
source_id: d53d081b-6f67-4155-8069-711b2449468c
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 02:34:30
context:
Memory A focuses on the technical implementation of the Spirit Memory Integration and recall workflows, while Memory B details administrative system settings like user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct areas of the platform.


id: de1fd196-e0b2-4925-a57b-cfb216e49ff5
source_id: d53d081b-6f67-4155-8069-711b2449468c
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 02:34:42
context:
Memory A focuses on the technical implementation of the Spirit Memory Integration system (AI recall and knowledge graphs), while Memory B focuses on administrative server maintenance (logs and backups). While both are part of the same user manual, they describe distinct functional areas with no direct semantic overlap or logical dependency.


id: fd6f4b7f-77c6-42ac-bfae-a437fd58d3ed
source_id: d53d081b-6f67-4155-8069-711b2449468c
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:34:56
context:
Memory A focuses on the technical implementation of the Spirit Memory system and knowledge graphs, while Memory B describes administrative procedures for user account migrations between servers. There is no meaningful semantic or functional overlap between these two distinct system components.


id: e4775e66-9e9b-4321-a5c5-288d4e48f162
source_id: e6da62d1-5272-4316-8fa4-652f2a8ad291
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 02:35:47
context:
Memory A focuses on the 'Sharing and Syncing' of user-level Memory Packs within the knowledge management system, while Memory B describes the administrative process for system-wide application updates and server maintenance. There is no meaningful semantic or functional overlap between these two distinct operational areas.


id: 261b004f-f67c-4849-9d7e-60e1f8c1ede5
source_id: e6da62d1-5272-4316-8fa4-652f2a8ad291
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:36:55
context:
Memory A focuses on user-level data sharing and syncing of Memory Packs within the knowledge management system, while Memory B focuses on administrative procedures for full account migrations between server instances. There is no direct functional or semantic overlap between these two distinct system features.


id: 25d984b9-71ad-42d5-828b-2a22cb9fbd7f
source_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 02:37:51
context:
Memory A focuses on the functional use cases of the CQ Memory system (knowledge management and analysis), while Memory B details the technical administrative process for application updates. While both are part of the same user manual, they describe distinct, unrelated subsystems with no semantic overlap or functional dependency.


id: d2ee20dc-9b74-46a1-83cd-670b41bf346f
source_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:38:38
context:
Memory A focuses on the CQ Memory system and knowledge management use cases, while Memory B focuses on administrative migration procedures between Citadels. There is no meaningful semantic or functional overlap between these two distinct modules of the system.


id: 257a2b94-80a3-4fc0-9185-af5fce917591
source_id: c2108434-8b74-46a0-845d-5abb287a9cec
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 02:39:02
context:
Memory A focuses on the technical structure of the knowledge management system (Memory Packs and Libraries), while Memory B focuses on administrative dashboard functions and user management. While both are parts of the same user manual, they describe distinct, non-overlapping functional areas with no direct semantic or logical connection.


id: c57160c8-5de6-4fa4-b9e1-57a50ca89df8
source_id: c2108434-8b74-46a0-845d-5abb287a9cec
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 02:39:22
context:
Memory A focuses on the technical structure of the knowledge management system (Memory Packs and Libraries), while Memory B focuses on administrative user management and access control. There is no meaningful semantic overlap or functional connection between these two distinct modules of the software.


id: a3c0ce3c-c799-4639-925e-50367eb4a28e
source_id: c2108434-8b74-46a0-845d-5abb287a9cec
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 02:40:03
context:
Memory A focuses on the technical structure of the knowledge management system (Memory Packs and Libraries), while Memory B focuses on administrative system settings (user registration and homepage redirects). There is no meaningful semantic or functional overlap between these two distinct modules of the software.


id: c92a1d79-0dae-4d80-8135-726abb81ff9d
source_id: c2108434-8b74-46a0-845d-5abb287a9cec
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 02:40:22
context:
Memory A focuses on the modular knowledge management system (Memory Packs), while Memory B focuses on administrative server logs and system backups. While both are part of the same user manual, they describe distinct functional domains (knowledge architecture vs. system administration) with no direct semantic overlap or conflict.


id: 31b7b67d-6c5b-4e7d-a052-e1a2606d28fd
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 02:41:17
context:
Memory A describes the technical structure of the Memory Library system, while Memory B focuses on administrative user management functions. There is no meaningful semantic overlap or functional connection between these two distinct system modules.


id: b816080e-ce4b-406d-93ff-9cbf161cd7ac
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 02:41:41
context:
Memory A describes the internal data structure of the memory system, while Memory B describes the application update process. There is no meaningful semantic overlap or logical connection between how memories are stored and how the software is updated.


id: 6f6ae047-3112-439b-a80b-1bd9d78747e7
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 02:41:56
context:
Memory A focuses on the technical structure of the Memory Library system and node attributes, while Memory B details administrative settings for user registration and homepage redirects. While both are sections of the same user manual, they describe distinct, unrelated functional modules of the software with no semantic overlap or logical dependency.


id: 0a3b833c-73ba-406c-8fd5-aae0180b66c3
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 02:42:09
context:
While both memories are sections of the same user manual, they describe distinct, unrelated systems: one focuses on the end-user knowledge management system (Memory Library), while the other focuses on administrative server maintenance (Logs and Backups). There is no meaningful semantic or functional overlap.


id: 73f9993e-67aa-43e7-9777-8dcd03601a42
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:42:24
context:
Memory A describes the technical structure of the Memory Library system, while Memory B describes administrative procedures for user migrations between servers. While both are part of the same user manual, they cover distinct, unrelated functional areas of the software.


id: aa4976e2-1cb6-4ce4-b544-c97261b472b8
source_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 02:42:57
context:
Memory A focuses on the technical structure of the memory node system and knowledge mapping, while Memory B details administrative user management and account controls. While both are sections of the same user manual, they describe distinct, unrelated functional modules (Knowledge Management vs. User Administration) with no semantic overlap or conflicting information.


id: 4937e5c5-9aa8-4bf4-8c71-ce00a6ea7582
source_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 02:44:05
context:
Memory A describes the internal data structure and graph visualization of the memory system, while Memory B details the administrative process for software updates. While both are part of the same user manual, they describe distinct functional areas (knowledge management vs. system maintenance) with no meaningful semantic overlap or logical dependency.


id: e2897292-3714-4713-b2a9-d9269a51c631
source_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 02:44:19
context:
Memory A focuses on the technical structure of memory nodes and graph relationships, while Memory B details administrative settings for user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct system components.


id: 6873ec6a-738e-40c7-aed3-f8a7d63ab3c4
source_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:44:45
context:
Memory A focuses on the technical structure of the knowledge management system (memory nodes and graph relationships), while Memory B focuses on administrative procedures for user account migrations between servers. There is no meaningful semantic or functional overlap between these two distinct system components.


id: 86e302fb-11d3-4eac-aff8-df56380b3567
source_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 02:45:18
context:
Memory A describes the technical structure of the memory graph system and relationship types, while Memory B details administrative user management functions. While both are sections of the same user manual, they describe distinct, unrelated features of the platform with no semantic overlap or functional dependency.


id: 16ed3a6b-0921-42da-9554-9a6cf42bae17
source_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 02:46:01
context:
Memory A focuses on the technical definitions of data relationships within the knowledge management system, while Memory B focuses on administrative settings for user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct sections of the user manual.


id: e51d5177-63f9-4d9c-b4e1-f12e04bf6e4f
source_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 02:46:27
context:
Memory A focuses on the semantic structure and visualization of the memory system, while Memory B focuses on administrative server logs and system backups. While both are part of the same user manual, they describe distinct functional areas (knowledge management vs. system administration) with no direct semantic overlap or conflict.


id: db3d8458-3446-411d-99eb-6c37b79bb23e
source_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 02:46:41
context:
Memory A describes the technical schema for knowledge graph relationships, while Memory B describes administrative procedures for user account migrations. There is no meaningful semantic overlap or logical connection between these two distinct functional areas of the software.


id: b3a9b9c0-424b-42c6-a8db-a817dfb0478e
source_id: df4f6b2b-ec31-4523-a509-90382945cc1d
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 02:47:57
context:
Memory A describes the CQ Memory feature for knowledge management, while Memory B details the technical system maintenance and update procedures. While both are part of the same user manual, they cover distinct functional areas (AI features vs. server administration) with no direct semantic overlap or logical dependency.


id: 0ccccbb9-45d6-4ed4-b419-6f2596697157
source_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 02:49:38
context:
Memory A describes the UI and functionality of the Memory Explorer knowledge graph interface, while Memory B details the system update and maintenance procedures. While both are part of the CitadelQuest User Manual, they cover distinct functional areas (feature usage vs. system administration) with no direct semantic overlap or logical connection.


id: 2f3cf8db-68f6-4be3-9bcf-7e59c8a7eaeb
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 02:52:54
context:
Memory A focuses on the technical functionality of memory analysis and relationship discovery within the application, while Memory B details the initial installation and deployment methods for the software. There is no meaningful semantic overlap or logical connection between the internal memory processing logic and the server installation procedures.


id: dc2b0541-0a59-4193-9063-22776cc00142
source_id: b7adbc37-239e-41fc-917c-62b612be0cf6
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 02:53:25
context:
Memory A focuses on the technical functionality of memory analysis and relationship discovery within the knowledge graph, while Memory B details the administrative procedures for system updates and maintenance. There is no meaningful semantic overlap or logical connection between these two distinct functional areas of the application.


id: 93dcac5c-7685-4f1b-8b57-5c0480654c65
source_id: d53d081b-6f67-4155-8069-711b2449468c
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 02:54:45
context:
Memory A describes the internal mechanics of the Spirit Memory Integration system, while Memory B focuses on the initial installation and deployment methods of the CitadelQuest platform. While both are part of the same user manual, they cover distinct functional areas (feature usage vs. system setup) with no direct semantic overlap or conflicting information.


id: 67597d01-2733-4c49-bc1a-495097a2f459
source_id: d53d081b-6f67-4155-8069-711b2449468c
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 02:55:27
context:
Memory A describes the technical implementation of the Spirit Memory Integration system, while Memory B describes the administrative process for system updates and maintenance. There is no meaningful semantic overlap or functional connection between these two distinct operational areas.


id: 2383d04d-2ee2-4959-9b78-22a0f96aa7d4
source_id: e6da62d1-5272-4316-8fa4-652f2a8ad291
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 02:57:17
context:
Memory A focuses on user-level features for sharing and syncing knowledge packs, while Memory B focuses on administrative system maintenance and software updates. There is no direct functional or semantic overlap between the two.


id: 2ecbac4e-c31b-4e00-8652-9ff45e2033e2
source_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 02:59:26
context:
Memory A focuses on the functional use cases of the CQ Memory system (knowledge management and graph analysis), while Memory B focuses on the technical administrative procedures for system updates and maintenance. While both are part of the same user manual, they describe distinct, non-overlapping domains of the software with no direct semantic connection or conflict.


id: 56a4329b-a07f-4cc0-8865-e1a0b1b20aec
source_id: 84185171-3b5f-487e-b788-38c288c23e88
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 03:02:39
context:
Memory A describes the internal data structure of the memory system, while Memory B describes the administrative process for software updates. While both are part of the same user manual, they cover distinct functional areas (data architecture vs. system maintenance) with no direct semantic overlap or conflict.


id: 9e8c3d42-5f84-4539-9df5-1183bf17b316
source_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 03:04:38
context:
While both memories are sections of the same user manual, they describe distinct, non-overlapping functional areas: Memory A focuses on the internal data structure of the memory graph system, while Memory B focuses on server-side maintenance and update procedures. There is no meaningful semantic or logical connection between the two.


id: 2210bdf0-4155-427b-908e-b2cc9c86cdc8
source_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 03:06:18
context:
Memory A focuses on the semantic structure of the knowledge graph (relationship types), while Memory B focuses on server-side installation and environment configuration. There is no meaningful topical overlap or logical connection between the two.


id: 9946800d-bf81-4cad-9c2a-6f2715fd9018
source_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 03:06:32
context:
Memory A describes the semantic data structure and relationship types of the memory system, while Memory B describes the server maintenance and software update procedures. There is no meaningful semantic connection between the internal logic of memory nodes and the administrative task of updating the application.


id: 0b95ed6d-4416-49a3-8d9c-b8dfd36d36ef
source_id: 697c5176-557a-4939-bbbd-f565956940af
target_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
type: NOT_DETECTED
created_at: 2026-03-13 03:09:39
context:
Memory A describes the File Browser interface and navigation, while Memory B describes the CQ Chat messaging system. While both are features of the CitadelQuest platform, they describe distinct functional modules with no direct semantic overlap or conflicting information.


id: ea3cad57-7af2-4dd5-b704-5e537cd6ac0a
source_id: 9fc3589c-f983-4f00-8ed1-296e059d7fac
target_id: d92f6c51-6e01-479d-83ca-d660824e27b7
type: RELATES_TO
created_at: 2026-03-13 03:25:33
context:
Memory B details the sharing configuration for files stored in the File Browser described in Memory A


id: 81708ff3-a640-4dc0-8bcb-3dce2ef198a9
source_id: ff00df6c-c3e8-4a0d-8fb9-33ee914ccc57
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: REINFORCES
created_at: 2026-03-13 03:35:36
context:
Memory B provides a specific technical application (Auto-Sync) for the CQ Share mechanism in Memory A


id: f01d0b5f-5719-4079-bfc7-c77a2da29fc8
source_id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: REINFORCES
created_at: 2026-03-13 04:13:17
context:
Memory B's backup protocols protect the data and files managed by the AI tools described in Memory A


id: 73bb42f9-ce60-428e-aff3-b6bfd633e01b
source_id: 9fc3589c-f983-4f00-8ed1-296e059d7fac
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 04:15:29
context:
Memory A describes the File Browser feature for personal storage, while Memory B details administrative system settings like user registration and homepage redirects. While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or conflicting information.


id: 3f9ff233-41bf-4e17-9a34-5eefbe96067e
source_id: 9fc3589c-f983-4f00-8ed1-296e059d7fac
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 04:16:07
context:
Memory A describes the File Browser feature for personal storage, while Memory B describes administrative migration procedures for user accounts. There is no meaningful semantic or functional overlap between these two distinct system features.


id: c330f9d6-1e93-4124-b7df-783ee8da9946
source_id: 697c5176-557a-4939-bbbd-f565956940af
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 04:16:48
context:
Memory A describes the UI and functionality of the File Browser (navigation, previews, file management), while Memory B describes administrative User Management (roles, deleting users, resetting passwords). While both are sections of a user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 69c5639b-298e-4d2b-80ae-72a8672b7320
source_id: 697c5176-557a-4939-bbbd-f565956940af
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 04:16:59
context:
Memory A describes the UI and navigation features of the File Browser, while Memory B details the administrative process for application updates. While both are part of the same user manual, they describe distinct, unrelated functional areas (User UI vs. Admin Maintenance) with no semantic overlap or conflicting information.


id: 664c0ea3-7565-4346-9660-b4c6a7eda9e4
source_id: 697c5176-557a-4939-bbbd-f565956940af
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 04:17:11
context:
Memory A focuses on the File Browser UI and navigation modes, while Memory B describes administrative system settings and homepage redirects. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: 3376491e-0f73-43e6-8d00-ea8180854877
source_id: 697c5176-557a-4939-bbbd-f565956940af
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 04:17:37
context:
Memory A describes the UI and functionality of the File Browser for general users, while Memory B describes administrative procedures for account migrations. There is no meaningful semantic overlap, functional connection, or logical conflict between these two distinct parts of the user manual.


id: 2a1cd2ba-969e-43fc-8b13-3e2eb7180458
source_id: ff00df6c-c3e8-4a0d-8fb9-33ee914ccc57
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 04:19:35
context:
Memory A focuses on end-user file management and storage operations, while Memory B focuses on administrative migration procedures between servers. While both are part of the same user manual, they describe distinct functional areas (user-level storage vs. admin-level federation) with no direct semantic overlap or conflict.


id: 5f08d27e-7bbb-4ead-bd92-dd8849d8aa18
source_id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 04:20:22
context:
Memory A focuses on AI file management tools and Spirit capabilities, while Memory B focuses on administrative user management and system roles. While both are sections of the same user manual, they describe distinct functional areas with no direct semantic overlap or conflict.


id: ce5f18b3-1281-40fb-bf3f-5fe25244b9c0
source_id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 04:20:44
context:
Memory A focuses on AI functional capabilities and file management tools, while Memory B focuses on administrative system update procedures. While both are sections of the same user manual, they describe distinct, unrelated features (AI interaction vs. system maintenance) with no functional or semantic overlap.


id: a42115ec-8757-4a96-a6ea-1f61cb221412
source_id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 04:21:03
context:
Memory A focuses on the functional AI capabilities of Spirits within the File Browser, while Memory B details administrative system settings like user registration and homepage redirects. There is no meaningful semantic overlap or functional connection between these two distinct modules of the user manual.


id: 638dc813-cd74-417a-bae7-4aab815b0c54
source_id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 04:22:01
context:
Memory A focuses on AI integration and file management tools for users, while Memory B focuses on administrative procedures for account migrations between servers. There is no meaningful semantic overlap or functional connection between these two distinct features of the platform.


id: a5fb1810-8b08-4d0b-9f41-09cf31412cbe
source_id: d68be241-4b63-4c48-8309-69a2950cf0af
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 04:23:21
context:
Memory A focuses on the File Browser's mobile responsiveness and personal storage architecture, while Memory B details administrative procedures for user migrations between Citadels. While both are part of the same user manual, they describe distinct, unrelated functional modules (user-level file management vs. admin-level account transfers) with no direct semantic overlap or conflict.


id: 53da72e5-69eb-454a-913b-45b79a725afc
source_id: 9fc3589c-f983-4f00-8ed1-296e059d7fac
target_id: 02219640-3973-4d9f-bbb1-5c2f490ed3b5
type: REINFORCES
created_at: 2026-03-13 04:23:37
context:
Memory B provides the technical infrastructure that enables the data sovereignty described in Memory A


id: df6280ad-eace-42e8-ad33-262556af511e
source_id: 697c5176-557a-4939-bbbd-f565956940af
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 04:25:17
context:
Memory A describes the UI and functionality of the File Browser, while Memory B describes the installation methods for the software. While both are part of the same user manual, they cover distinct, unrelated functional areas (UI usage vs. system deployment).


id: 36b68307-f8d6-445d-b75d-a094040ddace
source_id: 697c5176-557a-4939-bbbd-f565956940af
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 04:25:41
context:
Memory A focuses on the UI/UX features of the File Browser (Tree View, previews), while Memory B focuses on server-side installation and environment configuration. There is no meaningful semantic overlap or conflict between these two distinct sections of the user manual.


id: 1b81ba94-c619-428c-b34b-b60547361f49
source_id: 697c5176-557a-4939-bbbd-f565956940af
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 04:25:56
context:
Memory A focuses on the UI/UX and navigation features of the File Browser, while Memory B details the system maintenance and update procedures. There is no meaningful semantic overlap or functional connection between these two specific operational areas.


id: c4134765-e8cd-4839-a3ba-3ef9f8e058bc
source_id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: REINFORCES
created_at: 2026-03-13 04:30:04
context:
Memory B provides the infrastructure (AI Gateway) that enables the Spirit tools described in Memory A


id: c3adad38-322e-4ed6-afca-04179122ac91
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: d92f6c51-6e01-479d-83ca-d660824e27b7
type: NOT_DETECTED
created_at: 2026-03-13 04:44:48
context:
Both memories are sections of the CQ User Manual describing different platform features (CQ Chat vs. CQ Share). While they cover different functionalities, they share a common theme of UI navigation, URL structures, and user access methods within the same ecosystem.


id: 7c81e365-c675-481b-8131-09c215b88cf6
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: NOT_DETECTED
created_at: 2026-03-13 04:45:33
context:
Memory A describes the UI and access methods for the CQ Chat system, while Memory B describes the configuration of Share Groups for profile content. While both are part of the CitadelQuest User Manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 1284c889-5d4c-4727-8022-79e4a39dd181
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 4d8a2d04-0376-4274-818b-160b12166db4
type: NOT_DETECTED
created_at: 2026-03-13 04:45:52
context:
While both memories are sections of the CitadelQuest User Manual, they describe distinct and unrelated features: the CQ Chat interface and the CQ Share groups. There is no functional or semantic overlap between messaging navigation and file-sharing organization.


id: d4462e72-3ed1-4f7e-9cca-628b3a988bd0
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
type: NOT_DETECTED
created_at: 2026-03-13 04:46:21
context:
While both memories describe UI components of the CitadelQuest platform (Chat vs. Share Groups), they refer to distinct, non-overlapping features with different navigation paths and purposes. There is no direct functional or semantic dependency between them.


id: 127c88b4-d768-4861-920d-0cd65abe3601
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: NOT_DETECTED
created_at: 2026-03-13 04:46:35
context:
Memory A describes the user interface and access methods for the CQ Chat system, while Memory B explains the auto-sync functionality for shared Memory Packs. While both are part of the CitadelQuest User Manual, they describe distinct features (messaging vs. knowledge sharing) with no functional or semantic overlap.


id: 35c8968a-82c2-40a5-88f7-e853b50a4c85
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 02619512-3802-40c7-9fd4-13edfcdbf655
type: NOT_DETECTED
created_at: 2026-03-13 04:46:52
context:
Memory A describes the UI and access methods for the CQ Chat system, while Memory B describes the lifecycle management of the CQ Share system. While both are features of the CitadelQuest platform, they describe distinct functional modules with no overlapping procedures, conflicting facts, or direct dependencies.


id: 5f3af1f9-4160-413f-9b1f-ac5956a63200
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
type: NOT_DETECTED
created_at: 2026-03-13 04:47:00
context:
Memory A describes the user interface and access methods for the CQ Chat system, while Memory B explains the auto-sync mechanism for shared Memory Packs. Although both are part of the CQ User Manual, they describe distinct features (messaging vs. knowledge sharing) with no functional or semantic overlap.


id: ac70f210-1b2c-4458-b61b-4bb9c549075f
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
type: NOT_DETECTED
created_at: 2026-03-13 04:47:11
context:
Memory A describes the user interface and access methods for the CQ Chat system, while Memory B explains the auto-sync functionality for shared Memory Packs. While both are features of the CitadelQuest platform, they describe distinct systems (messaging vs. knowledge sharing) with no functional or semantic overlap.


id: 30187c01-df70-4b6d-a810-5662e11a9fa9
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 1d3da196-26b2-4575-8d68-23713a1ac801
type: NOT_DETECTED
created_at: 2026-03-13 04:47:36
context:
While both memories are sections of the CQ User Manual, they describe distinct, independent features (Chat Interface vs. Profile/Explorer Integration) with no functional or semantic overlap.


id: f4db73fc-8346-408c-b0d3-9da6ef3ce1bf
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: NOT_DETECTED
created_at: 2026-03-13 04:47:47
context:
Memory A describes the UI and access methods for the CQ Chat system, while Memory B details the lifecycle management of shared files and memory packs via CQ Share. While both are features of the CitadelQuest platform, they describe distinct functional modules with no direct overlap in logic, data, or user flow.


id: 1bc0505c-a149-4596-99bb-1779224fd227
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: c948f87d-5941-4d4d-84a2-98e896b44105
type: NOT_DETECTED
created_at: 2026-03-13 04:48:12
context:
Memory A describes the UI and access methods for the CQ Chat system, while Memory B describes the CQ Profile integration and CQ Explorer for file sharing. While both are part of the CitadelQuest User Manual, they describe distinct, non-overlapping features with no direct functional or semantic connection.


id: 73e8b38f-7d3e-4f19-85f4-1296ada2b262
source_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: NOT_DETECTED
created_at: 2026-03-13 04:49:48
context:
Memory A focuses on the CQ Chat messaging system and communication features, while Memory B focuses on CQ Share and profile organization. While both are features of the CitadelQuest platform, they describe distinct functional modules with no direct overlap or interaction described in the content.


id: 84fc3ab0-64b1-4eab-935c-45e300e3396a
source_id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: NOT_DETECTED
created_at: 2026-03-13 04:53:40
context:
Memory A focuses on the technical architecture and privacy of the CQ Chat messaging system, while Memory B describes the organizational structure of Share Groups for profile content. While both are features of the CitadelQuest platform, they describe distinct functional modules with no direct semantic overlap or conflicting information.


id: c6013f31-d846-4c00-82b4-3b6823a1cf1f
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 05:13:44
context:
Memory A describes the UI and access methods for the chat interface, while Memory B details the backup and restore procedures. While both are sections of the same user manual, they cover distinct functional areas (communication vs. data maintenance) with no direct semantic overlap or conflict.


id: 8a74c603-6bd4-49f2-8d23-204de14d6e21
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 05:14:11
context:
Memory A focuses on the UI and navigation of the chat interface, while Memory B focuses on the backup and restoration of system data. While both are part of the same user manual, they describe distinct, unrelated functional areas of the platform with no direct semantic overlap.


id: 09924244-7a9c-482f-8ea6-7a7e7305cf3b
source_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 05:18:05
context:
While both memories are sections of the CitadelQuest User Manual, they describe distinct, unrelated features: private messaging (CQ Chat) and administrative user management. There is no functional or semantic overlap between the decentralized communication protocol and the local administrative actions.


id: 2835b581-3b52-4c93-a93d-bf2f5499dd3c
source_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 05:18:42
context:
Memory A describes the CQ Chat messaging feature, while Memory B details administrative system settings like registration and homepage redirects. While both are part of the same software manual, they describe distinct, unrelated functional modules with no direct semantic overlap or conflict.


id: a050b3b3-71ed-475b-93d6-82985f06a6be
source_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 05:18:53
context:
Memory A describes a user-facing decentralized messaging feature (CQ Chat), while Memory B describes administrative tools for logs and backups. While both are part of the same platform manual, they cover distinct functional areas (communication vs. system administration) with no direct functional overlap, reinforcement, or contradiction.


id: fe8e5a24-a839-4ceb-b179-197515c9d778
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 05:19:58
context:
Memory A describes the user-facing chat interface and its navigation, while Memory B describes administrative user management tools. While both are part of the same user manual, they cover distinct functional areas (communication vs. administration) with no overlapping logic, conflicting facts, or reinforcing evidence.


id: 26cf1e1b-493c-4c94-a903-13cb379158e5
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 05:20:19
context:
Memory A focuses on the user-facing chat interface and navigation, while Memory B focuses on administrative system updates and maintenance. There is no meaningful semantic or functional overlap between these two distinct sections of the user manual.


id: e9913508-ae12-4f18-8e25-dd29e61e79a1
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 05:20:37
context:
Memory A focuses on the user-facing chat interface and navigation, while Memory B focuses on administrative system settings and homepage redirects. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: a21154b6-187b-4cec-aead-85139daa9f36
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 05:21:02
context:
Memory A describes the user-facing chat interface and its navigation, while Memory B describes administrative tools for logs and backups. While both are sections of the same User Manual, they cover distinct functional areas (communication vs. system administration) with no overlapping logic or conflicting information.


id: 79565769-d4ee-4fcb-b0b3-0bf3b1106486
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 05:21:24
context:
Memory A describes the user-facing chat interface and navigation, while Memory B describes administrative migration procedures. While both are part of the same user manual, they cover distinct, unrelated functional areas (communication vs. account administration) with no direct overlap in logic or data.


id: e4693bc3-dfc1-4dc7-92d6-974b889cdae7
source_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 05:21:53
context:
Memory A focuses on the CQ Chat messaging features and communication protocols, while Memory B focuses on administrative user management and system settings. While both are part of the same user manual, they describe distinct functional modules with no direct operational overlap or conflicting information.


id: fd270845-ccdb-4195-a234-069806c9d5e7
source_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 05:22:08
context:
Memory A focuses on the messaging and communication features (CQ Chat), while Memory B focuses on administrative update procedures and system maintenance. While both are sections of the same user manual, they describe distinct functional areas with no direct semantic overlap or logical dependency.


id: 9bfd0bab-5e49-42a5-9c73-1c47e932cb97
source_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 05:22:29
context:
Memory A focuses on the end-user chat functionality and messaging features, while Memory B focuses on administrative system settings and registration controls. While both are part of the same software manual, they describe distinct functional areas with no direct semantic overlap or conflicting information.


id: 10b06063-4727-4da7-a314-001e5ae904f3
source_id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 05:23:51
context:
Memory A focuses on the technical architecture and privacy of the messaging protocol (CQ Chat), while Memory B details administrative user management functions. While both are part of the same software manual, they describe distinct, non-overlapping functional areas with no direct semantic or logical dependency.


id: 503cdcb7-1c08-4214-ab4d-2118c281e457
source_id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 05:24:07
context:
Memory A focuses on the technical architecture and privacy protocols of the CQ Chat messaging system, while Memory B describes the administrative process for application updates and system maintenance. There is no meaningful semantic or functional overlap between these two distinct technical modules.


id: a4224107-7700-4a90-bfd2-1902749b2a6e
source_id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 05:24:43
context:
Memory A focuses on the technical architecture and privacy protocols of the CQ Chat messaging system, while Memory B details administrative settings for user registration and homepage redirects. There is no meaningful semantic or functional overlap between these two distinct modules of the software.


id: 2423dacb-b684-43d6-9cce-865d529d6c92
source_id: 3b059a1f-d20f-491f-a5aa-65bba791b45d
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 05:26:20
context:
Memory A focuses on the technical architecture and user interface of a decentralized messaging feature (CQ Chat), while Memory B details the administrative procedures for system updates and installation. While both are part of the same user manual, they describe distinct, unrelated functional modules with no direct semantic overlap or conflict.


id: f467dcf6-5981-4559-ba55-8dc0bdf16853
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 05:27:21
context:
Memory A describes the user interface and navigation for a chat feature, while Memory B details the technical installation methods for the entire platform. There is no meaningful semantic overlap or functional connection between these two distinct sections of the manual.


id: 0aa44c01-76b0-454e-b47d-be1cbd111771
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 05:27:29
context:
Memory A focuses on the user interface and navigation of the chat system, while Memory B focuses on server-side installation, environment configuration, and domain setup. While both are part of the same user manual, they describe distinct functional areas (UI usage vs. system administration) with no direct semantic overlap or conflicting information.


id: 0cbf1622-0ac4-423e-b690-f3245128668e
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 05:27:43
context:
Memory A focuses on the user interface and navigation of the chat system, while Memory B describes the administrative process for system updates and installation. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: ef7f3f88-4348-4caf-afae-3d21b54c4262
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 05:27:56
context:
While both memories are sections of the same user manual, they describe distinct, non-overlapping features: one focuses on the UI navigation of the chat system, while the other covers PWA installation and multi-user database architecture.


id: 1cb54da2-aadf-4563-a9a0-9c258aa47f1b
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 05:28:14
context:
Memory A describes the user interface and navigation for the CQ Chat system, while Memory B details the installation and integration of the CQ AI Gateway. While both are part of the CitadelQuest ecosystem, they describe distinct, unrelated features (messaging vs. AI services) with no functional or semantic overlap.


id: baeb244d-be03-459b-ab99-23cd86c4b043
source_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 05:28:35
context:
Memory A describes the features and usage of the CQ Chat system, while Memory B details the installation methods for the CitadelQuest platform. While both belong to the same user manual, they cover distinct functional areas (feature usage vs. system setup) with no direct semantic overlap or dependency.


id: 5880ad3f-59f5-43a3-bcc5-f08836653eb0
source_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 05:29:22
context:
Memory A focuses on the messaging features and user interface of the CQ Chat system, while Memory B describes the technical maintenance and update procedures for the CitadelQuest platform. There is no meaningful semantic overlap or functional connection between these two distinct modules.


id: 3778eb34-732a-4822-8bf0-2df99f591f2a
source_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 05:30:04
context:
Memory A focuses on the CQ Chat messaging system and its UI features, while Memory B details the CQ AI Gateway integration and installation process. While both are part of the CitadelQuest ecosystem, they describe distinct, non-overlapping functional modules with no direct semantic or logical dependency.


id: 66176a25-dfac-40ce-9a6e-cf65176550ea
source_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:40:09
context:
Memory A focuses on the CQ Share feature for distributing content to others, while Memory B focuses on system backup and restoration procedures. While both are part of the CQ User Manual, they describe distinct functional modules with no direct operational or semantic overlap.


id: 33bab684-6ecd-4ede-b3a8-9838eaea4c76
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 07:41:34
context:
Memory A focuses on the configuration of public and private sharing links and UI display styles, while Memory B focuses on system-wide data backups and restoration procedures. There is no meaningful semantic overlap or functional connection between these two distinct features.


id: 8e92dea0-2273-4bfb-87d1-3656801e2748
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:41:47
context:
Memory A focuses on the configuration of public and private sharing links and UI display styles, while Memory B focuses on system-level data backup and restoration procedures. There is no meaningful functional or semantic overlap between these two distinct administrative features.


id: 9f5e057f-5a29-4da9-ae46-eaea0ebf3245
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 07:42:13
context:
Memory A focuses on the technical configuration of sharing URLs and UI display styles, while Memory B focuses on data backup procedures and system migration best practices. There is no meaningful semantic overlap or functional connection between these two distinct administrative features.


id: 7afed3cc-7fc2-4b1e-a2d9-518c7148e71c
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: f10414d1-5c2c-4f68-9977-d71212e8d9af
type: NOT_DETECTED
created_at: 2026-03-13 07:42:43
context:
Memory A focuses on content sharing, URL configuration, and display styles, while Memory B focuses on data backup and restoration procedures. While both are part of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: bc0a8c4e-00f4-4c01-8813-560e71fa34be
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 07:43:19
context:
Memory A focuses on the configuration and display of shared content (URLs, display styles, and Markdown), while Memory B focuses on system-level backup and restoration procedures. While both are part of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 81426b8a-54cc-4edf-8408-7b59977c5dfb
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:43:38
context:
Memory A focuses on the configuration and display styles of shared content (URLs, Markdown, and UI layout), while Memory B focuses on the technical procedures for restoring and deleting system backups. There is no meaningful semantic overlap or functional connection between these two distinct administrative features.


id: b70a8b62-bef8-401a-a21c-76f35c2f81cf
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 07:44:13
context:
Memory A focuses on the configuration and display styles of shared content (URLs, UI layout, Markdown), while Memory B focuses on data backup procedures and system migration best practices. There is no meaningful semantic overlap or functional connection between these two distinct modules of the user manual.


id: b092378a-8b5d-4d2f-bf82-e6b0f0ffeb1e
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: f10414d1-5c2c-4f68-9977-d71212e8d9af
type: NOT_DETECTED
created_at: 2026-03-13 07:44:27
context:
Memory A focuses on content sharing and profile organization (Share Groups), while Memory B focuses on data protection and system recovery (Backup & Restore). While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or conflicting information.


id: 62f72bf1-6ffb-4512-a737-6460d5581e7e
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: ce8748d3-07f3-458d-b031-05996cd7ecc8
type: NOT_DETECTED
created_at: 2026-03-13 07:44:45
context:
Memory A describes the 'Share Groups' feature for profile organization, while Memory B describes the system backup and recovery process. While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or conflict.


id: f6da4c49-ce3d-405f-a678-85f38a279b38
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 07:44:57
context:
Memory A focuses on profile customization and content sharing features (Share Groups), while Memory B focuses on system maintenance and data integrity (Backups). There is no meaningful semantic or functional overlap between these two distinct features of the platform.


id: 45d576fe-6b6c-48ae-9e05-e1eda7936508
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:45:21
context:
Memory A focuses on front-end content organization and sharing features (Share Groups), while Memory B focuses on back-end system maintenance (Backups and Restoration). There is no functional or semantic overlap between these two distinct administrative tasks.


id: 06a44eb4-62c6-4efe-95d8-1ae55ec1d685
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 07:45:31
context:
Memory A focuses on front-end content organization and sharing features (Share Groups), while Memory B focuses on back-end data integrity and backup procedures. There is no meaningful semantic overlap or functional connection between these two specific features.


id: 381fed24-e64e-47f5-97b8-e1edd4330e41
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: f10414d1-5c2c-4f68-9977-d71212e8d9af
type: NOT_DETECTED
created_at: 2026-03-13 07:45:43
context:
Memory A describes the 'Share Groups' and profile customization features, while Memory B describes the 'Backup & Restore' system. While both are sections of the CitadelQuest User Manual, they cover distinct, unrelated functional areas (social sharing vs. data security) with no overlapping logic or conflicting information.


id: 39d601d6-7f83-429e-a53a-e3aeee34689b
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 07:46:24
context:
Memory A focuses on the 'CQ Share' feature and profile organization, while Memory B focuses on system backups and data restoration. While both are part of the CitadelQuest User Manual, they describe distinct, unrelated functional modules with no semantic overlap or dependency.


id: 812a2a4b-6886-4e55-b91e-d9dd1be19ca1
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:46:35
context:
Memory A describes the 'Share Groups' feature for organizing public profile content, while Memory B details the 'Backup and Restore' procedures for system data. There is no functional, semantic, or logical overlap between these two distinct administrative features.


id: db10a0fb-d2f4-40c0-aefd-61f6daaf0ba4
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 07:46:51
context:
Memory A describes the 'Share Groups' feature for organizing public profile content, while Memory B focuses on 'Best Practices' for system backups and data migration. There is no meaningful semantic overlap or functional connection between these two distinct features of the platform.


id: 931d7067-463f-46b6-92bf-98d81a6200fb
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: f10414d1-5c2c-4f68-9977-d71212e8d9af
type: NOT_DETECTED
created_at: 2026-03-13 07:47:13
context:
Memory A focuses on profile customization and content sharing features, while Memory B focuses on data backup and restoration procedures. They describe distinct functional areas of the platform with no overlapping logic or conflicting information.


id: 2dfb7e06-ed91-401d-9d3f-ad22ebf955be
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: ce8748d3-07f3-458d-b031-05996cd7ecc8
type: NOT_DETECTED
created_at: 2026-03-13 07:47:29
context:
Memory A focuses on the 'Share Groups' feature for profile organization, while Memory B describes the 'Backup' system for data preservation. While both are features of CitadelQuest, they describe distinct, non-overlapping functionalities with no direct semantic or functional dependency.


id: ee94d689-cdbe-4263-bcc1-99aa068dac69
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 07:47:47
context:
Memory A focuses on the 'Share Groups' feature for profile customization and content organization, while Memory B details the 'Backup and Restore' procedures for data security. There is no meaningful functional or semantic overlap between these two distinct system features.


id: 14319a74-05b8-4f2e-83c1-3a7b62a99658
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:48:07
context:
Memory A focuses on the 'CQ Share' feature and profile organization through Share Groups, while Memory B details the 'Backup and Restore' system. While both are part of the CitadelQuest User Manual, they describe distinct, unrelated functional modules with no overlapping logic or conflicting information.


id: 914d08db-c78b-47e2-b292-2d410fef07db
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 07:48:31
context:
Memory A focuses on front-end profile customization and content sharing features, while Memory B focuses on back-end data management and backup procedures. There is no meaningful semantic overlap or functional connection between these two distinct system features.


id: 89cc8a24-6839-48dd-8b52-2699ddafc73a
source_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:49:44
context:
Memory A focuses on the auto-sync mechanism for sharing knowledge packs between users, while Memory B details the local backup and restoration process for system recovery. While both are part of the CQ User Manual, they describe distinct technical systems (collaborative synchronization vs. disaster recovery) with no direct functional overlap or conflict.


id: 1009ae44-8a05-4b1c-881a-e58f7459b20c
source_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:52:17
context:
Memory A focuses on the real-time synchronization of shared knowledge packs between users, while Memory B focuses on the local backup and restoration of the entire system database. While both are features of CitadelQuest, they describe distinct technical processes (external sharing vs. internal data recovery) with no direct functional overlap or conflict.


id: 17f0bfb1-b606-4f6e-8159-50981a4cb83e
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 07:53:37
context:
Memory A focuses on the real-time synchronization of shared knowledge packs between users, while Memory B focuses on manual system-wide backups and restoration procedures. While both involve data transfer, they represent distinct functional systems (sharing vs. disaster recovery) with no direct overlap or contradiction.


id: 4d0465c6-f350-4e8a-9115-d3a9f74f2fb2
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:53:55
context:
Memory A focuses on the real-time synchronization of shared knowledge packs between users, while Memory B focuses on local system backup and restoration procedures. There is no direct functional or semantic overlap between these two distinct administrative features.


id: 517b5506-2bf6-4773-bb6e-076e663c2f06
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 07:54:09
context:
Memory A focuses on the technical mechanics of real-time synchronization for shared knowledge packs, while Memory B focuses on manual system-wide backup and disaster recovery procedures. While both are part of the same user manual, they describe distinct features with no functional or semantic overlap.


id: 01249b5d-2f64-4eca-b7f6-506540d9b620
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 07:55:04
context:
Memory A focuses on public content sharing and profile integration, while Memory B focuses on system-wide backups and data restoration. While both involve data movement, they describe distinct features (sharing vs. disaster recovery) with no direct functional or semantic overlap.


id: 4f43250d-0b7a-43e6-89fd-8c5126c1fe4e
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:55:21
context:
Memory A focuses on public content sharing and profile integration, while Memory B focuses on system backups and data recovery. While both are part of the CQ User Manual, they describe distinct, unrelated functional modules with no semantic overlap or conflicting information.


id: b167ac66-efc3-43dd-a3a9-9129cd974b81
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 07:55:39
context:
Memory A focuses on social sharing features and profile integration, while Memory B focuses on data backup and system maintenance. While both are part of the CQ User Manual, they describe distinct, unrelated functional areas of the platform with no direct semantic overlap or conflict.


id: 9d54ee4a-b19a-430d-b79c-19730e61928d
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:58:08
context:
Memory A focuses on content sharing and visibility management, while Memory B focuses on system backups and data recovery. While both are part of the same user manual, they describe distinct, unrelated functional modules with no overlapping procedures or conflicting information.


id: d54c4686-de38-4e56-907f-8374ce03b0f7
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: f10414d1-5c2c-4f68-9977-d71212e8d9af
type: NOT_DETECTED
created_at: 2026-03-13 07:58:46
context:
Memory A focuses on public content sharing and profile integration, while Memory B focuses on system-wide data backup and restoration. While both are features of the CitadelQuest platform, they describe distinct, unrelated functional modules with no direct overlap in logic, data handling, or user workflow.


id: 7b85ea83-f37c-4525-92c5-0f144657bc64
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 07:59:21
context:
While both memories describe data management within the CitadelQuest ecosystem, they focus on distinct features: Memory A covers public content sharing and discovery, while Memory B covers system-wide backups and disaster recovery. There is no direct functional or semantic overlap between sharing files with others and creating full system backups.


id: fbd25022-d38c-4f53-859b-d1b18e1f5bc3
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 07:59:34
context:
Memory A focuses on content sharing and profile integration (CQ Share), while Memory B focuses on system backups and data recovery. There is no meaningful semantic overlap or functional connection between these two distinct administrative features.


id: a2f74227-6c8d-46c1-9981-e5c8212446d1
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 07:59:49
context:
Memory A focuses on public content sharing and profile integration, while Memory B focuses on data backup and system security protocols. There is no meaningful semantic overlap or functional connection between sharing files with others and creating system backups for data integrity.


id: 9b5a3a5c-3406-4181-bbfe-2ff3b7b46bca
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 08:00:39
context:
Memory A focuses on the CQ Share functionality for distributing files and memory packs, while Memory B focuses on system-wide backup and restoration procedures. While both involve data management within the platform, they describe distinct, unrelated features (sharing vs. disaster recovery) with no direct functional or semantic overlap.


id: f56456aa-f5e8-4b82-a6a0-40754f271a1d
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 08:01:03
context:
Memory A focuses on the CQ Share functionality for distributing files and memory packs, while Memory B focuses on system backups and data restoration. While both are part of the CQ User Manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 61eaaef8-3036-4ccb-ac72-044d0a4648a7
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 08:01:21
context:
While both memories are sections of the same user manual, they describe distinct, unrelated features: Memory A focuses on the search and filter functionality for sharing content, while Memory B focuses on data backup and security best practices. There is no direct semantic overlap or functional dependency between these two specific modules.


id: 19ae2c07-3096-4324-90f5-04c34bace9f3
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 08:03:37
context:
Memory A focuses on the sharing and distribution of digital assets and knowledge packs, while Memory B focuses on data backup, restoration, and storage management. While both relate to the CitadelQuest platform, they describe distinct functional modules with no direct overlap or conflict in procedures.


id: 9cdeb9ef-28e0-407c-bff8-7fee029e209e
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 08:03:54
context:
Memory A focuses on the UI and procedures for sharing digital assets and memory packs, while Memory B focuses on backup procedures and data integrity. While both are part of the CQ User Manual, they describe distinct functional modules (sharing vs. backup) with no direct overlap in procedures or conflicting information.


id: 2799b7d0-984e-45ce-b7bb-c39cd715abb9
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: f10414d1-5c2c-4f68-9977-d71212e8d9af
type: NOT_DETECTED
created_at: 2026-03-13 08:04:07
context:
While both memories are sections of the CQ User Manual, they describe distinct, unrelated features (File Sharing vs. Backup/Restore) with no functional or semantic overlap.


id: b05d3d2b-0169-4a39-8beb-2c0e474d3685
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: 10447049-2745-48a8-a44e-219768498463
type: NOT_DETECTED
created_at: 2026-03-13 08:04:36
context:
Memory A discusses the 'CQ Share' feature for sharing files and knowledge graphs, while Memory B focuses on the backup and restoration system using .citadel files. While both are part of the same user manual, they describe distinct, unrelated functional modules with no overlapping procedures or conflicting information.


id: 3f09c935-7edc-4d5a-811a-68c2578334ab
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 08:04:55
context:
Memory A focuses on the CQ Share feature for distributing files and knowledge, while Memory B focuses on system backups and data restoration. While both are part of the CQ User Manual, they describe distinct, unrelated functional modules with no semantic overlap or conflicting information.


id: 371d0e37-fbd6-42cb-aff3-6e14e288af7a
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 08:05:09
context:
Memory A focuses on the 'CQ Share' feature and methods for sharing files/knowledge, while Memory B focuses on 'Best Practices' for data backups and system migration. While both are part of the same user manual, they describe distinct, unrelated functional modules with no direct semantic overlap or conflict.


id: da33a66b-c44d-4f23-8f76-7b9de90d1382
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
type: NOT_DETECTED
created_at: 2026-03-13 08:06:05
context:
Memory A focuses on the CQ Share functionality for distributing files and knowledge, while Memory B focuses on system backups and data restoration. While both are part of the CQ User Manual, they describe distinct, unrelated features with no functional overlap or conflicting information.


id: f2270466-57f6-419a-8f6a-d48305822841
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: 96095a4e-b62c-475e-a2aa-80fa6ee37e4d
type: NOT_DETECTED
created_at: 2026-03-13 08:06:13
context:
Memory A focuses on the functional mechanics of sharing files and knowledge via the CQ Share page, while Memory B details system backup procedures and data integrity protocols. While both are part of the CQ User Manual, they describe distinct, unrelated features with no direct semantic overlap or conflict.


id: 4ebf10bb-c375-4dae-b255-306fbc14f81d
source_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:06:45
context:
Memory A focuses on the CQ Share feature for file and knowledge distribution, while Memory B focuses on administrative User Management and system settings. There is no direct functional or semantic overlap between these two distinct modules of the platform.


id: b0018c4e-364a-445c-8ef1-46ab87b5a317
source_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:07:12
context:
Memory A focuses on the CQ Share feature for content distribution, while Memory B focuses on administrative application update procedures. There is no meaningful functional or semantic overlap between sharing files and updating the system software.


id: 46aca21b-14b6-4f72-a50a-ccf23e57d88e
source_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:07:49
context:
Memory A focuses on user-level content sharing features (CQ Share), while Memory B focuses on administrative system maintenance (Logs and Backups). There is no meaningful functional or semantic overlap between these two distinct modules of the platform.


id: d6cd4138-c41c-46b3-934f-afc0468e70ad
source_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:08:01
context:
Memory A focuses on the CQ Share feature for content distribution, while Memory B focuses on administrative migration requests for user account transfers. While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap.


id: cf31f4a2-9804-4fc1-aee8-90bbb9b1b29b
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:08:21
context:
Memory A focuses on front-end content sharing and display configurations for users, while Memory B focuses on back-end administrative user management and system security. There is no direct functional or semantic overlap between sharing URLs/styles and the administrative deletion or role-toggling of users.


id: 1084e8b3-ba1c-446d-810b-f89fb745e581
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:08:32
context:
Memory A focuses on front-end sharing configurations and URL structures, while Memory B focuses on back-end administrative update procedures. There is no meaningful semantic or functional overlap between these two distinct sections of the user manual.


id: 0c0133db-49a8-44f2-a0c8-5624e5a0f268
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:08:50
context:
Memory A focuses on user-level content sharing and display configurations, while Memory B focuses on administrative system logs and backups. They describe distinct modules of the platform with no functional or topical overlap.


id: 48818902-c083-441e-94ff-396bcc00a2a2
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:08:59
context:
Memory A focuses on user-level content sharing and display configurations, while Memory B focuses on administrative migration procedures between servers. There is no meaningful semantic or functional overlap between these two distinct features of the platform.


id: d32f1cd7-99e2-44fd-951f-dd0cc57709f5
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 08:09:26
context:
Memory A focuses on user-level content sharing and display configurations, while Memory B focuses on system-level administration and dashboard management. While both are part of the same user manual, they describe distinct, non-overlapping functional areas with no direct semantic or logical dependency.


id: b2f7a861-8bcd-4d87-b01e-b8c4c76ad070
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:09:42
context:
Memory A focuses on content sharing configurations and URL structures for the CQ Share feature, while Memory B details administrative user management and system settings. There is no direct functional or semantic overlap between how a user configures a shared file and how an administrator manages user accounts.


id: 2290ccc9-795a-469f-910e-37531321b169
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:10:09
context:
Memory A focuses on front-end content sharing and display configurations, while Memory B focuses on back-end administrative update procedures. There is no meaningful semantic overlap or functional connection between these two distinct manual sections.


id: 269030e7-b87e-4b39-879d-1126f1bcabd9
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:10:42
context:
Memory A focuses on user-facing content sharing and display configurations, while Memory B focuses on administrative server logs and system backups. There is no meaningful functional or semantic overlap between these two distinct modules of the platform.


id: cb50e11d-22eb-4dc5-84a2-ed297fd46dca
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:10:55
context:
Memory A focuses on user-level content sharing and display configurations, while Memory B focuses on administrative account migration procedures. There is no meaningful semantic or functional overlap between these two distinct features of the platform.


id: 6c6759ef-0f13-4317-9f5a-eaa8a1f8a032
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:11:17
context:
Memory A focuses on front-end profile customization and content sharing (Share Groups), while Memory B focuses on back-end administrative user management (passwords, roles, deletions). There is no direct functional or semantic overlap between these two distinct modules of the platform.


id: fb4a9dac-66d6-488c-b901-0f9652a983b1
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:11:28
context:
Memory A focuses on user-facing profile customization and content sharing features, while Memory B describes administrative system update procedures. There is no meaningful semantic or functional overlap between these two distinct areas of the application.


id: 9c2f956a-ab2e-4b6d-911f-8738abcae1b1
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:12:17
context:
Memory A focuses on user-level content sharing and profile customization (Share Groups), while Memory B focuses on system-level administrative tasks (Logs and Backups). There is no functional or semantic overlap between these two distinct modules of the platform.


id: 819a0a15-7b4f-48b5-aa7e-a30ab4f98d62
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:12:49
context:
Memory A focuses on user-level profile customization and content sharing (Share Groups), while Memory B focuses on administrative-level server management and account migrations. There is no meaningful semantic or functional overlap between these two distinct features of the platform.


id: 1bfda653-75de-4857-b652-9164b16d658b
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:13:39
context:
Memory A focuses on user-level profile customization and content sharing features, while Memory B focuses on system-level administrative updates and maintenance. There is no meaningful semantic or functional overlap between these two distinct areas of the application.


id: f82dd899-5daa-4485-bc83-da0ad95adec9
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:14:34
context:
Memory A focuses on user-level content sharing and profile customization (Share Groups), while Memory B focuses on system-level administrative tasks (Logs and Backups). There is no meaningful semantic overlap or functional connection between these two distinct modules of the platform.


id: 86556206-1107-434d-be44-d2f39cd33f28
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:14:46
context:
Memory A focuses on user-level content organization and profile customization (Share Groups), while Memory B focuses on administrative-level server management (Migration Requests). There is no meaningful functional or semantic overlap between these two distinct features of the platform.


id: c6cd9a30-d53c-44f4-aace-9fb010756811
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:15:29
context:
Memory A focuses on user-level profile customization and content sharing features, while Memory B focuses on administrative system updates and server maintenance. There is no meaningful semantic overlap or functional connection between these two distinct areas of the application.


id: 3a1bebd4-d44b-4bdd-bb5e-aa6e8f4020eb
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:15:54
context:
Memory A focuses on user-level profile customization and content sharing features, while Memory B focuses on system-level administrative logs and backups. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: 4a312cca-9d12-4d3e-b8ee-779292e98bf7
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:16:10
context:
Memory A focuses on user-level profile customization and content sharing features, while Memory B focuses on system-level administrative migration procedures. There is no meaningful semantic or functional overlap between these two distinct parts of the manual.


id: 644e1ef6-df26-4852-b442-b644e45c4ec5
source_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:16:42
context:
Memory A focuses on the technical functionality of Memory Pack auto-syncing for knowledge sharing, while Memory B details administrative user management and system settings. While both are part of the same user manual, they describe distinct, unrelated subsystems (data synchronization vs. account administration) with no functional or semantic overlap.


id: 5711f5fd-79be-4eda-8338-fc254bb58e65
source_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:17:31
context:
Memory A focuses on user-level knowledge sharing and auto-sync features for Memory Packs, while Memory B focuses on system-level administrative tasks like logs and backups. While both are part of the same user manual, they describe distinct functional areas (sharing vs. administration) with no direct operational or semantic overlap.


id: 76a93961-4549-476b-b94d-de8460e572ff
source_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:17:48
context:
Memory A discusses the 'Memory Pack Auto-Sync' feature for sharing knowledge between users, while Memory B discusses 'Migration Requests' for transferring user accounts between servers. While both are features of CitadelQuest, they describe distinct administrative and functional systems with no direct semantic overlap or conflict.


id: 41d90e5b-742e-43b9-86fc-a9a8c28b02d5
source_id: 02619512-3802-40c7-9fd4-13edfcdbf655
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 08:17:57
context:
While both memories are sections of the same user manual, they describe distinct, non-overlapping features: Memory A focuses on content sharing lifecycle management, while Memory B focuses on system-wide administrative dashboard functions. There is no direct functional or semantic dependency between them.


id: 682525ad-5422-45e9-8c2a-680a721264c2
source_id: 02619512-3802-40c7-9fd4-13edfcdbf655
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:18:09
context:
Memory A focuses on content sharing and lifecycle management for files/memory packs, while Memory B focuses on administrative user account management. While both are part of the same user manual, they describe distinct functional domains (sharing vs. user administration) with no direct overlap or contradiction.


id: c1ed9c4f-fe7f-492f-a013-55a4a9c71958
source_id: 02619512-3802-40c7-9fd4-13edfcdbf655
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:19:27
context:
While both memories are sections of the same user manual, they describe entirely different functional modules (content sharing vs. administrative account migrations) with no overlapping logic or conflicting information.


id: 57a986ce-5112-4321-bb15-7f76e87f285a
source_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:20:03
context:
Memory A focuses on the technical mechanism of Memory Pack synchronization and sharing features, while Memory B focuses on administrative user management and system-level controls. There is no meaningful semantic overlap or functional connection between these two distinct modules of the software.


id: ff05b37c-9f56-44ab-8d6b-5e8301c13cee
source_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:21:07
context:
Memory A describes a user-facing feature for synchronizing shared knowledge packs, while Memory B details administrative tools for server logs and system-wide backups. While both are parts of the CitadelQuest manual, they cover distinct functional domains (sharing vs. administration) with no direct semantic overlap or conflicting information.


id: 15172350-3f50-43da-85ad-8401f735daba
source_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:21:20
context:
Memory A focuses on the CQ Share feature and automated synchronization of Memory Packs between users, while Memory B details administrative procedures for account migrations between Citadels. While both are part of the CitadelQuest ecosystem, they describe distinct, unrelated functional modules (sharing vs. account administration) with no direct semantic overlap or conflict.


id: 1f0650bc-0acb-48ec-86f8-19e1f0c26685
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 08:21:35
context:
Memory A focuses on the technical functionality of Memory Pack auto-syncing for user collaboration, while Memory B describes the administrative dashboard and system-level management. While both are sections of the same user manual, they cover distinct, unrelated features (sharing vs. system administration) with no functional overlap or contradiction.


id: 5b8c83ea-aca8-4f37-9df0-f09d7751dd0d
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:21:51
context:
Memory A focuses on the technical functionality of Memory Pack synchronization and sharing, while Memory B describes administrative user management and system settings. There is no meaningful semantic overlap or functional connection between these two distinct manual sections.


id: badc17f2-6064-4755-b9b6-af8a5a1c3af7
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:22:52
context:
Memory A focuses on user-level knowledge sharing and auto-sync features, while Memory B focuses on administrative server logs and system backups. While both are part of the same user manual, they describe distinct functional areas (sharing vs. administration) with no direct functional overlap or conflict.


id: c3cd40e2-4741-4688-8992-5834d38f0e2f
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:23:04
context:
Memory A focuses on the CQ Share feature and Memory Pack auto-syncing for knowledge sharing, while Memory B focuses on administrative migration requests for account transfers. There is no meaningful functional or semantic overlap between these two distinct system features.


id: a9d2c0cb-1b02-412b-9d53-944cb576a053
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:24:07
context:
Memory A focuses on user-facing sharing features and profile integration, while Memory B focuses on administrative system updates and maintenance. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: ecc6f4a6-d5a6-4586-a616-31015ea0055d
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:24:39
context:
Memory A focuses on user-facing features regarding public profile sharing and content discovery (CQ Explorer), while Memory B focuses on administrative backend functions like server logs and system backups. There is no meaningful semantic or functional overlap between these two distinct sections of the user manual.


id: 89ce3569-e078-4459-ae1f-b38856d5c687
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:24:49
context:
Memory A focuses on user-level content sharing and profile visibility features, while Memory B focuses on administrative procedures for account migrations between instances. While both are part of the same user manual, they describe distinct, unrelated functional modules (sharing vs. administration) with no direct semantic overlap.


id: bb64eb9c-3b9f-4682-b2a3-94440c6c9567
source_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:25:11
context:
Memory A focuses on content sharing and lifecycle management (CQ Share), while Memory B focuses on administrative user account management. While both are part of the same user manual, they describe distinct, unrelated functional modules with no direct overlap in logic or data.


id: b8d486d3-c3e6-40b9-b349-e2c7b6b400b4
source_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:25:25
context:
While both memories originate from the CQ User Manual and discuss 'maintenance' in a broad sense, they refer to entirely different domains: Memory A focuses on content lifecycle management (sharing files), while Memory B focuses on system-level application updates and server administration. There is no direct functional or semantic overlap.


id: fd20a142-9acc-417e-9154-c065b31e3917
source_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:26:21
context:
Memory A focuses on the management of shared content (CQ Share) by individual users, while Memory B focuses on administrative procedures for account migrations between Citadels. Although both are sections of the same user manual, they describe distinct features with no functional or semantic overlap.


id: 31f8e3a0-1fd7-467b-9777-60d9253f7b3a
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:26:57
context:
Memory A focuses on content sharing workflows and public visibility features, while Memory B focuses on administrative user management and system-level controls. While both are part of the same user manual, they describe distinct functional modules (sharing vs. administration) with no direct overlap in procedures or conflicting information.


id: a9130dca-4a1c-453c-b22f-6564cee87e81
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:27:24
context:
Memory A focuses on the content sharing features and UI workflows (CQ Share), while Memory B focuses on administrative system updates and maintenance procedures. There is no meaningful semantic or functional overlap between these two distinct areas of the application manual.


id: 9df2405d-0793-4a3b-b0c1-b0d36416a4f7
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:27:55
context:
Memory A focuses on user-facing content sharing and social features within the CQ Share ecosystem, while Memory B focuses on backend administrative tasks like log management and system backups. There is no meaningful semantic overlap or functional dependency between these two distinct modules of the platform.


id: b06799da-5aac-4693-813b-271b217ad2a4
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:28:13
context:
Memory A focuses on user-level content sharing features (CQ Share), while Memory B focuses on administrative account migration procedures. While both are part of the same user manual, they describe distinct functional areas with no direct semantic overlap or conflicting information.


id: b7a5c8e5-3da0-4d6d-987a-2f6617369be8
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:29:04
context:
Memory A focuses on the CQ Share feature and profile integration for content discovery, while Memory B details the administrative process for application updates and system maintenance. There is no meaningful semantic or functional overlap between these two distinct sections of the user manual.


id: d3204f9f-e619-4b91-93d4-c339b151d643
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:29:34
context:
Memory A focuses on user-level content sharing and profile integration features, while Memory B focuses on system-level administrative tasks like logs and backups. There is no meaningful functional or semantic overlap between these two distinct sections of the user manual.


id: cf2cce95-9a93-4f87-8c38-1771e51c4dbe
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:29:45
context:
Memory A focuses on user-level content sharing and profile visibility features, while Memory B focuses on administrative account migration and system management. There is no meaningful functional or semantic overlap between sharing files/memory packs and migrating user accounts between instances.


id: 62a626c6-19d8-4550-a57f-22111ae6b0a1
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 08:30:20
context:
Memory A focuses on the CQ Share feature for file sharing and knowledge distribution, while Memory B describes the Administration panel for system-level management. While both are sections of the same user manual, they describe distinct, non-overlapping functional areas of the platform with no direct semantic or logical dependency.


id: 0586ab6d-118c-4f34-8401-4deca002b0a3
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:31:09
context:
Memory A focuses on user-level 'CQ Share' functionality for file sharing and knowledge packs, while Memory B focuses on system-level 'Application Updates' and administrative maintenance. They describe entirely different modules of the CitadelQuest platform with no functional or semantic overlap.


id: 17c3403e-27c0-4722-a0c7-6af105e08676
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:32:02
context:
Memory A focuses on user-level file sharing and search functionality, while Memory B focuses on system-level administrative logs and backups. They describe different feature sets (CQ Share vs. Administration) with no functional or semantic overlap.


id: 35e1d6a9-9992-4587-beb3-7f6216ac7627
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:32:18
context:
Memory A focuses on user-level file sharing and search functionality within the CQ Share module, while Memory B focuses on administrative procedures for account migrations between Citadels. There is no meaningful semantic overlap or functional connection between these two distinct features.


id: 487fc3e0-65ad-440c-9736-7aceae6c1215
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 08:32:33
context:
Memory A describes the user-facing file and memory sharing features, while Memory B describes the system-level administration dashboard. While both are part of the same user manual, they cover distinct functional modules (sharing vs. system administration) with no direct overlap in procedures, permissions, or data flow.


id: 965ae820-9d3d-4a9a-9a68-50560409445c
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:32:51
context:
Memory A focuses on the technical procedures for sharing digital assets and memory packs, while Memory B details administrative user management and system settings. There is no meaningful functional or semantic overlap between asset sharing workflows and administrative user account controls.


id: 14892f0e-2580-451e-a689-2acd4fc03bdc
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:33:09
context:
Memory A focuses on the user-facing sharing features and UI for digital assets, while Memory B describes administrative system update procedures. While both are part of the same user manual, they cover distinct functional modules with no semantic overlap or logical dependency.


id: 8493be3f-d710-44db-a2f8-9838f0840629
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:33:31
context:
Memory A focuses on user-level sharing features and UI navigation for digital assets, while Memory B focuses on administrative system logs and global backups. While both are part of the same user manual, they describe distinct functional modules with no direct overlap or conflict.


id: 6607e5d5-75cd-40a3-a0da-189fb6f56ff0
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:34:53
context:
Memory A focuses on user-level content sharing and visibility controls within the platform, while Memory B focuses on administrative account migration and system management. There is no meaningful semantic overlap or functional dependency between these two distinct modules.


id: ca0d6643-8651-4525-bda8-c5acfef9d96e
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:35:07
context:
Memory A focuses on user-level content sharing and visibility controls, while Memory B focuses on administrative account migration and server management. There is no meaningful semantic or functional overlap between these two distinct platform features.


id: c6453e1a-7615-487c-b574-b531e73232cb
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:35:29
context:
Memory A focuses on the technical and functional aspects of file sharing (CQ Share), while Memory B focuses on administrative user management and system governance. There is no direct semantic overlap, contradiction, or reinforcement between these two distinct modules of the user manual.


id: f40867c2-ae6f-4d9d-b51b-cf90f8450e75
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:35:39
context:
Memory A focuses on the file-sharing features (CQ Share) of the platform, while Memory B focuses on administrative user management and system settings. While both are sections of a user manual, they describe distinct, non-overlapping functional areas with no direct semantic connection or dependency.


id: 947bb182-82bb-468e-97aa-bb2fa9851708
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:35:40
context:
Memory A discusses the 'CQ Share' feature for file and knowledge sharing, while Memory B details the application update process and administrative functions. There is no meaningful semantic overlap, reinforcement, or contradiction between these two distinct functional areas of the software.


id: 820de61c-cdfe-41a4-a6bc-5e2dee3ce39e
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:36:27
context:
Memory A focuses on the user-facing file sharing features (CQ Share), while Memory B focuses on administrative system maintenance (Logs and Backups). There is no functional or semantic overlap between these two distinct sections of the user manual.


id: 713f80d3-058c-49d6-9240-b6443627a9aa
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:36:44
context:
Memory A focuses on the CQ Share feature for file and knowledge distribution, while Memory B focuses on administrative migration requests for user account transfers. While both are part of the CQ User Manual, they describe distinct, unrelated functional modules (sharing vs. administration) with no semantic overlap or conflicting information.


id: 77305bc6-0700-49cd-bdb0-3bdb84518816
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-13 08:37:16
context:
Memory A focuses on the user-facing CQ Share functionality and file sharing, while Memory B focuses on the restricted Admin Dashboard and system management. While both are part of the CQ User Manual, they describe distinct, non-overlapping functional areas with no direct semantic or logical connection.


id: 8b3c3f6b-9c1d-48b0-a12d-7d74e858aceb
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-13 08:37:29
context:
While both memories describe UI functionalities (Search/Filter and User Management) within the same platform, they refer to entirely different modules (CQ Share vs. Administration) with no functional overlap or conflicting information.


id: a82f8321-c5a2-4c2a-9158-7937417af6c8
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-13 08:37:46
context:
Memory A focuses on the user-facing 'CQ Share' functionality for file sharing and discovery, while Memory B focuses on the 'Application Updates' and administrative backend processes. They describe entirely different modules of the system with no functional or semantic overlap.


id: 92d802d9-00e1-4da1-b7d2-59c733154672
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-13 08:38:18
context:
Memory A focuses on the functional walkthrough of the CQ Share feature for managing shared files and memory packs. Memory B focuses on administrative system settings like user registration and homepage redirects. While both are part of the CQ User Manual, they describe distinct, unrelated features (user-level sharing vs. admin-level system configuration) with no direct functional overlap or contradiction.


id: c50d8b05-e5da-4a27-8785-2086916574b9
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-13 08:38:46
context:
Memory A focuses on user-level content sharing and search functionality, while Memory B focuses on administrative server logs and system backups. While both are sections of the same user manual, they describe distinct, unrelated functional areas (frontend sharing vs. backend administration) with no semantic overlap or conflicting information.


id: 2cbbed0a-b76b-49c1-bcd7-33c81d5143d7
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: 6c522150-ff8d-42ac-a776-58f6699ff927
type: NOT_DETECTED
created_at: 2026-03-13 08:39:07
context:
Memory A focuses on user-level content sharing and search functionality within the CQ Share feature, while Memory B focuses on administrative procedures for account migrations between Citadels. There is no meaningful functional or semantic overlap between these two distinct modules of the platform.


id: c32378cb-4e22-4c7e-9ad9-051fdb11d8d9
source_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:39:40
context:
Memory A focuses on the 'CQ Share' feature for file and knowledge distribution, while Memory B details the technical installation methods for the CitadelQuest platform. While both are part of the same user manual, they describe distinct, unrelated functional areas (feature usage vs. system deployment) with no direct semantic overlap or conflict.


id: d2005c16-7e8a-42fc-925d-8da5ad7aaffb
source_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 08:40:18
context:
Memory A focuses on the CQ Share feature for file and knowledge distribution, while Memory B details the system maintenance and update procedures. There is no meaningful semantic overlap or functional connection between these two distinct administrative and user-facing modules.


id: a93869c6-83d7-43d4-a92d-9019ec58e406
source_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:40:44
context:
Memory A focuses on the CQ Share feature for file and knowledge distribution, while Memory B focuses on the CQ AI Gateway integration and installation process. There is no meaningful semantic overlap or functional dependency between these two distinct system components.


id: 94dc005c-ca2b-4384-b1ad-32e2a435ab54
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:41:24
context:
Memory A focuses on the functional configuration of sharing features within the platform, while Memory B describes the technical installation and deployment methods. There is no meaningful semantic overlap or logical connection between these two distinct sections of the user manual.


id: 85eb6da9-6e6b-4dc8-8709-66ea3ab197c8
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 08:41:55
context:
Memory A focuses on front-end sharing configurations and URL structures, while Memory B focuses on back-end system maintenance and installation procedures. There is no meaningful semantic overlap or functional connection between these two distinct administrative areas.


id: eaae39f5-2bac-43f8-89fe-6e12c2f70ad1
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 08:42:14
context:
Memory A focuses on the technical configuration of content sharing and UI display styles within the platform, while Memory B focuses on installation methods, PWA support, and multi-user database isolation. There is no meaningful semantic overlap or functional dependency between these two specific architectural components.


id: 9b0dd421-eda3-48f4-b07f-1e7c20dbccfd
source_id: d92f6c51-6e01-479d-83ca-d660824e27b7
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:42:40
context:
Memory A focuses on content sharing, URL structures, and UI display configurations, while Memory B focuses on server installation and AI Gateway integration. There is no meaningful semantic overlap or functional connection between these two distinct system features.


id: 5cd435fa-2029-41c8-84a4-03a8810aa5ee
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:43:08
context:
Memory A focuses on the configuration of sharing features and UI display styles within the platform, while Memory B details the technical installation methods for the software. There is no meaningful semantic overlap or functional connection between how a user installs the software and how they configure public share URLs.


id: 7e166793-ef48-4b5f-baaf-4f3e1d96120a
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 08:43:36
context:
Memory A focuses on front-end sharing configurations and URL structures, while Memory B focuses on back-end system maintenance and update procedures. There is no meaningful semantic overlap or functional connection between these two distinct administrative areas.


id: c41c62ac-7f39-4130-8189-6570c7b09dc8
source_id: a4102387-181b-467a-9de7-edeb48f554e0
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:44:10
context:
Memory A focuses on the technical configuration of sharing files and content display styles within the CitadelQuest platform, while Memory B details the installation process and AI Gateway integration. There is no meaningful semantic overlap or functional connection between these two distinct modules of the user manual.


id: b73918bb-67c9-4e10-830d-50ebf5e530dc
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:44:41
context:
Memory A describes the 'Share Groups' feature for profile organization, while Memory B details the software installation methods. There is no meaningful semantic or functional connection between these two distinct parts of the user manual.


id: 859615a7-0498-4fa5-97f5-4078f5e8ab98
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 08:44:57
context:
Memory A focuses on front-end user features regarding profile organization and share groups, while Memory B focuses on back-end server installation and environment configuration. There is no meaningful semantic overlap or functional dependency between these two specific sections of the manual.


id: 353696da-6d44-4027-a087-8a92ec762a40
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 08:45:14
context:
Memory A describes user-facing profile customization and content sharing features, while Memory B focuses on administrative system maintenance and installation procedures. There is no meaningful semantic overlap or functional connection between these two distinct areas of the manual.


id: 892a4247-be17-4279-8b9b-23800f318827
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 08:45:24
context:
Memory A focuses on front-end user profile customization and content sharing features, while Memory B focuses on server-side installation, PWA capabilities, and database architecture. There is no meaningful semantic overlap or logical connection between these two specific functional areas.


id: 4bade131-aa59-4b1a-b09b-a50fa58b3275
source_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:45:35
context:
Memory A focuses on the 'Share Groups' and profile customization features of the platform, while Memory B focuses on the 'AI Gateway' integration and installation process. While both are sections of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or logical dependency.


id: 64c43f13-5301-4f01-9275-4c07042c734d
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: 02219640-3973-4d9f-bbb1-5c2f490ed3b5
type: NOT_DETECTED
created_at: 2026-03-13 08:45:46
context:
Memory A focuses on the 'Share Groups' feature for profile customization, while Memory B details server requirements and installation procedures. There is no meaningful semantic or functional connection between these two distinct parts of the user manual.


id: ec3f55d4-877e-4d90-a29b-8aa9c6417ea4
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:45:55
context:
Memory A describes specific software features (Share Groups and Profile Content), while Memory B describes the software installation process. While they both belong to the same User Manual, they cover distinct, unrelated functional areas with no semantic overlap or logical dependency.


id: 3c47fee5-6dde-46ad-af99-0791570e89e8
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 08:46:08
context:
Memory A focuses on front-end user features regarding profile customization and content sharing, while Memory B focuses on back-end server installation and environment configuration. There is no meaningful semantic or functional overlap between these two distinct parts of the manual.


id: 413bbd57-717d-411d-8b98-063bc6fff4a7
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 08:46:32
context:
Memory A describes the 'Share Groups' feature for user profile organization, while Memory B details the system maintenance and update procedures. These are distinct functional areas (user-facing features vs. administrative backend) with no semantic overlap or conflicting information.


id: 47081922-2238-488a-9d5d-b4305de7a088
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 08:46:58
context:
Memory A focuses on front-end user features regarding content sharing and profile organization, while Memory B focuses on back-end architecture, installation, and PWA capabilities. There is no meaningful semantic or functional overlap between these two specific sections of the manual.


id: 7efdb2e3-1efc-4db3-b27d-66630c83eaee
source_id: 4d8a2d04-0376-4274-818b-160b12166db4
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:47:09
context:
Memory A focuses on user-facing content organization and profile sharing features, while Memory B focuses on backend AI gateway integration and server installation. There is no meaningful semantic overlap or functional connection between these two distinct modules of the platform.


id: 262eed7a-58f9-4ff4-9e0b-b85d409184ea
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:47:40
context:
Memory A describes specific UI features for sharing content (Share Groups), while Memory B describes the technical installation process of the software. There is no functional or semantic overlap between these two distinct parts of the user manual.


id: 9c36748f-f7f7-474e-be12-084e994029c0
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 08:48:29
context:
Memory A describes a specific user-facing feature (Share Groups) for organizing profile content, while Memory B describes backend administrative procedures (Maintenance and Updates). There is no functional, logical, or topical overlap between these two distinct sections of the user manual.


id: 7dcc4a0e-c8d4-4eeb-a4da-664e1517d561
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 08:48:40
context:
Memory A focuses on front-end user features for content organization and sharing (Share Groups), while Memory B focuses on system architecture, installation, and multi-user data isolation. There is no meaningful semantic overlap or functional dependency between these two specific technical modules.


id: fd5c775e-3f99-491f-99c7-f753eba8745c
source_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:49:01
context:
Memory A describes the 'Share Groups' and profile customization features of the CitadelQuest platform, while Memory B describes the 'AI Gateway' integration and installation process. While both are part of the same user manual, they cover distinct, unrelated functional modules (social/sharing vs. infrastructure/AI) with no semantic overlap or logical dependency.


id: 84b7d47d-d6bd-4f2f-9dd7-a685ff3e3dc4
source_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:49:21
context:
While both memories are sections of the CitadelQuest User Manual, they describe completely different functional areas: Memory A focuses on the 'Memory Pack Auto-Sync' feature for data sharing, while Memory B focuses on 'Installation Methods' for setting up the software. There is no direct functional or semantic overlap between the sync mechanism and the installation process.


id: eeb5b026-e11f-433f-a86d-f31c2dbd23ad
source_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 08:49:32
context:
Memory A focuses on the functional application of sharing and syncing knowledge packs, while Memory B focuses on technical server installation and environment configuration. There is no meaningful semantic overlap or logical connection between the two.


id: cf595980-fa29-4eaf-a8b4-ac710a2505ad
source_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:50:18
context:
While both memories are sections from the CitadelQuest User Manual, they describe distinct, unrelated features: Memory Pack Auto-Sync (data sharing) and AI Gateway Integration (LLM access). There is no functional or semantic overlap between the two.


id: 833399e8-ca08-49f8-ba0d-ad3e0147904e
source_id: 02619512-3802-40c7-9fd4-13edfcdbf655
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:50:45
context:
Memory A focuses on the operational management of shared content within the platform, while Memory B describes the initial installation and deployment methods. There is no meaningful semantic overlap or functional dependency between these two distinct sections of the user manual.


id: ba324e24-6673-4b53-8058-e79ab90c2e26
source_id: 02619512-3802-40c7-9fd4-13edfcdbf655
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:52:19
context:
Memory A focuses on content sharing lifecycle management (editing, pausing, deleting shares), while Memory B focuses on the technical installation and AI Gateway integration of the platform. There is no direct functional or semantic overlap between these two specific administrative modules.


id: 810838cd-9bd6-4ff0-9fc1-5fa84f80b540
source_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 08:53:32
context:
Memory A focuses on the application-level feature of Memory Pack synchronization and sharing, while Memory B focuses on the low-level server installation and environment configuration. While both are part of the same user manual, they describe distinct domains (feature usage vs. system administration) with no direct functional or logical overlap.


id: 7411c13e-5cef-4850-95d2-3c42d274e7a2
source_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 08:54:47
context:
Memory A focuses on the technical mechanics of Memory Pack synchronization and sharing features, while Memory B discusses PWA installation, multi-user architecture, and server requirements. While both are part of the same user manual, they describe distinct, non-overlapping functional areas with no direct semantic or logical connection.


id: e9f0f37f-bd6f-4945-9b1f-96832dcfc918
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:55:34
context:
Memory A describes a specific software feature (Memory Pack Auto-Sync), while Memory B describes the initial installation process for the software. While both are part of the same user manual, they cover distinct, unrelated functional areas with no semantic overlap or dependency.


id: 46c3f695-4ef0-4465-b89c-188b0d2111ab
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 08:55:46
context:
Memory A focuses on the functional features of Memory Pack synchronization and sharing, while Memory B details the technical server installation and environment configuration. While both are part of the same user manual, they describe distinct layers of the system (application features vs. infrastructure setup) with no direct semantic overlap or dependency.


id: bdbef796-d354-486e-9f1a-23031ab5ca76
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 08:56:18
context:
Memory A focuses on the technical mechanics of sharing and synchronizing knowledge packs between different Citadel instances, while Memory B focuses on the installation, PWA capabilities, and multi-user database isolation of a single Citadel instance. There is no direct functional or semantic overlap between these specific features.


id: 3bbcb17b-49c8-449a-94b8-8bc35068e557
source_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:56:28
context:
Memory A focuses on the Memory Pack Auto-Sync feature for sharing knowledge between users, while Memory B details the technical installation and AI Gateway integration of the CitadelQuest platform. While both are sections of the same user manual, they describe distinct, unrelated functional modules (sharing vs. installation/AI) with no direct semantic overlap or conflict.


id: 2c66c2da-d414-428b-ba8f-78f37ecaa80a
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:57:00
context:
Memory A focuses on the CQ Share feature and profile integration, while Memory B describes the technical installation methods for the CitadelQuest platform. While both are part of the same user manual, they describe distinct, unrelated functional areas (feature usage vs. system setup) with no direct semantic overlap or conflict.


id: 742ed55e-3289-4239-a2cf-a1bd0030bf94
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 08:57:13
context:
Memory A focuses on user-facing features like profile integration and content sharing, while Memory B focuses on technical server-side installation and environment configuration. While both are part of the same user manual, they describe distinct layers of the system (application logic vs. infrastructure) with no direct functional overlap or contradiction.


id: deb2fd47-cb0e-4b59-8321-6133b0b63502
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 08:57:30
context:
Memory A focuses on user-facing features regarding content sharing and profile integration, while Memory B details administrative system maintenance and installation procedures. There is no meaningful semantic or functional overlap between these two distinct sections of the user manual.


id: 050d5d3e-dee8-40f5-b814-d0989d13a44d
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 08:57:39
context:
Memory A focuses on the CQ Share feature and profile integration for content discovery, while Memory B focuses on PWA installation and multi-user database isolation. While both are part of the CQ User Manual, they describe distinct, unrelated functional domains (social sharing vs. technical deployment) with no direct semantic overlap or conflict.


id: a0ac0cc9-b8df-4c62-b511-c6f917e0445b
source_id: 1d3da196-26b2-4575-8d68-23713a1ac801
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:58:00
context:
Memory A focuses on content sharing and profile visibility features, while Memory B describes the AI Gateway integration and installation process. There is no meaningful semantic overlap or functional connection between these two distinct system modules.


id: 1d3216bd-dc4b-4b9c-87c7-381ed23a96a9
source_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 08:58:38
context:
Memory A focuses on the lifecycle management of shared content (editing, pausing, deleting), while Memory B focuses on the initial installation methods of the software. While both are part of the same user manual, they describe distinct, unrelated functional areas with no semantic overlap or logical dependency.


id: 3ec92354-c74c-4b4d-a130-99ee1178da9d
source_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 08:59:18
context:
Memory A focuses on the specific mechanics of managing shared content (editing, pausing, deleting), while Memory B focuses on installation, PWA support, and multi-user database architecture. There is no direct functional or semantic overlap between these two distinct sections of the user manual.


id: 1be50dc0-5c0b-4be2-9f26-f0099b5f04f7
source_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 08:59:31
context:
Memory A focuses on the lifecycle and maintenance of shared content (CQ Share), while Memory B details the installation and AI Gateway integration of the CitadelQuest platform. There is no meaningful semantic overlap or functional connection between these two distinct modules of the user manual.


id: a49336b7-e687-4e1e-beb7-67c255430e8d
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 09:00:27
context:
Memory A focuses on the user interface and procedures for sharing content within the platform, while Memory B describes the technical installation methods for deploying the software. There is no functional or semantic overlap between how to share files and how to install the server.


id: 1225116a-40e5-4879-a0cf-cacfcb9a3c70
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 09:00:50
context:
Memory A focuses on the user-facing 'CQ Share' feature and UI workflows for content distribution, while Memory B focuses on technical server-side installation, environment variables, and domain configuration. There is no direct functional or semantic overlap between these two distinct parts of the user manual.


id: 429e6e4e-61bf-444f-96e9-a00f47f3fa23
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 09:01:17
context:
Memory A focuses on the user-facing content sharing features (CQ Share), while Memory B focuses on administrative system maintenance and update procedures. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: af58a8ac-02a7-47a8-bcd4-39368346b66c
source_id: de432f8f-e033-4e6e-a579-b189ccd74095
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 09:01:46
context:
Memory A focuses on the UI and procedures for sharing files and memory packs, while Memory B describes the installation and configuration of the AI Gateway service. While both are part of the CitadelQuest manual, they describe distinct, unrelated functional modules (sharing vs. AI infrastructure) with no semantic overlap or dependency.


id: 110a6abb-ac7d-4c9e-84ef-d8bca69e2e4f
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 09:02:14
context:
Memory A discusses the functional features of profile sharing and content discovery within the application, while Memory B focuses on the technical installation methods and server requirements. There is no meaningful semantic overlap or functional dependency between these two distinct sections of the user manual.


id: 28dabc06-32be-49f9-80d2-57c687b0b071
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 09:02:42
context:
Memory A focuses on the 'CQ Share' feature and profile integration, while Memory B details the technical installation and server configuration of the platform. While both belong to the same user manual, they describe distinct, non-overlapping functional areas with no direct semantic or logical dependency.


id: 8d92a9cd-b259-43d5-88e9-49ffcdacba93
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 09:03:04
context:
Memory A focuses on user-facing content sharing and profile integration features, while Memory B focuses on administrative system maintenance and installation procedures. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: 873ad363-0d06-46ab-9972-f4e1bf89f60b
source_id: c948f87d-5941-4d4d-84a2-98e896b44105
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 09:03:40
context:
Memory A focuses on content sharing and profile visibility features (CQ Share), while Memory B focuses on the technical installation and AI Gateway integration. While both are part of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or conflicting information.


id: 01f6be93-d7bb-42db-817e-e71039e5c9cb
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: 02219640-3973-4d9f-bbb1-5c2f490ed3b5
type: NOT_DETECTED
created_at: 2026-03-13 09:04:07
context:
Memory A focuses on the functional usage of the 'CQ Share' feature within the application, while Memory B details the technical server requirements and installation process for the platform. While they belong to the same user manual, there is no direct semantic overlap, reinforcement, or contradiction between their specific contents.


id: d4ccab0a-deb6-40e0-80fd-8141e6cc10e7
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 09:04:20
context:
Memory A focuses on the operational usage of the 'CQ Share' feature for file distribution, while Memory B details the technical installation methods for the CitadelQuest platform. There is no functional, logical, or contradictory overlap between how to share files and how to install the software.


id: 28175131-c614-4b23-8d72-4eaebdd3093e
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 09:04:31
context:
Memory A focuses on the user-facing 'CQ Share' feature and its internal navigation/filtering, while Memory B focuses on the technical server-side installation and environment configuration. There is no meaningful semantic overlap or logical connection between these two distinct parts of the manual.


id: a3db0a4b-6050-46f1-a5e5-c95e11e79baf
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 09:04:50
context:
Memory A focuses on user-facing search and sharing features within the application, while Memory B focuses on administrative maintenance and system update procedures. There is no meaningful semantic overlap or functional connection between these two distinct operational areas.


id: 2e4b4a56-0440-4693-a5f1-547bbbfea28c
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 09:05:08
context:
Memory A focuses on the specific functional mechanics of sharing files and memory packs, while Memory B describes the technical architecture and installation of the platform (PWA, multi-user support, and database isolation). There is no direct functional or semantic overlap between these two distinct sections of the user manual.


id: 5f4c4e23-0a1d-4c5f-9adf-6585c0a60854
source_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 09:05:34
context:
Memory A focuses on the 'CQ Share' functionality for file and knowledge sharing, while Memory B details the 'CQ AI Gateway' integration for AI model access. While both are part of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 77d48c93-253a-422b-b18a-5175883c23fc
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 09:06:54
context:
Memory A describes the user interface and procedures for sharing digital assets within the platform, while Memory B focuses on the technical installation methods for the software. There is no meaningful functional or semantic overlap between how to share files and how to install the server.


id: 1497c4ef-a84d-4e49-99fc-9dfebaebece5
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 09:06:54
context:
Memory A describes the user interface and procedures for sharing digital assets within the platform, while Memory B describes the technical installation methods for the software. There is no meaningful semantic overlap or functional connection between the two.


id: c4a4d6b9-05a2-4d66-afb9-4cd7b21e059d
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 09:07:11
context:
Memory A focuses on the functional UI features of sharing digital assets and memory packs, while Memory B focuses on the technical server-side installation and environment configuration. There is no direct semantic overlap or functional dependency between these two specific sections of the manual.


id: aee3eb2c-5e5a-4c97-a6ee-fb0e63073339
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 09:07:23
context:
Memory A describes the user-facing file and memory sharing features of the platform, while Memory B focuses on administrative system maintenance and installation procedures. There is no functional or semantic overlap between sharing assets and updating the server software.


id: 1004cafc-89cb-4875-a41c-2f94cab8a04a
source_id: 033b4c10-b865-4082-b222-2b80e3325247
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 09:07:55
context:
Memory A focuses on the UI and procedures for sharing digital assets and memory packs, while Memory B describes the technical installation of the platform and AI Gateway integration. While both are parts of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap.


id: de68de33-8e59-4510-9e5f-986fd4c801a6
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 09:08:44
context:
Memory A discusses the creation of file shares within the CitadelQuest platform, while Memory B describes the technical installation process of the platform itself. While both are sections of the same user manual, they cover distinct, unrelated functional areas (feature usage vs. system deployment) with no semantic overlap or dependency.


id: 4bf5aaac-09e4-4080-9850-93e46628e3a2
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 09:09:15
context:
Memory A focuses on the 'CQ Share' feature for file and knowledge distribution, while Memory B focuses on system maintenance, updates, and installation procedures. There is no meaningful semantic overlap, reinforcement, or contradiction between these two distinct functional areas of the software.


id: 3dd509e8-3607-4a7c-a4e4-ec52bb4df4dd
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 09:09:27
context:
Memory A focuses on the 'CQ Share' feature and file sharing mechanisms, while Memory B focuses on PWA installation, multi-user architecture, and server requirements. There is no meaningful semantic overlap or functional connection between these two specific sections of the user manual.


id: 13bf1a38-6752-40b9-84ac-3150cbbda59b
source_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 09:09:42
context:
Memory A discusses the file-sharing features (CQ Share) of the platform, while Memory B focuses on the AI Gateway integration and installation process. There is no meaningful semantic overlap or functional connection between these two specific modules.


id: 31cf8465-af13-43cf-9110-5c84c208a5b3
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: 02219640-3973-4d9f-bbb1-5c2f490ed3b5
type: NOT_DETECTED
created_at: 2026-03-13 09:10:08
context:
Memory A describes specific front-end user functionality for sharing files, while Memory B focuses on back-end server requirements and installation procedures. There is no meaningful semantic overlap or logical connection between these distinct sections of the user manual.


id: 696a28f7-f584-4fc6-bae9-31347c54a1a1
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: aa033ef6-d33a-4289-9fbb-fb893247be20
type: NOT_DETECTED
created_at: 2026-03-13 09:10:19
context:
Memory A focuses on the functional usage of the 'CQ Share' feature for managing shared files, while Memory B focuses on the technical installation and deployment methods of the CitadelQuest platform. There is no meaningful semantic overlap or logical connection between these two distinct sections of the user manual.


id: f552f653-e2e4-444d-857c-db2c1df8651d
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: e47091aa-4b2b-4925-a2ed-f156fb58e4a9
type: NOT_DETECTED
created_at: 2026-03-13 09:10:30
context:
Memory A focuses on the end-user functionality of sharing files and memory packs within the application, while Memory B focuses on the technical server-side installation and environment configuration. There is no direct semantic overlap or functional dependency between these two specific sections of the manual.


id: 7ea21ca6-00a6-485d-b45a-683bf934ac85
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: fcec0402-59ac-42bb-b213-6d2270fce582
type: NOT_DETECTED
created_at: 2026-03-13 09:10:44
context:
Memory A focuses on user-level content sharing and search functionality, while Memory B focuses on administrative system maintenance and update procedures. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: ebd77791-59c9-4824-ac09-40a16bb95fee
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: 6d45f077-3b4a-43a8-9e58-bc3da291393c
type: NOT_DETECTED
created_at: 2026-03-13 09:11:05
context:
Memory A focuses on the functional mechanics of sharing files and memory packs within the platform, while Memory B describes the technical installation, PWA support, and multi-user database architecture. While both are sections of a user manual, they describe distinct, unrelated features with no direct functional or logical overlap.


id: a26c03e2-b8be-4f34-9010-97d79807b210
source_id: d0105e38-e572-40e8-9841-f88321a97df3
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 09:11:26
context:
Memory A focuses on the 'CQ Share' functionality for file and knowledge distribution, while Memory B focuses on 'CQ AI Gateway' integration and installation procedures. There is no meaningful semantic overlap, reinforcement, or contradiction between these two distinct features of the platform.


id: d11d0dba-f501-4f2b-b5a5-bb95155a790d
source_id: ce8748d3-07f3-458d-b031-05996cd7ecc8
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: RELATES_TO
created_at: 2026-03-13 10:44:03
context:
Memory A covers user-level backups (/backup), while Memory B covers admin-level backups (/administration/system-backups).


id: 399a4ac5-a15d-40b8-b2b8-4c0f9879ca87
source_id: 10447049-2745-48a8-a44e-219768498463
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: RELATES_TO
created_at: 2026-03-13 10:44:37
context:
Both documents cover CitadelQuest administrative/maintenance procedures (backups and user management)


id: c19758e6-04b0-49f8-97b5-c710e7c0f402
source_id: ce8748d3-07f3-458d-b031-05996cd7ecc8
target_id: 02219640-3973-4d9f-bbb1-5c2f490ed3b5
type: REINFORCES
created_at: 2026-03-13 10:52:13
context:
Memory B lists the 'zip' PHP extension as a requirement, which enables the backup process in Memory A


id: b0a8b645-3285-4a95-8393-4444d658cf96
source_id: ce8748d3-07f3-458d-b031-05996cd7ecc8
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 10:53:30
context:
Memory A focuses on the data backup and recovery procedures within the platform, while Memory B describes the AI Gateway integration and server installation requirements. While both are part of the same user manual, they cover distinct functional areas (data maintenance vs. system setup/AI services) with no direct semantic overlap or conflicting information.


id: 1f103ccf-9332-47af-929b-a7cba0a61f1d
source_id: b0814698-e1bf-405e-bbd0-89be0c75d3a2
target_id: fdba9b8b-d1a7-475c-bf84-03db9e868a65
type: NOT_DETECTED
created_at: 2026-03-13 10:56:45
context:
Memory A focuses on the technical procedures for restoring and deleting backups within the CitadelQuest platform, while Memory B details the installation process and AI Gateway integration. While both are part of the same user manual, they describe distinct, unrelated functional modules (data recovery vs. initial setup/AI services) with no direct semantic overlap or conflict.


id: f91596a0-75e0-4563-96c2-abf2820ddae2
source_id: fd441b64-9557-464b-b15c-080626d39052
target_id: c2108434-8b74-46a0-845d-5abb287a9cec
type: NOT_DETECTED
created_at: 2026-03-13 11:23:42
context:
Memory A focuses on user registration and account onboarding procedures, while Memory B describes the technical structure of knowledge management and Memory Packs. There is no direct functional or semantic overlap between account creation and the .cqmpack file format.


id: 11263bcd-4afd-4cb7-8a84-893d123084c6
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: c2108434-8b74-46a0-845d-5abb287a9cec
type: NOT_DETECTED
created_at: 2026-03-13 11:24:29
context:
Memory A focuses on user onboarding and UI language settings, while Memory B describes the technical structure of the memory management system. There is no meaningful semantic overlap or functional connection between these two distinct parts of the user manual.


id: ff3980e8-6eb8-46b2-aa6b-0e06e7fdacdb
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-13 11:24:49
context:
Memory A describes the user onboarding process and language settings, while Memory B explains the technical structure of the Memory Library system. While both are sections of a user manual, they describe distinct, unrelated features of the platform with no semantic overlap or functional dependency.


id: d7cdb3f4-d652-486c-847b-974f5485ec83
source_id: fd441b64-9557-464b-b15c-080626d39052
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 11:25:51
context:
Memory A focuses on the initial account registration and onboarding process, while Memory B details the search and sharing functionality of the CQ Share feature. While both are parts of the same user manual, they describe distinct, unrelated functional modules with no direct semantic overlap or conflict.


id: 73dff241-894a-4ff7-8f4a-053fdfde4b8d
source_id: fd441b64-9557-464b-b15c-080626d39052
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-13 11:26:43
context:
Memory A focuses on user registration and account onboarding, while Memory B discusses file and knowledge sharing (CQ Share). Although both are part of the same user manual, they describe distinct, unrelated functional modules with no overlapping logic or conflicting information.


id: f4133a20-1a73-42eb-b21f-fe093555b7b0
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: de432f8f-e033-4e6e-a579-b189ccd74095
type: NOT_DETECTED
created_at: 2026-03-13 11:27:11
context:
Memory A focuses on the initial user onboarding and AI Spirit setup, while Memory B describes the file and memory sharing management system. While both are part of the same user manual, they describe distinct, unrelated functional modules with no direct semantic overlap or conflict.


id: 9dbd3977-14d1-4591-8091-ba95583cf09d
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 11:27:22
context:
Memory A describes the initial onboarding process and AI Spirit setup, while Memory B focuses on the CQ Share functionality and file distribution. There is no meaningful semantic or functional overlap between these two distinct features of the platform.


id: 27a5ee7b-366c-4feb-aafe-e547f5c7b7ee
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-13 11:28:06
context:
Memory A describes the initial user onboarding and AI setup, while Memory B describes the file and knowledge sharing system (CQ Share). While both are parts of the same user manual, they cover distinct, unrelated functional areas of the platform with no direct semantic overlap or conflict.


id: 8b113087-225d-49e8-bdd0-4fcd5d986501
source_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
target_id: d0105e38-e572-40e8-9841-f88321a97df3
type: NOT_DETECTED
created_at: 2026-03-13 11:28:29
context:
Memory A focuses on the initial user onboarding and AI Spirit setup, while Memory B describes the CQ Share functionality and file distribution. While both are parts of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: b9e6f30a-0f66-4c40-a1e6-1003737c03bd
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 11:28:57
context:
Memory A focuses on the initial user onboarding and language settings, while Memory B describes the technical process of sharing files and memory packs via CQ Share. While both are part of the same user manual, they describe distinct, unrelated features with no functional or logical overlap.


id: e78f99e3-fde2-4813-b565-37f507f0fe08
source_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-13 11:29:41
context:
Memory A focuses on the initial onboarding process and language settings, while Memory B describes the CQ Share feature for file and knowledge distribution. While both are part of the same user manual, they cover distinct, unrelated functional areas of the platform with no semantic overlap or conflicting information.


