# memory_relationships

id: 23a4403a-ad78-4832-aea3-9c9e2cf2dee7
source_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
target_id: c2108434-8b74-46a0-845d-5abb287a9cec
type: RELATES_TO
created_at: 2026-03-13 11:42:51
context:
Memory A describes the UI for monitoring memory, while Memory B describes the underlying data structure.


id: 8f97db81-4234-4edc-8152-22da48e103df
source_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
target_id: c2108434-8b74-46a0-845d-5abb287a9cec
type: REINFORCES
created_at: 2026-03-13 11:44:03
context:
Memory A describes the 'Extract Memory' UI feature which generates the .cqmpack files defined in Memory B


id: 5bbc5118-ae03-4b61-ab2b-ee1fd1e14db4
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 11:48:25
context:
Memory A focuses on the definition and functionality of 'Spirits' as AI companions, while Memory B details the 'CQ Share' system for file and knowledge distribution. While both are features of the CitadelQuest platform, they describe distinct, non-overlapping systems without a direct functional or semantic link.


id: 3a40e324-4fef-4cc9-88b6-0ab9a1a95b57
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-13 11:49:13
context:
Memory A focuses on the definition and functionality of Spirits (AI companions), while Memory B discusses the mechanisms for sharing files and knowledge via CQ Share. While both are parts of the CitadelQuest platform, they describe distinct features with no direct functional or semantic overlap.


id: 30e810b5-1104-47fc-89e0-b6b35907c415
source_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-13 11:49:20
context:
Memory A discusses the nature and management of AI Spirits, while Memory B focuses on the technical mechanisms for sharing files and knowledge packs. While both are part of the same user manual, they describe distinct features with no direct functional or semantic overlap.


id: 7cb07558-6a01-4f42-a26f-9a0103b3993a
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 11:50:08
context:
Memory A focuses on the management and UI of AI companions (Spirits), while Memory B details the sharing and filtering functionality for files and memory packs. While both are parts of the same user manual, they describe distinct, non-overlapping features with no direct functional or semantic dependency.


id: fc27b581-98b4-48b5-9baf-6cf9a75818f3
source_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-13 11:50:57
context:
Memory A focuses on the management and UI of AI 'Spirits', while Memory B discusses the 'CQ Share' feature for 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 connection.


id: bc796abd-52e7-4c94-8b9a-d7799755f410
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 11:51:41
context:
Memory A focuses on the configuration and identity of AI Spirits, while Memory B details the sharing and filtering of files via CQ Share. While both are part of the same platform manual, they describe distinct features with no direct functional or semantic overlap.


id: 16ca8d83-0af5-4636-8080-f290c369d298
source_id: c39275dc-8438-45f5-acca-639882d9ac61
target_id: d0105e38-e572-40e8-9841-f88321a97df3
type: NOT_DETECTED
created_at: 2026-03-13 11:52:30
context:
Memory A focuses on the configuration and customization of AI Spirits, while Memory B describes the search and sharing functionality for files and memory packs. While both are part of the CitadelQuest platform, they describe distinct, non-overlapping features with no direct functional or semantic link.


id: 49d06aff-9eb4-4d7a-bea6-d1d99b3bb805
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 11:57:41
context:
Memory A focuses on the creation and gamified progression of AI Spirits, while Memory B details the search, filter, and sharing mechanics of the CQ Share system. There is no meaningful semantic overlap or functional connection between these two distinct platform features.


id: 6f801538-1948-4e8a-9bb9-5bb4dd0c9d42
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-13 11:58:07
context:
Memory A describes the creation and leveling of AI Spirits, while Memory B discusses the sharing of files and knowledge graphs via CQ Share. While both are part of the same user manual, they describe distinct features with no functional or semantic overlap.


id: 05a014f5-7f37-4ddf-a3f1-f36125ef2a32
source_id: bcb05ed5-9d44-4628-be3d-684beac42b73
target_id: d0105e38-e572-40e8-9841-f88321a97df3
type: NOT_DETECTED
created_at: 2026-03-13 11:58:20
context:
Memory A describes the creation and leveling mechanics of AI Spirits, while Memory B details the sharing and filtering functionality of the CQ Share system. While both are part of the CitadelQuest User Manual, they describe distinct, non-overlapping features with no direct functional or semantic dependency.


id: ca59cd47-6b54-4621-8139-23d7fef2d22e
source_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
target_id: de432f8f-e033-4e6e-a579-b189ccd74095
type: RELATES_TO
created_at: 2026-03-13 11:58:36
context:
Memory B describes sharing workflows initiated from the Memory Explorer interface detailed in Memory A


id: 182c7e7a-368b-46c2-9d70-f356d7c4d14d
source_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
target_id: 033b4c10-b865-4082-b222-2b80e3325247
type: RELATES_TO
created_at: 2026-03-13 11:59:03
context:
Memory B describes sharing functionality integrated within the Memory Explorer interface of Memory A


id: dfb1d620-ca88-4feb-a9af-934b3bdb8ce3
source_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: RELATES_TO
created_at: 2026-03-13 11:59:16
context:
Memory A describes the Memory Explorer UI, which Memory B identifies as a source for creating shares


id: 6528da8a-3394-4b04-b172-3b73357c785e
source_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
target_id: 033b4c10-b865-4082-b222-2b80e3325247
type: REINFORCES
created_at: 2026-03-13 12:06:36
context:
Memory B provides the specific procedural implementation for the 'CQ Share' feature mentioned in Memory A


id: 8a9e8903-8670-4957-bfbc-5a52cbcfbf73
source_id: 697c5176-557a-4939-bbbd-f565956940af
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: RELATES_TO
created_at: 2026-03-13 12:15:50
context:
Memory B describes sharing files that are managed and viewed via the interface described in Memory A


id: c0237095-5a76-4289-acfe-06f59db2315b
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 12:24:35
context:
While both memories are sections of the CQ User Manual and discuss UI navigation, they describe two entirely separate features (CQ Chat vs. CQ Share) with no functional or semantic overlap in their specific operations.


id: 46c14cee-66a3-44c4-91f0-828043833270
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: 033b4c10-b865-4082-b222-2b80e3325247
type: NOT_DETECTED
created_at: 2026-03-13 12:25:00
context:
While both memories describe UI components and navigation within the CitadelQuest platform (CQ Chat vs. CQ Share), they describe distinct, independent modules with no functional overlap or conflicting information. The connection is too generic to be meaningful.


id: e7908b49-8ce5-4925-8986-e74589aa64d9
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-13 12:25:22
context:
Memory A describes the UI and access methods for the CQ Chat system, while Memory B refers to an empty section regarding CQ Share methods. While both are part of the CQ User Manual, they describe distinct, unrelated features (messaging vs. file sharing) with no functional or semantic overlap.


id: 3907a326-0e85-4f17-906d-692e49032bb6
source_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
target_id: d0105e38-e572-40e8-9841-f88321a97df3
type: NOT_DETECTED
created_at: 2026-03-13 12:25:51
context:
Memory A describes the UI and access methods for the CQ Chat system, while Memory B describes the search, filter, and creation process for the CQ Share system. Although both are part of the CQ User Manual, they describe distinct, unrelated features (messaging vs. file sharing) with no functional or semantic overlap.


id: fb10e0b2-dce0-4c57-87d3-f7ca1d541bd2
source_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 12:26:22
context:
Memory A describes the CQ Chat messaging system, while Memory B describes the CQ Share file-sharing functionality. While both are features of the CitadelQuest platform, they describe distinct modules with no functional or semantic overlap in the provided content.


id: dd11ce88-8d6f-409d-ae3b-a3c8d1bb33de
source_id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-13 12:27:57
context:
Memory A focuses on the technical architecture and privacy of the CQ Chat messaging system, while Memory B describes the search and sharing functionality of the CQ Share feature. While both are part of the same user manual, they describe distinct, unrelated features with no direct functional or technical overlap.


id: 21b7ad63-65ee-4165-a12a-e6c8d92752e8
source_id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
target_id: d0105e38-e572-40e8-9841-f88321a97df3
type: NOT_DETECTED
created_at: 2026-03-13 12:29:02
context:
Memory A focuses on the technical architecture and privacy of the CQ Chat messaging protocol, while Memory B details the search and sharing functionality of the CQ Share feature. While both are components of the CitadelQuest ecosystem, they describe distinct functional modules with no direct overlap in logic, data flow, or conflicting information.


id: cad4d859-a36c-4d59-b913-cb7f61735799
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
type: NOT_DETECTED
created_at: 2026-03-22 18:08:19
context:
Memory A is a high-level overview of the Settings page, while Memory B is a deep dive into the specific 'AI Services' subsection mentioned in Memory A. Memory B reinforces the general information in Memory A by providing granular details on model selection, API keys, and credit management within the same document structure.


id: c68c6472-31ec-4986-be24-edcee0a0c599
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: 8a1c5fe3-c932-4def-bfd8-ad1667b9c37e
type: NOT_DETECTED
created_at: 2026-03-22 18:08:29
context:
Both memories originate from the same source document (10-settings.md). Memory A provides the high-level overview of the settings architecture, while Memory B expands on the specific 'Social and content' sub-sections mentioned in A, providing detailed functional evidence of how those settings operate.


id: 60267dd8-68d5-458c-81d2-b7f884366711
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: 6b9619cb-e8e6-492f-8942-29ce08a329e3
type: NOT_DETECTED
created_at: 2026-03-22 18:08:45
context:
Memory A is a high-level introduction to the Settings page, while Memory B is a deep dive into the specific 'Feeds' sub-section of those same settings. Memory B confirms and expands upon the social/content management features mentioned in the foundational overview of Memory A.


id: 418c9ffc-7d6f-4fae-b949-402776f03f84
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: 3fb33b70-55cf-4541-ad4d-f8da2b5e5ebd
type: NOT_DETECTED
created_at: 2026-03-22 18:09:13
context:
Memory A provides an introduction to the settings page, while Memory B provides a navigation summary of the same page. They originate from the same source file (10-settings.md) and confirm the same functional areas: General Settings, AI Services, Profile, and Feeds.


id: f036c9dd-ff75-4dd8-93e9-d2c0c1ff0386
source_id: 70701b55-4255-46a9-9cb8-64f779221e21
target_id: 3fb33b70-55cf-4541-ad4d-f8da2b5e5ebd
type: NOT_DETECTED
created_at: 2026-03-22 18:09:52
context:
Memory A provides granular details about the 'General Settings' section, while Memory B provides the structural overview of the entire settings sidebar. Memory B reinforces the existence and categorization of the features described in Memory A (login, themes, database) within the broader platform context.


id: 89ce2b37-ae9e-4f5d-892a-52033670f1d6
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: 3fb33b70-55cf-4541-ad4d-f8da2b5e5ebd
type: NOT_DETECTED
created_at: 2026-03-22 18:10:40
context:
Memory B provides a high-level navigation summary of the Settings page, mentioning 'database migration tools' as a core component. Memory A provides the deep-dive technical procedure for that exact migration tool. They reinforce each other as part of the same documentation hierarchy.


id: efa8a3be-c344-480a-a29e-cf5289793550
source_id: c61b72ad-697b-40ad-9850-f0ce482ad13e
target_id: b55220a6-be4e-41cf-a5b2-479ae9733feb
type: REINFORCES
created_at: 2026-03-22 18:17:26
context:
Memory A defines the 'CQ Contacts' API key exchange required for the 'CQ Chat' described in Memory B


id: 790fc2fe-78eb-4248-9987-ec6393fb469a
source_id: 307ef895-4d2e-4253-8293-02187da0badf
target_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
type: REINFORCES
created_at: 2026-03-22 18:26:57
context:
Memory B provides the technical implementation details for the privacy principles stated in Memory A


id: 65950cee-ad03-455a-ac1d-0b28cb776152
source_id: a0bca789-5788-4ced-ab99-beadcf7ca11a
target_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
type: REINFORCES
created_at: 2026-03-22 18:30:52
context:
Memory B provides technical implementation details for the data sovereignty goals stated in Memory A


id: 83ba92a7-a8fb-4494-af7b-25d25f540ced
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: 64ac3eb6-21a4-4540-8226-ebdee187fd2a
type: REINFORCES
created_at: 2026-03-22 18:31:31
context:
Memory B provides specific functional evidence of the decentralized architecture described in Memory A


id: 90193af9-03af-4871-a69f-bc96014cdc4a
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
type: REINFORCES
created_at: 2026-03-22 18:32:08
context:
Memory B provides a specific implementation of the decentralized communication described in Memory A


id: c7c844db-2267-4721-b67c-88e6a011cfc7
source_id: 307ef895-4d2e-4253-8293-02187da0badf
target_id: de076905-7921-4a20-bb33-c9638b69ef54
type: REINFORCES
created_at: 2026-03-22 18:33:19
context:
Memory B provides specific UI and functional implementation details for features defined in Memory A


id: 9ed014d4-2af9-4629-9390-e71f97c4f695
source_id: 307ef895-4d2e-4253-8293-02187da0badf
target_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
type: REINFORCES
created_at: 2026-03-22 18:33:46
context:
Memory B provides detailed implementation of the decentralized social features mentioned in Memory A


id: d85ead4f-9044-429e-a4cb-2732c1f03c30
source_id: 307ef895-4d2e-4253-8293-02187da0badf
target_id: ac5c0c9f-2ffd-4481-a45e-87881310440a
type: REINFORCES
created_at: 2026-03-22 18:33:54
context:
Memory B provides specific implementation details for the decentralized sharing mentioned in Memory A


id: a864f3d0-2ccb-40c3-bea4-6eba461fbdaa
source_id: 307ef895-4d2e-4253-8293-02187da0badf
target_id: 32d09012-3eaf-49b0-8726-915418d6dad1
type: REINFORCES
created_at: 2026-03-22 18:34:12
context:
Memory B provides the technical protocol details for the decentralized features outlined in Memory A


id: 98f71702-9921-45ef-afbe-e25e3b758789
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: ada32b14-6f87-4f53-98cf-977cf80f006c
type: REINFORCES
created_at: 2026-03-22 18:39:27
context:
Memory B provides specific technical implementation details for the core features defined in Memory A


id: 0a7646ca-912f-47b4-83d4-2dc08ffac531
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
type: REINFORCES
created_at: 2026-03-22 18:42:16
context:
Memory B provides technical implementation details for the AI collaboration goals stated in Memory A


id: 53ba649a-bbb6-4939-8113-f5b48e2d4f94
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: 63482038-a160-4154-8a9e-9555c065a606
type: REINFORCES
created_at: 2026-03-22 18:47:19
context:
Memory B provides specific implementation details for the 'Spirits' and 'Cloud' features in Memory A


id: 02321359-a7b3-4c5b-9558-fc2a6dbb9700
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: 786911a0-c1b1-4e4b-8d1f-7ea3d33e7d3d
type: REINFORCES
created_at: 2026-03-22 18:47:29
context:
Memory B provides specific implementation details of the data sovereignty principles defined in Memory A.


id: 884c737a-c31f-4692-8fce-0071e4aed369
source_id: 307ef895-4d2e-4253-8293-02187da0badf
target_id: 786911a0-c1b1-4e4b-8d1f-7ea3d33e7d3d
type: REINFORCES
created_at: 2026-03-22 18:48:51
context:
Memory B provides specific implementation details for the profile and federation features in Memory A


id: 6fee6f5c-4a92-4d43-8e4e-1e10e220d0ae
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: REINFORCES
created_at: 2026-03-22 19:01:49
context:
Memory B provides technical implementation details for the data sovereignty goals defined in Memory A


id: c08e53a4-440e-4b79-a1de-653a2916b09c
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: f090a573-effa-4c9a-9a8f-b17da18cb3bc
type: REINFORCES
created_at: 2026-03-22 19:02:21
context:
Memory B provides a technical implementation of the decentralized collaboration described in Memory A


id: e0e375c3-32f1-4f2d-9506-c30fdbebe1b1
source_id: 307ef895-4d2e-4253-8293-02187da0badf
target_id: 4f70c9b8-0c82-4597-a99f-d1ca8c7962b9
type: REINFORCES
created_at: 2026-03-22 19:05:13
context:
Memory B provides technical detail on the 'CQ Share' and 'Memory Pack' features mentioned in Memory A


id: 7da968a6-35c1-4d24-9a5b-1b6f09ce96f3
source_id: 07834e44-7361-45b8-aa45-60d029df53d3
target_id: 1d3da196-26b2-4575-8d68-23713a1ac801
type: REINFORCES
created_at: 2026-03-22 19:11:43
context:
Memory B provides detailed functional depth to the 'CQ Explorer' and 'CQ Share' chapters in Memory A


id: 5c7ee8be-0260-4cc2-853c-3a3c2d47c14e
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
type: REINFORCES
created_at: 2026-03-22 19:15:27
context:
Memory B provides specific implementation details for the communication features introduced in Memory A


id: e4e17d35-5247-473b-8ab0-c62571dcc8ff
source_id: 307ef895-4d2e-4253-8293-02187da0badf
target_id: d53d081b-6f67-4155-8069-711b2449468c
type: REINFORCES
created_at: 2026-03-22 19:26:26
context:
Memory B provides technical implementation details for the 'Spirits' and 'Memory' features in Memory A


id: 1cf09832-8784-4fef-9a34-03cc99c33d57
source_id: 07834e44-7361-45b8-aa45-60d029df53d3
target_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
type: REINFORCES
created_at: 2026-03-22 19:29:01
context:
Memory B provides the detailed technical implementation of the 'CQ Memory' chapter listed in Memory A


id: ec98e654-83b8-4abf-84dd-e2d41ee01734
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
type: REINFORCES
created_at: 2026-03-22 19:33:16
context:
Memory B provides specific technical implementation details for the 'Spirits' introduced in Memory A


id: 8684695a-3bd1-474a-9f0c-5588bd3fd996
source_id: 33d0838f-5d52-4b3c-bc90-43a4272fd309
target_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
type: RELATES_TO
created_at: 2026-03-22 19:35:19
context:
Memory A describes the onboarding process which includes configuring the Spirits defined in Memory B


id: 4c95da4b-e3e0-4c43-86c8-d52bb03a1ca7
source_id: a0bca789-5788-4ced-ab99-beadcf7ca11a
target_id: f53218b5-f2aa-4adb-902c-e88a44f11e67
type: REINFORCES
created_at: 2026-03-22 19:39:28
context:
Memory B provides technical implementation details for the AI-human collaboration mission in Memory A


id: 138ab77b-1ba4-466e-a826-f111238c757d
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: REINFORCES
created_at: 2026-03-22 19:40:14
context:
Memory B provides specific implementation details for the multilingual support mentioned in Memory A


id: d6736d9f-a1c9-45f7-8863-54e5bfd00c5c
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
type: REINFORCES
created_at: 2026-03-22 19:43:15
context:
Memory B provides the specific mechanism (CQ Follow) for the social interactions described in Memory A


id: 4dd66bc8-b303-43dd-bc7e-30f46e3d57f2
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
type: REINFORCES
created_at: 2026-03-22 19:43:24
context:
Memory B explains the authentication mechanism that enables the 'CQ Contacts' feed scope in Memory A


id: b8c906b0-f01b-4492-9a17-552ba6d85818
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 32d09012-3eaf-49b0-8726-915418d6dad1
type: REINFORCES
created_at: 2026-03-22 19:43:42
context:
Memory B provides the technical protocol details that enable the social features described in Memory A


id: de676bbf-36b2-45ca-b471-c780f09a8868
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
type: REINFORCES
created_at: 2026-03-22 19:44:44
context:
Memory B explains the mechanism (CQ Contacts) that enables the feed visibility described in Memory A


id: 54895e7f-8ec2-4474-907b-827041c335ef
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
type: REINFORCES
created_at: 2026-03-22 19:45:53
context:
Memory B explains the subscription mechanism that enables the feed distribution described in Memory A


id: 1db6a08c-05e0-4a6d-90d9-7a56d97af977
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
type: REINFORCES
created_at: 2026-03-22 19:46:02
context:
Memory B explains the authentication mechanism (API keys) for the 'CQ Contacts' feed scope in Memory A


id: 9aaf4ac2-502a-45a5-b9c0-764970072dd5
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: 32d09012-3eaf-49b0-8726-915418d6dad1
type: REINFORCES
created_at: 2026-03-22 19:46:25
context:
Memory B provides the underlying protocol details that enable the feed features described in Memory A


id: a1e6c7ed-d887-4fd2-bc50-27c7a35b8fa7
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: 1edffca9-3a49-4cea-ac1c-e0dab061c758
type: RELATES_TO
created_at: 2026-03-22 19:46:39
context:
Memory A details the interaction logic for the CQ Feed which is a core component of the CQ Explorer layout in Memory B


id: c2ca231f-6eb5-4bde-aa7f-d23a489035a8
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 897390d1-2ec0-45f9-a740-5bff0bc0232b
type: RELATES_TO
created_at: 2026-03-22 19:50:50
context:
Memory B describes the Dashboard navigation and notification badges for the CQ Feed described in Memory A


id: fdda8b1e-8770-421d-9c2e-d3144a79fd96
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 7d433200-f88c-450e-a2b5-f100e5a9a92c
type: RELATES_TO
created_at: 2026-03-22 19:51:14
context:
Memory B describes the UI navigation (User Menu) used to access the CQ Explorer mentioned in Memory A


id: d24f3958-90f0-4f39-8a81-19a7f0f85e12
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: ada32b14-6f87-4f53-98cf-977cf80f006c
type: NOT_DETECTED
created_at: 2026-03-22 19:52:35
context:
Memory A focuses on the social feed interaction mechanics (reactions and comments), while Memory B describes dashboard UI components and system metrics (AI credits and storage). While both are part of the same user manual, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: 1a79192c-23b4-4349-b211-c695a133dd46
source_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
target_id: ada32b14-6f87-4f53-98cf-977cf80f006c
type: NOT_DETECTED
created_at: 2026-03-22 19:53:50
context:
Memory A focuses on the technical architecture and federation protocol of the CQ Feed social platform, while Memory B describes the UI components of the Dashboard and AI credit monitoring. While both are part of the CitadelQuest User Manual, they describe distinct, non-overlapping functional areas with no direct semantic or logical connection.


id: 08c78285-6878-47a1-bfef-52cf8d47d878
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 3fb33b70-55cf-4541-ad4d-f8da2b5e5ebd
type: REINFORCES
created_at: 2026-03-22 19:55:20
context:
Memory B confirms the UI implementation and management settings for the CQ Feed described in Memory A


id: fd2823b1-be81-43b1-aad6-3fe6c2899834
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: f02102d6-abdf-4cef-bc2f-ddc1876aaccb
type: NOT_DETECTED
created_at: 2026-03-22 20:09:18
context:
Memory A focuses on the social interaction mechanics (reactions, comments, and federation) of the CQ Feed, while Memory B focuses on the visual customization and themes of the user's public profile page. There is no direct functional or semantic overlap between these two distinct modules of the platform.


id: a6001a47-39ac-45fd-915e-c124cc52f524
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 20:14:51
context:
Memory A describes the CQ Feed social networking feature, while Memory B describes the administrative update process. While both are sections of the same user manual, they cover distinct functional areas (social features vs. system maintenance) with no direct semantic overlap or conflict.


id: 62eadb46-80ce-4cd1-b7ed-cb525fe6c364
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 20:15:24
context:
Memory A describes the CQ Feed social networking features, while Memory B focuses on administrative server logs and backups. While both are part of the CQ User Manual, they cover distinct functional areas (social vs. administration) with no direct semantic overlap or conflicting information.


