| ac8fbf2b738acd98… | The CLIENTS:TOLMAR sub-set is classified as active and focused on document analysis and pharmaceutical manufacturing so that Tolmar-related knowledge is grouped by those domains. | active | contextual | yes | |
| 22c20e285c51e557… | The CLIENTS:JNJ sub-set is classified as active and centered on SDLC co-pilot, pharmaceutical, and life sciences domains so that JNJ knowledge is organized around those operating areas. | active | contextual | yes | |
| e8df5c95ae3a2120… | The CLIENTS:PATRICK sub-set is classified as an active primary client domain focused on financial analysis, eCommerce, AI strategy, and manufacturing so that Patrick knowledge is treated as a major current account. | active | contextual | yes | |
| 996aad1d7d194365… | The current client portfolio defines eleven client sub-sets, including ten named client accounts and one life sciences vertical sub-set, so that client knowledge is partitioned by account or shared industry domain. | active | contextual | yes | |
| 8d58e9d432a14519… | Each client must have its own sub-set that inherits from the parent CLIENTS set so that queries can be scoped to one client while still supporting cross-client pattern analysis. | active | contextual | yes | |
| e6824bdfc866785a… | The CLIENTS set is defined as the client-specific knowledge domain containing relationship history, project context, organizational structure, key contacts, domain terminology, and negotiated terms so that each client's business context can be queried and reused. | active | contextual | yes | |
| aafbbf7765001d47… | The COMPANY_POLICIES set is expected to yield approximately 50 to 100 CXUs during extraction so that planning assumptions reflect a moderate policy knowledge volume. | active | contextual | yes | |
| c9e1bfb1dd844665… | Rank 0 CXUs for the COMPANY_POLICIES set must cover core information security requirements, AI model usage guardrails, and BYOD device requirements so that the highest-priority policy knowledge is captured first. | active | contextual | yes | |
| c3116b1c6a98e7f6… | The COMPANY_POLICIES extraction scope includes four named source documents covering information security, BYOD, AI model security and usage, and comprehensive security policy content so that policy CXUs are derived from these specific files. | active | contextual | yes | |
| b0f518d470084460… | CXUs extracted from the COMPANY_POLICIES set should primarily use requirement, procedure, and prescribed-style claims because the policy documents mostly express mandatory internal rules and operational instructions. | active | contextual | yes | |
| 7f55802c0efe805d… | The COMPANY_POLICIES set is defined as the internal policy collection that governs employee conduct, security practices, technology usage, and operational standards so that company rules are organized under a single policy domain. | active | contextual | yes | |
| 78ceb9efd6c1c6f0… | For the Patrick client example, extraction sources include strategy decks, SOWs, an MSA, financial and use-case spreadsheets, research documents, security assessments, planning documents, order forms, and meeting notes via Granola integration so that Patrick knowledge is assembled from diverse artifacts. | active | contextual | yes | |
| ab73e5770f65570c… | Client knowledge types include prescribed for client-specific requirements and preferences so that negotiated constraints and preferred ways of working are captured as enforceable client knowledge. | active | contextual | yes | |
| d46a0204239fedab… | Client knowledge types include derived for insights from project delivery about what worked and what did not so that experiential lessons are represented separately from facts and requirements. | active | contextual | yes | |
| 0310ba6ebba7f76c… | Client knowledge types include axiom for client facts such as industry, size, and headquarters so that foundational client attributes are distinguished from derived insights and prescribed requirements. | active | contextual | yes | |
| 8ac283d49903a62e… | For each client, the relationship claim example states that Patrick's eCommerce division uses a separate Nessus-scanned infrastructure from the main corporate network so that relationship and environment context can be captured. | active | contextual | yes | |
| 6ec2bb1bc670f459… | For each client, the procedure claim type can describe recurring operational processes, exemplified by Patrick SOW renewals following a quarterly review cycle with IT leadership. | active | contextual | yes | |
| 04b9013fa367487b… | For each client, the specification claim type can describe solution details, exemplified by Patrick's financial analysis solution processing quarterly earnings across 50+ subsidiaries. | active | contextual | yes | |
| fdaf7fe5a5dc5639… | For each client, the requirement claim type can capture client-specific constraints, exemplified by Patrick requiring all data to remain within US Azure regions so that deployment boundaries are enforced. | active | contextual | yes | |
| 8868749a8defe67f… | For each client, the definition claim type can express foundational client facts, exemplified by the statement that Patrick Industries is a building products and materials company headquartered in Elkhart, IN. | active | contextual | yes | |
| a6d58de14b891df9… | The client sub-set CLIENTS:LIFE_SCIENCES is a vertical sub-set for cross-client life sciences knowledge so that domain knowledge shared across multiple clients can be queried together. | active | contextual | yes | |
| 1333a9336a541de6… | The client sub-set CLIENTS:ZENDA is marked Active/Prospect and its key domain is listed as TBD so that Zenda remains represented even though its domain categorization is not yet defined. | active | contextual | yes | |
| 77b3ce2973fbfeff… | The client sub-set CLIENTS:PROFITERO is marked Active/Prospect and its key domains are eCommerce analytics and retail so that Profitero knowledge is grouped by status and commercial analytics focus. | active | contextual | yes | |
| ea930c3cc51bc52d… | The client sub-set CLIENTS:CELLDEX is marked Active/Prospect and its key domains are biotech and therapeutics so that Celldex knowledge is classified by status and life-sciences specialization. | active | contextual | yes | |
| 9a418891df460f5a… | The client sub-set CLIENTS:ASSUREA is marked Active/Prospect and its key domains are insurance and compliance so that Assurea knowledge is organized by engagement status and regulated-business focus. | active | contextual | yes | |
| 690d2c97ca91c0c2… | The client sub-set CLIENTS:LASTMILE is marked Active/Prospect and its key domains are logistics and delivery so that Lastmile knowledge is categorized by mixed status and operational domain. | active | contextual | yes | |
| 7908008f4bd6fa64… | The client sub-set CLIENTS:HUNTER_ONSITE is marked Active/Prospect and its key domain is field services so that Hunter Onsite knowledge is tracked despite mixed active and prospect status. | active | contextual | yes | |
| 9a58444d629c5add… | The client sub-set CLIENTS:EY is marked Active/Prospect and its key domains are professional services, audit, and consulting so that EY knowledge reflects both engagement ambiguity and domain focus. | active | contextual | yes | |
| eebd06291f37f1ce… | The client sub-set CLIENTS:TOLMAR is active and its key domains are document analysis and pharmaceutical manufacturing so that Tolmar knowledge is organized by active status and domain specialization. | active | contextual | yes | |
| 0059fb1da6346be1… | The client sub-set CLIENTS:JNJ is active and its key domains are SDLC co-pilot, pharmaceutical, and life sciences so that JNJ knowledge is classified by current engagement status and domain coverage. | active | contextual | yes | |
| d99dd98ff8b68133… | The client sub-set CLIENTS:PATRICK is active as the primary client and its key domains are financial analysis, eCommerce, AI strategy, and manufacturing so that Patrick knowledge is categorized by both status and business focus. | active | contextual | yes | |
| 3bfd60482d752c50… | Each client receives its own sub-set that inherits from the parent CLIENTS set so that queries can be scoped to a specific client while also supporting cross-client pattern queries. | active | contextual | yes | |
| 80494a8445196192… | The CLIENTS set is organized as per-client sub-sets that contain client-specific knowledge such as relationship history, project context, organizational structure, key contacts, domain-specific terminology, and negotiated terms so that each client’s context is separately maintained. | active | contextual | yes | |
| 29a3891564941c64… | The estimated CXU count for the COMPANY_POLICIES set is 50-100 so that extraction planning reflects a moderate volume of policy knowledge units. | active | contextual | yes | |
| 472e35b926afc54e… | Rank 0 CXUs for the COMPANY_POLICIES set include core information security requirements, AI model usage guardrails, and BYOD device requirements so that the highest-priority policy knowledge is explicitly targeted. | active | contextual | yes | |
| c81f1aaa24dfaf94… | The COMPANY_POLICIES extraction sources include Information Security - Company Policies.pdf, BYOD Policy - Company Policies.pdf, AI Model Security and Usage Policy - Company Policies.pdf, and Comprehensive Security Policy for Zeroth Agents.docx so that policy CXUs are sourced from these four documents. | active | contextual | yes | |
| 9a57e76b4ccc6767… | Knowledge extracted from the COMPANY_POLICIES set is almost exclusively prescribed so that the set primarily captures official internal rules rather than observations or derived insights. | active | contextual | yes | |
| ec6505b46e7d5a5c… | CXUs extracted from the COMPANY_POLICIES set should use requirement, procedure, and prescribed claim types so that policy knowledge is represented in forms aligned to enforceable internal rules. | active | contextual | yes | |
| 0de1271127880667… | The COMPANY_POLICIES set contains internal company policies that govern employee conduct, security practices, technology usage, and operational standards so that organizational rules are centrally defined. | active | contextual | yes | |
| 26f8217caf32d86d… | The next major section after COMPANY_POLICIES is CLIENTS Set with per-client sub-sets, indicating the specification organizes client-specific knowledge into separate subdomains. | active | contextual | yes | |
| 96eed8c81f599b4f… | The estimated extraction volume for the COMPANY_POLICIES set is 50 to 100 CXUs, indicating a moderate amount of internal policy knowledge to capture. | active | contextual | yes | |
| d9a8c43b65b7a205… | Rank 0 CXUs for COMPANY_POLICIES must prioritize core information security requirements, AI model usage guardrails, and BYOD device requirements. | active | contextual | yes | |
| 2b2b042c9d97219c… | Policy knowledge for the COMPANY_POLICIES set must be extracted from the listed security, BYOD, AI model usage, and comprehensive security policy documents. | active | contextual | yes | |
| 9562bd5f19083661… | The COMPANY_POLICIES set is almost exclusively prescribed knowledge because it primarily records internal rules and standards rather than observations or derived conclusions. | active | contextual | yes | |
| acd2b318c32308a3… | The COMPANY_POLICIES set uses requirement, procedure, and prescribed as its CXU claim types so that policy knowledge is captured as mandates, processes, and approved rules. | active | contextual | yes | |
| b9d32963fc69d7cc… | The COMPANY_POLICIES set contains internal company policies governing employee conduct, security practices, technology usage, and operational standards so that internal rules are grouped in one policy domain. | active | contextual | yes | |
| df54b60439dabd8e… | The estimated extraction volume for the CONTRACT_STANDARDS set is 150 to 250 CXUs, indicating a substantial body of contractual knowledge to capture. | active | contextual | yes | |
| 3f8b701cb35ca4fd… | Rank 0 CXUs for CONTRACT_STANDARDS must prioritize standard payment terms, limitation of liability language, confidentiality obligations, IP ownership clauses, and required SOW structure or sections. | active | contextual | yes | |
| 503846c9dad4bc17… | Contract knowledge for the CONTRACT_STANDARDS set must be extracted from listed agreement and policy templates, including MSA, SOW, SLA, TOS, AUP, and enterprise terms documents. | active | contextual | yes | |
| b278ee8ec4056b9a… | Derived knowledge in CONTRACT_STANDARDS consists of patterns observed across executed contracts rather than fixed template language so that recurring negotiated outcomes can be captured. | active | contextual | yes | |