| 26132e86afb8e2e3… | Project knowledge extracted from statements of work and project documents must establish GOVERNS, SCOPED_BY, and DELIVERED_UNDER relationships so that project records are structurally linked within the knowledge graph. | active | contextual | yes | |
| 569b128babf48192… | The document includes an Appendix A titled Full Set Registry, indicating that a complete registry of sets follows this section so that readers can reference the full set inventory. | active | contextual | yes | |
| 21861f0b64da65e9… | During Phase 5, the team must add new client sub-sets as engagements begin so that the graph structure expands in step with new client work. | active | contextual | yes | |
| baad2c93016d4a16… | During Phase 5, the team must refine set boundaries based on usage patterns so that the organizational structure better matches real system use. | active | contextual | yes | |
| 442507c60b72b737… | During Phase 5, the team must expand extraction to new source documents so that the knowledge graph continues to grow with additional inputs. | active | contextual | yes | |
| 4e587791415621f5… | During Phase 5, the team must review AmbientAgent gap detection reports weekly so that missing knowledge or coverage issues are identified on a regular cadence. | active | contextual | yes | |
| bb2998bd97ba5340… | During Phase 5, the team must monitor Q-value learning and adjust retrieval weights so that retrieval performance can improve through ongoing tuning. | active | contextual | yes | |
| 830dcd8fba1af36d… | Phase 5 of the implementation roadmap is the Continuous Improvement phase and it is ongoing so that the system can be refined after initial deployment. | active | contextual | yes | |
| 1daee91c5e833557… | During Phase 4, the team must set up Granola continuous extraction so that meeting transcript ingestion becomes part of the integrated system. | active | contextual | yes | |
| 2565993dffebd40b… | During Phase 4, the team must update the daily research task to use the live context engine so that recurring research work benefits from current graph context. | active | contextual | yes | |
| a9899c4cad6282fa… | During Phase 4, the team must connect the system to Claude Code through MCP configuration so that Claude Code can use the context engine integration. | active | contextual | yes | |
| 4072d7435dd971ac… | During Phase 4, the team must connect the system to Cowork through an MCP connector so that Cowork can access the context engine via MCP. | active | contextual | yes | |
| bf2bf5f032477676… | During Phase 4, the team must deploy the Context Engine MCP Server so that the context engine can be exposed through MCP-based integration. | active | contextual | yes | |
| 2af6f6b24f31853e… | Phase 4 of the implementation roadmap is the MCP Server & Agent Integration phase and is scheduled to last 2 weeks so that external agent connectivity can be established. | active | contextual | yes | |
| 99dce6ba47b57ef0… | During Phase 3, the team must enable CORTEX agents for Retrieval, Learning, and Ambient functions so that agent-based capabilities become available on the internal graph. | active | contextual | yes | |
| bb8f91fff8602f40… | During Phase 3, the team must extract FINANCIAL_OPS from financial documents so that operational finance knowledge is incorporated into the system. | active | contextual | yes | |
| ba30770a5673c2ec… | During Phase 3, the team must extract MARKETING_CONTENT from blog posts and demos so that marketing knowledge is captured from public-facing materials. | active | contextual | yes | |
| 5cad05a72d147d11… | During Phase 3, the team must extract SECURITY_COMPLIANCE from security documents so that compliance and security knowledge is represented in the graph. | active | contextual | yes | |
| c5ac9f9c0877c225… | During Phase 3, the team must extract SALES_POSITIONING from pitch materials so that sales messaging and positioning knowledge is captured from go-to-market sources. | active | contextual | yes | |
| 6cb4d24d7ebf769c… | Phase 3 of the implementation roadmap is the Sales & Operations phase and is scheduled to last 2 weeks so that commercial and operational knowledge can be added next. | active | contextual | yes | |
| 24dec88d350d85eb… | During Phase 2, the team must establish GOVERNS, SCOPED_BY, and DELIVERED_UNDER relationships so that client and project knowledge is connected through defined graph semantics. | active | contextual | yes | |
| 9778b40ea57efdcc… | During Phase 2, the team must extract the CLIENTS:PATRICK sub-set first because it has the highest priority so that the most important client knowledge is available earliest. | active | contextual | yes | |
| 17f2a907efbeaa8e… | Phase 2 of the implementation roadmap is the Client Knowledge phase and is scheduled to last 2 weeks so that client and project knowledge can be added after foundation sets. | active | contextual | yes | |
| 4a5ea2aefd4f4ece… | During Phase 1, the team must configure initial Named Relationships so that foundational graph links are available for the first extracted sets. | active | contextual | yes | |
| e0adda2e52feed86… | During Phase 1, Rank 0 CXUs must undergo manual review and approval so that the highest-priority extracted knowledge is validated before use. | active | contextual | yes | |
| e86aa829a86fdc2d… | During Phase 1, the team must extract the COMPANY_POLICIES set from policy documents so that internal policy knowledge is represented in the graph. | active | contextual | yes | |
| 19b63800de33e2f9… | During Phase 1, the team must extract the CONTRACT_STANDARDS set from template documents so that standard contract knowledge is captured from reusable templates. | active | contextual | yes | |
| 9dc6a9dc287428b1… | During Phase 1, the team must extract the PYRANA_PLATFORM set from GitHub repositories so that platform knowledge is loaded from code-related sources. | active | contextual | yes | |
| 01df0a28ce115f06… | Phase 1 of the implementation roadmap is the Foundation Sets phase and is scheduled to last 2 weeks so that core knowledge sets are established after infrastructure. | active | contextual | yes | |
| 330669ff99ea9ae9… | During Phase 0, the team must create graph hierarchy nodes for Company, Pillars, and Groups so that the base organizational structure exists in the graph. | active | contextual | yes | |
| 7a48c582f60f3db4… | During Phase 0, the team must set up a Google Drive webhook or polling for sync so that source documents can be synchronized into the system. | active | contextual | yes | |
| 33d5fdecc7c8e69e… | During Phase 0, the team must configure the `zeroth-internal` extraction profile so that internal documents use the intended extraction settings. | active | contextual | yes | |
| 924a81a95538828c… | 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. | active | contextual | yes | |
| e8bbdab8e622c47d… | Phase 0 of the implementation roadmap is the Infrastructure phase and is scheduled to last 1 week so that foundational setup occurs before extraction work begins. | active | contextual | yes | |
| fbaf829ed6b55fab… | The number of PostgreSQL rows is expected to equal the CXU count plus metadata so that relational storage planning includes both units and supporting records. | active | contextual | yes | |
| 43b6a3235db662c9… | The number of Qdrant vectors is expected to equal the CXU count so that vector storage scales directly with extracted knowledge units. | active | contextual | yes | |
| eba27b8ed9cb7ec8… | The Neo4j graph is estimated to contain about 100 non-CXU nodes for hierarchy, agents, and memory so that non-document graph structures are included in capacity planning. | active | contextual | yes | |
| 31a628acb5a1d2b7… | The source corpus is estimated at more than 150 files so that ingestion planning accounts for the expected document volume. | active | contextual | yes | |
| fdf37db11a47a96d… | The graph is estimated to include about 15 named relationship types and more than 500 relationship instances so that relationship modeling capacity is anticipated. | active | contextual | yes | |
| 7a8735b7052ce523… | The set structure is estimated at 12 top-level sets plus approximately 15 sub-sets so that hierarchy planning reflects the expected organizational scope. | active | contextual | yes | |
| 3ef9f55edb67032c… | The estimated total CXU count after 6 months is 3,000 to 5,000 so that medium-term growth expectations are defined for the knowledge graph. | active | contextual | yes | |
| cbf31fee9b5b5ec7… | The estimated initial load for the system is 1,200 to 2,500 total CXUs so that implementation planning can size the starting knowledge base. | active | contextual | yes | |
| 5056612aa56ddcd5… | The Granola integration must flag action items and decisions with high confidence so that important meeting outcomes are emphasized for downstream use. | active | contextual | yes | |
| 9aac33faa305265e… | Meeting-derived CXUs must be auto-assigned to CLIENTS and PROJECTS sets based on meeting attendees and title so that transcript knowledge is categorized without manual sorting. | active | contextual | yes | |
| 2e27d7a7ee4b1a5b… | Granola transcripts must be processed with the `zeroth-internal` extraction profile so that meeting-derived CXUs follow the internal extraction configuration. | active | contextual | yes | |
| 74bd6090228aa420… | After each meeting, the integration process must query Granola for the transcript so that the latest meeting content becomes available for extraction. | active | contextual | yes | |
| 2da2a5114ce0e341… | Granola meeting integration should be configured for continuous extraction from meeting transcripts so that meeting knowledge is regularly ingested into the internal graph. | active | contextual | yes | |
| 4852fe67c05326ec… | The changed-document extraction workflow must flag potential conflicts between new and existing CXUs for human review so that inconsistent knowledge can be evaluated before acceptance. | active | contextual | yes | |
| 7788bb61c5a20029… | 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 current CXUs. | active | contextual | yes | |
| fd57aa381298ced1… | The document includes an Appendix A section titled Full Set Registry, indicating that a complete registry of sets exists or is intended to follow this section. | active | contextual | yes | |