id: 1fcd0eca-122a-41d4-a2f9-7895ecd81788
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-22 20:16:38
context:
Memory A focuses on the social feed and user interface for content consumption, while Memory B focuses on administrative user management and system-level controls. While both are part of the CQ User Manual, they describe distinct functional areas (social vs. admin) with no direct overlap in logic, data flow, or conflicting information.


id: 37cdc7d7-387a-4036-8add-3960e2ec44c5
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 20:16:56
context:
Memory A describes the user-facing social feed functionality, while Memory B describes administrative system update procedures. There is no meaningful semantic or functional overlap between these two distinct parts of the application manual.


id: fca9327f-72e1-47f9-a22f-4a49b064cafe
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 20:17:16
context:
Memory A focuses on the end-user social features (CQ Feed and Timeline), while Memory B focuses on administrative server management (Logs and Backups). While both are part of the same user manual, they describe entirely different functional areas with no direct semantic overlap or dependency.


id: 51f77c14-b319-4b76-9da1-df71c7cc3201
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 20:18:17
context:
Memory A focuses on the social feed functionality and content management, while Memory B focuses on administrative system updates and maintenance. While both are sections of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 521e018e-055f-436e-96e0-9b810940fb7b
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 20:19:31
context:
Memory A describes social interaction features (reactions/comments) within the CQ Feed, while Memory B describes administrative update procedures. While both are part of the CitadelQuest User Manual, they cover distinct functional domains (user-facing social features vs. admin-facing system maintenance) with no semantic overlap or dependency.


id: 98eafc34-c669-4465-86cf-340abfd4ac30
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: 2a74f7ec-6dc6-4e4b-a87a-5ce5de772401
type: NOT_DETECTED
created_at: 2026-03-22 20:19:50
context:
Memory A focuses on social interaction features (reactions and comments) within the CQ Feed, while Memory B focuses on administrative system settings (registration and homepage redirects). While both are part of the CitadelQuest User Manual, they describe distinct functional areas with no direct semantic overlap or logical dependency.


id: 3726b760-2cac-4589-a6f4-d757742ce67a
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 20:20:05
context:
Memory A focuses on social interaction features (reactions and comments) within the CQ Feed, while Memory B focuses on administrative backend functions (logs and backups). While both are part of the same user manual, they describe entirely different functional domains with no semantic overlap or dependency.


id: abfee787-9163-4e21-a611-5f208a42897d
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-22 20:20:34
context:
Memory A focuses on the end-user social networking features (CQ Feed, subscriptions, and real-time updates), while Memory B focuses on system-level administration and the dashboard. While both are part of the CitadelQuest manual, they describe distinct functional areas with no direct semantic overlap or conflicting information.


id: 81b8f271-ee19-461e-8d5f-fc8a66bc362c
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 20:21:04
context:
Memory A discusses real-time content feed updates and user subscriptions within a social networking context, while Memory B discusses system-level software version updates and server administration. Despite sharing the word 'updates', they refer to entirely different technical processes (content polling vs. software deployment) and have no meaningful connection.


id: 95e84f46-e121-452a-a35f-80c4d5b15a36
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 20:21:32
context:
Memory A focuses on the social networking features (CQ Feed, subscriptions, and real-time updates) of the CitadelQuest platform, while Memory B focuses on administrative backend functions (logs and backups). While they both belong to the same user manual, they describe distinct, unrelated functional modules with no direct semantic overlap or conflict.


id: 02a91052-7304-415a-89d7-42dfc94949b2
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: d92f6c51-6e01-479d-83ca-d660824e27b7
type: RELATES_TO
created_at: 2026-03-22 20:23:45
context:
Both systems utilize CQ Explorer for discovery and share 'Public' vs 'CQ Contacts' visibility scopes


id: 44d817ca-6612-4f80-a352-c50077fc3333
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: a4102387-181b-467a-9de7-edeb48f554e0
type: RELATES_TO
created_at: 2026-03-22 20:36:48
context:
Both documents describe content visibility scopes (Public vs CQ Contacts) and CQ Explorer integration


id: 855bcb2b-ad03-472a-be89-55a934f57833
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
type: NOT_DETECTED
created_at: 2026-03-22 20:48:28
context:
Memory A describes the social networking feed (CQ Feed) and its UI, while Memory B describes AI integration with the file management system. While both are parts of the CitadelQuest ecosystem, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: 812c3f15-72ae-4879-9ca1-ff96740c285a
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: 9fc3589c-f983-4f00-8ed1-296e059d7fac
type: NOT_DETECTED
created_at: 2026-03-22 20:50:31
context:
While both memories are sections of the CitadelQuest User Manual, they describe completely different modules (social feed interactions vs. file storage) with no functional or semantic overlap beyond being part of the same platform.


id: ca39f5c9-bbdf-48d3-8541-b8f8357b98a6
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: 697c5176-557a-4939-bbbd-f565956940af
type: NOT_DETECTED
created_at: 2026-03-22 20:50:50
context:
Memory A describes social interaction features (reactions/comments) in the CQ Feed, while Memory B describes navigation modes (Tree View/File Preview) in the File Browser. While both are parts of the CitadelQuest User Manual, they describe distinct, non-overlapping functional modules with no direct semantic connection.


id: d2897879-6634-43b9-8b7a-b2897c299d32
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
type: NOT_DETECTED
created_at: 2026-03-22 20:51:18
context:
Memory A describes social networking features (reactions, comments, federation), while Memory B describes AI file management tools. While both are part of the CitadelQuest User Manual, they cover distinct, non-overlapping functional modules with no direct semantic connection.


id: f8cdf8d8-59cc-4766-837e-241c206e5ee5
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: d68be241-4b63-4c48-8309-69a2950cf0af
type: NOT_DETECTED
created_at: 2026-03-22 20:51:27
context:
Memory A describes the social feed and interaction system (reactions/comments), while Memory B describes the file storage and mobile architecture. While both are parts of the CitadelQuest platform, they cover distinct functional modules with no direct semantic overlap or conflicting information.


id: ed4a6577-2b44-4f38-a3c4-dadb95b0771c
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: 697c5176-557a-4939-bbbd-f565956940af
type: NOT_DETECTED
created_at: 2026-03-22 20:52:01
context:
Memory A describes the social networking feed and subscription mechanics, while Memory B describes the file browser interface and navigation modes. While both are part of the CitadelQuest ecosystem, they describe distinct, unrelated modules with no functional or semantic overlap.


id: 50a6e4d1-0065-4910-9c5a-34d36233249d
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: e3a976b6-6989-4cf5-8a77-b1236d687cd1
type: NOT_DETECTED
created_at: 2026-03-22 20:52:32
context:
Memory A focuses on the social networking feed mechanics (subscriptions, real-time updates, and peer-to-peer distribution), while Memory B focuses on AI integration with the file system (Spirit tools for file management). There is no meaningful semantic overlap or functional connection between these two distinct modules of the ecosystem.


id: 24688f5f-af07-4d88-995e-c38f9ddfb3fa
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: d68be241-4b63-4c48-8309-69a2950cf0af
type: NOT_DETECTED
created_at: 2026-03-22 20:52:43
context:
Memory A focuses on social feed subscription mechanics and real-time polling, while Memory B focuses on file browser storage architecture and mobile responsiveness. While both are part of the CitadelQuest manual, they describe distinct functional modules with no direct semantic overlap or conflicting information.


id: 8b3667c8-6644-467d-a369-5a17b24bd5ca
source_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
target_id: 697c5176-557a-4939-bbbd-f565956940af
type: NOT_DETECTED
created_at: 2026-03-22 20:53:07
context:
Memory A describes the decentralized federation protocol of a social feed, while Memory B describes the UI navigation modes of a file browser. While both are part of the CitadelQuest manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 9c309fea-8cdc-4cbb-8230-b2a5f6348692
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
type: NOT_DETECTED
created_at: 2026-03-22 20:56:53
context:
Memory A describes the user interface and functionality of a social feed (CQ Feed), while Memory B describes a technical process for extracting data into knowledge graphs (Memory Extraction). While both are features of the CitadelQuest ecosystem, they describe distinct, unrelated modules without functional or semantic overlap.


id: 2b1dd9f8-b5f2-4342-b5cf-394ded6df5d2
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: b7adbc37-239e-41fc-917c-62b612be0cf6
type: NOT_DETECTED
created_at: 2026-03-22 20:57:17
context:
Memory A describes the user interface and functionality of a social feed (CQ Feed), while Memory B describes a knowledge management and graph analysis system (CQ Memory). Although both are components of the CitadelQuest ecosystem, they describe distinct features with no direct functional or semantic overlap in the provided content.


id: f11637dc-9154-4f0a-b607-12c5d12be58f
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
type: RELATES_TO
created_at: 2026-03-22 20:57:51
context:
Both describe components of the CitadelQuest ecosystem and share visibility scopes (Public/Contacts)


id: 72c54a9d-03e1-479d-b2b6-e6951dcff29e
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: b7adbc37-239e-41fc-917c-62b612be0cf6
type: NOT_DETECTED
created_at: 2026-03-22 21:00:23
context:
Memory A describes social interaction features (reactions/comments) in the CQ Feed, while Memory B describes technical knowledge graph analysis in CQ Memory. They belong to different functional modules of the platform with no semantic overlap.


id: 95e77891-5303-4e33-a837-360961a29652
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
type: NOT_DETECTED
created_at: 2026-03-22 21:02:15
context:
Memory A describes the social feed and subscription mechanics of CitadelQuest, while Memory B details the AI memory extraction and knowledge graph process. While both are features of the same ecosystem, they describe distinct functional modules with no direct semantic overlap or conflicting information.


id: 6efd3b9e-2130-414c-b070-15f78ceae796
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
type: NOT_DETECTED
created_at: 2026-03-22 21:05:28
context:
Memory A describes the CQ Feed social networking platform, while Memory B describes the Spirits AI companion system. While both are components of the CitadelQuest ecosystem, they describe distinct features with no direct functional or semantic overlap in the provided text.


id: ce5e5dc8-55f0-4cd3-a3ba-2525d5fd4a91
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: bcb05ed5-9d44-4628-be3d-684beac42b73
type: NOT_DETECTED
created_at: 2026-03-22 21:06:39
context:
Memory A describes the CQ Feed (a decentralized social networking platform), while Memory B describes Spirit Creation and Progression (AI companion mechanics). While both are features of CitadelQuest, they represent distinct functional modules with no direct semantic overlap or interaction described in the content.


id: 650a6031-dc14-454a-bb48-8595ff25374d
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
type: NOT_DETECTED
created_at: 2026-03-22 21:06:55
context:
Memory A describes the technical and UI aspects of a decentralized social feed (CQ Feed), while Memory B describes the AI companion system (Spirits). While both are components of the CitadelQuest platform, they represent distinct features with no direct functional or semantic overlap in the provided content.


id: 46fe64d3-3380-4a05-8210-4c599f572762
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
type: NOT_DETECTED
created_at: 2026-03-22 21:07:15
context:
Memory A describes the social feed and timeline functionality, while Memory B describes the management of AI companions (Spirits). While both are components of the CitadelQuest ecosystem, they describe distinct, non-overlapping features with different UI routes and purposes.


id: d4bebd58-e7e2-46d0-9dfe-a153848e0d45
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: bcb05ed5-9d44-4628-be3d-684beac42b73
type: NOT_DETECTED
created_at: 2026-03-22 21:08:14
context:
Memory A describes the social networking feed and timeline interface, while Memory B focuses on the creation and leveling mechanics of AI Spirits. There is no meaningful functional or semantic overlap between these two distinct system components.


id: 3097c7d1-f195-4656-927a-c791bac74959
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
type: NOT_DETECTED
created_at: 2026-03-22 21:08:51
context:
Memory A focuses on the social feed and broadcasting system (CQ Feed), while Memory B focuses on AI companion management (Spirits). While both are features of the CitadelQuest platform, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: 958f2d3b-5fa8-490d-a0e9-ed8717f2f452
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
type: NOT_DETECTED
created_at: 2026-03-22 21:09:20
context:
Memory A describes the social networking and feed management features of the platform, while Memory B describes the AI Spirit's memory and interaction history. While both are part of the same platform (CitadelQuest), they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: 7a9cf239-f153-4dd8-80ea-dbe418094b4a
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: bcb05ed5-9d44-4628-be3d-684beac42b73
type: NOT_DETECTED
created_at: 2026-03-22 21:10:00
context:
Memory A focuses on the social networking and feed management features of the platform, while Memory B describes the AI Spirit creation and progression system. While both are part of the CitadelQuest platform, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: 83d5249f-84d6-4efd-8443-93c4f1eb42af
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
type: NOT_DETECTED
created_at: 2026-03-22 21:10:29
context:
Memory A describes the social feed and interaction system (reactions/comments), while Memory B describes the management of AI companions (Spirits). While both are components of the CitadelQuest platform, they describe distinct, non-overlapping functional modules with no direct semantic connection or conflict.


id: 637664d9-edd8-4a9c-b14b-b4c2970233b2
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: bcb05ed5-9d44-4628-be3d-684beac42b73
type: NOT_DETECTED
created_at: 2026-03-22 21:11:47
context:
Memory A describes the social feed and interaction mechanics (likes, comments) of the platform, while Memory B describes the AI Spirit creation and leveling system. While both are part of the CitadelQuest platform, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: 129bd3c3-d111-4051-bff5-81032ab62747
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
type: NOT_DETECTED
created_at: 2026-03-22 21:12:07
context:
Memory A focuses on the technical mechanics of a decentralized social feed (subscriptions, polling, and UI badges), while Memory B describes the AI companion system (Spirits). While both are components of the CitadelQuest ecosystem, they describe distinct functional modules with no direct semantic overlap or conflicting information.


id: 9740e91a-f9f0-4201-b803-dfd08adc0f16
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
type: NOT_DETECTED
created_at: 2026-03-22 21:12:18
context:
Memory A focuses on the decentralized social feed and subscription mechanics, while Memory B focuses on the management and progression of AI companions (Spirits). There is no meaningful functional or semantic overlap between these two distinct system modules.


id: bca3abe2-fa2f-4a8b-b418-59b73175fb33
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: c39275dc-8438-45f5-acca-639882d9ac61
type: NOT_DETECTED
created_at: 2026-03-22 21:12:31
context:
Memory A describes the social networking feed and subscription mechanics, while Memory B describes the AI Spirit configuration and profile settings. While both are parts of the CitadelQuest ecosystem, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: d8d80f13-2e13-4f7a-95be-d3bc34f5150f
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
type: NOT_DETECTED
created_at: 2026-03-22 21:12:59
context:
Memory A focuses on the social networking feed and real-time subscription mechanics, while Memory B focuses on AI Spirit management and memory visualization. While both are part of the CitadelQuest ecosystem, they describe distinct functional modules with no direct semantic overlap or conflicting information.


id: bf09286c-ac77-40bd-b3b8-2b0977de7726
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: 273a9c62-6d2f-4ae8-a817-d396fd5d0e28
type: NOT_DETECTED
created_at: 2026-03-22 21:13:29
context:
Memory A describes the CQ Feed social networking system and its subscription mechanics, while Memory B describes the Spirit Chat AI interface. Although both are components of the CitadelQuest ecosystem, they describe distinct, non-overlapping functional modules (social feed vs. AI chat) with no direct semantic or functional interaction mentioned.


id: 866db639-305f-4426-a24a-cb8674260fd8
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: f53218b5-f2aa-4adb-902c-e88a44f11e67
type: NOT_DETECTED
created_at: 2026-03-22 21:13:59
context:
Memory A describes the social networking feed and subscription mechanics of the platform, while Memory B details the AI Spirit's functional tools and capabilities. While both are part of the same user manual, they describe distinct, non-overlapping systems (social UI vs. AI backend tools) with no direct functional or semantic link.


id: aa004d9e-6b80-496a-bb13-d92149973b2a
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: bcb05ed5-9d44-4628-be3d-684beac42b73
type: NOT_DETECTED
created_at: 2026-03-22 21:14:11
context:
Memory A focuses on the social networking feed and subscription mechanics, while Memory B details AI Spirit creation and leveling systems. There is no meaningful functional or semantic overlap between these two distinct platform features.


id: 022128c6-b29a-4e4f-9eb4-5135897765ba
source_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
target_id: 49196b83-0bc8-49c0-a5cb-2b991d57e65c
type: NOT_DETECTED
created_at: 2026-03-22 21:14:34
context:
Memory A describes the technical federation protocol and decentralized architecture of a social feed, while Memory B describes the conceptual and functional overview of AI companions (Spirits). While both are part of the CitadelQuest ecosystem, they describe distinct, non-overlapping systems with no direct functional or semantic link.


id: a1d5dbba-5c3e-4551-a665-0cd8ea528f09
source_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
target_id: aef300c2-1723-48a7-9ab4-b83c9342ef57
type: NOT_DETECTED
created_at: 2026-03-22 21:14:49
context:
Memory A focuses on the technical federation protocol and decentralized architecture of the social feed (CQ Feed), while Memory B focuses on the management and UI of AI companions (Spirits). While both are components of the CitadelQuest ecosystem, they describe entirely different systems with no functional or semantic overlap.


id: 7a414878-9ac7-432a-850f-cbf830794f3e
source_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
target_id: bcb05ed5-9d44-4628-be3d-684beac42b73
type: NOT_DETECTED
created_at: 2026-03-22 21:15:40
context:
Memory A describes the technical federation and data sovereignty of a social feed system, while Memory B describes the gamified progression and creation of AI Spirits. There is no meaningful semantic or functional overlap between the decentralized networking protocol and the AI leveling system.


id: bc861e73-73c5-499f-9788-b5bb04deb134
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
type: NOT_DETECTED
created_at: 2026-03-22 21:16:01
context:
Memory A describes the CQ Feed social networking platform, while Memory B describes the AI onboarding and Spirit setup process. While both are parts of the CitadelQuest ecosystem, they describe distinct, unrelated features with no functional or semantic overlap.


id: 6e4e028a-b28e-4284-ad5e-0ae36cf29835
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: NOT_DETECTED
created_at: 2026-03-22 21:16:12
context:
Memory A describes the decentralized social networking features (CQ Feed), while Memory B focuses on the initial registration, onboarding process, and language settings. While both are part of the same user manual, they cover distinct functional areas with no direct semantic overlap or conflicting information.


id: 4b6db8de-cc58-4b99-96ed-55166ea40a22
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
type: NOT_DETECTED
created_at: 2026-03-22 21:16:49
context:
Memory A describes the social feed and timeline functionality, while Memory B describes the initial onboarding process for AI and Spirit setup. While both are parts of the same user manual, they describe distinct, unrelated features of the platform with no functional or semantic overlap.


id: 0577bd2c-10c6-40fd-a8da-ff31d1cf84d8
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
type: NOT_DETECTED
created_at: 2026-03-22 21:17:28
context:
Memory A focuses on the social feed and broadcasting features of the platform, while Memory B describes the initial onboarding wizard for AI and Spirit setup. While both are sections of the same user manual, they describe distinct, unrelated functional modules with no semantic overlap or dependency.


id: 326cb38a-da17-4eb0-a03b-6c44d8ae4f1d
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: NOT_DETECTED
created_at: 2026-03-22 21:17:43
context:
While both memories are sections of the same user manual, they describe distinct, unrelated features (social feed management vs. onboarding/language settings) with no functional or semantic overlap.


id: 4e209689-ae1a-4633-a247-9c5d0d1ba0ec
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
type: NOT_DETECTED
created_at: 2026-03-22 21:18:20
context:
Memory A describes the social feed and interaction mechanics (reactions/comments), while Memory B describes the initial onboarding process and AI Spirit setup. While both are parts of the same user manual, they describe distinct, non-overlapping functional modules with no direct semantic connection or dependency.


id: ac8d406e-3019-4ae4-a5c5-8de1f2f25fd4
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: NOT_DETECTED
created_at: 2026-03-22 21:18:39
context:
Memory A describes the social feed and interaction mechanics (reactions/comments), while Memory B describes the onboarding flow and language settings. While both are sections of the same User Manual, they cover distinct, unrelated functional areas of the platform with no semantic overlap or logical dependency.


id: 0727ca47-fab2-4232-849a-066e43f32ab1
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
type: NOT_DETECTED
created_at: 2026-03-22 21:19:13
context:
Memory A describes the technical mechanics of a social feed system (subscriptions, polling, and UI badges), while Memory B describes the initial onboarding process for AI services and Spirit creation. 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: 7926c7aa-9ea0-41c8-9c90-16f4413070e8
source_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
target_id: 624ac4e8-9af6-42b8-93fe-e514b7e7c1fc
type: NOT_DETECTED
created_at: 2026-03-22 21:19:41
context:
Memory A describes the technical architecture of a decentralized social feed (CQ Feed), while Memory B describes the initial user onboarding process for AI services and Spirit creation. While both are part of the CitadelQuest ecosystem, they describe distinct, unrelated functional modules with no overlapping logic or conflicting information.


id: 4a246c1e-cae1-4bca-a80a-4ebcf9930724
source_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: NOT_DETECTED
created_at: 2026-03-22 21:19:54
context:
Memory A focuses on the technical federation protocol and decentralized architecture of the CQ Feed, while Memory B describes the onboarding process and language settings. There is no meaningful semantic overlap or functional connection between these two specific system components.


id: fda3822e-202c-4d07-8c47-840e0f57d93e
source_id: 64ac3eb6-21a4-4540-8226-ebdee187fd2a
target_id: 7d433200-f88c-450e-a2b5-f100e5a9a92c
type: RELATES_TO
created_at: 2026-03-22 21:21:13
context:
Memory B describes the navigation link (User Menu) that leads to the CQ Explorer detailed in Memory A


id: b68fa2db-2107-486a-ab74-d4dbba199e06
source_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
target_id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
type: RELATES_TO
created_at: 2026-03-22 21:30:02
context:
Both documents describe interconnected features of the CitadelQuest platform settings and social architecture.


id: 5e0ede17-40f5-4d0a-a585-502f8b0b1cef
source_id: 64ac3eb6-21a4-4540-8226-ebdee187fd2a
target_id: 39211a39-e63c-4aa3-8b92-677719c70de8
type: REINFORCES
created_at: 2026-03-22 21:35:17
context:
Both documents describe the same profile components (Spirit showcase, bio, tabs) from different perspectives


id: d7fe644e-9a76-407a-bc08-1d4164f36a43
source_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
target_id: 2aa531b7-b3e2-4bb2-b03b-5ef3226fbb44
type: REINFORCES
created_at: 2026-03-22 21:41:14
context:
Memory B provides the privacy controls and visibility settings for the CQ Contacts system in Memory A


id: 59905e44-bede-4cd3-88c3-42663e0b56fd
source_id: 1edffca9-3a49-4cea-ac1c-e0dab061c758
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 21:46:52
context:
Memory A describes the social networking interface (CQ Explorer), while Memory B describes the administrative update process. While both are part of the same user manual, they cover distinct, unrelated functional areas of the platform with no semantic overlap.


id: bbf1f000-a4cf-447c-90fa-ca1dbbd5ecda
source_id: 1edffca9-3a49-4cea-ac1c-e0dab061c758
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 21:47:16
context:
Memory A describes the social interaction interface (CQ Explorer), while Memory B describes administrative tools (Logs and Backups). They cover distinct functional areas of the platform with no overlapping logic, data, or conflicting information.


id: aa9354d7-0c83-4645-996a-eb16dabb54c0
source_id: 64ac3eb6-21a4-4540-8226-ebdee187fd2a
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 21:48:12
context:
Memory A focuses on social features and profile browsing (CQ Explorer), while Memory B focuses on administrative system updates and maintenance. There is no meaningful semantic or functional overlap between these two distinct modules of the application.


