| cf12a5646956d109… | The document includes an Appendix A titled Full Set Registry so that readers can refer to a dedicated registry of sets beyond the implementation roadmap. | active | contextual | yes | |
| 0ed3e2bc70e39efb… | Phase 5 requires adding new client sub-sets as engagements begin so that the graph can represent newly started client relationships over time. | active | contextual | yes | |
| 61a52c8bdb8cb1d4… | Phase 5 requires refining set boundaries based on usage patterns so that the graph taxonomy evolves in response to actual system use. | active | contextual | yes | |
| 77429793054e10b0… | Phase 5 requires expanding extraction to new source documents so that the knowledge graph continues to grow as additional materials become available. | active | contextual | yes | |
| 499cb8798d12a6dc… | Phase 5 requires reviewing AmbientAgent gap detection reports weekly so that missing knowledge and coverage gaps are regularly identified. | active | contextual | yes | |
| b57c1421d8551749… | Phase 5 requires monitoring Q-value learning and adjusting retrieval weights so that retrieval performance can be continuously tuned based on observed learning behavior. | active | contextual | yes | |
| 8e8f2ac8e92fc802… | Phase 5 of the implementation roadmap is the Continuous Improvement phase and it is ongoing so that the system can be iteratively refined after initial deployment. | active | contextual | yes | |
| ec79a4ec0aa43930… | Phase 4 requires setting up Granola continuous extraction so that meeting transcript ingestion becomes part of the integrated MCP and agent environment. | active | contextual | yes | |
| 7f9a0372f88bd734… | Phase 4 requires updating the daily research task to use the live context engine so that recurring research work benefits from current graph context. | active | contextual | yes | |
| 9d0b56a4cce5e097… | Phase 4 requires connecting the system to Claude Code via MCP configuration so that Claude Code can access the context engine through configured MCP settings. | active | contextual | yes | |
| cf0ab9a4a9f2a127… | Phase 4 requires connecting the system to Cowork via an MCP connector so that Cowork can use the live context engine through MCP. | active | contextual | yes | |
| 23f9293e8de30718… | Phase 4 requires deploying the Context Engine MCP Server so that the context engine can be accessed through MCP-based integrations. | active | contextual | yes | |
| 1c4dd2bc050229f6… | Phase 4 of the implementation roadmap is the MCP Server & Agent Integration phase and is scheduled to last two weeks so that external agent connectivity is added after core knowledge loading. | active | contextual | yes | |
| c00963f0158927de… | Phase 3 enables CORTEX agents for Retrieval, Learning, and Ambient functions so that agent-based capabilities become available after sales and operations knowledge is loaded. | active | contextual | yes | |
| 061a8202491503d9… | Phase 3 requires extracting the FINANCIAL_OPS set from financial documents so that financial operations knowledge is included in the internal graph. | active | contextual | yes | |
| 2c60fc854c725914… | Phase 3 requires extracting the MARKETING_CONTENT set from blog posts and demos so that marketing knowledge is sourced from published and demo materials. | active | contextual | yes | |
| 8dbb6f0c8eaaa146… | Phase 3 requires extracting the SECURITY_COMPLIANCE set from security documents so that compliance and security knowledge is represented in the graph. | active | contextual | yes | |
| 450495691be41758… | Phase 3 requires extracting the SALES_POSITIONING set from pitch materials so that sales messaging knowledge is captured from go-to-market documents. | active | contextual | yes | |
| 764e3287e1e8ee1c… | Phase 3 of the implementation roadmap is the Sales & Operations phase and is scheduled to last two weeks so that commercial and operational knowledge is added next. | active | contextual | yes | |
| fe8afbcf78a3e91d… | Phase 2 requires establishing GOVERNS, SCOPED_BY, and DELIVERED_UNDER relationships so that client and project knowledge is connected through defined relationship types. | active | contextual | yes | |
| dcc21ae3fc22123c… | Phase 2 requires extracting PROJECTS knowledge from statements of work and project documents so that project-specific context is represented in the graph. | active | contextual | yes | |
| c4ce67b95403fd95… | Phase 2 requires extracting the remaining client sub-sets after the highest-priority client set so that broader client coverage is completed. | active | contextual | yes | |
| 90f53d53cab78187… | Phase 2 prioritizes extraction of the CLIENTS:PATRICK sub-set as the highest-priority client knowledge so that the most important client context is ingested first. | active | contextual | yes | |
| 859a82943e2a1510… | Phase 2 of the implementation roadmap is the Client Knowledge phase and is scheduled to last two weeks so that client-specific knowledge is added after foundation sets. | active | contextual | yes | |
| d4133ed71b4503a7… | Phase 1 requires configuring the initial Named Relationships so that foundational graph connections are available once core sets are extracted. | active | contextual | yes | |
| 6cbeb943bba9be27… | Phase 1 includes manual review and approval of Rank 0 CXUs so that the most critical extracted units are validated before broader use. | active | contextual | yes | |
| 3ec82d185cb45c10… | Phase 1 requires extracting the COMPANY_POLICIES set from policy documents so that internal policy knowledge becomes part of the foundation graph. | active | contextual | yes | |
| a70e9a06eb2b2e1a… | Phase 1 requires extracting the CONTRACT_STANDARDS set from template documents so that standard contractual knowledge is captured from reusable templates. | active | contextual | yes | |
| c2d70a10e7deb37c… | Phase 1 requires extracting the PYRANA_PLATFORM set from GitHub repositories so that platform knowledge is loaded into the graph from code-related sources. | active | contextual | yes | |
| 04ac5b6bef640d95… | Phase 1 of the implementation roadmap is the Foundation Sets phase and is scheduled to last two weeks so that core knowledge sets are established after infrastructure. | active | contextual | yes | |
| 538ed5b683e98177… | Phase 0 requires creating graph hierarchy nodes for Company, Pillars, and Groups so that the graph has its initial structural hierarchy. | active | contextual | yes | |
| a0ba3f8230a88667… | Phase 0 requires setting up a Google Drive webhook or polling for synchronization so that source documents can be monitored and synced into the system. | active | contextual | yes | |
| 6093f1ebfc95fcbe… | Phase 0 requires configuring the `zeroth-internal` extraction profile so that internal document extraction uses the designated profile from the start. | active | contextual | yes | |
| 0ad16b76b4842ea2… | Phase 0 requires deploying a context engine instance for internal use that is separate from client instances so that internal knowledge infrastructure is isolated from client environments. | active | contextual | yes | |
| 8b8241f6f0f337c6… | Phase 0 of the implementation roadmap is the Infrastructure phase and is scheduled to last one week so that foundational platform setup occurs first. | active | contextual | yes | |
| 23b4f2d39dbd4067… | The estimated number of non-CXU Neo4j nodes is about 100, covering hierarchy, agents, and memory, so that graph infrastructure beyond CXUs is accounted for. | active | contextual | yes | |
| d9edc2c189e8d018… | The estimated source corpus contains more than 150 files so that document ingestion scope is understood for implementation planning. | active | contextual | yes | |
| 56d83e913f33f75b… | The estimated graph includes about 15 named relationship types and more than 500 relationship instances so that relationship modeling scope is quantified. | active | contextual | yes | |
| 50325e11a37cff88… | The estimated set structure includes 12 top-level sets and approximately 15 sub-sets so that the graph taxonomy has a defined organizational scale. | active | contextual | yes | |
| 8518904dabb1dc4b… | The estimated total CXU count after six months is between 3,000 and 5,000 so that medium-term growth of the knowledge graph is anticipated. | active | contextual | yes | |
| 0ceeb0e4f6764767… | The estimated total CXU count for the initial load is between 1,200 and 2,500 so that implementation planning can size the first ingestion phase. | active | contextual | yes | |
| 8b778d74017a2bdf… | Action items and decisions identified in Granola meeting extraction are flagged with high confidence so that important meeting outcomes are emphasized for downstream use. | active | contextual | yes | |
| e7adc263326ff8bd… | CXUs from Granola meetings are auto-assigned to CLIENTS and PROJECTS sets based on meeting attendees and the meeting title so that meeting knowledge is categorized without manual sorting. | active | contextual | yes | |
| b59b787eb9cb4cbc… | Granola meeting transcripts must be processed with the `zeroth-internal` extraction profile so that extracted CXUs follow the internal extraction configuration. | active | contextual | yes | |
| 4c59b4861580d7bb… | After each meeting, the system queries Granola for the transcript so that the meeting content can be used as the source for CXU extraction. | active | contextual | yes | |
| 829051dd63beb6e1… | Granola meeting integration must be configured for continuous extraction from meeting transcripts so that meeting knowledge is regularly ingested into the system. | active | contextual | yes | |
| 07e311fa438185ae… | The change-processing workflow flags potential conflicts between new and existing CXUs for human review when updated documents are processed so that inconsistencies can be resolved manually. | active | contextual | yes | |
| d2438748d1e2439b… | The change-processing workflow assigns newly extracted CXUs to appropriate sets after processing changed documents so that the knowledge graph remains organized by set membership. | active | contextual | yes | |
| e3168a50dcb9dcec… | The change-processing workflow runs the extraction pipeline on documents that are new or modified so that updated source content is converted into current CXUs. | active | contextual | yes | |
| 77759a0deb9847cf… | The number of PostgreSQL rows is expected to equal the CXU count plus metadata so that relational storage covers both units and their associated metadata. | active | contextual | yes | |