| add88f7742f3b7b6… | The full set registry defines TEAM_NETWORK as a top-level set with no parent, a rank 0 count of 1, an estimated 50-100 CXUs, and Standard approval so that team network knowledge is maintained as a standalone set. | active | contextual | yes | |
| 212694bd2cde6b49… | The full set registry defines FINANCIAL_OPS as a top-level set with no parent, a rank 0 count of 0, an estimated 30-80 CXUs, and REGULATED approval so that financial operations knowledge is controlled under regulated approval. | active | contextual | yes | |
| d141ad0f6cfa34c9… | The full set registry defines IP_PATENTS as a top-level set with no parent, a rank 0 count of 1, an estimated 20-50 CXUs, and REGULATED approval so that patent-related intellectual property knowledge is regulated. | active | contextual | yes | |
| 7e3cac0f4970d372… | The full set registry defines MARKETING_CONTENT as a top-level set with no parent, a rank 0 count of 2, an estimated 50-100 CXUs, and Standard approval so that marketing knowledge is stored outside regulated approval. | active | contextual | yes | |
| 264d4c32d23cd245… | The full set registry defines SECURITY_COMPLIANCE as a top-level set with no parent, a rank 0 count of 3, an estimated 50-100 CXUs, and REGULATED approval so that security compliance knowledge is maintained under regulated controls. | active | contextual | yes | |
| a3018ec8fdccb66b… | The full set registry defines SALES_POSITIONING as a top-level set with no parent, a rank 0 count of 4-6, an estimated 100-200 CXUs, and REGULATED approval so that sales positioning knowledge is controlled under regulated access. | active | contextual | yes | |
| 6a0c8f0243c4bda9… | The full set registry defines PROJECTS as a top-level set with no parent, a rank 0 count of 0, an estimated 200-500 CXUs, and Standard approval so that project knowledge exists as a standalone root set. | active | contextual | yes | |
| 12a15105c4c207cb… | The full set registry defines CLIENTS:LIFE_SCIENCES as a child of CLIENTS with a rank 0 count of 2, an estimated 30-50 CXUs, and Standard approval so that life sciences client knowledge is grouped in a shared subset. | active | contextual | yes | |
| e2ad4b2ec59d5d4c… | The full set registry defines CLIENTS:ZENDA as a child of CLIENTS with a rank 0 count of 1, an estimated 20-40 CXUs, and Standard approval so that Zenda client knowledge is represented as a dedicated subset. | active | contextual | yes | |
| 23a792e222c1151a… | The full set registry defines CLIENTS:PROFITERO as a child of CLIENTS with a rank 0 count of 1, an estimated 20-40 CXUs, and Standard approval so that Profitero client knowledge is maintained in its own subset. | active | contextual | yes | |
| 1fad09598fc0fd94… | The full set registry defines CLIENTS:CELLDEX as a child of CLIENTS with a rank 0 count of 1, an estimated 20-40 CXUs, and Standard approval so that Celldex client knowledge is separately organized. | active | contextual | yes | |
| 0f61cdb35ea338f5… | The full set registry defines CLIENTS:ASSUREA as a child of CLIENTS with a rank 0 count of 1, an estimated 20-40 CXUs, and Standard approval so that Assurea client knowledge is stored as a dedicated subset. | active | contextual | yes | |
| f531037c414fe623… | The full set registry defines CLIENTS:LASTMILE as a child of CLIENTS with a rank 0 count of 1, an estimated 20-40 CXUs, and Standard approval so that Lastmile client knowledge is maintained independently. | active | contextual | yes | |
| 41ebd8c54da89b6a… | The full set registry defines CLIENTS:HUNTER_ONSITE as a child of CLIENTS with a rank 0 count of 1, an estimated 20-40 CXUs, and Standard approval so that Hunter Onsite client knowledge is separately tracked. | active | contextual | yes | |
| 2f705e7684307ad7… | The full set registry defines CLIENTS:EY as a child of CLIENTS with a rank 0 count of 1, an estimated 20-40 CXUs, and Standard approval so that EY client knowledge is represented as a smaller subset. | active | contextual | yes | |
| 735a8abafb3fce72… | The full set registry defines CLIENTS:TOLMAR as a child of CLIENTS with a rank 0 count of 2, an estimated 40-60 CXUs, and Standard approval so that Tolmar client knowledge is maintained in its own subset. | active | contextual | yes | |
| 01c087fdb8df5d2f… | The full set registry defines CLIENTS:JNJ as a child of CLIENTS with a rank 0 count of 2, an estimated 50-80 CXUs, and Standard approval so that JNJ client knowledge is separately scoped. | active | contextual | yes | |
| d5fc8a4d64152e30… | The full set registry defines CLIENTS:PATRICK as a child of CLIENTS with a rank 0 count of 3, an estimated 100-150 CXUs, and Standard approval so that Patrick client knowledge is maintained as a dedicated subset. | active | contextual | yes | |
| b83962120449a545… | The full set registry defines CLIENTS as a top-level set with no parent, a rank 0 count of 2, an estimated 500-1000 CXUs, and Standard approval so that client knowledge is grouped under a broad non-regulated root. | active | contextual | yes | |
| 088b1fe1c4e928e3… | The full set registry defines COMPANY_POLICIES as a top-level set with no parent, a rank 0 count of 3-5, an estimated 50-100 CXUs, and REGULATED approval so that company policy knowledge is controlled at a regulated level. | active | contextual | yes | |
| 7e175f6898c061f7… | The full set registry defines CONTRACT_STANDARDS:LICENSING as a child of CONTRACT_STANDARDS with a rank 0 count of 1, an estimated 10-20 CXUs, and REGULATED approval so that licensing knowledge is separately regulated. | active | contextual | yes | |
| 7b4f3633269bb170… | The full set registry defines CONTRACT_STANDARDS:AUP as a child of CONTRACT_STANDARDS with a rank 0 count of 1, an estimated 10-15 CXUs, and REGULATED approval so that acceptable-use knowledge is regulated within contract standards. | active | contextual | yes | |
| 639185cd3071def3… | The full set registry defines CONTRACT_STANDARDS:NDA as a child of CONTRACT_STANDARDS with a rank 0 count of 1, an estimated 15-20 CXUs, and REGULATED approval so that NDA knowledge is stored in a tightly scoped regulated subset. | active | contextual | yes | |
| 5434038e8cae96f6… | The full set registry defines CONTRACT_STANDARDS:SLA as a child of CONTRACT_STANDARDS with a rank 0 count of 2, an estimated 20-30 CXUs, and REGULATED approval so that service-level knowledge is maintained under regulated contract standards. | active | contextual | yes | |
| b4ee9c3054836670… | The full set registry defines CONTRACT_STANDARDS:TOS as a child of CONTRACT_STANDARDS with a rank 0 count of 2, an estimated 25-40 CXUs, and REGULATED approval so that terms-of-service knowledge is separately regulated. | active | contextual | yes | |
| ed0457682fcf20cd… | The full set registry defines CONTRACT_STANDARDS:SOW as a child of CONTRACT_STANDARDS with a rank 0 count of 2, an estimated 30-50 CXUs, and REGULATED approval so that statement-of-work knowledge is regulated within contract standards. | active | contextual | yes | |
| 0755c1d06eb8d112… | The full set registry defines CONTRACT_STANDARDS:MSA as a child of CONTRACT_STANDARDS with a rank 0 count of 3, an estimated 40-60 CXUs, and REGULATED approval so that MSA knowledge is separately controlled. | active | contextual | yes | |
| 14ca61de159b7c9a… | The full set registry defines CONTRACT_STANDARDS as a top-level set with no parent, a rank 0 count of 5-8, an estimated 150-250 CXUs, and REGULATED approval so that contract knowledge is governed at a regulated level. | active | contextual | yes | |
| f5da2cb89b65426c… | The full set registry defines PYRANA_PLATFORM:INFRASTRUCTURE as a child of PYRANA_PLATFORM with a rank 0 count of 2, an estimated 30-50 CXUs, and Standard approval so that infrastructure knowledge is partitioned within the platform hierarchy. | active | contextual | yes | |
| eb9d9ec51d158f93… | The full set registry defines PYRANA_PLATFORM:FRONTEND as a child of PYRANA_PLATFORM with a rank 0 count of 2, an estimated 40-60 CXUs, and Standard approval so that frontend knowledge is maintained as a separate platform subset. | active | contextual | yes | |
| 28869cc5f14a59e6… | The full set registry defines PYRANA_PLATFORM:CODE_INTERPRETER as a child of PYRANA_PLATFORM with a rank 0 count of 2, an estimated 50-80 CXUs, and Standard approval so that code interpreter knowledge has its own platform subset. | active | contextual | yes | |
| e1f435628440cf9e… | The full set registry defines PYRANA_PLATFORM:CONTEXT_ENGINE as a child of PYRANA_PLATFORM with a rank 0 count of 3, an estimated 80-120 CXUs, and Standard approval so that context engine knowledge is isolated within the platform hierarchy. | active | contextual | yes | |
| 78185e42f2bc499b… | The full set registry defines PYRANA_PLATFORM:CORE as a child of PYRANA_PLATFORM with a rank 0 count of 3, an estimated 100-150 CXUs, and Standard approval so that core platform knowledge is separately scoped. | active | contextual | yes | |
| 93ec87b87c13bf20… | The full set registry defines PYRANA_PLATFORM as a top-level set with no parent, a rank 0 count of 5-10, an estimated 300-500 CXUs, and Standard approval so that platform knowledge is broadly organized under a non-regulated root. | active | contextual | yes | |
| 9eb0bd61873491c8… | The full set registry defines UNIVERSAL as a top-level set with no parent, a rank 0 count of 3-5, an estimated 20-30 CXUs, and a REGULATED approval level so that universal knowledge is tightly controlled. | active | contextual | yes | |
| f9996e80621c42f3… | Phase 5 Continuous Improvement requires adding new client sub-sets as engagements begin so that the client knowledge structure expands in step with new business activity. | active | contextual | yes | |
| 4bb460a898fca5d8… | Phase 5 Continuous Improvement requires refining set boundaries based on usage patterns so that the set structure reflects actual system use. | active | contextual | yes | |
| 24439b2699648ee0… | Phase 5 Continuous Improvement requires expanding extraction to new source documents over time so that the knowledge graph continues to grow beyond the initial corpus. | active | contextual | yes | |
| 3f66f109e1b4a8d9… | Phase 5 Continuous Improvement requires weekly review of AmbientAgent gap detection reports so that missing knowledge or coverage gaps can be identified on a regular cadence. | active | contextual | yes | |
| 57a4302297197530… | Phase 5 Continuous Improvement is ongoing and includes monitoring Q-value learning while adjusting retrieval weights so that retrieval performance can be continuously tuned. | active | contextual | yes | |
| 7fdd726fff95c00e… | Phase 4 MCP Server & Agent Integration requires setting up Granola continuous extraction so that ongoing document extraction is automated within the integrated environment. | active | contextual | yes | |
| f6434039e5346cd3… | Phase 4 MCP Server & Agent Integration requires updating the daily research task to use the live context engine so that research workflows consume current context services. | active | contextual | yes | |
| a9205f13df6e92c7… | Phase 4 MCP Server & Agent Integration requires connecting to Claude Code via MCP configuration so that Claude Code can access the context engine through MCP. | active | contextual | yes | |
| adb795d87886a750… | Phase 4 MCP Server & Agent Integration requires connecting to Cowork via an MCP connector during its 2-week implementation so that Cowork can use the MCP-based context infrastructure. | active | contextual | yes | |
| 186be12fbf2119e1… | Phase 4 MCP Server & Agent Integration is scheduled for 2 weeks and requires deployment of the Context Engine MCP Server so that the integration layer is operational. | active | contextual | yes | |
| 913a62935dffa7d1… | Phase 3 Sales & Operations must enable CORTEX agents including Retrieval, Learning, and Ambient so that these agent capabilities become active during the sales and operations stage. | active | contextual | yes | |
| f40805bd5dc7e6eb… | Phase 3 Sales & Operations requires extracting FINANCIAL_OPS from financial documents during its 2-week timeline so that financial operations knowledge is available in the system. | active | contextual | yes | |
| 6fe629cb51ca44d2… | Phase 3 Sales & Operations requires extracting MARKETING_CONTENT from blog posts and demos within a 2-week period so that marketing knowledge sources are represented in the graph. | active | contextual | yes | |
| c7a39106beb44bf5… | Phase 3 Sales & Operations requires extracting SECURITY_COMPLIANCE from security documents during its 2-week execution so that security-related knowledge is incorporated into the system. | active | contextual | yes | |
| 2ee8f412bc3d29f0… | Phase 3 Sales & Operations is scheduled to last 2 weeks and includes extracting SALES_POSITIONING from pitch materials so that sales messaging knowledge is captured. | active | contextual | yes | |