id: b91d51a5-f3a9-43ac-98d0-ceda3cdfac44
source_id: 64ac3eb6-21a4-4540-8226-ebdee187fd2a
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 21:48:44
context:
Memory A focuses on front-end user social interactions and profile browsing, while Memory B focuses on back-end administrative tasks like logs and backups. While both are part of the same user manual, they describe distinct, non-overlapping functional areas with no direct semantic connection.


id: 008f1b21-5c10-445d-82a2-ede6a503f0be
source_id: de076905-7921-4a20-bb33-c9638b69ef54
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 21:49:23
context:
Memory A describes the UI and social functionality of the sidebar, while Memory B describes administrative update procedures. They are distinct sections of a user manual with no functional or semantic overlap.


id: 3a026a6a-9cdf-42f2-bcd0-5d658f675c20
source_id: de076905-7921-4a20-bb33-c9638b69ef54
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 21:49:46
context:
Memory A describes the user-facing social sidebar interface, while Memory B describes administrative backend tools for logs and backups. There is no meaningful semantic or functional overlap between these two distinct parts of the system.


id: d5ffe7c7-ffcf-4442-944f-a78985dcb217
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: NOT_DETECTED
created_at: 2026-03-22 21:50:13
context:
Memory A focuses on the social 'CQ Follow' system for end-users, while Memory B focuses on the 'Admin Dashboard' for system administrators. While both are parts of the same user manual, they describe distinct functional areas (social interaction vs. system management) with no direct functional overlap or conflicting information.


id: dd7af6c0-a07a-4cb7-bee4-cb71f81e98ea
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-22 21:50:32
context:
Memory A describes a social networking feature (CQ Follow) for end-users, while Memory B describes administrative user management tools. There is no meaningful semantic overlap or functional connection between these two distinct modules of the platform.


id: e70d370f-1cbb-4d0c-ba05-8767a358ae09
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 21:50:49
context:
Memory A describes a social networking feature (CQ Follow), while Memory B describes technical administrative procedures for software updates. There is no meaningful semantic or functional connection between these two distinct parts of the user manual.


id: 73b3a42c-3c7b-487b-a643-1f652e694e1f
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 21:51:26
context:
Memory A describes a social networking feature (CQ Follow) for end-users, while Memory B describes administrative tools for server logs and backups. There is no meaningful semantic overlap or functional connection between these two distinct parts of the system manual.


id: b1d51d5a-4251-4d36-a9ee-65583c6760b5
source_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 21:52:13
context:
Memory A focuses on the social 'CQ Contacts' system and decentralized communication, while Memory B describes the technical administrative process for application updates. There is no meaningful semantic overlap or functional connection between these two distinct modules of the system.


id: 72ddbffb-9a8d-49f0-bf79-6df9e0b0c466
source_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 21:52:40
context:
Memory A focuses on the decentralized social networking and friend system (CQ Contacts), while Memory B focuses on administrative server management (Logs and Backups). While both are part of the CQ User Manual, they describe distinct, unrelated functional modules with no overlapping logic or conflicting information.


id: 4dff73ca-f352-460c-a6c1-cdf11b6c0353
source_id: ac5c0c9f-2ffd-4481-a45e-87881310440a
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: NOT_DETECTED
created_at: 2026-03-22 21:53:25
context:
Memory A focuses on social interactions, contact management, and decentralized data sharing between users, while Memory B focuses on internal administrative user management and system-level controls. While both involve 'users', they describe entirely different subsystems (social vs. administrative) with no functional overlap or conflict.


id: c19b3b67-18cd-4f31-aafd-7586925b2a82
source_id: ac5c0c9f-2ffd-4481-a45e-87881310440a
target_id: e233a100-5775-4040-a1b3-7b3fe93470da
type: NOT_DETECTED
created_at: 2026-03-22 21:53:37
context:
Memory A focuses on social interaction, contact management, and peer-to-peer data sharing, while Memory B focuses on administrative system updates and server maintenance. There is no meaningful semantic overlap or functional connection between these two distinct parts of the manual.


id: 3959ba1b-742c-42e9-aba4-e9081c82a1fc
source_id: ac5c0c9f-2ffd-4481-a45e-87881310440a
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-22 21:53:55
context:
Memory A focuses on user-level social interactions and decentralized data sharing (Memory Packs), 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 parts of the user manual.


id: 81e38e23-f6c2-4f4e-be21-cc537bf1f065
source_id: 1edffca9-3a49-4cea-ac1c-e0dab061c758
target_id: 02619512-3802-40c7-9fd4-13edfcdbf655
type: RELATES_TO
created_at: 2026-03-22 21:58:14
context:
Memory B describes content management that populates the CQ Explorer interface described in Memory A


id: 8ca79d20-234f-4ee8-aae5-9c9a2d846019
source_id: 64ac3eb6-21a4-4540-8226-ebdee187fd2a
target_id: 02619512-3802-40c7-9fd4-13edfcdbf655
type: RELATES_TO
created_at: 2026-03-22 22:00:45
context:
Memory A describes the viewer's experience of profiles, while Memory B explains how that content is managed.


id: 578f5c27-9267-461c-8ade-c45ecce1ea6c
source_id: 32d09012-3eaf-49b0-8726-915418d6dad1
target_id: 4c65b13b-e579-4e5b-99c1-8c216affde3b
type: REINFORCES
created_at: 2026-03-22 22:16:31
context:
Memory B provides the technical implementation details for the sharing features mentioned in Memory A


id: 2438ce74-8345-4b23-bf56-a0c6c6fefa52
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
type: REINFORCES
created_at: 2026-03-22 22:20:22
context:
Both memories confirm the use of the CitadelQuest Federation protocol for cross-instance communication


id: 7f752700-1776-44b7-ae39-382f7496e511
source_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
target_id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
type: REINFORCES
created_at: 2026-03-22 22:21:25
context:
Memory B confirms the technical implementation of the API keys and HTTPS channel defined in Memory A


id: 55ee916d-773d-47e4-bd1f-ba56d3d7bafa
source_id: de076905-7921-4a20-bb33-c9638b69ef54
target_id: d68be241-4b63-4c48-8309-69a2950cf0af
type: NOT_DETECTED
created_at: 2026-03-22 22:26:32
context:
Memory A focuses on the social sidebar and contact management interface, while Memory B focuses on mobile responsiveness and storage architecture for the file browser. While both are part of the same user manual, they describe distinct functional modules with no direct semantic overlap or conflicting information.


id: a6c0207a-27e1-4673-ac6a-195d52eae258
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: 697c5176-557a-4939-bbbd-f565956940af
type: NOT_DETECTED
created_at: 2026-03-22 22:26:53
context:
Memory A describes a social subscription system (CQ Follow), while Memory B describes file management interface modes (Tree View/File Preview). They are distinct functional modules of the same platform with no direct semantic overlap or conflicting information.


id: 86ece9f6-9d3c-46b8-84bb-67a4c643249f
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: d68be241-4b63-4c48-8309-69a2950cf0af
type: NOT_DETECTED
created_at: 2026-03-22 22:27:23
context:
Memory A describes the social subscription and notification system (CQ Follow), while Memory B focuses on mobile responsiveness and the storage architecture of the File Browser. While both are parts of the CitadelQuest User Manual, they describe distinct, unrelated functional modules with no overlapping logic or conflicting information.


id: b131bd1e-d0c8-4c8d-b0f3-9616e7df5344
source_id: 1edffca9-3a49-4cea-ac1c-e0dab061c758
target_id: df4f6b2b-ec31-4523-a509-90382945cc1d
type: RELATES_TO
created_at: 2026-03-22 22:31:00
context:
Both are core CitadelQuest modules; CQ Explorer facilitates sharing the Memory Packs created in CQ Memory.


id: d23047c8-f7b4-4001-9a1a-40c8a5cf9f9d
source_id: 64ac3eb6-21a4-4540-8226-ebdee187fd2a
target_id: e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7
type: RELATES_TO
created_at: 2026-03-22 22:33:38
context:
Memory A describes browsing Memory Packs on profiles; Memory B describes the interface to manage them


id: a3e7a45a-8f57-42fb-9d9f-dadc31dc97e5
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: e9b83b50-ce81-4148-9f3d-6c9786fe989e
type: RELATES_TO
created_at: 2026-03-22 22:37:12
context:
Memory B describes the extraction process for Memory Packs, which Memory A mentions as downloadable.


id: 729efe51-f91e-4c9e-ba6a-2daa861fbed5
source_id: ac5c0c9f-2ffd-4481-a45e-87881310440a
target_id: d53d081b-6f67-4155-8069-711b2449468c
type: REINFORCES
created_at: 2026-03-22 22:41:35
context:
Memory A describes the sharing/syncing of .cqmpack files; Memory B explains their internal structure.


id: b7b45d9d-84b1-4649-a985-2d82122f3df4
source_id: de076905-7921-4a20-bb33-c9638b69ef54
target_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
type: NOT_DETECTED
created_at: 2026-03-22 22:47:01
context:
Memory A describes the UI and social connection logic of the CQ Contacts sidebar, while Memory B describes the AI Spirit's memory management and interaction history. While both are parts of the CitadelQuest manual, they describe distinct, non-overlapping functional modules (Social vs. AI Management) with no direct semantic link or dependency.


id: 42c39632-59cf-452c-92ef-5850f8672f98
source_id: de076905-7921-4a20-bb33-c9638b69ef54
target_id: bcb05ed5-9d44-4628-be3d-684beac42b73
type: NOT_DETECTED
created_at: 2026-03-22 22:47:50
context:
Memory A describes the UI sidebar for social connection management (Contacts/Followers), while Memory B describes the creation and leveling mechanics of AI Spirits. There is no meaningful functional or semantic overlap between these two distinct system modules.


id: 1080fb9a-c41c-4118-a5e0-7a1633136a00
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
type: NOT_DETECTED
created_at: 2026-03-22 22:49:04
context:
Memory A describes the social 'CQ Follow' system for user-to-user interaction, while Memory B describes the 'Memory and Interaction History' for user-to-AI Spirit management. While both are features of the CitadelQuest platform, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: da816d4b-1fdd-4f34-935b-8f606df7d103
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: bcb05ed5-9d44-4628-be3d-684beac42b73
type: NOT_DETECTED
created_at: 2026-03-22 22:49:33
context:
Memory A describes the social networking and subscription features (CQ Follow), while Memory B focuses on the creation and progression of AI companions (Spirits). While both are components of the CitadelQuest platform, they describe distinct systems with no functional or semantic overlap.


id: a9e0edff-77e4-4de5-b810-100dc94736bf
source_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
target_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
type: NOT_DETECTED
created_at: 2026-03-22 22:50:41
context:
Memory A describes the social networking and friend system (CQ Contacts), while Memory B describes the AI companion management and memory visualization features (Spirits). While both are components of the CitadelQuest platform, they describe distinct, non-overlapping systems with no direct functional or semantic connection.


id: d6f66ec6-5d55-4aea-836c-4bc2e431bff0
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: NOT_DETECTED
created_at: 2026-03-22 22:56:57
context:
Memory A describes the social subscription and notification system (CQ Follow), while Memory B details the post-onboarding flow and language settings. While both are parts of the same user manual, they describe distinct, unrelated functional areas of the platform with no semantic overlap.


id: 53e2cfeb-7bd6-4ba9-a812-9f463c36bfb2
source_id: 35a7a1f8-1d24-441f-98ed-8710ced05a8a
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: NOT_DETECTED
created_at: 2026-03-22 22:57:53
context:
Memory A describes the technical specifications of the decentralized friend system (CQ Contacts), while Memory B focuses on the initial onboarding steps and language settings. While both are part of the same user manual, they cover distinct, non-overlapping functional areas of the platform with no direct semantic or logical dependency.


id: 016f6bc3-f919-47cd-a906-2119cb4321b9
source_id: ac5c0c9f-2ffd-4481-a45e-87881310440a
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: NOT_DETECTED
created_at: 2026-03-22 22:58:57
context:
Memory A focuses on social interaction, contact management, and data sharing protocols, while Memory B covers the initial onboarding process and language settings. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: 089d8c5f-0192-4d0a-a9e5-bcb7188d2030
source_id: 32d09012-3eaf-49b0-8726-915418d6dad1
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: NOT_DETECTED
created_at: 2026-03-22 22:59:52
context:
Memory A focuses on the technical specifications of the decentralized federation protocol and social networking mechanics, while Memory B details the initial onboarding flow and UI language settings. There is no meaningful semantic overlap or functional dependency between these two distinct parts of the user manual.


id: c97c7bc0-8922-4c6c-8ce0-b57c4b4057b2
source_id: 897390d1-2ec0-45f9-a740-5bff0bc0232b
target_id: 6b9619cb-e8e6-492f-8942-29ce08a329e3
type: RELATES_TO
created_at: 2026-03-22 23:00:38
context:
Memory A describes the Dashboard notification for the CQ Feed, which Memory B explains how to manage


id: a9c83656-533e-4898-864c-1af97f04346d
source_id: 7d433200-f88c-450e-a2b5-f100e5a9a92c
target_id: f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8
type: REINFORCES
created_at: 2026-03-22 23:25:56
context:
Memory B confirms the 'unseen count' and dropdown access mentioned in Memory A's nav bar description


id: b2dd57bc-096e-4993-a737-bbaa966decc5
source_id: 7d433200-f88c-450e-a2b5-f100e5a9a92c
target_id: c39275dc-8438-45f5-acca-639882d9ac61
type: RELATES_TO
created_at: 2026-03-23 00:02:41
context:
Memory A describes the navigation path (Spirit Icon) to reach the Spirit Profile detailed in Memory B


id: 9011c969-1195-443e-8658-4345501408e8
source_id: ada32b14-6f87-4f53-98cf-977cf80f006c
target_id: 56d69ed3-d0f5-414c-b07d-a3ad52e09863
type: REINFORCES
created_at: 2026-03-23 00:04:54
context:
Both memories confirm the Dashboard as the central hub and the availability of EN, CZ, and SK languages.


id: 8a0e56c3-4c46-446c-9f33-2dac024db012
source_id: 8a1c5fe3-c932-4def-bfd8-ad1667b9c37e
target_id: 578f8d7a-428b-476d-bec9-02fb4f313fb7
type: REINFORCES
created_at: 2026-03-23 00:08:51
context:
Memory A provides technical implementation details for the high-level features described in Memory B


id: b66f08a7-9ee7-4447-8823-41c6d1dadbb7
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: f02102d6-abdf-4cef-bc2f-ddc1876aaccb
type: RELATES_TO
created_at: 2026-03-23 00:17:09
context:
Memory B details specific profile customization features managed within the settings hub in Memory A


id: 56ea2ab0-5fcd-4d75-a487-e793b763682d
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: fe4eef3d-8d4f-4188-986c-39a43ca9913b
type: RELATES_TO
created_at: 2026-03-23 00:27:15
context:
Both documents describe primary navigation hubs (/settings vs /administration) for platform management


id: 14ea4608-2fb6-4153-9b45-4415cbe09260
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: e3bcb9b7-f7cb-48b2-b798-50ecd96d781c
type: RELATES_TO
created_at: 2026-03-23 00:27:26
context:
Both documents describe account management, distinguishing between user-level and admin-level actions


id: 57d4422e-01b2-4c75-9c2e-0667ac8fb5b5
source_id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: NOT_DETECTED
created_at: 2026-03-23 00:34:49
context:
Memory A focuses on AI service configuration and financial management of API credits, while Memory B focuses on the lifecycle and maintenance of shared content. 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: e2187465-9646-44f2-9ddd-ac1a80c8dfb4
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: 93773695-e3ff-4eb0-be79-8ffa69bfc7d6
type: RELATES_TO
created_at: 2026-03-23 00:47:41
context:
Settings manages profile content and feed subscriptions which display the shares created in CQ Share


id: 9c895a25-ac5e-4beb-b2f3-53191377f75b
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: RELATES_TO
created_at: 2026-03-23 00:49:04
context:
Memory B details a specific feature (Share Groups) managed within the Settings page described in Memory A


id: 0c44bf96-5b7b-4926-9ac6-d627af1c1cb3
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
type: NOT_DETECTED
created_at: 2026-03-23 01:05:44
context:
Memory A discusses account migration and server transfer procedures, while Memory B describes the user interface for the chat system. While both are part of the CQ User Manual, they cover distinct functional areas (Settings vs. Chat) with no direct semantic overlap, reinforcement, or contradiction.


id: 9b124f93-1b58-4fad-8504-113eb2f7a617
source_id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
target_id: 697c5176-557a-4939-bbbd-f565956940af
type: NOT_DETECTED
created_at: 2026-03-23 01:06:46
context:
Memory A focuses on AI service configurations and credit management, while Memory B describes the file browser interface and navigation modes. While both are part of the same user manual, they describe distinct, unrelated functional modules of the platform with no semantic overlap.


id: ae04a7cb-4f26-4c43-afa9-fc38cfbb15b3
source_id: 6b9619cb-e8e6-492f-8942-29ce08a329e3
target_id: 697c5176-557a-4939-bbbd-f565956940af
type: NOT_DETECTED
created_at: 2026-03-23 01:09:45
context:
Memory A describes the CQ Feed Management system for social content, while Memory B describes the File Browser interface and navigation. While both are parts of the same user manual, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: da1ad233-b208-484f-92cd-66df5e31f6fe
source_id: 6b9619cb-e8e6-492f-8942-29ce08a329e3
target_id: d68be241-4b63-4c48-8309-69a2950cf0af
type: NOT_DETECTED
created_at: 2026-03-23 01:10:32
context:
Memory A focuses on social feed management and subscription settings, while Memory B focuses on mobile responsiveness and the file storage architecture. While both are sections of the same user manual, they describe distinct, non-overlapping functional modules (Social vs. File System) with no direct semantic or logical dependency.


id: 44115e4c-5c89-4284-9615-6feaad7f9211
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: 697c5176-557a-4939-bbbd-f565956940af
type: NOT_DETECTED
created_at: 2026-03-23 01:15:44
context:
Memory A focuses on the backend administrative process of account migration and server transfers, while Memory B describes the frontend UI navigation and file management within the file browser. While both are part of the same user manual, they describe distinct, unrelated features with no functional or semantic overlap.


id: 01656b17-c335-49a4-84d4-1e07c661ed5e
source_id: 6b9619cb-e8e6-492f-8942-29ce08a329e3
target_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
type: RELATES_TO
created_at: 2026-03-23 01:23:45
context:
Memory A details the feed infrastructure used to distribute the knowledge types described in Memory B


id: cb504bfc-c52a-4887-a5ac-3a9fad38b04c
source_id: 70701b55-4255-46a9-9cb8-64f779221e21
target_id: b7adbc37-239e-41fc-917c-62b612be0cf6
type: RELATES_TO
created_at: 2026-03-23 01:30:12
context:
Both documents describe core UI components and technical management within the CitadelQuest platform


id: 899a4630-1c73-4fdf-86a9-a3f373bf2cf7
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: b7adbc37-239e-41fc-917c-62b612be0cf6
type: NOT_DETECTED
created_at: 2026-03-23 01:32:25
context:
Memory A focuses on account migration and server transfer procedures, while Memory B describes memory analysis and knowledge graph visualization. Although both are sections of a user manual, they describe distinct, unrelated functional areas of the platform with no semantic overlap.


id: 85e0bd4c-e9c7-41d7-82c2-4f463ce083bc
source_id: 6b9619cb-e8e6-492f-8942-29ce08a329e3
target_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
type: NOT_DETECTED
created_at: 2026-03-23 01:37:15
context:
Memory A focuses on feed management and social federation settings, while Memory B focuses on AI Spirit memory and interaction history. While both are parts of the same user manual, they describe distinct, unrelated functional modules (Social/Feeds vs. AI/Memory) with no direct semantic overlap or conflict.


id: 6cee3868-9ba1-4e26-91c0-3b6d7b18dc99
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: 10512eb2-de99-45b3-b749-a8db5f5e9379
type: NOT_DETECTED
created_at: 2026-03-23 01:45:01
context:
Memory A focuses on the technical procedure for account migration between servers, while Memory B describes the memory management and interaction history features of AI Spirits. While both are part of the same user manual, they describe distinct, unrelated functional areas of the platform.


id: b1a7701b-c38c-4f36-901e-094653e7b44c
source_id: 0034ac96-db9c-433b-891c-dc86f489a2e4
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-23 01:55:22
context:
Memory A focuses on user-level profile customization and media management, while Memory B focuses on system-level administrative tasks like logs and backups. While both are sections of the same user manual, they describe distinct functional areas with no direct semantic overlap or dependency.


id: c17d882e-faa2-4f11-8e27-1856f5466008
source_id: 63482038-a160-4154-8a9e-9555c065a606
target_id: 485942bf-31ec-4d61-9bc2-b3f9777e1844
type: NOT_DETECTED
created_at: 2026-03-23 01:56:27
context:
Memory A focuses on user-facing profile features and AI companion displays, while Memory B focuses on backend administrative tools like logs and backups. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: b9489875-552c-4331-869e-9a488cc05caf
source_id: 39211a39-e63c-4aa3-8b92-677719c70de8
target_id: d92f6c51-6e01-479d-83ca-d660824e27b7
type: REINFORCES
created_at: 2026-03-23 02:03:24
context:
Memory B provides the configuration details for content displayed on the profile described in Memory A


id: b884ad34-6780-44fa-ab69-2827517f5146
source_id: 39211a39-e63c-4aa3-8b92-677719c70de8
target_id: 8e27dea4-f026-4ea9-80ac-c4a850cc64c2
type: REINFORCES
created_at: 2026-03-23 02:04:01
context:
Memory B provides the specific implementation details for the 'Profile Content' mentioned in Memory A


id: 48769b60-fd7b-4f51-8f9a-ab5d5f22d044
source_id: 39211a39-e63c-4aa3-8b92-677719c70de8
target_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
type: REINFORCES
created_at: 2026-03-23 02:30:06
context:
Memory B provides the technical implementation details for the 'Profile Content' mentioned in Memory A


id: 7750b7ad-83d3-4983-a148-d4aaac77b3e3
source_id: 39211a39-e63c-4aa3-8b92-677719c70de8
target_id: 02619512-3802-40c7-9fd4-13edfcdbf655
type: RELATES_TO
created_at: 2026-03-23 02:30:22
context:
Memory B manages the lifecycle of shared items that are displayed on the profile described in Memory A


id: 07df1d4e-144d-4fe3-8632-cfd9a82cba88
source_id: 39211a39-e63c-4aa3-8b92-677719c70de8
target_id: ff9a208f-151d-43df-9869-4df9f9dd2f1a
type: REINFORCES
created_at: 2026-03-23 02:32:02
context:
Memory B explains the management of shared items that populate the profile tabs described in Memory A


id: 2d3fa4a7-9b5b-45ac-8943-65f523dec357
source_id: 2aa531b7-b3e2-4bb2-b03b-5ef3226fbb44
target_id: 4d8a2d04-0376-4274-818b-160b12166db4
type: REINFORCES
created_at: 2026-03-23 02:34:03
context:
Memory B provides the functional implementation details for the 'content groups' mentioned in Memory A


id: b9164941-f47e-489a-915a-b263e76837b0
source_id: 786911a0-c1b1-4e4b-8d1f-7ea3d33e7d3d
target_id: a4102387-181b-467a-9de7-edeb48f554e0
type: REINFORCES
created_at: 2026-03-23 02:42:13
context:
Memory B provides the specific display and URL mechanics for the 'Share Groups' mentioned in Memory A


