| 3132f247872356fe… | The main PYRANA source repositories include the pyrana monorepo, the pyrana-context-engine KAG system, the pyrana-code-interpreter-tiered execution service, the pyrana-frontend-template starter shell, and the pyrana-demo-2 financial analysis frontend. | active | contextual | yes | |
| b6b7d3f2ea61f651… | The PYRANA platform philosophy requires new functionality to start in library packages, planning to occur before coding, tests to maintain at least 80% coverage, and client behavior to be driven by YAML configuration rather than hardcoded logic. | active | contextual | yes | |
| 935742f4cb88b834… | PYRANA is an agentic orchestration platform built by Zeroth Agents that is designed to be generalizable and configuration-driven so that multiple clients with distinct agentic workflows can share the same core infrastructure. | active | contextual | yes | |
| 45e16f0ff095d216… | The document includes an Appendix B section titled Drive-to-Set Mapping, indicating that a mapping between drive sources and sets is part of the specification even though its contents are not shown in the provided excerpt. | active | contextual | yes | |
| 91f23cedbc45065b… | 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 a Standard approval level so that team network knowledge is grouped in a non-regulated root set. | active | contextual | yes | |
| b56937785f2acc28… | 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 a REGULATED approval level so that financial operations knowledge is controlled under regulated access despite having no initial Rank 0 items. | active | contextual | yes | |
| 377126f7403f44e8… | 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 a REGULATED approval level so that intellectual property knowledge is controlled under regulated access. | active | contextual | yes | |
| 215032b8fdcb84d7… | 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 a Standard approval level so that marketing knowledge is grouped in a non-regulated root set. | active | contextual | yes | |
| 8d5be6ba74ff0583… | 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 a REGULATED approval level so that security and compliance knowledge is controlled under regulated access. | active | contextual | yes | |
| 060bf9f754f95b4e… | 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 a REGULATED approval level so that sales positioning knowledge is controlled under regulated access. | active | contextual | yes | |
| 514bad0ecf68697c… | 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 a Standard approval level so that project knowledge is represented without initial Rank 0 items. | active | contextual | yes | |
| 2d30a1b0bd139b1b… | 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 a Standard approval level so that life sciences client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| 8b5bc6d776d5d555… | 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 a Standard approval level so that Zenda client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| b9c8ed5ad94d03ea… | 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 a Standard approval level so that Profitero client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| 8e1e82fc24c5838f… | 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 a Standard approval level so that Celldex client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| d80952da24b0b45f… | 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 a Standard approval level so that Assurea client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| 9355d1e836bccd75… | 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 a Standard approval level so that Lastmile client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| 1c676302af7c447e… | 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 a Standard approval level so that Hunter Onsite client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| 947d6eac5d4d06db… | 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 a Standard approval level so that EY client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| b586f72f7a5ef8ad… | 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 a Standard approval level so that Tolmar client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| 178a74961f0e08d0… | 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 a Standard approval level so that JNJ client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| d6d5e969dbb961f3… | 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 a Standard approval level so that Patrick client knowledge is maintained as a dedicated client subset. | active | contextual | yes | |
| 24732ef609a63e5d… | 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 a Standard approval level so that client knowledge is grouped under a large shared root set. | active | contextual | yes | |
| 80a727abe0848ec2… | 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 a REGULATED approval level so that company policy knowledge is controlled under regulated access. | active | contextual | yes | |
| a8d8f4c6db1ebbd0… | 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 a REGULATED approval level so that licensing knowledge is managed as a regulated contract subset. | active | contextual | yes | |
| 33df1f5284866f91… | 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 a REGULATED approval level so that acceptable-use knowledge is managed as a regulated contract subset. | active | contextual | yes | |
| 856550a4482dde4e… | 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 a REGULATED approval level so that NDA knowledge is managed as a regulated contract subset. | active | contextual | yes | |
| ff7beaa467f54ecd… | 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 a REGULATED approval level so that SLA knowledge is managed as a regulated contract subset. | active | contextual | yes | |
| 03d7d24c34e19a6e… | 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 a REGULATED approval level so that terms-of-service knowledge is managed as a regulated contract subset. | active | contextual | yes | |
| 2ea8875bffa33066… | 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 a REGULATED approval level so that SOW knowledge is managed as a regulated contract subset. | active | contextual | yes | |
| a30b9f0dcc0a8110… | 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 a REGULATED approval level so that MSA knowledge is managed as a regulated contract subset. | active | contextual | yes | |
| f08af93ac82fc0b4… | 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 a REGULATED approval level so that contract knowledge is governed under stricter controls. | active | contextual | yes | |
| 77fbc65602c9805c… | 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 a Standard approval level so that infrastructure knowledge is tracked separately within the platform hierarchy. | active | contextual | yes | |
| 1f722267917aaf57… | 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 a Standard approval level so that frontend knowledge is represented as a dedicated platform subset. | active | contextual | yes | |
| 0bc60fb2d760a154… | 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 a Standard approval level so that code interpreter knowledge is isolated within the platform hierarchy. | active | contextual | yes | |
| 69c099c006675606… | 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 a Standard approval level so that context engine knowledge is maintained as a distinct platform subset. | active | contextual | yes | |
| 71ff6566356c3a31… | 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 a Standard approval level so that core platform knowledge is separated into a dedicated subset. | active | contextual | yes | |
| 305a0f4fd0b1363d… | 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 a Standard approval level so that platform knowledge is broadly organized under a primary root set. | active | contextual | yes | |
| 24956f9606c0193d… | Phase 5 requires adding new client sub-sets as engagements begin so that the set registry expands in step with new client work. | active | contextual | yes | |
| 04e4a1f0a0c09e6f… | Phase 5 requires refining set boundaries based on usage patterns so that the set structure better reflects how the knowledge system is actually used. | active | contextual | yes | |
| 4781170e11035676… | Phase 5 requires reviewing AmbientAgent gap detection reports weekly so that missing knowledge or coverage gaps can be identified on a recurring cadence. | active | contextual | yes | |
| 921d843c36cb11ce… | The Phase 5 Continuous Improvement workstream is ongoing and includes monitoring Q-value learning while adjusting retrieval weights so that retrieval performance can be improved over time. | active | contextual | yes | |
| 011c128fc4516ded… | Phase 4 requires setting up Granola continuous extraction so that knowledge ingestion can continue automatically after the MCP server and agent integrations are in place. | active | contextual | yes | |
| c0d295740b5574de… | Phase 4 requires updating the daily research task to use the live context engine so that research operations run against current contextual data rather than a static setup. | active | contextual | yes | |
| 6f654cb7769283ec… | Phase 4 requires connecting the system to Claude Code via MCP configuration so that Claude Code can use the MCP-based context integration. | active | contextual | yes | |
| cd99870f81a37656… | Phase 4 requires connecting the system to Cowork via an MCP connector so that Cowork can interoperate with the Context Engine through the MCP integration layer. | active | contextual | yes | |
| 36b190502849629b… | The Phase 4 MCP Server & Agent Integration workstream is scheduled for 2 weeks and includes deploying the Context Engine MCP Server so that MCP-based context services become available for integrations. | active | contextual | yes | |
| 1e7ef8fd6cb5bd4d… | Phase 3 requires enabling CORTEX agents for Retrieval, Learning, and Ambient functions so that the extracted sales and operations knowledge can be used by those agent capabilities. | active | contextual | yes | |
| d8e3ef251b6c7190… | The Phase 3 Sales & Operations workstream is scheduled for 2 weeks and includes extracting SALES_POSITIONING, SECURITY_COMPLIANCE, MARKETING_CONTENT, and FINANCIAL_OPS knowledge from specified source materials so that sales and operational knowledge becomes available to the system. | active | contextual | yes | |
| aaea1b892d910e3b… | Appendix B is titled Drive-to-Set Mapping, indicating that the document includes a section intended to map drives to sets even though no mapping rows are shown in the provided excerpt. | active | contextual | yes | |