| c724e8699824d453… | During Phase 5, new client sub-sets must be added as engagements begin so that the graph can represent newly active client relationships over time. | active | contextual | yes | |
| 762e191d963f1e91… | During Phase 5, set boundaries must be refined based on usage patterns so that the organizational structure evolves according to how the system is actually used. | active | contextual | yes | |
| 1dabd52ff2d086c2… | During Phase 5, extraction must be expanded to new source documents so that the knowledge graph continues to grow as additional materials become available. | active | contextual | yes | |
| b261b8b829c924d0… | During Phase 5, AmbientAgent gap detection reports must be reviewed weekly so that missing knowledge or coverage gaps are identified on a regular cadence. | active | contextual | yes | |
| 93457193fd30c636… | During Phase 5, the team must monitor Q-value learning and adjust retrieval weights so that retrieval behavior can be improved based on observed learning outcomes. | active | contextual | yes | |
| b6f97f130bf9226d… | Implementation Phase 5 is the Continuous Improvement phase and it is ongoing so that the system can be refined after initial deployment and integration. | active | contextual | yes | |
| b5722639e16164db… | During Phase 4, the team must set up Granola continuous extraction so that meeting transcripts are continuously incorporated into the knowledge graph. | active | contextual | yes | |
| e4e5d11fb9f9fdda… | During Phase 4, the daily research task must be updated to use the live context engine so that research workflows rely on current graph-backed context. | active | contextual | yes | |
| 30bb044eddc80367… | During Phase 4, the team must connect the system to Claude Code through MCP configuration so that Claude Code can access the context engine. | active | contextual | yes | |
| 2e22b8c6bd4b0055… | During Phase 4, the team must connect the system to Cowork through an MCP connector so that Cowork can use the context engine via MCP. | active | contextual | yes | |
| bcc8a35acb1e2ac3… | During Phase 4, the team must deploy the Context Engine MCP Server so that the knowledge system can be accessed through the MCP interface. | active | contextual | yes | |
| 17ed60a68299c482… | Implementation Phase 4 is the MCP Server and Agent Integration phase and is scheduled for two weeks so that external tool and agent connectivity is added after core extraction phases. | active | contextual | yes | |
| eb7110666c5a90b4… | During Phase 3, the team must enable CORTEX agents including Retrieval, Learning, and Ambient so that agent-based capabilities become available for the knowledge system. | active | contextual | yes | |
| 6efa72eaf8247d3c… | During Phase 3, the team must extract FINANCIAL_OPS from financial documents so that operational financial knowledge is available in the graph. | active | contextual | yes | |
| 8e1aced2e428df5e… | During Phase 3, the team must extract MARKETING_CONTENT from blog posts and demos so that marketing knowledge is incorporated from public-facing materials. | active | contextual | yes | |
| 440dde430e899aa9… | During Phase 3, the team must extract SECURITY_COMPLIANCE from security documents so that compliance and security knowledge is represented in the system. | active | contextual | yes | |
| 5f7eedc1732c4691… | During Phase 3, the team must extract SALES_POSITIONING from pitch materials so that sales messaging and positioning knowledge is captured. | active | contextual | yes | |
| 93f4997e24270740… | Implementation Phase 3 is the Sales and Operations phase and is scheduled for two weeks so that commercial and operational knowledge is added after client knowledge. | active | contextual | yes | |
| 11e6b725f5710ef1… | During Phase 2, the team must establish GOVERNS, SCOPED_BY, and DELIVERED_UNDER relationships so that client and project knowledge is connected through the intended relationship model. | active | contextual | yes | |
| 9c2d023d979c0929… | During Phase 2, the team must extract PROJECTS knowledge from statements of work and project documents so that project-specific context is represented in the graph. | active | contextual | yes | |
| 5439332bf4271f60… | During Phase 2, the team must extract the remaining client sub-sets so that client knowledge coverage extends beyond the highest-priority account. | active | contextual | yes | |
| 6838b748ab562a56… | During Phase 2, the team must extract the CLIENTS:PATRICK sub-set first because it has the highest priority among client knowledge sources. | active | contextual | yes | |
| b8d84f75bb8fecee… | Implementation Phase 2 is the Client Knowledge phase and is scheduled for two weeks so that client-specific extraction follows the foundation setup. | active | contextual | yes | |
| 9ce242fa94c00490… | During Phase 1, the team must configure initial Named Relationships so that foundational graph connections are available for the first extracted sets. | active | contextual | yes | |
| b65afeee4abe2c18… | During Phase 1, Rank 0 CXUs must undergo manual review and approval so that the most critical extracted units are validated before broader use. | active | contextual | yes | |
| 528c48663481ac95… | During Phase 1, the team must extract the COMPANY_POLICIES set from policy documents so that organizational policy knowledge is represented in the graph. | active | contextual | yes | |
| 71c57adf34ba81d1… | During Phase 1, the team must extract the CONTRACT_STANDARDS set from template documents so that standard contractual knowledge is captured from reusable templates. | active | contextual | yes | |
| 198bf08b8cf2f9c7… | During Phase 1, the team must extract the PYRANA_PLATFORM set from GitHub repositories so that platform knowledge is captured from code-related sources. | active | contextual | yes | |
| 3f7acec65a5c6502… | Implementation Phase 1 is the Foundation Sets phase and is scheduled for two weeks so that core knowledge sets are established after infrastructure is in place. | active | contextual | yes | |
| f5fca25429b34e17… | During Phase 0, the team must create graph hierarchy nodes representing Company to Pillars to Groups so that the base organizational structure exists in the graph. | active | contextual | yes | |
| 4394f9eeaf724aa1… | During Phase 0, the team must set up a Google Drive webhook or polling for synchronization so that source document changes can be detected and ingested. | active | contextual | yes | |
| 1b99837bba405ed2… | During Phase 0, the team must configure the `zeroth-internal` extraction profile so that internal document extraction uses the intended profile settings. | active | contextual | yes | |
| 4826545dd366bc01… | During Phase 0, the team must deploy a context engine instance for internal use that is separate from client instances so that internal knowledge processing remains isolated from client environments. | active | contextual | yes | |
| 698579d5e4687373… | Implementation Phase 0 is the Infrastructure phase and is scheduled for one week so that foundational platform setup occurs before knowledge extraction phases begin. | active | contextual | yes | |
| 9541326a2fa87a3e… | The number of PostgreSQL rows is expected to equal the CXU count plus metadata so that relational storage accounts for both extracted units and their associated metadata. | active | contextual | yes | |
| dfc9f8b5d13cf20b… | The number of Qdrant vectors is expected to equal the CXU count so that vector storage scales directly with the number of extracted context units. | active | contextual | yes | |
| b068f2b76ab97902… | The Neo4j graph is estimated to contain about 100 non-CXU nodes for hierarchy, agents, and memory so that graph storage includes supporting structures beyond extracted units. | active | contextual | yes | |
| e571e6f6435a75fb… | The source corpus is estimated to include more than 150 files so that ingestion and synchronization planning reflects the expected document volume. | active | contextual | yes | |
| d9296b92985a7eab… | The graph is estimated to use about 15 named relationship types and more than 500 relationship instances so that relationship modeling can be sized appropriately. | active | contextual | yes | |
| d5769109fbe1d1e9… | The set hierarchy is estimated to contain 12 top-level sets and approximately 15 sub-sets so that the graph structure can support the planned organizational taxonomy. | active | contextual | yes | |
| 6b84f7014c6c4ebc… | The estimated total CXU count after six months is 3,000 to 5,000 so that medium-term growth expectations are incorporated into capacity planning. | active | contextual | yes | |
| 7a4e97f03931df71… | The estimated initial load for the system is 1,200 to 2,500 total CXUs so that infrastructure planning can account for the expected starting knowledge volume. | active | contextual | yes | |
| b2ee624277cf0ba2… | The Granola integration must flag action items and decisions with high confidence so that important meeting outcomes are emphasized for downstream use or review. | active | contextual | yes | |
| caad75a9c515683a… | Meeting-derived CXUs must be auto-assigned to CLIENTS and PROJECTS sets based on meeting attendees and meeting title so that transcript knowledge is categorized without manual sorting. | active | contextual | yes | |
| 824c6a99497905a7… | Granola meeting transcripts must be processed using the `zeroth-internal` extraction profile so that CXUs from meetings follow the internal extraction configuration. | active | contextual | yes | |
| 70ca286b14ff5845… | After each meeting, the system must query Granola for the transcript so that the latest meeting content becomes available for CXU extraction. | active | contextual | yes | |
| 3d32d2bdf8b4db06… | Granola meeting integration must be configured for continuous extraction from Granola meeting transcripts so that meeting-derived knowledge is regularly incorporated into the system. | active | contextual | yes | |
| 9098b49159fedbb6… | The changed-document extraction workflow must flag potential conflicts between new and existing CXUs for human review so that contradictory or overlapping knowledge can be resolved manually. | active | contextual | yes | |
| a27053aeb4bb1e8d… | The changed-document extraction workflow must assign newly extracted CXUs to appropriate sets after processing changed documents so that the knowledge graph remains organized by set membership. | active | contextual | yes | |
| 9833eb0af9bfc052… | The changed-document extraction workflow must run the extraction pipeline on documents that are new or modified so that updated source content is converted into CXUs after file changes are detected. | active | contextual | yes | |