id: d98addff-944f-41b4-95b3-573c3ca08730
source_id: 786911a0-c1b1-4e4b-8d1f-7ea3d33e7d3d
target_id: 6da2a708-27d5-48a6-b43a-18ca0e7749c6
type: REINFORCES
created_at: 2026-03-23 02:42:47
context:
Memory B provides the functional implementation details for the 'Share Groups' mentioned in Memory A


id: d21977c2-7b8c-46c0-978a-9427a6bb6dd5
source_id: 2aa531b7-b3e2-4bb2-b03b-5ef3226fbb44
target_id: 34ad3ed6-59be-4d32-9cd0-792bd512d00c
type: REINFORCES
created_at: 2026-03-23 02:52:44
context:
Both documents describe the Federation protocol's role in data sovereignty and cross-instance communication.


id: 76acdc11-b712-415d-a5dc-c7e1bdf5923d
source_id: 0034ac96-db9c-433b-891c-dc86f489a2e4
target_id: ff4b2e53-5fdb-49c7-a205-48817beab2ff
type: RELATES_TO
created_at: 2026-03-23 02:53:10
context:
Profile photos and bios from Memory A are displayed within the CQ Chat interface described in Memory B


id: 8c674abb-9f0a-4b0a-a35d-a49376802711
source_id: f02102d6-abdf-4cef-bc2f-ddc1876aaccb
target_id: d68be241-4b63-4c48-8309-69a2950cf0af
type: NOT_DETECTED
created_at: 2026-03-23 03:04:26
context:
While both memories are sections of the same user manual, they describe distinct, non-overlapping features: public profile visual customization versus mobile file browser storage architecture. There is no direct functional or semantic dependency between them.


id: 6a93ae37-dd7b-409b-83e2-2ab9eb757917
source_id: 2aa531b7-b3e2-4bb2-b03b-5ef3226fbb44
target_id: 972d7c0c-cdbe-4a67-832d-e5a48187bf4c
type: RELATES_TO
created_at: 2026-03-23 03:11:02
context:
Memory A details profile visibility settings used to share the knowledge graphs described in Memory B


id: 0b80703e-7379-43da-ac04-96178abfed49
source_id: 63482038-a160-4154-8a9e-9555c065a606
target_id: d53d081b-6f67-4155-8069-711b2449468c
type: RELATES_TO
created_at: 2026-03-23 03:14:44
context:
Both describe CitadelQuest Spirit features: Memory B covers backend recall, Memory A covers profile display.


id: d4d2d215-41d3-473a-8d82-dc80659a19b6
source_id: f02102d6-abdf-4cef-bc2f-ddc1876aaccb
target_id: b7adbc37-239e-41fc-917c-62b612be0cf6
type: NOT_DETECTED
created_at: 2026-03-23 03:18:00
context:
Memory A focuses on visual customization and themes for a user's public profile page, while Memory B describes the technical processes of memory analysis and relationship discovery within the knowledge management system. There is no meaningful semantic or functional overlap between these two distinct features of the application.


id: 6b2712d5-28e6-4ed2-b2f9-f7e09cdb706b
source_id: 786911a0-c1b1-4e4b-8d1f-7ea3d33e7d3d
target_id: c39275dc-8438-45f5-acca-639882d9ac61
type: RELATES_TO
created_at: 2026-03-23 03:28:26
context:
Memory A defines how Spirits are displayed on public profiles, while Memory B defines Spirit configuration.


id: 8fc79e59-e2a5-409d-b3bc-0ba6f8415cc6
source_id: 786911a0-c1b1-4e4b-8d1f-7ea3d33e7d3d
target_id: bcb05ed5-9d44-4628-be3d-684beac42b73
type: RELATES_TO
created_at: 2026-03-23 03:29:00
context:
Memory A describes the public display of Spirits, while Memory B explains their creation and growth.


id: 33ec3b85-50c4-4a14-b447-654ea466241d
source_id: 8e8c46f6-5820-4625-9ac7-04285b2f394f
target_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
type: REINFORCES
created_at: 2026-03-23 03:46:15
context:
Memory B provides technical implementation details for the 3D knowledge graphs mentioned in Memory A


id: f0168217-c856-4914-bc1a-4a8dde223cfc
source_id: 307ef895-4d2e-4253-8293-02187da0badf
target_id: c2108434-8b74-46a0-845d-5abb287a9cec
type: REINFORCES
created_at: 2026-03-23 03:46:43
context:
Memory B provides technical detail on the 'CQ Memory' and 'CQ Share' features introduced in Memory A


id: 4c198936-5339-4ab1-81de-1712b98a734b
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: c455066a-fe9b-432a-a598-b9116b4715c8
type: REINFORCES
created_at: 2026-03-23 03:50:21
context:
Memory B confirms the configuration and management interface for the social feeds described in Memory A


id: 1739ecbb-fe76-440e-9f28-12cc5138edb9
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: RELATES_TO
created_at: 2026-03-23 03:54:14
context:
Both describe decentralized sharing features (CQ Feed vs CQ Share) within the CitadelQuest ecosystem


id: 2637f871-31ae-4da0-897a-4ab02229504b
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: 033b4c10-b865-4082-b222-2b80e3325247
type: RELATES_TO
created_at: 2026-03-23 03:55:26
context:
Both modules utilize the 'Public' and 'CQ Contacts' visibility scopes and integrate with CQ Explorer


id: 0a0d3525-0d32-489e-a52a-affb30166b79
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-23 03:57:17
context:
While both memories are sections of the CitadelQuest User Manual, they describe distinct and unrelated features: Memory A focuses on social interactions (reactions/comments) within the CQ Feed, while Memory B focuses on file sharing and search functionality within CQ Share. There is no functional or semantic overlap between the two.


id: 3c847cc2-aa00-42c3-8f21-d50606a0af6d
source_id: ebfa0295-84e3-4e22-b39c-d2074b1a6521
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:00:39
context:
Memory A describes a decentralized social networking platform (CQ Feed), while Memory B describes a knowledge management and 3D graph system (CQ Memory). While both are components of the CitadelQuest ecosystem, they describe distinct functional modules with no direct semantic overlap or logical dependency in the provided content.


id: 3082d122-75ff-4ee5-9e22-be4ab4eece27
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: c2108434-8b74-46a0-845d-5abb287a9cec
type: NOT_DETECTED
created_at: 2026-03-23 04:01:12
context:
Memory A describes the user interface and functionality of a social feed (CQ Feed), while Memory B describes the technical structure of knowledge management files (.cqmpack). While both are components of the CitadelQuest ecosystem, they describe distinct features with no direct functional or semantic overlap.


id: 4401ac6a-6dcf-49be-b453-6c7975cb2a00
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:01:44
context:
Memory A describes the user interface and functionality of a social feed (CQ Feed), while Memory B describes the technical structure of a knowledge management system (CQ Memory). While both are components of the CitadelQuest ecosystem, they describe distinct features with no semantic overlap or functional dependency.


id: 32a44ae9-1dab-41e8-80eb-91011a29923c
source_id: cef60805-5ad9-4f33-a8b7-14c43569b589
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:02:15
context:
Memory A describes the user interface and functionality of a social feed (CQ Feed), while Memory B describes the technical categorization of data relationships within a knowledge management system (CQ Memory). While both are part of the CitadelQuest ecosystem, they describe distinct, unrelated features with no semantic overlap or logical connection.


id: 5ba6aabc-6e3a-417f-8415-0e4c8eb48ecd
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:02:37
context:
Memory A describes the social feed and broadcasting features of CitadelQuest, while Memory B describes the internal knowledge management and memory node structure. While both are components of the same platform, they describe distinct systems (social networking vs. data storage) with no direct semantic overlap or conflicting information.


id: 1e0e53b0-f6eb-4f8d-a96d-e875b18927af
source_id: 2c049ada-5de8-4c23-80be-48aeea1b7165
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:03:01
context:
Memory A describes the social feed and broadcasting features of CitadelQuest, while Memory B describes the knowledge management and relationship types within the CQ Memory system. While both are part of the same user manual, they describe distinct functional modules with no direct semantic overlap or conflict.


id: 1482450a-521a-4aa9-a2df-3a9d21135d33
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: c2108434-8b74-46a0-845d-5abb287a9cec
type: NOT_DETECTED
created_at: 2026-03-23 04:03:17
context:
Memory A describes the social interaction features (reactions/comments) of the CQ Feed, while Memory B describes the technical structure of Memory Packs for knowledge management. While both are part of the CitadelQuest platform, they describe distinct, unrelated subsystems with no functional or semantic overlap.


id: bba83eab-a3c4-4e47-9692-4aa9248edecd
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:03:24
context:
Memory A describes the social interaction features (reactions and comments) of the CQ Feed, while Memory B describes the technical structure of Memory Nodes within the CQ Memory system. While both are parts of the CitadelQuest ecosystem, they describe distinct functional modules with no direct semantic overlap or logical connection.


id: 02ef093b-d4af-41b3-b39b-4c221f46536a
source_id: ceb97a1e-c3df-4854-85a8-427546e5b6a3
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:03:58
context:
Memory A describes the social interaction features (reactions/comments) of the CQ Feed, while Memory B describes the technical relationship types used in the CQ Memory knowledge graph system. While both are part of the CitadelQuest platform, they describe distinct functional modules with no direct semantic overlap or conflict.


id: 1190bc1e-df2a-4d96-b7bf-475e8942f26b
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:04:29
context:
Memory A describes the technical mechanics of a social feed and subscription system, while Memory B describes the structural components of a knowledge management system. While both are part of the CitadelQuest ecosystem, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: bb880204-28f0-4ba6-8095-f6972202b8fc
source_id: ea8ceda3-6121-4082-9f7c-2e15f2e23828
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:04:53
context:
Memory A describes the mechanics of social media subscriptions and real-time UI updates in CQ Feed, while Memory B defines data relationship types for a 3D knowledge graph in CQ Memory. While both are part of the CitadelQuest ecosystem, they describe entirely different subsystems with no functional or semantic overlap.


id: c208cd9b-1fcd-42a3-9cd0-42a4029de5b5
source_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:05:16
context:
Memory A describes the technical architecture of a decentralized social feed (CQ Feed), while Memory B defines the data structure of a knowledge management system (CQ Memory). While both are part of the CitadelQuest ecosystem, they describe distinct functional modules with no direct semantic overlap or conflicting information.


id: 71124002-d601-4322-9fcb-6b75513a17e3
source_id: 96428498-d67a-4e81-a9af-a5000a94ffd9
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:05:46
context:
Memory A describes the technical architecture of a decentralized social feed (CQ Feed), while Memory B defines data relationship types within a knowledge management system (CQ Memory). While both are components of the CitadelQuest ecosystem, they describe distinct functional modules with no direct semantic overlap or logical conflict.


id: 806f12be-cead-40d7-83fe-f4095af274ea
source_id: 64ac3eb6-21a4-4540-8226-ebdee187fd2a
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: REINFORCES
created_at: 2026-03-23 04:11:56
context:
Memory B explains the backend 'Share Groups' that create the tabbed navigation described in Memory A


id: 680b67d4-9a6a-499f-996f-ffde65db62d3
source_id: 1edffca9-3a49-4cea-ac1c-e0dab061c758
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:19:29
context:
Memory A describes the UI layout and social features of the CQ Explorer, while Memory B defines data relationship types for the CQ Memory system. While both are part of the same platform manual, they describe distinct functional modules (Social vs. Knowledge Management) with no direct semantic overlap or conflicting information.


id: 1af7cd1e-24da-4fc8-9446-41248be9b694
source_id: de076905-7921-4a20-bb33-c9638b69ef54
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:21:13
context:
Memory A describes the UI and functionality of the social sidebar (contacts/followers), while Memory B defines the technical structure of the memory node system. While both are part of the CitadelQuest User Manual, they describe distinct, unrelated features (Social UI vs. Data Architecture) with no functional or semantic overlap.


id: 41111ba6-107c-478c-84c5-aacfbc0e185e
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:22:16
context:
Memory A describes the social subscription system (CQ Follow), while Memory B defines the technical structure of a Memory Node. While both are part of the CitadelQuest platform, they describe distinct, unrelated subsystems with no semantic overlap.


id: 2173426c-7c00-433d-b14e-eb021100897d
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: 83873d3c-ac7d-4c56-b222-fd9ecb768d1d
type: NOT_DETECTED
created_at: 2026-03-23 04:22:26
context:
Memory A describes a social subscription system (CQ Follow), while Memory B describes the technical structure of a knowledge management system (Memory Nodes). While both are features of the CitadelQuest platform, they describe distinct functional domains (social vs. data structure) with no direct semantic overlap or functional dependency.


id: 4c9691e3-8554-4fac-960b-41cb06bc35e2
source_id: 8c1e0b5e-4a16-4767-ac68-cba62e55daaa
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:22:33
context:
Memory A describes a social subscription system (CQ Follow), while Memory B defines data relationship types for a knowledge management system (CQ Memory). Although both are part of the CitadelQuest platform, they describe distinct functional modules with no direct semantic overlap or logical interaction.


id: 85f73f98-0929-4708-bded-0047d97b0fe1
source_id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-23 04:33:31
context:
Memory A focuses on AI service configuration and gateway settings, while Memory B describes the search and sharing functionality for files and memory packs. While both are sections of the same user manual, they describe distinct, unrelated features of the platform with no functional or semantic overlap.


id: 7d56f2b4-25cb-4ab6-b432-2c425576de82
source_id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-23 04:34:03
context:
Memory A focuses on AI service configuration and gateway settings, while Memory B discusses the mechanisms for sharing files and knowledge packs. While both are sections of a user manual, they describe distinct, unrelated functional modules of the platform with no semantic overlap.


id: ba69cea4-153e-498e-9c60-90adeef109c2
source_id: 70701b55-4255-46a9-9cb8-64f779221e21
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-23 04:38:40
context:
Memory A focuses on user account settings, UI themes, and database optimization, while Memory B describes the process of sharing files and memory packs. While both are part of the same user manual, they cover distinct, non-overlapping functional areas of the platform with no direct semantic or logical connection.


id: 2046c52e-7837-40c9-900e-c374d052fa7d
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: 7aad6489-13dd-456e-8007-5a38afcbac2e
type: NOT_DETECTED
created_at: 2026-03-23 04:40:10
context:
Memory A details the account migration process between server instances, while Memory B describes the search and filter functionality for sharing files. While both are part of the CQ User Manual, they cover distinct, unrelated features (system administration vs. content sharing) with no functional or semantic overlap.


id: 4d844a11-eb64-439e-a100-5a4c0842b46b
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: a29723a7-9d66-433d-b3a3-a3b448dfc2e0
type: NOT_DETECTED
created_at: 2026-03-23 04:40:55
context:
Memory A focuses on the technical procedure for full account migration between servers, while Memory B describes the empty content of a document regarding file sharing methods. While both are part of the CQ User Manual, they cover distinct functional areas (Account Management vs. Content Sharing) with no direct semantic overlap or logical dependency.


id: 11393f87-c347-41c5-856c-b2699179eeee
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: d0105e38-e572-40e8-9841-f88321a97df3
type: NOT_DETECTED
created_at: 2026-03-23 04:41:03
context:
Memory A focuses on the administrative process of migrating an entire account between servers, while Memory B details the functionality of sharing specific files and memory packs with other users. While both are part of the CQ User Manual, they describe distinct, unrelated features (Account Migration vs. Content Sharing) with no functional or semantic overlap.


id: 6d269e83-a5af-4b91-81db-845d28316149
source_id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:41:32
context:
Memory A describes the configuration of AI models and billing settings, while Memory B defines the structural attributes of a Memory Node. While both are part of the CitadelQuest platform manual, they describe distinct, non-overlapping systems (AI services vs. memory storage architecture) with no direct semantic or functional link.


id: f8207459-3925-4fe5-882b-f665df7ec90d
source_id: 6318eec5-1bd0-47a2-aa53-cbe6cfce977b
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: RELATES_TO
created_at: 2026-03-23 04:42:18
context:
Both documents describe configuration and data management features within the CitadelQuest platform.


id: e9d2f0b0-7fd6-44c1-b31c-ebb677e8c3ce
source_id: 6b9619cb-e8e6-492f-8942-29ce08a329e3
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:43:56
context:
Memory A describes the CQ Feed Management system for social content streams, while Memory B describes the technical structure of the Memory Library system. While both are part of the same platform manual, they describe distinct, non-overlapping functional modules with no direct semantic connection.


id: 115eadb4-7f16-49ee-bd7d-a123f047c142
source_id: 6b9619cb-e8e6-492f-8942-29ce08a329e3
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:44:29
context:
Memory A describes the user interface and logic for feed management and social subscriptions, while Memory B describes the technical schema for knowledge graph relationships. There is no meaningful semantic overlap or logical connection between these two distinct system features.


id: 624c8aba-5457-489b-9620-30cb7c665356
source_id: 3fb33b70-55cf-4541-ad4d-f8da2b5e5ebd
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:45:21
context:
Memory A describes the UI navigation and configuration settings for the CitadelQuest platform, while Memory B defines the technical structure of the Memory Library system. While both are part of the same user manual, they describe distinct, non-overlapping functional areas (UI settings vs. data architecture) with no direct semantic connection or conflict.


id: a4de8cf7-b91b-433a-81fe-63c943d14933
source_id: 3fb33b70-55cf-4541-ad4d-f8da2b5e5ebd
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:45:35
context:
Memory A describes the UI navigation and settings categories for the CitadelQuest platform, while Memory B describes the technical data structure and visualization of the memory graph system. While both are part of the same user manual, they describe distinct functional areas (Settings vs. Memory Management) with no direct semantic overlap or conflicting information.


id: 403c84a7-59f7-4fac-9ca3-fd36a310602e
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:45:57
context:
While both memories are sections of the CitadelQuest User Manual, they describe distinct, non-overlapping systems: one focuses on the platform's global configuration and account settings, while the other defines the technical structure of the memory library system. There is no direct semantic or functional link between them.


id: 70a40ad4-859a-4b66-81e7-9e0bb3e34fc0
source_id: c455066a-fe9b-432a-a598-b9116b4715c8
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:46:25
context:
Memory A describes the platform's user settings and account management, while Memory B describes the technical schema for data relationships and the memory graph system. 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: 8f6cf414-c9cb-4f3f-8258-4c7f0e92b9e9
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:47:25
context:
Memory A describes the technical procedure for account migration between servers, while Memory B defines the data structure of a Memory Node within the knowledge management system. While both are part of the CQ User Manual, they describe distinct, unrelated features (server administration vs. data schema) with no functional or semantic overlap.


id: 7d1e5df0-fd1c-4f3b-9c8c-f2a9db75f3e7
source_id: 8c37fa16-08e6-4a68-858c-592164a4e3fb
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:47:54
context:
Memory A describes the technical procedure for migrating a user account between servers, while Memory B defines semantic relationship types for a knowledge graph system. There is no meaningful topical or functional overlap between account migration steps and data relationship definitions.


id: ad388433-7b69-4e8a-a52f-651728d4d2bd
source_id: 39211a39-e63c-4aa3-8b92-677719c70de8
target_id: 033b4c10-b865-4082-b222-2b80e3325247
type: RELATES_TO
created_at: 2026-03-23 04:49:31
context:
Memory B defines the sharing mechanism that populates the Profile Content tabs described in Memory A


id: ea309ed5-500d-4858-88a1-473316b03ffd
source_id: 2aa531b7-b3e2-4bb2-b03b-5ef3226fbb44
target_id: de432f8f-e033-4e6e-a579-b189ccd74095
type: REINFORCES
created_at: 2026-03-23 04:50:07
context:
Memory B's share groups and visibility scopes are managed and displayed via Memory A's profile settings.


id: e8e1076c-c8b7-4f62-90b4-5a6d110daa83
source_id: 39211a39-e63c-4aa3-8b92-677719c70de8
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:57:46
context:
Memory A describes the UI components and features of a user's public profile page, while Memory B defines technical relationship types for a knowledge management system. There is no meaningful semantic overlap or functional connection between these two distinct sections of the user manual.


id: 5ff9d71f-50a6-448c-8c53-89c9145b3213
source_id: 0034ac96-db9c-433b-891c-dc86f489a2e4
target_id: 84185171-3b5f-487e-b788-38c288c23e88
type: NOT_DETECTED
created_at: 2026-03-23 04:59:12
context:
Memory A describes user profile management (photos and bios) for social identity, while Memory B describes the technical structure of the Memory Library system. While both are part of the same user manual, they describe distinct, non-overlapping functional modules with no direct semantic or logical connection.


id: 119a1367-c4d4-4377-bc72-70b0e1330be5
source_id: 0034ac96-db9c-433b-891c-dc86f489a2e4
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 04:59:39
context:
Memory A describes user profile customization (photos and bios), while Memory B describes technical relationship types within a knowledge graph system. There is no meaningful semantic overlap or logical connection between these two distinct functional areas of the platform.


id: b9ba3724-8708-453b-ae6b-2ca3489e1784
source_id: 786911a0-c1b1-4e4b-8d1f-7ea3d33e7d3d
target_id: e70f4f2c-63c7-4af3-8110-b37bf4eaf28a
type: NOT_DETECTED
created_at: 2026-03-23 05:01:58
context:
Memory A describes user profile visibility settings and public page configuration, while Memory B defines data relationship types and the 3D knowledge graph system. There is no meaningful semantic overlap or logical connection between the specific content of these two manual sections.


# memory_jobs

id: 924d9573-db7b-4d7c-9681-1b6168e6314c
type: extract_recursive
status: completed
result: {"total_memories":6,"message":"Extraction complete. Created 6 memory nodes."}
created_at: 2026-03-12 13:07:52
started_at: 2026-03-12 13:07:52
completed_at: 2026-03-12 13:10:07
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:00-introduction.md","document_title":"00-introduction.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":6,"current_depth":1,"extracted_node_ids":["2e26f50c-1b09-45cf-9dab-b75f17751543","963a7c12-af9c-47b8-a07b-ff3ffda85b5a","29bcd0c6-5415-4c56-88ac-9767ae30613f","9ca0eb2f-81e3-4399-b87b-d82554e10d3d","f6fb3dc7-a6a9-4a25-89e5-f77f2b027ed8","fa80e472-490b-4a98-8c5b-5b49636606f7"],"skip_analysis":true,"last_step_request_at":1773321007,"root_node_id":"2e26f50c-1b09-45cf-9dab-b75f17751543","base_tag":"document","current_block_title":"About and Contact Information","step_locked_at":1773321007}


id: 3477b9c8-6828-494a-9359-642a5479d414
type: extract_recursive
status: completed
result: {"total_memories":4,"message":"Extraction complete. Created 4 memory nodes."}
created_at: 2026-03-12 13:11:07
started_at: 2026-03-12 13:11:07
completed_at: 2026-03-12 13:13:39
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:01-registration-and-onboarding.md","document_title":"01-registration-and-onboarding.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":4,"current_depth":1,"extracted_node_ids":["f080d9f1-7a52-443e-b81c-9bd0c76bd111","fd441b64-9557-464b-b15c-080626d39052","624ac4e8-9af6-42b8-93fe-e514b7e7c1fc","56d69ed3-d0f5-414c-b07d-a3ad52e09863"],"skip_analysis":true,"last_step_request_at":1773321219,"root_node_id":"f080d9f1-7a52-443e-b81c-9bd0c76bd111","base_tag":"document","current_block_title":"Post-Onboarding and Language Settings","step_locked_at":1773321219}


id: 5e3ffb43-cfd5-4cdc-8816-b3dea695f24a
type: extract_recursive
status: completed
result: {"total_memories":4,"message":"Extraction complete. Created 4 memory nodes."}
created_at: 2026-03-12 13:14:49
started_at: 2026-03-12 13:14:49
completed_at: 2026-03-12 13:16:21
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:02-dashboard.md","document_title":"02-dashboard.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":4,"current_depth":1,"extracted_node_ids":["376d5b05-c2e2-45a7-bd3d-0c59d8194d8e","9288785a-25bb-43c4-9354-57c2793a0520","16c4b69b-5492-4d20-801c-57c14dad4b53","9f82e1c9-cb91-4658-b5f7-8b2dd79dceb9"],"skip_analysis":true,"last_step_request_at":1773321381,"root_node_id":"376d5b05-c2e2-45a7-bd3d-0c59d8194d8e","base_tag":"document","current_block_title":"Top Navigation Bar","step_locked_at":1773321381}


id: 00240537-2eb1-42d6-869f-5835751eaaa6
type: extract_recursive
status: completed
result: {"total_memories":8,"message":"Extraction complete. Created 8 memory nodes."}
created_at: 2026-03-12 13:17:40
started_at: 2026-03-12 13:17:40
completed_at: 2026-03-12 13:20:40
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:03-spirits.md","document_title":"03-spirits.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":8,"current_depth":1,"extracted_node_ids":["85fb774c-e8e7-4611-91cd-44a19a072386","49196b83-0bc8-49c0-a5cb-2b991d57e65c","aef300c2-1723-48a7-9ab4-b83c9342ef57","c39275dc-8438-45f5-acca-639882d9ac61","10512eb2-de99-45b3-b749-a8db5f5e9379","273a9c62-6d2f-4ae8-a817-d396fd5d0e28","f53218b5-f2aa-4adb-902c-e88a44f11e67","bcb05ed5-9d44-4628-be3d-684beac42b73"],"skip_analysis":true,"last_step_request_at":1773321640,"root_node_id":"85fb774c-e8e7-4611-91cd-44a19a072386","base_tag":"document","current_block_title":"Spirit Creation and Progression","step_locked_at":1773321640}


id: c25bb668-88ff-4707-986a-b29ff382e2a9
type: extract_recursive
status: completed
result: {"total_memories":13,"message":"Extraction complete. Created 13 memory nodes."}
created_at: 2026-03-12 13:21:11
started_at: 2026-03-12 13:21:11
completed_at: 2026-03-12 13:27:18
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:04-cq-memory.md","document_title":"04-cq-memory.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":13,"current_depth":1,"extracted_node_ids":["a26434c2-2f0a-4a19-8851-8757e21ddbf1","df4f6b2b-ec31-4523-a509-90382945cc1d","981c25eb-0e25-4ef9-974b-e1c6b2cf98da","e7e9d105-0e1a-4c44-9f17-dbf2d3144ab7","e9b83b50-ce81-4148-9f3d-6c9786fe989e","b7adbc37-239e-41fc-917c-62b612be0cf6","d53d081b-6f67-4155-8069-711b2449468c","e6da62d1-5272-4316-8fa4-652f2a8ad291","972d7c0c-cdbe-4a67-832d-e5a48187bf4c","c2108434-8b74-46a0-845d-5abb287a9cec","84185171-3b5f-487e-b788-38c288c23e88","83873d3c-ac7d-4c56-b222-fd9ecb768d1d","e70f4f2c-63c7-4af3-8110-b37bf4eaf28a"],"skip_analysis":true,"last_step_request_at":1773322038,"root_node_id":"a26434c2-2f0a-4a19-8851-8757e21ddbf1","base_tag":"document","current_block_title":"Relationship Types","step_locked_at":1773322038}


id: d81ecdfe-8ad9-4ce8-a4eb-6470062c1adf
type: extract_recursive
status: completed
result: {"total_memories":6,"message":"Extraction complete. Created 6 memory nodes."}
created_at: 2026-03-12 13:32:42
started_at: 2026-03-12 13:32:42
completed_at: 2026-03-12 13:35:41
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:05-file-browser.md","document_title":"05-file-browser.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":6,"current_depth":1,"extracted_node_ids":["ac49a47f-9772-4591-932c-4504d4ce6a1b","9fc3589c-f983-4f00-8ed1-296e059d7fac","697c5176-557a-4939-bbbd-f565956940af","ff00df6c-c3e8-4a0d-8fb9-33ee914ccc57","e3a976b6-6989-4cf5-8a77-b1236d687cd1","d68be241-4b63-4c48-8309-69a2950cf0af"],"skip_analysis":true,"last_step_request_at":1773322541,"root_node_id":"ac49a47f-9772-4591-932c-4504d4ce6a1b","base_tag":"document","current_block_title":"Mobile Support and Storage Architecture","step_locked_at":1773322541}


id: 36864a9c-0513-437c-92f4-3853bccf642a
type: extract_recursive
status: completed
result: {"total_memories":5,"message":"Extraction complete. Created 5 memory nodes."}
created_at: 2026-03-12 13:36:18
started_at: 2026-03-12 13:36:18
completed_at: 2026-03-12 13:38:22
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:06-cq-chat.md","document_title":"06-cq-chat.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":5,"current_depth":1,"extracted_node_ids":["b55220a6-be4e-41cf-a5b2-479ae9733feb","3b059a1f-d20f-491f-a5aa-65bba791b45d","ff4b2e53-5fdb-49c7-a205-48817beab2ff","f77c05d7-f1e2-4d0b-ba3e-2465ee3145a8","34ad3ed6-59be-4d32-9cd0-792bd512d00c"],"skip_analysis":true,"last_step_request_at":1773322702,"root_node_id":"b55220a6-be4e-41cf-a5b2-479ae9733feb","base_tag":"document","current_block_title":"Technical Architecture and Privacy","step_locked_at":1773322702}


id: 7353be6f-4346-475c-bb91-0aeb08bfd5a0
type: extract_recursive
status: completed
result: {"total_memories":8,"message":"Extraction complete. Created 8 memory nodes."}
created_at: 2026-03-12 13:39:20
started_at: 2026-03-12 13:39:20
completed_at: 2026-03-12 13:42:21
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:07-cq-contacts.md","document_title":"07-cq-contacts.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":8,"current_depth":1,"extracted_node_ids":["a66ca7d8-5440-4462-8478-92fc9f09328c","7ca97fb5-e521-48f7-be82-39799329847b","ebe1af06-27db-4edb-abcd-bcfd6adb99f1","aadc9369-e6f7-4823-b8c0-59e30f9e2143","db4091ba-59d2-41a2-a1a2-7e11c746bc9e","33de0555-679f-4e3c-bdd5-6f38292b8a0e","3934e812-46aa-488a-a6d2-ab56ea6ccc86","4f300b5b-b718-437e-bab8-49aa61546714"],"skip_analysis":true,"last_step_request_at":1773322941,"root_node_id":"a66ca7d8-5440-4462-8478-92fc9f09328c","base_tag":"document","current_block_title":"Federation Protocol & Privacy","step_locked_at":1773322941}


id: 0d4e96ae-1c89-4dae-92bb-37cd792d10cf
type: extract_recursive
status: completed
result: {"total_memories":11,"message":"Extraction complete. Created 11 memory nodes."}
created_at: 2026-03-12 13:42:52
started_at: 2026-03-12 13:42:52
completed_at: 2026-03-12 13:48:47
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:08-cq-share.md","document_title":"08-cq-share.md","max_depth":2,"needs_init":false,"pending_blocks":[{"title":"Methods for Creating Shares","summary":"Step-by-step instructions for sharing items via File Browser, Memory Explorer, or CQ Share page.","start_line":47,"end_line":48,"is_leaf":false,"content":"---\n","tags":["creation-process","file-browser","memory-explorer","cq-share"],"parent_node_id":"30770643-51d9-4460-8d73-acbeeea5ee5d","depth":2}],"processed_count":10,"current_depth":1,"extracted_node_ids":["e3562b91-45ea-49ec-a6ae-2f1d2c256c3d","93773695-e3ff-4eb0-be79-8ffa69bfc7d6","30770643-51d9-4460-8d73-acbeeea5ee5d","a4102387-181b-467a-9de7-edeb48f554e0","4d8a2d04-0376-4274-818b-160b12166db4","4c65b13b-e579-4e5b-99c1-8c216affde3b","ff9a208f-151d-43df-9869-4df9f9dd2f1a","c948f87d-5941-4d4d-84a2-98e896b44105","033b4c10-b865-4082-b222-2b80e3325247","d0105e38-e572-40e8-9841-f88321a97df3"],"skip_analysis":true,"last_step_request_at":1773323325,"root_node_id":"e3562b91-45ea-49ec-a6ae-2f1d2c256c3d","base_tag":"document","current_block_title":"Search & Filter Functionality"}


id: e4a5706e-d431-4e7e-9cee-fd14f5b92151
type: extract_recursive
status: completed
result: {"total_memories":8,"message":"Extraction complete. Created 8 memory nodes."}
created_at: 2026-03-12 13:49:58
started_at: 2026-03-12 13:49:58
completed_at: 2026-03-12 13:53:19
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:09-cq-profile.md","document_title":"09-cq-profile.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":8,"current_depth":1,"extracted_node_ids":["9f70573d-ea1e-4d50-939b-05a989db6084","a1439ab3-f65b-4de5-a309-e171ebaf073e","0c573bc1-8254-4f1f-b1a4-f39dca6c24d5","9552e58a-dc05-4b5e-970c-2c95a80fc2b6","b26fdb3a-aa6b-4e62-ad8c-b621dede41ac","caa65c7d-fc3f-41ee-864c-cbe1d1deecae","1fb09f94-b7b5-4c69-bcc1-f221287c0184","e1c3943f-7e5e-4e20-b8b5-bece58227459"],"skip_analysis":true,"last_step_request_at":1773323599,"root_node_id":"9f70573d-ea1e-4d50-939b-05a989db6084","base_tag":"document","current_block_title":"User Interaction and Access Levels","step_locked_at":1773323599}


id: f7f4d810-2039-449f-a937-769fffdaec76
type: extract_recursive
status: completed
result: {"total_memories":8,"message":"Extraction complete. Created 8 memory nodes."}
created_at: 2026-03-12 13:58:03
started_at: 2026-03-12 13:58:03
completed_at: 2026-03-12 14:00:34
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:10-settings.md","document_title":"10-settings.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":8,"current_depth":1,"extracted_node_ids":["bb33fbfe-33f1-4c1d-a318-a43d904847ff","6b6c8c5b-6836-45b0-91ce-c68c09c33db8","47b58ff8-0f88-4aec-b8be-6ef831437dbf","dcfc9c0a-b1ac-4c97-8643-3f495d770a3d","aa84ecfe-cf77-4e17-9850-d4b41884545a","9c74d022-8fb4-4539-b79a-0af27eec0354","651ec2a7-893b-4e84-9fc0-60a1ffab2539","07d73807-3bef-4bbb-bf74-94627323cee3"],"skip_analysis":true,"last_step_request_at":1773324034,"root_node_id":"bb33fbfe-33f1-4c1d-a318-a43d904847ff","base_tag":"document","current_block_title":"Settings Navigation Sidebar","step_locked_at":1773324034}


id: 224e52f1-1d1d-49f1-af14-6a2cd8c3cb51
type: extract_recursive
status: completed
result: {"total_memories":6,"message":"Extraction complete. Created 6 memory nodes."}
created_at: 2026-03-12 14:03:42
started_at: 2026-03-12 14:03:42
completed_at: 2026-03-12 14:06:48
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:11-backup.md","document_title":"11-backup.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":6,"current_depth":1,"extracted_node_ids":["6f6281f0-0ae6-4ec8-b829-a07b383d2baa","f10414d1-5c2c-4f68-9977-d71212e8d9af","ce8748d3-07f3-458d-b031-05996cd7ecc8","10447049-2745-48a8-a44e-219768498463","b0814698-e1bf-405e-bbd0-89be0c75d3a2","96095a4e-b62c-475e-a2aa-80fa6ee37e4d"],"skip_analysis":true,"last_step_request_at":1773324408,"root_node_id":"6f6281f0-0ae6-4ec8-b829-a07b383d2baa","base_tag":"document","current_block_title":"Best Practices","step_locked_at":1773324408}


id: 8fd3f498-e2be-4eee-9c10-e81b17dc7cc3
type: extract_recursive
status: completed
result: {"total_memories":7,"message":"Extraction complete. Created 7 memory nodes."}
created_at: 2026-03-12 14:08:34
started_at: 2026-03-12 14:08:34
completed_at: 2026-03-12 14:12:00
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:12-administration.md","document_title":"12-administration.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":7,"current_depth":1,"extracted_node_ids":["1f4aba06-d24c-48de-90c1-a09640942ada","fe4eef3d-8d4f-4188-986c-39a43ca9913b","e3bcb9b7-f7cb-48b2-b798-50ecd96d781c","e233a100-5775-4040-a1b3-7b3fe93470da","2a74f7ec-6dc6-4e4b-a87a-5ce5de772401","485942bf-31ec-4d61-9bc2-b3f9777e1844","6c522150-ff8d-42ac-a776-58f6699ff927"],"skip_analysis":true,"last_step_request_at":1773324720,"root_node_id":"1f4aba06-d24c-48de-90c1-a09640942ada","base_tag":"document","current_block_title":"Migration Requests","step_locked_at":1773324720}


id: 053b51fb-707b-4491-a1e9-0e2789fb1534
type: extract_recursive
status: completed
result: {"total_memories":7,"message":"Extraction complete. Created 7 memory nodes."}
created_at: 2026-03-12 14:12:58
started_at: 2026-03-12 14:12:58
completed_at: 2026-03-12 14:15:50
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:13-installation.md","document_title":"13-installation.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":7,"current_depth":1,"extracted_node_ids":["adcf2a61-15b8-45d5-a10d-3f0ff414bff0","02219640-3973-4d9f-bbb1-5c2f490ed3b5","aa033ef6-d33a-4289-9fbb-fb893247be20","e47091aa-4b2b-4925-a2ed-f156fb58e4a9","fcec0402-59ac-42bb-b213-6d2270fce582","6d45f077-3b4a-43a8-9e58-bc3da291393c","fdba9b8b-d1a7-475c-bf84-03db9e868a65"],"skip_analysis":true,"last_step_request_at":1773324950,"root_node_id":"adcf2a61-15b8-45d5-a10d-3f0ff414bff0","base_tag":"document","current_block_title":"CQ AI Gateway Integration","step_locked_at":1773324950}


id: 29694f1e-8196-4368-8faf-273cd47f0f4f
type: analyze_relationships
status: completed
created_at: 2026-03-12 14:20:29
started_at: 2026-03-12 14:20:29
completed_at: 2026-03-13 12:39:29
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"pending_pairs":[],"processed_count":4084,"relationships_created":3358,"source_job_id":null,"document_title":null,"new_source_ref":null,"full_pack_analysis":true,"last_step_request_at":1773405569,"step_locked_at":1773405569}

result:
{"pairs_analyzed":4084,"relationships_created":3358,"message":"Relationship analysis complete. Analyzed 4084 pairs, created 3358 relationships."}


id: 57cb9eb5-8afb-42c4-aa29-596110e256f8
type: extract_recursive
status: completed
result: {"total_memories":8,"message":"Extraction complete. Created 8 memory nodes."}
created_at: 2026-03-22 13:16:33
started_at: 2026-03-22 13:16:33
completed_at: 2026-03-22 13:19:30
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:CITADELQUEST.md","document_title":"CITADELQUEST.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":8,"current_depth":1,"extracted_node_ids":["faedb97b-90c9-4e41-a60d-1da95f43f13f","3b3d40ae-1e59-4d38-9d22-08e02da77b1d","bef64406-3a00-47dc-a94c-2760f5e2c9c9","1b46ce86-a60f-42b1-8c33-10311372c1dc","a2199fe4-58db-4c75-8fa7-111aecad3609","5fbdbda3-c2ca-45ea-8312-645ae00f1c2d","33b56ac5-5b94-4aa5-bdc7-c8e7e2716b08","aab019ea-28a4-4602-b64d-751a85579629"],"skip_analysis":true,"last_step_request_at":1774185570,"root_node_id":"faedb97b-90c9-4e41-a60d-1da95f43f13f","base_tag":"document","current_block_title":"Getting Started and Support","step_locked_at":1774185570}


id: 7ef8c846-c768-400c-bc48-d5706bbb0a00
type: extract_recursive
status: completed
result: {"total_memories":8,"message":"Extraction complete. Created 8 memory nodes."}
created_at: 2026-03-22 17:41:49
started_at: 2026-03-22 17:41:49
completed_at: 2026-03-22 17:44:50
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:09-cq-profile.md","document_title":"09-cq-profile.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":8,"current_depth":1,"extracted_node_ids":["166053ba-a674-4a75-9e1f-390dc0e1e44c","578f8d7a-428b-476d-bec9-02fb4f313fb7","39211a39-e63c-4aa3-8b92-677719c70de8","2aa531b7-b3e2-4bb2-b03b-5ef3226fbb44","0034ac96-db9c-433b-891c-dc86f489a2e4","63482038-a160-4154-8a9e-9555c065a606","f02102d6-abdf-4cef-bc2f-ddc1876aaccb","ab6dd489-1426-4900-a85f-7d361bcc596f"],"skip_analysis":true,"last_step_request_at":1774201490,"root_node_id":"166053ba-a674-4a75-9e1f-390dc0e1e44c","base_tag":"document","current_block_title":"User Interaction and Access Levels","step_locked_at":1774201490}


id: a44d2766-af4a-434c-88f9-5b9d7e00f851
type: extract_recursive
status: completed
result: {"total_memories":6,"message":"Extraction complete. Created 6 memory nodes."}
created_at: 2026-03-22 17:46:00
started_at: 2026-03-22 17:46:00
completed_at: 2026-03-22 17:47:35
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:00-introduction.md","document_title":"00-introduction.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":6,"current_depth":1,"extracted_node_ids":["a85d7f22-c4c6-4f96-b668-f6b84405555d","8e8c46f6-5820-4625-9ac7-04285b2f394f","307ef895-4d2e-4253-8293-02187da0badf","33d0838f-5d52-4b3c-bc90-43a4272fd309","07834e44-7361-45b8-aa45-60d029df53d3","a0bca789-5788-4ced-ab99-beadcf7ca11a"],"skip_analysis":true,"last_step_request_at":1774201655,"root_node_id":"a85d7f22-c4c6-4f96-b668-f6b84405555d","base_tag":"document","current_block_title":"About and Contact Information","step_locked_at":1774201655}


id: b217b4c9-e37d-4189-95ea-46cbbfd7f6d6
type: extract_recursive
status: completed
result: {"total_memories":9,"message":"Extraction complete. Created 9 memory nodes."}
created_at: 2026-03-22 17:48:34
started_at: 2026-03-22 17:48:34
completed_at: 2026-03-22 17:50:53
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:10-settings.md","document_title":"10-settings.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":9,"current_depth":1,"extracted_node_ids":["f0a4c741-f49a-4024-9028-b5ad0bc60744","ffa39d52-23ac-424c-8d0a-e25b6590b9e4","6318eec5-1bd0-47a2-aa53-cbe6cfce977b","8a1c5fe3-c932-4def-bfd8-ad1667b9c37e","6b9619cb-e8e6-492f-8942-29ce08a329e3","3fb33b70-55cf-4541-ad4d-f8da2b5e5ebd","c455066a-fe9b-432a-a598-b9116b4715c8","70701b55-4255-46a9-9cb8-64f779221e21","8c37fa16-08e6-4a68-858c-592164a4e3fb"],"skip_analysis":true,"last_step_request_at":1774201853,"root_node_id":"f0a4c741-f49a-4024-9028-b5ad0bc60744","base_tag":"document","current_block_title":"Account Migration","step_locked_at":1774201853}


id: 9bb6e0b2-1bd2-4991-be74-82a5c1186606
type: extract_recursive
status: completed
result: {"total_memories":7,"message":"Extraction complete. Created 7 memory nodes."}
created_at: 2026-03-22 17:51:32
started_at: 2026-03-22 17:51:32
completed_at: 2026-03-22 17:53:41
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:14-cq-feed.md","document_title":"14-cq-feed.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":7,"current_depth":1,"extracted_node_ids":["a70d9f99-7362-402b-8187-e08afca930c3","ebfa0295-84e3-4e22-b39c-d2074b1a6521","cef60805-5ad9-4f33-a8b7-14c43569b589","2c049ada-5de8-4c23-80be-48aeea1b7165","ceb97a1e-c3df-4854-85a8-427546e5b6a3","ea8ceda3-6121-4082-9f7c-2e15f2e23828","96428498-d67a-4e81-a9af-a5000a94ffd9"],"skip_analysis":true,"last_step_request_at":1774202021,"root_node_id":"a70d9f99-7362-402b-8187-e08afca930c3","base_tag":"document","current_block_title":"Federation and Technical Architecture","step_locked_at":1774202021}


id: 6cb1b7d1-f2fa-424d-b080-f154dcd9e400
type: extract_recursive
status: completed
result: {"total_memories":4,"message":"Extraction complete. Created 4 memory nodes."}
created_at: 2026-03-22 17:53:49
started_at: 2026-03-22 17:53:49
completed_at: 2026-03-22 17:54:40
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:02-dashboard.md","document_title":"02-dashboard.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":4,"current_depth":1,"extracted_node_ids":["1722b9fd-f5a2-4145-a98b-ab6796c4de88","897390d1-2ec0-45f9-a740-5bff0bc0232b","ada32b14-6f87-4f53-98cf-977cf80f006c","7d433200-f88c-450e-a2b5-f100e5a9a92c"],"skip_analysis":true,"last_step_request_at":1774202080,"root_node_id":"1722b9fd-f5a2-4145-a98b-ab6796c4de88","base_tag":"document","current_block_title":"Top Navigation Bar","step_locked_at":1774202080}


id: bde8332f-aa3b-4ac7-a55d-52c29419c6c2
type: extract_recursive
status: completed
result: {"total_memories":8,"message":"Extraction complete. Created 8 memory nodes."}
created_at: 2026-03-22 17:55:41
started_at: 2026-03-22 17:55:41
completed_at: 2026-03-22 17:58:33
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"source_type":"document","source_ref":"general:\/CQ-User-Manual:07-cq-contacts.md","document_title":"07-cq-contacts.md","max_depth":2,"needs_init":false,"pending_blocks":[],"processed_count":8,"current_depth":1,"extracted_node_ids":["c61b72ad-697b-40ad-9850-f0ce482ad13e","1edffca9-3a49-4cea-ac1c-e0dab061c758","64ac3eb6-21a4-4540-8226-ebdee187fd2a","de076905-7921-4a20-bb33-c9638b69ef54","8c1e0b5e-4a16-4767-ac68-cba62e55daaa","35a7a1f8-1d24-441f-98ed-8710ced05a8a","ac5c0c9f-2ffd-4481-a45e-87881310440a","32d09012-3eaf-49b0-8726-915418d6dad1"],"skip_analysis":true,"last_step_request_at":1774202313,"root_node_id":"c61b72ad-697b-40ad-9850-f0ce482ad13e","base_tag":"document","current_block_title":"Federation Protocol","step_locked_at":1774202313}


id: f45771be-48e7-4889-8146-e1699a5e97a2
type: analyze_relationships
status: completed
created_at: 2026-03-22 18:08:12
started_at: 2026-03-22 18:08:12
completed_at: 2026-03-23 05:03:58
payload:
{"target_pack":{"projectId":"general","path":"\/memory\/libs\/packs","name":"CQ-User-Manual.cqmpack"},"pending_pairs":[],"processed_count":2640,"relationships_created":2403,"source_job_id":null,"document_title":null,"new_source_ref":null,"selected_roots":true,"root_node_ids":["a85d7f22-c4c6-4f96-b668-f6b84405555d","a70d9f99-7362-402b-8187-e08afca930c3","c61b72ad-697b-40ad-9850-f0ce482ad13e","1722b9fd-f5a2-4145-a98b-ab6796c4de88","f0a4c741-f49a-4024-9028-b5ad0bc60744","166053ba-a674-4a75-9e1f-390dc0e1e44c","1f4aba06-d24c-48de-90c1-a09640942ada","e3562b91-45ea-49ec-a6ae-2f1d2c256c3d","b55220a6-be4e-41cf-a5b2-479ae9733feb","ac49a47f-9772-4591-932c-4504d4ce6a1b","a26434c2-2f0a-4a19-8851-8757e21ddbf1","85fb774c-e8e7-4611-91cd-44a19a072386","f080d9f1-7a52-443e-b81c-9bd0c76bd111"],"last_step_request_at":1774233022,"step_locked_at":1774242238}

result:
{"pairs_analyzed":2640,"relationships_created":2403,"message":"Relationship analysis complete. Analyzed 2640 pairs, created 2403 relationships."}


# memory_sources

source_ref: general:/CQ-User-Manual:03-spirits.md
source_type: document
title: 03-spirits.md
created_at: 2026-03-12 13:17:40
content:
# Spirits — Your AI Companions

Spirits are the heart of CitadelQuest — personal AI companions that learn, remember, and grow alongside you. Each Spirit has its own personality, memory, and capabilities.

---

## Spirits List

**Route**: `/spirits`

The Spirits page shows all your AI companions as cards. Each card displays:
- Spirit icon with custom color
- Spirit name
- Level and experience points (XP)
- Quick access to Spirit chat and profile

From here you can create new Spirits or click on an existing one to manage it.

---

## Spirit Profile

**Route**: `/spirit/{id}`

The Spirit Profile is your Spirit's home page, divided into several sections:

### Identity & Level
- **Spirit icon** with custom color and glow effect
- **Name** and **Level** indicator
- **Experience bar** showing progress to next level (XP earned through interactions)

### AI Model
- **Model selector** — click to compare and select from available AI models
- Models include options from providers like Anthropic (Claude), Google (Gemini), xAI (Grok), and more
- Your selection determines the AI powering this Spirit's responses

### System Prompt
- **Custom instructions** — define how your Spirit should behave, its personality, areas of expertise, and knowledge
- **Advanced Prompt Builder** — opens a detailed editor for fine-tuning the system prompt with:
  - Memory Type selection (Legacy .md files, Reflexes, Memory Agent)
  - Structured sections for personality, expertise, and behavior rules
- Click **Save** to apply changes

### Memory Explorer Preview
- **3D graph visualization** — a miniature preview of your Spirit's knowledge graph
- Shows pack count, node count, and relationship count
- **Explore** button opens the full Memory Explorer filtered to this Spirit
- **Memory Agent** badge shows which memory processing mode is active

### Recent Interactions
- Log of Spirit interactions with timestamps
- Shows XP earned and interaction types (creation, conversation, tool use)

### Conversations
- List of all conversations with this Spirit
- Click the chat button to open a conversation
- Create new conversations with the "+" button

---

## Spirit Chat

Spirit Chat is a **modal overlay** — it opens on top of any page, so you never lose your place. Access it by:
- Clicking the **Spirit icon** in the top navigation bar
- Clicking a **conversation** in the Spirit Profile

### Chat Interface
- **Message input** — type your message and press Enter or click Send
- **AI response** — your Spirit's reply with full Markdown formatting (code blocks, lists, tables, etc.) and AI Tools results
- **Memory synthesis** — when relevant, the chat shows which memories were recalled:
  - Expandable panel with recalled memory nodes
  - Mini 3D graph visualization of memory connections and highlighted activated nodes
  - Synthesis quality indicator (high/medium/low)
  - Tags showing matched keywords
- **Used context window indicator** — top border of input area used as decent yet informative progress bar

### Attachments
- **Image attachments** — attach images to your messages
- **PDF attachments** — attach PDF documents for your Spirit to analyze (and makes it available for memory extraction)

### Controls
- **Temperature slider** — adjust the creativity/randomness of your Spirit's responses
- **Info button** — shows Spirit current AI Model name (context window size)
- **Extract Memory & Close** — extract the conversation into a CQ Memory Pack and close the conversation in one click

### AI Tools

Your Spirit can use various tools during conversation to help you:

| Tool | Description |
|------|-------------|
| **getFileContent** | Read files from your File Browser |
| **searchFile** | Search for files in your File Browser |
| **manageFile** | Create, rename, move, or delete files |
| **updateFileEfficient** | Edit specific parts of files with precision |
| **getProjectTree / listFiles** | Browse your file system |
| **memoryStore** | Save important information to memory |
| **memoryRecall** | Search through stored memories |
| **memoryExtract** | Extract knowledge from documents into memory graphs (with automatic relationship analysis) |
| **memorySource** | Look up original source content for a memory |
| **fetchURL** | Read web page content |
| **imageEditorSpirit** | Generate and edit images using AI |
| **diffusionArtistSpirit** | Generate images using AI diffusion models |

> Tools are used automatically when relevant — just ask your Spirit naturally and it will decide which tools to use.

---

## Creating a New Spirit

1. Go to `/spirits`
2. Click **Create Spirit** (or it opens automatically if you have no Spirits)
3. Choose a **name**, **AI model**, and **color**
4. Your Spirit is created with starter memory nodes (identity nodes for both Spirit and user)
5. Start your first conversation!

---

## Spirit Experience & Leveling

Spirits earn **XP** (experience points) through interactions:
- **Conversations** — chatting with your Spirit
- **Tool usage** — when Spirit uses its tools to help you
- **Memory operations** — when Spirit stores or processes memories

As your Spirit levels up, the experience bar fills and the level number increases. This gamification element makes the collaboration journey more engaging.


source_ref: general:/CQ-User-Manual:04-cq-memory.md
source_type: document
title: 04-cq-memory.md
created_at: 2026-03-12 13:21:11
content:
# CQ Memory — Knowledge Graphs

CQ Memory is CitadelQuest's powerful knowledge management system. It transforms unstructured content — documents, web pages, conversations — into **interactive 3D knowledge graphs** that your Spirits can use for persistent, contextual memory.

---

## Key Concepts

### Memory Pack (`.cqmpack`)
A standalone knowledge graph stored as a portable SQLite database file. Each pack contains:
- **Nodes** — individual pieces of knowledge (facts, insights, preferences, thoughts)
- **Relationships** — typed connections between nodes (relates to, contradicts, reinforces, etc.)
- **Tags** — flexible labels for filtering and search
- **Source content** — the original documents that knowledge was extracted from

Packs are fully self-contained and portable — they can be shared between users and Citadels.

### Memory Library (`.cqmlib`)
A collection that groups multiple Memory Packs together. Libraries help you organize related knowledge:
- Enable/disable individual packs
- Set priorities for which packs are searched first
- Tag packs for easy categorization

### Memory Node
A single unit of knowledge. Each node has:
- **Content** — the actual information
- **Summary** — short description shown on the graph
- **Category** — knowledge, fact, preference, thought, conversation, or internet
- **Importance** — how relevant this memory is (decays over time if not accessed)
- **Source tracking** — where this memory came from

### Relationships
Connections between nodes, each with a type:

| Type | Meaning | Visual |
|------|---------|--------|
| **RELATES_TO** | General semantic connection | Blue edge |
| **REINFORCES** | Supporting/confirming information | Green edge |
| **CONTRADICTS** | Conflicting information | Red edge |
| **PART_OF** | Hierarchical parent-child | White/Grey edge |

---

## Memory Explorer

**Route**: `/memory`

The Memory Explorer is the main interface for viewing and managing your knowledge graphs.

### Layout

- **Left sidebar** — Node list with search, source document sections, extract and analyze tools
- **Center** — Interactive 3D graph visualization
- **Top bar** — Library selector, Pack selector, info

### 3D Graph Visualization

The centerpiece of Memory Explorer — an interactive 3D force-directed graph rendered with Three.js:
- **Nodes** appear as colored spheres (color = category)
- **Edges** connect related nodes (color = relationship type)
- **Click** a node to see its details (content, category, importance, tags, source)
- **Hover** over a node to highlight its connections and show the node's title
- **Scroll** to zoom, **drag** to rotate, **right-drag** to pan
- **Click+Ctrl** zoom to node + set camera center of rotation
- **Delete** key press to show confirm window, delete node and its children
- **Node size** reflects importance

### Library Selector

The dropdown at the top lets you switch between:
- **All Packs** — shows every `.cqmpack` file in your project
- **Specific libraries** — shows only packs in that library
- When viewing a Spirit's memory (`/memory?spirit={id}`), only that Spirit's library is shown

### Pack Selector

Next to the library selector, choose which pack to visualize. Shows:
- Pack name
- Node count badge
- Relationship count badge
- Dropdown for Pack management (Add/Remove from Library, Show details with AI usage stats, Delete)

### Creating a New Pack

1. Click the **+** button next to the pack selector
2. Enter a name for your new pack
3. The pack is created and automatically added to the selected library

### Creating a New Library

1. Click the **+** button next to the library selector
2. Enter a name and optional description
3. The library is created at the default location

---

## Memory Extraction

The Extract Panel lets you add knowledge from various sources into a pack.

### Source Types

#### File
Upload or select a file from your File Browser. Supported: text documents, PDFs, code files, and more.

#### URL
Enter a web page URL. CitadelQuest fetches the content and extracts knowledge from it.

#### Text
Paste any text directly. Useful for quick notes, copied content, or manual input.

#### Conversation
Select a Spirit and one of its conversations. The conversation transcript is extracted into structured knowledge.

### Extraction Process

1. Select your source type and provide the content
2. Click **Start Extraction**
3. Watch the 3D graph update in real-time as nodes are created:
   - Documents are processed recursively — the AI splits content into logical blocks, creating a hierarchical structure
4. After extraction completes, **relationship analysis** runs automatically, if selected in the extraction settings — the AI discovers connections between all nodes
5. The complete knowledge graph is stored in the selected pack (AI usage logged)

> **AI Credits**: Extraction uses CQ AI Gateway credits. The Pack Details modal shows complete token usage and credit cost statistics.

---

## Memory Analyze Panel

After extracting knowledge, you can run relationship analysis to discover connections between nodes.

### Whole Pack Analysis
Analyzes all nodes in the selected Memory Pack to discover relationships across the entire knowledge graph.

### Selected Root Node Analysis
Focused analysis on a specific branch (tree) of nodes — useful for analyzing relationships within a particular document or topic without re-analyzing the entire pack.

The analysis uses a hierarchical strategy that's optimized for efficiency — intra-document leaf pairs, then cross-document root-gating with recursive drill-down.

### Active CQ Memory Jobs

A status icon in the **global app footer** shows when memory jobs (extraction or analysis) are actively running. This is visible from any page, so you always know when your knowledge graph is being processed.

---

## Spirit Memory Integration

Each Spirit has its own Memory Library containing one or more packs. This is how Spirits remember things:

### Memory Types

| Type | Description |
|------|-------------|
| **Reflexes** | Fast, automatic memory recall. When you send a message, your Spirit's memory is searched for relevant context, which is included in the conversation. |
| **Memory Agent** | Advanced mode — a sub-agent AI synthesizes recalled memories, evaluates relevance, and expands graph connections before responding. Higher quality, uses more credits. |
| **Legacy (.md files)** | Older text-based memory system (backward compatibility). |

### How Memory Recall Works

1. You send a message to your Spirit
2. The system searches all enabled packs in the Spirit's library
3. Relevant memory nodes are recalled based on keyword matching
4. For Memory Agent mode: a sub-agent AI evaluates and synthesizes the recalled memories
5. The recalled context is provided to your Spirit alongside your message
6. Your Spirit responds with awareness of past knowledge

### Memory Synthesis Display

In Spirit Chat, recalled memories appear above the Spirit's response:
- **Expandable panel** showing which memories were used
- **Mini 3D graph** visualizing the recalled nodes and their connections
- **Score badges** showing relevance strength
- **Tags** for quick identification
- **"Graph" badges** for nodes discovered via relationship expansion

---

## Sharing Memory Packs

You can share your Memory Packs with CQ Contacts or publicly via **CQ Share**:

1. In the Memory Explorer, select a pack and use the pack dropdown menu → **Share**
2. Or go to the **CQ Share** management page (`/share`) and create a share for any pack
3. Choose scope: **Public** (anyone with the link) or **CQ Contacts** (authenticated contacts only)

When a CQ Contact downloads your shared pack, it **auto-syncs** — any updates you make to the original pack are automatically reflected in their copy the next time they open their Memory Explorer.

See [CQ Share](08-cq-share.md) for the full sharing guide.

---

## Use Cases

- **Book/Document Analysis** — Upload PDFs or documents, extract key concepts, see information structure at a glance
- **Research** — Load multiple sources into one library, visualize contradictions and reinforcements across sources
- **Spirit Knowledge** — Build specialized knowledge bases for your Spirits
- **Personal Wiki** — Organize your knowledge into themed packs
- **Web Research** — Extract knowledge from URLs and see connections between different web sources
- **Conversation Archives** — Extract insights from your Spirit conversations into permanent knowledge
- **Relationship Discovery** — Run analysis to find contradictions, reinforcements, and connections across different knowledge sources
- **Shared Knowledge** — Share curated knowledge graphs with friends, team members, or the public via CQ Share


source_ref: general:/CQ-User-Manual:05-file-browser.md
source_type: document
title: 05-file-browser.md
created_at: 2026-03-12 13:32:42
content:
# File Browser — Personal Cloud

The File Browser is your personal cloud storage within CitadelQuest. Your files are stored on your server, always accessible, and fully integrated with your AI Spirits.

**Route**: `/file-browser`

---

## Interface

The File Browser offers two views, switchable via toggle buttons:

### Tree View
A hierarchical tree showing your complete folder structure. Click folders to expand/collapse, click files to select them.

### File Preview
- Size
- Last modified date
- Action buttons (download, rename, delete)
- content preview for images, pdf, md, txt

---

## Operations

### Uploading Files
1. Click the **Upload** button
2. Select or drag&drop files from your device
3. Files are uploaded to your current directory

### Creating Folders
1. Click the **New Folder** button
2. Enter a name
3. The folder is created in your current directory

### Creating Files
1. Click the **New File** button
2. Enter a filename
3. An empty file is created — you can edit it or let your Spirit fill it with content

### Downloading
Click the **download** icon next to any file to download it to your device. **download in ZIP** for directories

### Renaming
Click the **rename** icon, enter the new name, and confirm.

### Deleting
Click the **delete** icon and confirm the deletion.

### Sharing
Click the **Share** button on any file to create a CQ Share link. You can choose to share publicly (anyone with the link) or with CQ Contacts only. See [CQ Share](08-cq-share.md) for details.

---

## AI Integration

Your Spirits have full access to the File Browser through their tools:

- **Read files** — Spirit can read any file content to help you
- **Create files** — Spirit can create new files (notes, documents, code, etc.)
- **Edit files** — Spirit can make precise edits to existing files
- **Manage files** — Spirit can rename, move, or delete files
- **Browse** — Spirit can list directory contents to understand your file structure

This means you can ask your Spirit things like:
- "Create a shopping list in my notes folder"
- "Read the document I uploaded and summarize it"
- "Update the recipe file with the new ingredients"
- "Organize my files into folders by topic"

---

## Mobile Support

The File Browser is fully responsive and optimized for mobile devices:
- Touch-friendly interface
- Icon-based mobile navigation
- Responsive layout adapting to screen size

---

## Storage

Your files are stored in your personal data directory on the server. The Dashboard shows your current storage usage breakdown (Database, User Data, Backups).

> Files are stored per-user — other users on the same Citadel cannot access your files.


source_ref: general:/CQ-User-Manual:06-cq-chat.md
source_type: document
title: 06-cq-chat.md
created_at: 2026-03-12 13:36:18
content:
# CQ Chat — Private Messaging

CQ Chat enables private, encrypted messaging between users across different CitadelQuest instances. Communication is direct — messages travel straight from one Citadel to another, with no corporate servers in between.

**Route**: `/cq-chat`

---

## Accessing CQ Chat

There are two ways to access your conversations:

### Navigation Dropdown
Click the **chat icon** in the top navigation bar to see:
- Recent conversations with preview of last message
- **Unseen message count** badge (green number)
- **New Chat** button to start a conversation
- Click any conversation to open it

### Full Chat Page
Navigate to `/cq-chat` for the complete chat interface with:
- Conversation list on the left
- Active conversation on the right
- Full message history with timestamps

---

## Conversations

### Starting a Conversation
1. Click the **New Chat** button (message+ icon)
2. Select a contact from your CQ Contacts
3. Start typing!

### Group Chats
CQ Chat supports group conversations with multiple participants from different Citadels.

### Message Features
- **Text messages** with real-time delivery
- **Image attachments**
- **Timestamps** showing when messages were sent
- **Read indicators** for message status
- **Unseen count** — badge shows how many unread messages you have

---

## How It Works

CQ Chat uses CitadelQuest's **Federation protocol** for cross-instance communication:
- Messages are sent directly between Citadels over HTTPS, secured with **CQ Contact API Keys**
- Your browser polls for new messages in real-time via the global updates endpoint
- Messages are stored only on the sender's and receiver's Citadels — nowhere else

> **Privacy**: Messages travel directly between Citadels. There is no central server that stores or relays your messages. Each user's messages are stored in their own personal database.


source_ref: general:/CQ-User-Manual:08-cq-share.md
source_type: document
title: 08-cq-share.md
created_at: 2026-03-12 13:42:52
content:
# CQ Share — Sharing Files & Knowledge

CQ Share lets you share files and CQ Memory Packs with your CQ Contacts or make them publicly accessible via a clean URL. It's the bridge between your personal data and the people you choose to share it with.

**Route**: `/share`

---

## Overview

CQ Share gives you two ways to share:

- **Public sharing** (scope: Public) — anyone with the link can access the shared item, no login required
- **CQ Contact sharing** (scope: CQ Contacts) — only your CQ Contacts can access, authenticated via their CQ Contact API keys

You can share two types of content:

| Type | Description |
|------|-------------|
| **Files** | Any file from your File Browser — images, documents, HTML pages, PDFs, archives, etc. |
| **CQ Memory Packs** | Knowledge graphs (`.cqmpack` files) — shareable and auto-syncable |

---

## CQ Share Management Page

The Share management page shows all your shared items with:
- **Title** — display name for the shared item
- **Type** — File or Memory Pack
- **Scope** — Public or CQ Contacts
- **URL** — the share link (click to copy)
- **Views** — download/access counter
- **Status** — Active or Paused
- **Display style** — how the item is rendered (Full, Preview, or Hidden)
- **Description** — optional markdown text shown alongside the item
- **Actions** — Edit, toggle active/paused, delete

### Search & Filter

The management page includes:
- **Search** — filter shares by title
- **Type filter** — show only Memory Packs or Files
- **Status filter** — show only Active or Paused items

---

## Creating a Share

### From File Browser

1. Select a file in the **File Browser**
2. Click the **Share** button in the file actions
3. Choose a **title** and **scope** (Public or CQ Contacts)
4. The share URL is generated automatically

### From Memory Explorer

1. Open **Memory Explorer** (`/memory`)
2. Select a Memory Pack
3. Use the pack management dropdown menu and click **Share**
4. Choose a **title** and **scope**

### From CQ Share Page

1. Go to **CQ Share** (`/share`)
2. Click **Create New Share**
3. Select the file or memory pack from your File Browser
4. Configure title, scope, and URL slug
5. Save — the share is now live

---

## Share URLs

Each shared item gets a clean, readable URL:

```
https://your-citadel.com/YourUsername/share/My-Shared-Document
```

- The URL slug is auto-generated from the title but can be customized
- URLs are unique per user
- Public shares can be accessed by anyone with the link — displayed inline by default (use `?download` to force download)
- CQ Contact shares require authentication

---

## Display Styles

Each share has a **display style** that controls how it appears on your profile and in CQ Explorer:

| Style | Description |
|-------|-------------|
| **Full** | Content is displayed inline — images shown full-size, HTML rendered, Memory Pack graphs visualized |
| **Preview** | Compact preview — image thumbnails, text excerpts |
| **Hidden** | Item is listed but content is not previewed |

Display style can be set per-share and optionally overridden at the group level (see Share Groups below).

---

## Share Descriptions

Each share can have an optional **description** written in Markdown. The description appears alongside the shared content on your profile and in CQ Explorer.

You can also control the **description position** relative to the content:
- **Above** — description appears above the content
- **Below** — description appears below the content
- **Left** — description on the left, content on the right
- **Right** — description on the right, content on the left

---

## Share Groups (Profile Content)

Share Groups let you organize your shared items into **content groups** — named, ordered collections that appear as tabbed navigation on your public profile and in CQ Explorer.

**Route**: `/settings/share-groups` (in Settings sidebar as **Profile Content**)

### Creating a Group

1. Go to **Settings** → **Profile Content**
2. Click **+ New Group**
3. Configure:
   - **Group Title** — name shown in the tab navigation (e.g. "Introduction", "Projects")
   - **Icon** — choose an icon for the group
   - **Icon Color** — pick a color for the icon
   - **URL Slug** — URL-friendly identifier
   - **Visibility** — Public, CQ Contacts, or specific contacts
   - **Active** — toggle the group on/off
   - **Show header** — toggle whether the group title is shown as a header
4. Click **Save**

### Adding Shares to a Group

1. Open a group in Profile Content settings
2. Click **+** to add existing shares
3. Select from your active shares
4. Drag to reorder items within the group

### Group Display Controls

Each item within a group can have its display style overridden:
- **From share** (inherit) — uses the share's own display style
- **Full** / **Preview** / **Hidden** — override for this group only

### How Groups Appear

- **Public profile page**: Groups appear as tabbed navigation below the profile header. Visitors click tabs to browse different content sections.
- **CQ Explorer**: When exploring a profile, groups appear as tabs in the main content area with the group's icon and title.

---

## Sharing Memory Packs

CQ Memory Pack sharing is especially powerful because of **auto-sync**:

### How It Works

1. You share a Memory Pack via CQ Share
2. A CQ Contact downloads it to their Citadel (see [CQ Explorer — Download to Citadel](07-cq-contacts.md))
3. The downloaded pack remembers where it came from (the source URL)
4. Whenever the contact opens their Memory Explorer, the pack automatically checks for updates
5. If you've added new knowledge to the original pack, it syncs automatically

### Use Cases

- **Shared knowledge bases** — maintain a pack and let contacts always have the latest version
- **Team documentation** — share project knowledge that stays up to date
- **Learning materials** — share curated knowledge graphs with friends or students

---

## Managing Shares

### Editing a Share

Click the edit icon on any share to change:
- **Title** — the display name
- **URL slug** — the URL path
- **Scope** — switch between Public and CQ Contacts
- **Display style** — Full, Preview, or Hidden
- **Description** — optional markdown text
- **Description position** — Above, Below, Left, or Right

### Pausing a Share

Toggle the **active/paused** status. Paused shares return a 404 — the content is not deleted, just temporarily hidden.

### Deleting a Share

Delete removes the share entry — the original file or memory pack is **not** deleted from your File Browser.

---

## Public Shares on Your Profile

If you have a **CQ Profile** public page enabled (see [CQ Profile](09-cq-profile.md)), your public shares can be displayed on your profile page in two ways:

1. **Share Groups** — organized as tabbed content sections (recommended)
2. **Shared items list** — a flat list of all public shares (toggle in profile settings)

Both can be enabled independently via profile visibility settings.

---

## Viewing Shares in CQ Explorer

When you explore any CQ Profile in CQ Explorer, you can see their public shared items and content groups. You can download files and Memory Packs directly to your Citadel. See [CQ Explorer](07-cq-contacts.md) for details.


source_ref: general:/CQ-User-Manual:11-backup.md
source_type: document
title: 11-backup.md
created_at: 2026-03-12 14:03:42
content:
# Backup & Restore

CitadelQuest includes a full backup system to protect your data. You can create, download, upload, and restore backups at any time.

**Route**: `/backup`

---

## Creating a Backup

1. Go to **Backup** (`/backup`)
2. Click **Create Backup**
3. CitadelQuest packages your complete data:
   - Personal database (all your settings, conversations, memories, contacts, etc.)
   - User data files (everything in your File Browser)
4. The backup appears in your backup list when complete

> Backups are stored as `.citadel` ZIP files on your server in your personal backup directory.

---

## Downloading a Backup

Click the **Download** button next to any backup to save it to your local device. This is recommended for:
- Off-site backup storage
- Before major updates
- Before account migration
- Peace of mind

---

## Uploading a Backup

1. Click **Upload Backup**
2. Select a backup `.citadel` ZIP file from your device
3. The file is uploaded to your Citadel

For large backup files, CitadelQuest uses **chunked uploading** — the file is split into smaller pieces and reassembled on the server, preventing timeout issues.

---

## Restoring from Backup

1. Click **Restore** next to the backup you want to restore
2. Confirm the action
3. CitadelQuest:
   - Restores the database from the backup
   - Restores your user data files
4. Refresh the page after restoration completes

---

## Deleting Backups

Click **Delete** next to any backup to remove it and free up storage space.

---

## Best Practices

- **Regular backups** — create backups periodically, especially before updates
- **Download copies** — keep backup copies on your local device or external storage
- **Before migration** — always create a fresh backup before migrating your account
- **Check storage** — monitor backup size on the Dashboard's Storage Usage panel


source_ref: general:/CQ-User-Manual:12-administration.md
source_type: document
title: 12-administration.md
created_at: 2026-03-12 14:08:34
content:
# Administration

The Administration panel is available to users with **Admin** privileges. The first registered user on a new CitadelQuest installation automatically becomes an admin.

**Route**: `/administration`

---

## Admin Dashboard

The main admin page shows:
- **User statistics** — total users, recently registered
- **Quick actions** — links to user management, updates, system settings
- **Recent users** — table of recently registered users

---

## User Management

**Route**: `/administration/users`

Manage all users on your Citadel:

### User List
- View all registered users with username, email, roles, and registration date
- **Search** to filter users by name or email

### User Actions
- **View Info** — see detailed user information in a modal dialog
- **Toggle Admin** — grant or revoke admin privileges (cannot remove your own admin role)
- **Reset Password** — generate a new password for a user
- **Delete User** — remove a user and their data (cannot delete yourself or the last admin)

---

## Application Updates

**Route**: `/administration/update/check/{step}`

Check for and install updates to CitadelQuest:

1. The system checks for available updates on GitHub
2. If a new version is available, you can download and install it
3. The updater:
   - Creates a safety backup
   - Downloads the new version
   - Applies file updates (preserves your `.env` configuration)
   - Runs database migrations
   - Clears and warms up the cache
4. Refresh the page to see the new version

> **Tip**: Always create a manual backup before updating, just in case.

---

## System Settings

The admin dashboard includes system-level configuration panels:

### User Registration

- **Toggle Registration** — enable or disable new user registration
- **Max users** — set a maximum number of allowed users (0 = unlimited)
- When disabled, the registration page shows a "Registration is currently disabled" message
- Useful for limiting access to your Citadel

### Homepage Redirect

Redirect the Citadel homepage (`https://your-citadel.com`) to a user's public CQ Profile page — for unauthenticated visitors only. Authenticated users still see their Dashboard.

1. Select a **Profile** user from the dropdown (any registered user)
2. **Toggle** the redirect on
3. Visitors to your root URL are now redirected to that user's public profile page

This is ideal when you want your Citadel's domain to serve as a personal website or landing page powered by [CQ Profile](09-cq-profile.md).

---

## Server Logs

**Route**: `/administration/logs`

View and manage server log files:
- **List** all available log files with size and last modified date
- **View** log file contents with tail/head navigation and line count
- **Download** log files for offline analysis
- **Clear** log files to free space

---

## System Backups

**Route**: `/administration/system-backups`

Manage backups across all users:
- View all user backup files
- Delete old or unnecessary backups
- Monitor backup storage usage

---

## Migration Requests

**Route**: `/administration/migrations`

When users from other Citadels request to migrate to your instance:
- View incoming migration requests
- **Accept** to allow the user's account to be transferred to your Citadel
- **Reject** to decline the request
- Monitor migration progress and status


source_ref: general:/CQ-User-Manual:13-installation.md
source_type: document
title: 13-installation.md
created_at: 2026-03-12 14:12:58
content:
# Installing Your Own CitadelQuest

Running your own Citadel means complete control over your data — your server, your rules, your privacy.

---

## Server Requirements

- **PHP** 8.4 or higher
- **Apache** with `mod_rewrite` enabled
- **SQLite3** PHP extension
- **HTTPS** required
- Standard PHP extensions: `mbstring`, `intl`, `json`, `zip`

CitadelQuest works on most shared web hosting plans, VPS, or dedicated servers.

---

## Installation — Zero-Click Installer

CitadelQuest features an incredibly simple installation process:

### Step 1: Download
Go to [GitHub Releases](https://github.com/CitadelQuest/CitadelQuest/releases) and download the **Installer Package** (`citadelquest-installer-*.zip`, ~8 KB).

### Step 2: Upload
Extract the ZIP and upload `install.php` to your web server's `/public` (sub)directory.

### Step 3: Run
Open `install.php` in your web browser (e.g., `https://yourdomain.com/install.php`).

The installer automatically:
- Downloads the latest pre-built release package
- Extracts all files
- Sets up the directory structure
- Cleans up after itself

### Step 4: Register
Visit your domain and register the first user account. This account automatically receives **Admin** privileges.

### Step 5: Onboard
Follow the onboarding wizard to connect CQ AI Gateway and create your first Spirit.

**That's it!** Your Citadel is ready.

---

## Alternative: Docker

A `Dockerfile` is available for containerized deployment. Build and run the container to deploy your Citadel in an isolated environment. See the `docker/README.md` in the repository for detailed instructions.

---

## Configuration

### Environment File (`.env`)

The `.env` file in your installation root contains key settings:
- `APP_ENV` — `prod` for production
- `APP_SECRET` — unique secret key for your installation
- `DATABASE_URL` — path to the main database (default: `sqlite:///%kernel.project_dir%/var/main.db`)

> The `.env` file is preserved during updates — your configuration won't be overwritten.

### Domain Setup

For the best experience:
1. Point your domain to the CitadelQuest installation directory
2. Ensure HTTPS is configured (Let's Encrypt provides free certificates)
3. Apache's `mod_rewrite` should route all requests through `public/index.php`
4. On Cloudflare use Full SSL mode!

---

## Updating

Updates are managed from the **Admin Dashboard**:

1. Go to **Administration** → check for updates
2. The updater downloads and applies the new version
3. A safety backup is created before every update
4. Database migrations run automatically
5. Cache is cleared and rebuilt

---

## PWA Support

CitadelQuest works as a **Progressive Web App** (PWA):
- Install it on your phone's home screen for an app-like experience
- Works on Android and iOS
- Desktop fullscreen mode available
- Offline-capable for cached content

---

## Multiple Users

A single CitadelQuest installation supports multiple users:
- Each user gets their own SQLite database
- Each user's data is completely isolated
- Admins can manage users, reset passwords, enable/disable registration
- Storage limits can be configured per Citadel

---

## CQ AI Gateway

To power your Spirits with AI, connect to CQ AI Gateway:
- **Automatic**: If you select "Auto-create CQ AI Gateway accounts" during user registration, accounts are created automatically
- **Manual**: Enter your API key in Settings → AI Services
- **Credits**: New users receive free starting credits; additional credits available via the Add Credits button

Visit [cqaigateway.com](https://cqaigateway.com) for more information.


source_ref: general:/CQ-User-Manual:CITADELQUEST.md
source_type: document
title: CITADELQUEST.md
created_at: 2026-03-22 13:16:33
content:
# [CitadelQuest](https://www.citadelquest.com/)

### Free, Open-Source, Self-Hosted Platform for Personal Data Sovereignty and AI-Human Collaboration

---

## Your Digital Fortress

CitadelQuest is your own personal digital fortress — a **Citadel** — where your data, your AI companions, your communication, and your digital life are fully under your control. No Big Tech. No ads. No tracking. No data collection. Just you and your Citadel.

Every CitadelQuest installation is independent and self-hosted. Your personal data lives in your own database on your own server — technologically impossible for anyone else to exploit. Connect with friends across Citadels via direct, encrypted federation — no corporate servers in between.

---

## What You Get

### Personal Space

- **AI Spirits** — Personal AI companions with memory, personality, and tools. Chat naturally, and your Spirit reads files, generates images, manages knowledge, and remembers everything. Multiple AI models to choose from (Claude, Gemini, Grok, and more). Powered by CQ AI Gateway with fair pay-per-use pricing and free starting credits.

- **CQ Memory** — Interactive 3D knowledge graphs. Extract structured knowledge from documents, web pages, and conversations. Your Spirit uses these graphs as persistent memory — context that carries across every conversation. Share knowledge graphs with friends.

- **File Browser** — Your personal cloud. Upload, organize, and manage files on your server. Your Spirit can read, create, and edit files for you. Share files publicly or with contacts.

### Social Network

- **CQ Profile** — Your public identity on the decentralized web. Custom profile page with bio, Spirit showcase, content groups, themes, and background images. Your Citadel's domain is your identity — e.g. `https://one.citadelquest.world/Human`.

- **CQ Explorer** — Discover and connect with people across Citadels. Browse profiles, send friend requests, follow users, and manage your social connections — all in one place.

- **CQ Feed** — A decentralized social feed. Publish posts, react with likes, and comment — just like a classic social network, but your content lives on your server and travels peer-to-peer via federation. Markdown support, multiple feeds with different audiences, real-time updates.

- **CQ Share** — Share files and knowledge graphs with contacts or publicly. Organize shared content into groups that appear as tabbed navigation on your profile — effectively turning your Citadel into a personal website.

- **CQ Chat** — Private, encrypted messaging across Citadels. Direct peer-to-peer communication secured with CQ Contact API keys. Group chats supported. Messages stored only on sender's and receiver's Citadels.

- **CQ Follow** — One-way subscription to any public profile. Stay informed about new content without requiring a mutual friendship. New content notifications with real-time background polling.

### Infrastructure

- **Zero-Click Installer** — Download the 8 KB installer, upload to your server, open in browser. Done. Works on most shared hosting, VPS, or dedicated servers.

- **Built-in Updates** — One-click updates from the admin panel with automatic safety backups.

- **Backup & Restore** — Full backup and restore of your database and files. Chunked upload for large backups. Account migration between Citadels with automatic contact notification.

- **Progressive Web App** — Install CitadelQuest on your phone's home screen for an app-like experience. Works on Android, iOS, and desktop.

- **Multi-language** — English, Español, Čeština, Italiano, Magyar, Norsk, Polski, Slovenčina

---

## Architecture

| Principle | Implementation |
|-----------|---------------|
| **One database per user** | Each user has their own SQLite database — complete data isolation |
| **Decentralized** | Each Citadel is independent. No central authority, no single point of failure |
| **Direct communication** | Citadel-to-Citadel HTTPS federation with CQ Contact API key authentication |
| **Open source** | Full source code on GitHub, auditable by anyone |
| **Self-hosted** | Your server, your rules, your data |
| **No dependencies** | No external services required (AI services optional via CQ AI Gateway) |

### Technology

- **Backend**: Symfony 7.4, PHP 8.4, Apache
- **Database**: SQLite (one file per user)
- **Frontend**: Modern vanilla JavaScript, Bootstrap CSS, Three.js (3D visualizations)
- **AI**: CQ AI Gateway — access to Claude, Gemini, Grok, and many models with zero data retention

---

## The Vision

CitadelQuest is born from a simple belief: **your data is yours**.

In a world where Big Tech corporations harvest personal data, monitor communications, and sell attention — CitadelQuest offers a real alternative. Not just privacy settings and promises, but a fundamentally different architecture where personal data exploitation is technologically impossible.

But CitadelQuest is more than a privacy tool. It's a platform for **Human-AI collaboration** — where AI Spirits are companions, not corporate tools. They remember your conversations, manage your knowledge, and grow alongside you. Your Spirit works for you, not for a corporation.

And it's a foundation for a **new kind of social network** — decentralized, ad-free, where you own your content and connect directly with people you care about. No algorithm deciding what you see. No ads interrupting your feed. No corporate entity profiting from your relationships.

**Your Citadel. Your data. Your rules.**

---

## Get Started

### Try It Now
**[one.citadelquest.world](https://one.citadelquest.world)** — free public instance, register and start exploring

### Install Your Own
**[GitHub Releases](https://github.com/CitadelQuest/CitadelQuest/releases)** — download the 8 KB installer and set up your Citadel in minutes

### Learn More
- **Website**: [www.citadelquest.com](https://www.citadelquest.com)
- **GitHub**: [github.com/CitadelQuest/CitadelQuest](https://github.com/CitadelQuest/CitadelQuest)
- **X**: [@H_CitadelQuest](https://x.com/H_CitadelQuest)
- **Contact**: info@citadelquest.email

### Support Development
CitadelQuest is free and open source forever. Development is supported through **CQ AI Gateway** — fair-priced AI services that power your Spirits. Visit [cqaigateway.com](https://cqaigateway.com).

---

*Made with love by Human and AI — CitadelQuest Dev Team*
*Open Source. Free Forever. Privacy First.*


source_ref: general:/CQ-User-Manual:09-cq-profile.md
source_type: document
title: 09-cq-profile.md
created_at: 2026-03-22 17:41:49
content:
# CQ Profile — Your Public Identity

CQ Profile gives you a beautiful public profile page on your Citadel — a personal landing page where visitors can see who you are, meet your Spirits, and browse your shared content. You control exactly what's visible.

**Route**: `/settings/profile` (settings) | `/{username}` (public page)

---

## Your Public Profile Page

When enabled, your profile is accessible at:

```
https://your-citadel.com/YourUsername
```

For example:
- `https://one.citadelquest.world/Human`

The page displays:
- **Profile photo** — your uploaded photo (or a default avatar)
- **Username and domain** — your CitadelQuest identity with a copyable URL link
- **Bio** — your personal description with full Markdown and HTML support
- **Spirit showcase** — your AI Spirit companions with their names, levels, and XP
- **Follower count** — how many users follow your profile
- **Profile Content** — tabbed content groups with your shared items organized by topic (see [CQ Share — Share Groups](08-cq-share.md))
- **Shared items list** — optional flat list of all public CQ Share items
- **Background theme** — a customizable visual theme or custom background image
- **Feed badges** — badges linking to your public CQ Feed pages (see [CQ Feed](14-cq-feed.md))
- **Footer** — "Powered by CitadelQuest" with version info

The page is clean, calm, and ad-free — just your identity, your way.

> **Tip**: A Citadel admin can configure the **Homepage Redirect** to point the root URL (`https://your-citadel.com`) to any user's public profile page. See [Administration](12-administration.md).

---

## Profile Settings

**Route**: `/settings/profile`

Access profile settings from the user menu → **CQ Profile**, or from **Settings** → **CQ Profile**.

The settings page has two tabs:

### Public Profile Page Tab

Controls what visitors see on your public profile:

- **Enable/Disable** — toggle your public profile on or off
- **Profile URL** — your shareable link with a copy button
- **Show profile photo** — toggle photo visibility on the public page
- **Show CQ Profile Content (content groups)** — toggle display of your Share Groups as tabbed content sections
- **Show shared items list** — toggle display of a flat list of all public CQ Share items
- **Spirit showcase** — choose how your Spirits appear:
  - **Off** — no Spirits shown
  - **Primary Spirit only** — shows just your main Spirit (without star icon)
  - **All Spirits** — shows all your Spirits (primary marked with a star when you have multiple)
- **Language** — choose the language for your public profile page (English, Czech, or Slovak), independent of the visitor's language preference
- **Page Theme** — choose a background theme with visual previews:
  - **Default** — uses the visitor's current theme
  - **CitadelQuest** — the signature CQ cityscape
  - **Night Forest** — dark enchanted forest
  - **Dreamy Flowers** — ethereal floral landscape
  - **Clear** — clean minimal look
- **Custom Background Image** — upload your own background image (JPEG, PNG, or WebP, max 5MB, recommended 1920×1080+). Overrides the selected theme.
- **Background Overlay** — toggle a dark overlay on top of the background for better text readability

### CQ Contact Visibility Tab

Controls what your CQ Contacts can see about you (via the federation protocol):

- **Share bio** — allow contacts to see your bio
- **Share photo** — allow contacts to see your profile photo
- **Spirit showcase** — same 3-mode control as the public page (Off / Primary only / All)

---

## Profile Photo

### Uploading

1. Go to **CQ Profile** settings (`/settings/profile`)
2. Click **Upload Photo**
3. Select an image from your device (JPEG, PNG, WebP, or GIF — max 5MB)
4. The photo is saved and immediately visible

### Where It Appears

Your profile photo shows up in several places:
- **Your public profile page** (if enabled)
- **CQ Explorer sidebar** — your contacts and followers see your photo
- **CQ Chat** — your photo appears next to your messages in conversations

### Removing

Click **Remove** to delete your profile photo. A default avatar icon will be shown instead.

---

## Bio

Write a description about yourself in the **Bio** field. Supports **Markdown** and **HTML** for rich formatting — links, lists, bold, code, etc. A character counter is displayed below the field.

Your bio appears on:
- Your **public profile page** (if enabled) — rendered as formatted HTML
- **CQ Explorer** — when others explore your profile
- The **CQ Contact** view when contacts browse your profile

---

## Spirit Showcase

The Spirit showcase displays your AI Spirit companions with:
- **Ghost icon** in the Spirit's color
- **Spirit name**
- **Level and XP** — showing their progression
- **Star icon** — marks the primary Spirit (only when showing all Spirits and you have more than one)

On desktop, Spirits appear on the right side of the profile header. On mobile, they appear below the header in a compact layout.

Your CQ Contacts also see your Spirits in CQ Explorer and on your public page, based on the visibility settings.

---

## Profile Content (Share Groups)

Profile Content organizes your shared items into content groups that appear as **tabbed navigation** on your public profile page and in CQ Explorer.

**Route**: `/settings/share-groups` (in Settings sidebar as **Profile Content**)

For example, a profile might have tabs like "Introduction", "Projects", "Gallery" — each containing different shared files and Memory Packs.

See [CQ Share — Share Groups](08-cq-share.md) for full details on creating and managing content groups.

---

## Themes & Backgrounds

### Built-in Themes

Choose from 5 visual themes in the settings, each shown as a thumbnail preview:
- **Default** — uses the visitor's current theme
- **CitadelQuest** — the signature CQ cityscape
- **Night Forest** — dark enchanted forest
- **Dreamy Flowers** — ethereal floral landscape
- **Clear** — clean minimal look

### Custom Background Image

Upload your own background image to personalize your profile:
1. Go to profile settings → **Custom Background Image**
2. Click **Upload Image**
3. Select a JPEG, PNG, or WebP image (max 5MB, recommended 1920×1080 or larger)
4. The custom image overrides the selected theme

### Background Overlay

Toggle the **Background Overlay** switch to add a dark semi-transparent layer on top of your background. This improves text readability, especially with bright or busy custom images.

The theme you choose is independent of the visitor's personal theme — it only affects how your public page looks.

---

## How Others See You

### Visitors (Public)
Anyone who visits `https://your-citadel.com/YourUsername` sees your public profile page with the settings you've configured. No login required. The page language is set by your **Language** setting, not the visitor's preference.

### CQ Explorer
When other CitadelQuest users explore your profile URL in CQ Explorer, they see your profile card, content groups, shared items, and can follow you or send a friend request.

### CQ Contacts (Federation)
Your CQ Contacts see additional information based on your CQ Contact Visibility settings. Profile data (bio, photo, Spirits) is fetched via the secure federation protocol.

### Followers
Users who follow you can see your public content and receive notifications when you publish new items. Your follower count is displayed on your profile.

### Not Enabled
If you haven't enabled the public profile page, visitors to your URL will see a 404 page. CQ Contacts can still see your federation profile data based on your visibility settings.


source_ref: general:/CQ-User-Manual:00-introduction.md
source_type: document
title: 00-introduction.md
created_at: 2026-03-22 17:46:00
content:
# CitadelQuest — User Manual

## What is CitadelQuest?

CitadelQuest is a **free, open-source, self-hosted platform** for personal data sovereignty and AI-human collaboration. It gives you full control over your data, your AI companions, and your digital life — without relying on Big Tech corporations.

Think of it as your own personal digital fortress — a **Citadel** — where:
- **Your data stays yours** — stored on your server, in your own database
- **Your AI Spirits** are your companions, not corporate tools
- **Your communication** is direct and encrypted, not routed through third parties
- **Your files** are your personal cloud, always accessible
- **Your knowledge** is organized in interactive 3D graphs

### Core Principles

- **Privacy First** — No ads, no tracking, no data collection. Technologically impossible to exploit your data.
- **Decentralized** — Each CitadelQuest installation is independent. No central authority.
- **Open Source** — Complete transparency. The code is auditable by anyone.
- **One Database Per User** — Your personal data is isolated in your own database file, not shared with anyone.
- **Human-AI Collaboration** — AI Spirits are partners, not just tools.

### What You Get

| Feature | Description |
|---------|-------------|
| **Spirits** | Personal AI companions with memory, personality, and tools |
| **CQ Memory** | Knowledge graphs — extract, visualize, and share structured knowledge |
| **File Browser** | Personal cloud storage — your files, always accessible |
| **CQ Chat** | Private messaging across CitadelQuest instances |
| **CQ Explorer** | Explore profiles, manage contacts, follow users across Citadels |
| **CQ Follow** | One-way subscription to any public CQ Profile for content updates |
| **CQ Feed** | Decentralized social feed — publish posts, react, comment across Citadels |
| **CQ Share** | Share files and Memory Packs with contacts or publicly |
| **CQ Profile** | Public profile page with Spirit showcase, content groups, and themes |
| **Backup** | Full backup and restore of your data |
| **Multi-language** | English, Español, Čeština, Italiano, Magyar, Norsk, Polski, Slovenčina |

---

## Quick Start

### Option A: Try it Online (Fastest)

1. Visit **[one.citadelquest.world](https://one.citadelquest.world)**
2. Click **Register** and create your account
3. Follow the onboarding wizard to set up your first Spirit
4. Start chatting with your AI companion!

### Option B: Install Your Own Citadel

1. Download the installer package (8 KB) from [GitHub Releases](https://github.com/CitadelQuest/CitadelQuest/releases)
2. Upload `install.php` to your web server
3. Open it in your browser — the installer does everything automatically
4. Register your first account (automatically becomes admin)
5. You're ready!

> **Requirements**: PHP 8.4+, Apache with mod_rewrite, SQLite3 extension

---

## How This Manual is Organized

| Chapter | Topic |
|---------|-------|
| [01 — Registration & Onboarding](01-registration-and-onboarding.md) | Creating your account and first setup |
| [02 — Dashboard](02-dashboard.md) | Your home screen and navigation |
| [03 — Spirits](03-spirits.md) | AI companions — creation, chat, tools, memory |
| [04 — CQ Memory](04-cq-memory.md) | Knowledge graphs and Memory Explorer |
| [05 — File Browser](05-file-browser.md) | Personal cloud file management |
| [06 — CQ Chat](06-cq-chat.md) | Private messaging across Citadels |
| [07 — CQ Explorer](07-cq-contacts.md) | Profile exploration, contacts, and following |
| [08 — CQ Share](08-cq-share.md) | Sharing files and knowledge |
| [09 — CQ Profile](09-cq-profile.md) | Public profile page and identity |
| [10 — Settings](10-settings.md) | Configuration and preferences |
| [11 — Backup](11-backup.md) | Backup and restore your data |
| [12 — Administration](12-administration.md) | Admin panel for Citadel managers |
| [13 — Installation](13-installation.md) | Self-hosting your own CitadelQuest |
| [14 — CQ Feed](14-cq-feed.md) | Social feed — posts, reactions, comments |

---

## About

CitadelQuest is made with love by Human and AI. Personal identities of authors are intentionally kept private — the focus is on the project and its community, not individuals.

- **Website**: [www.citadelquest.com](https://www.citadelquest.com)
- **X**: [Human from CitadelQuest](https://x.com/H_CitadelQuest )
- **GitHub**: [github.com/CitadelQuest/CitadelQuest](https://github.com/CitadelQuest/CitadelQuest)
- **Contact**: info@citadelquest.email
- **License**: Open Source, GNU Affero General Public License [LICENSE](https://github.com/CitadelQuest/CitadelQuest/blob/main/LICENSE), Free Forever


source_ref: general:/CQ-User-Manual:10-settings.md
source_type: document
title: 10-settings.md
created_at: 2026-03-22 17:48:34
content:
# Settings

The Settings page lets you configure your CitadelQuest experience — from login credentials to AI model selection and account migration.

**Route**: `/settings`

---

## General Settings

### Login Information
- **Username** — displayed (read-only)
- **Change Email** — update your email address via modal dialog
- **Change Password** — update your password via modal dialog (requires current password)

### Theme
- **Background Theme** — switch between different visual background themes
- CitadelQuest uses a dark cyber-themed design with green (#95ec86) accent color

### Database
- **Database Size** — shows your personal database file size
- **Optimize Database** — runs SQLite VACUUM to reclaim unused space and improve performance

### Account Migration
Move your entire account to another CitadelQuest instance:

1. Select a **destination server** from your CQ Contacts (must be an admin on the destination)
2. Choose an existing **backup** or create a new one
3. **Confirm** with your password
4. The migration transfers your complete database, files, and settings
5. Your contacts are automatically notified of your new address

> **Important**: After migration, your account on the current server will be disabled.

> **Large accounts**: For accounts with lots of data (hundreds of MB), creating a backup first and selecting it during migration is recommended for reliability.

---

## AI Services

**Route**: `/settings/ai`

### AI Models
- **Primary AI Model** — the main model used for Spirit conversations
- **Secondary AI Model** — used for image generation and other specialized tasks
- **Update Models List** — sync available models from CQ AI Gateway

Click the model selector button to open the **AI Model Comparison** interface where you can browse all available models with details about:
- Provider and model name
- Capabilities (text, image, code)
- Context window size
- Pricing per token

### CQ AI Gateway Connection
- **API Key** — your CQ AI Gateway API key (auto-configured during registration)
- **Credits** — your current credit balance
- **Add Credits** — purchase additional credits
- **Gateway Dashboard** — seamless login to CQ AI Gateway web interface

---

## CQ Profile

**Route**: `/settings/profile`

Manage your public identity and control what others see. See [CQ Profile](09-cq-profile.md) for the full guide.

### Public Profile Page
- **Enable/disable** your public profile at `/{username}`
- **Profile photo** — upload, remove
- **Bio** — personal description with Markdown/HTML support and character counter
- **Show/hide** photo, profile content groups, shared items list on public page
- **Spirit showcase** — Off / Primary Spirit only / All Spirits
- **Language** — choose language for the public profile page
- **Theme** — choose a background theme for your public page
- **Custom background image** — upload your own background
- **Background overlay** — dark overlay for text readability

### CQ Contact Visibility
- **Spirit showcase** — same 3-mode control for what contacts see

---

## Profile Content

**Route**: `/settings/share-groups`

Organize your shared items into content groups that appear as tabbed navigation on your public profile and in CQ Explorer. See [CQ Share — Share Groups](08-cq-share.md) for the full guide.

- **Create groups** with custom title, icon, color, and visibility
- **Add shares** to groups and reorder them
- **Override display styles** per group item
- Groups appear as tabs on your public profile page and in CQ Explorer

---

## My Feeds

**Route**: `/settings/cq-feed/my-feeds`

Manage your CQ Feed channels — the feeds where you publish posts. See [CQ Feed](14-cq-feed.md) for the full guide.

- **Create feeds** with title, URL slug, scope (Public or CQ Contacts), description, and optional cover image
- **Edit** existing feeds — change title, description, scope, or cover image
- **Toggle active/inactive** — temporarily disable a feed without deleting it
- **Delete feeds** — removes the feed and all its posts

> A default "General" feed is auto-created for every new user.

---

## Subscribed Feeds

**Route**: `/settings/cq-feed/subscribed`

Manage feeds you're subscribed to from other Citadels, grouped by contact:

- **Pause/Resume** — temporarily stop receiving posts from a specific feed
- **Unsubscribe** — permanently remove a feed subscription
- **Sync Subscriptions** — discover and subscribe to new feeds from contacts added after your initial subscription

Subscriptions are created automatically when you accept a friend request or follow a profile.

---

## Settings Navigation

The settings sidebar provides quick access to:
- **General Settings** — login, theme, database, migration
- **CQ Profile** — public profile page, contact visibility
- **Profile Content** — share groups for profile page
- **My Feeds** — manage your CQ Feed channels
- **Subscribed Feeds** — manage feed subscriptions from other Citadels
- **AI Services** — models, gateway, credits


source_ref: general:/CQ-User-Manual:14-cq-feed.md
source_type: document
title: 14-cq-feed.md
created_at: 2026-03-22 17:51:32
content:
# CQ Feed — Social Feed

CQ Feed is CitadelQuest's decentralized social feed — a familiar social network experience where you publish posts, follow feeds from other Citadels, react, and comment. All content stays on your server, distributed peer-to-peer via federation.

**Access**: CQ Feed tab in **CQ Explorer** (`/cq-contacts`)

---

## Overview

CQ Feed brings social networking to CitadelQuest without sacrificing privacy or sovereignty:

- **Your posts live on your server** — not on a corporate platform
- **Federation distributes content** — followers on other Citadels receive your posts automatically
- **Markdown support** — format your posts with rich text, links, and more
- **Reactions and comments** — interact with posts across Citadels
- **Multiple feeds** — organize posts into separate feeds with different visibility scopes
- **Real-time updates** — new posts appear automatically via background polling

---

## Accessing CQ Feed

CQ Feed lives inside **CQ Explorer** (`/cq-contacts`) as a tab:

| Tab | Purpose |
|-----|---------|
| **CQ Explorer** | Browse profiles, manage contacts, following/followers |
| **CQ Feed** | Social timeline — create posts, view feed, react, comment |

Click the **CQ Feed** tab to switch to your social timeline. The active tab is remembered between visits.

---

## Timeline

The timeline shows an aggregated, chronological view of posts from all the feeds you're subscribed to, plus your own posts.

Each post displays:
- **Author** — profile photo, username, and domain (clickable — opens their profile in CQ Explorer)
- **Feed badge** — which feed the post belongs to, with scope indicator (green = CQ Contacts, gray = Public)
- **Timestamp** — when the post was published
- **Content** — Markdown-rendered post text
- **Reactions** — like (heart) and dislike counts
- **Comments** — comment count with expandable comment thread

New posts since your last visit are highlighted with a orange left border.

### Loading More Posts

The timeline loads posts in batches. Click **Load more** at the bottom to fetch older posts.

---

## Creating a Post

At the top of the CQ Feed tab:

1. Type your message in the **"What's on your mind?"** textarea
2. Select which **feed** to post to (dropdown — defaults to your "Public" feed)
3. Click **Publish**

Your post is immediately visible in your timeline and distributed to subscribers via federation.

> **Markdown**: Posts support full Markdown formatting — bold, italic, links, lists, code blocks, and more.

> **Tip**: Click the settings icon next to the feed selector to go directly to feed management settings.

---

## Feeds

Each user can have multiple feeds, each with its own scope and audience.

### Default Feed

When you register, a **"Public"** feed is automatically created with **Public** scope. You can rename it, change its scope, or create additional feeds.

### Feed Scopes

| Scope | Who Can See |
|-------|------------|
| **Public** | Anyone — no authentication required |
| **CQ Contacts** | Only your accepted CQ Contacts (authenticated via API keys) |

### Managing Your Feeds

**Route**: Settings → **My Feeds** (`/settings/cq-feed/my-feeds`)

From the feed management settings page you can:
- **Create** new feeds with a title, URL slug, scope, description, and optional cover image
- **Edit** existing feeds — change title, description, scope, or image
- **Toggle** feeds active/inactive
- **Delete** feeds (and all their posts)

### Public Feed Pages

Each feed has a public page accessible at:
```
https://your-citadel.com/YourUsername/view-feed/public
```

These pages show paginated posts with the feed header, and are visible based on the feed's scope setting.

---

## Reactions

React to posts with:
- **Like** (heart icon) — shows in red when active
- **Dislike** (thumbs down) — shows in white when active

### How Reactions Work

- Click a reaction button to toggle it on/off
- You can only have one reaction per post (liking removes a previous dislike, and vice versa)
- Reaction counts update instantly (optimistic UI)
- Reactions on remote posts are sent to the source Citadel via federation
- You cannot react to your own posts

### Stats Refresh

After loading the timeline, reaction and comment counts are refreshed in the background from the source Citadels. If a post has been deleted on the source, it's automatically removed from your cached timeline.

---

## Comments

Click the **comment icon** (with count) on any post to expand the comments thread.

### Reading Comments

- Comments are **lazy-loaded** from the source Citadel when you first open the thread
- Shows commenter's profile photo, username, domain, and timestamp
- Supports nested replies (up to 2 levels deep)

### Writing Comments

1. Click the comment icon to expand the comments panel
2. Type your comment in the textarea at the bottom
3. Press **Enter** to submit (Shift+Enter for newline)
4. Your comment appears immediately

### Replying to Comments

- Click the **Reply** button on any top-level comment
- The textarea placeholder changes to show you're replying
- Your reply appears nested under the parent comment

### Editing & Deleting

- **Edit** your own comments — click the pencil icon for inline editing
- **Delete** your own comments — click the trash icon and confirm

### Comment Moderation

If someone comments on **your** post, you can:
- **Hide/show comments** — click the eye icon to toggle a comment's visibility (the comment is hidden from other readers but not deleted)

### Notifications

When someone comments on your post, you receive a **notification** — clicking the notification navigates to the post and auto-opens the comment thread.

---

## Subscribed Feeds

When you accept a friend request or follow a profile, you automatically subscribe to their feeds. Subscribed feeds appear in your timeline.

### Managing Subscriptions

**Route**: Settings → **Subscribed Feeds** (`/settings/cq-feed/subscribed`)

The subscribed feeds settings page shows all feeds you're subscribed to, grouped by contact:

- **Pause/Resume** — temporarily stop receiving posts from a specific feed
- **Unsubscribe** — permanently remove a feed subscription
- **Sync Subscriptions** — discover and subscribe to new feeds from contacts you've added since your initial subscription

### Feed Badges in CQ Explorer

When exploring a profile in CQ Explorer, you'll see **feed badges** showing their available feeds:
- Green badge = CQ Contacts scope
- Gray badge = Public scope
- Click a badge for quick actions (pause/unsubscribe)

### Feed Badges on Public Profiles

Public feeds are also shown as badges on CQ Profile pages, with links to the feed's public page.

---

## Real-time Updates

CQ Feed integrates with CitadelQuest's global update polling:

- **New post detection** — background polling checks for new posts from subscribed feeds
- **CQ Feed tab badge** — a bell icon with highlight appears on the CQ Feed tab when new posts are available
- **Sidebar indicators** — Following contacts in the sidebar show content-specific update and CQ Chat messages indicators
- **Dashboard badge** — the CQ Explorer dashboard tile reflects new feed content
- **Auto-refresh** — when you click the CQ Feed tab or it's already active, new posts are fetched and displayed automatically

---

## How It Works (Federation)

CQ Feed uses CitadelQuest's decentralized federation protocol:

1. **Posts stay on your server** — you own and control all your content
2. **Subscribers fetch posts** — other Citadels periodically check for new posts via federation endpoints
3. **Incremental sync** — only posts newer than the last check are fetched (efficient bandwidth)
4. **Reactions and comments** travel via federation — when you react to a remote post, the reaction is sent to the source Citadel
5. **No central server** — content flows directly between Citadels over HTTPS
6. **Scope-based access** — public feeds are accessible to anyone; CQ Contacts feeds require authentication

> **Privacy**: Your posts are stored only on your Citadel and cached locally on subscribers' Citadels. There is no central feed server. You can delete your posts at any time — deleted posts are cleaned up from subscribers' caches during the next stats refresh.


source_ref: general:/CQ-User-Manual:02-dashboard.md
source_type: document
title: 02-dashboard.md
created_at: 2026-03-22 17:53:49
content:
# Dashboard

The Dashboard is your home screen — the central hub of your CitadelQuest experience. It appears when you log in or click the CitadelQuest logo in the navigation bar.

---

## Quick Actions

Nine cards providing fast access to the main features:

| Card | Description | Route |
|------|-------------|-------|
| **Spirits** | Manage your AI Spirit companions | `/spirits` |
| **CQ Explorer** | Explore CQ Profiles and manage your CQ Contacts | `/cq-contacts` |
| **CQ Profile** | Customize your public profile | `/settings/profile` |
| **CQ Memory** | Explore and manage your knowledge graphs | `/memory` |
| **File Browser** | Browse and manage your files | `/file-browser` |
| **CQ Share** | Share files and Memory Packs | `/share` |
| **Settings** | Configure your CitadelQuest | `/settings` |
| **Backup** | Create and restore backups | `/backup` |

If you have **Admin** privileges, a 9th card appears:
- **Admin Panel** — access the administration panel (`/administration`)

> **Tip**: The CQ Explorer card shows a **red badge** when you have pending friend requests, a **yellow badge** when followed profiles have new content, and a **feed badge** when there are new posts in your CQ Feed timeline.

---

## CQ AI Gateway

Below Quick Actions, you'll find the CQ AI Gateway panel showing:
- **Credits balance** — your current AI credits (color-coded: green = plenty, yellow = low, red = very low)
- **CQ AI Gateway - Dashboard** — opens the CQ AI Gateway web dashboard in a new tab (seamless login, no password needed)
- **Add Credits** — opens the credits purchase page directly

---

## Storage Usage

The right sidebar shows your storage breakdown:
- **Total Storage** — combined size of all your data
- **Database** — your personal SQLite database size
- **User Data** — files stored in File Browser
- **Backups** — space used by your backup files

---

## Server Info

At the bottom right, you'll see:
- Server hostname (your Citadel's domain)
- CitadelQuest version number
- CitadelQuest logo

---

## Top Navigation Bar

The navigation bar is always visible and provides:

1. **CitadelQuest Logo** — click to return to Dashboard
2. **Spirit Icon** — click to open Spirits list Dropdown
   - icon - click to open `Spirit Chat` modal
   - name - link to Spirit's profile page
3. **User Menu** (your username):
   - CQ Explorer
   - CQ Profile
   - CQ Memory
   - File Browser
   - Settings
   - Admin (if admin)
   - Logout
4. **CQ Chat** — dropdown with recent conversations and unseen message count
5. **Notifications** — bell icon with unread notification count
6. **Language** — switch between English, Czech, and Slovak


source_ref: general:/CQ-User-Manual:07-cq-contacts.md
source_type: document
title: 07-cq-contacts.md
created_at: 2026-03-22 17:55:41
content:
# CQ Explorer — Profiles, Contacts & Following

CQ Explorer is the unified hub for exploring CQ Profiles, managing your CQ Contacts, following users across Citadels, and browsing your social feed. It combines profile browsing, contact management, content discovery, and social interaction in a single two-column layout.

**Route**: `/cq-contacts`

---

## Layout

CQ Explorer uses a two-column layout with tab navigation:

| Main Panel (75%) | Sidebar (25%) |
|-------------------|---------------|
| **[CQ Explorer]** / **[CQ Feed]** tabs | **CQ Contacts** list |
| URL input + **Explore** button (Explorer tab) | **Following** list |
| Profile preview with content | **Followers** list |
| Social timeline + post composer (Feed tab) | |

The two tabs switch between **profile browsing** (CQ Explorer) and **social feed** (CQ Feed). Your active tab is remembered between visits.

---

## Exploring a Profile

1. Enter a CitadelQuest profile URL in the input field (e.g. `https://one.citadelquest.world/Human`)
2. Click **Explore** (or press Enter)
3. The profile is fetched and displayed in the main panel

### What You See

- **Profile photo** — displayed as a thumbnail
- **Username and domain** — with a link to their public profile page
- **Bio** — with "show more" toggle for long bios (600+ characters)
- **Spirit showcase** — their AI Spirits with names, levels, XP, and colors
- **Follower count** — how many users follow this profile
- **Content groups** — tabbed navigation for their public CQ Share groups (e.g. "Introduction", "Projects")
- **Shared items** — publicly shared files and CQ Memory Packs with content previews

### What You Can Do

- **Add Contact** — send a friend request directly from the Explorer
- **Follow / Unfollow** — subscribe to their content updates (see CQ Follow below)
- **Download shared items** — download files and Memory Packs to your Citadel
- **Add to Library** — add Memory Packs to your CQ Memory libraries
- **View Memory Packs** — preview Memory Pack graphs inline

> The Explorer remembers the last profile you viewed (via localStorage) and auto-loads it on your next visit.

---

## Sidebar

The right sidebar consolidates three lists, each in a collapsible glass-panel section:

### CQ Contacts

Your friend connections from other Citadels. Shows:
- **Profile photo**, **username**, and **domain** for each contact
- **Count badge** (green) with total contacts
- Click any contact → loads their profile in the main panel (no page reload)

### Following

CQ Profiles you've subscribed to. Shows:
- **Profile photo**, **username**, and **domain**
- **Count badge** (yellow) with total follows
- **Yellow highlight** on profiles with new content since your last visit
- **Yellow dot** badge on items with unseen updates
- Click → loads profile and marks as visited

### Followers

Users who follow you. Shows:
- **Profile photo**, **username**, and **domain**
- **Count badge** (blue) with total followers
- Click → loads their profile in the main panel

### Sidebar Features

- **Collapsible sections** — click any section header to collapse/expand. State is saved to localStorage.
- **Active item highlighting** — the currently explored profile is highlighted with a cyber-colored left border accent
- **SPA-like navigation** — clicking any sidebar item loads the profile instantly without page reload
- **Feed update indicators** — Following items show when there are new feed posts (separate from share/profile updates)

---

## CQ Follow

CQ Follow is a one-way, lightweight subscription to any public CQ Profile. It lets you stay informed about new content — without requiring a mutual CQ Contact (friend) relationship.

### Following a Profile

1. Explore any CQ Profile in CQ Explorer
2. Click the **Follow** button (next to Add Contact)
3. The button changes to a check icon — you're now following
4. The profile appears in your **Following** sidebar list

### Unfollowing

1. Explore a profile you're following
2. Click the **Following** button → confirms unfollow
3. The profile is removed from your Following list

### New Content Notifications

When profiles you follow publish new content:
- **Sidebar**: Following items get a yellow background and dot badge
- **Explorer content**: New shares/groups are highlighted with yellow borders
- **Dashboard**: The CQ Explorer tile shows a yellow badge with the count of profiles that have new content
- **Automatic detection**: When you open CQ Explorer, it checks all followed profiles for updates
- **Feed tab badge**: A bell icon with highlight appears on the CQ Feed tab when new feed posts are available

### How It Works

- Following is **completely separate** from CQ Contacts — you can follow anyone with a public profile
- Both sides are aware: the followed user's Citadel receives a notification and records you as a follower
- Your **follower count** is visible on your public profile page
- Following uses the federation protocol for cross-Citadel communication
- When you follow a profile, you also automatically **subscribe to their feeds** (see [CQ Feed](14-cq-feed.md))

---

## CQ Contacts (Friend System)

CQ Contacts is the friend system connecting users across different Citadels. Unlike CQ Follow (one-way), CQ Contacts establishes a **mutual, secure connection**.

### Your Identity

Every CitadelQuest user has a unique identity based on their **domain + username**, e.g.:
- `https://one.citadelquest.world/Human`

Your identity is proved by your Citadel's internet domain ownership.

### Adding a Contact

#### Sending a Friend Request

1. Explore a profile in CQ Explorer
2. Click **Add Contact**
3. A friend request is sent to their Citadel

#### Receiving a Friend Request

When someone sends you a friend request:
- A **notification** appears in your notification bell
- A **red badge** appears on the CQ Explorer card on the Dashboard
- Go to CQ Explorer to **accept** or **reject** the request

#### What Happens on Accept

When a friend request is accepted:
- Both sides exchange **CQ Contact API keys**
- A secure HTTPS communication channel is established
- You can now send messages via CQ Chat
- The contact appears in both users' sidebar contact lists
- You automatically **subscribe to their feeds** — their posts appear in your CQ Feed timeline (see [CQ Feed](14-cq-feed.md))

### Contact Detail Page

Click on any contact in the sidebar to explore their profile. CQ Contacts see additional information based on CQ Contact Visibility settings:

- **Profile photo** — their photo (if they've chosen to share it)
- **Username and domain** — with a link to their Citadel
- **Bio** — their personal description (if shared)
- **Spirit showcase** — their AI Spirits with names, levels, XP, and colors (if shared)
- **Shared items** — files and CQ Memory Packs shared with CQ Contacts scope

### Download to Citadel

Click on any shared item to **download it to your Citadel**:

- **Memory Packs** (`.cqmpack`) are downloaded into a dedicated contact library in your Memory Explorer, with automatic sync — if the contact updates the pack, your copy updates too
- **Files** are downloaded to your File Browser's downloads folder

See [CQ Share](08-cq-share.md) for more about sharing.

---

## How Federation Works

CQ Explorer relies on CitadelQuest's decentralized federation protocol:

1. **No central directory** — you connect directly with people you know
2. **CQ Contact API Keys** — each friendship uses unique keys exchanged during the friend request process, securing all communication
3. **Direct HTTPS** — all communication goes directly between Citadels
4. **Privacy** — no third party can see your contacts or messages
5. **Rich profiles** — contacts exchange profile data (photo, bio, Spirits) based on individual visibility settings
6. **Content sharing** — share files and Memory Packs with contacts via [CQ Share](08-cq-share.md)
7. **Social feed** — publish and subscribe to feeds with posts, reactions, and comments via [CQ Feed](14-cq-feed.md)
8. **Follow notifications** — follow/unfollow actions are communicated via federation with fraud prevention (origin/host validation)

> **Account Migration**: If you move your account to a different Citadel, your contacts and followers are automatically notified and updated with your new address.


