| 3e7bf09e47c9a114… | Axiomatic knowledge in CONTRACT_STANDARDS consists of stable legal definitions that do not change, such as the meaning of Confidential Information. | active | contextual | yes | |
| 8c7dc3ffef2e73b7… | The dominant knowledge type for CONTRACT_STANDARDS is prescribed because the set primarily captures standard terms, approved language, and required clauses used in contracts. | active | contextual | yes | |
| 153de2f725d8b5a1… | Within CONTRACT_STANDARDS, prescribed claims include standard commercial terms such as payment terms being Net 30 from invoice date unless otherwise negotiated. | active | contextual | yes | |
| 5bf178357c66fba3… | Within CONTRACT_STANDARDS, specification claims record measurable standard terms such as a standard SLA uptime commitment of 99.9 percent measured monthly. | active | contextual | yes | |
| a60fd304e5fd2c86… | Within CONTRACT_STANDARDS, procedure claims describe contract processes such as requiring amendments to be made through written agreement signed by both parties. | active | contextual | yes | |
| 1c3232f3641f0bf7… | Within CONTRACT_STANDARDS, requirement claims capture mandatory drafting rules such as requiring all SOWs to reference the governing MSA by execution date and parties. | active | contextual | yes | |
| bf3af0199162be89… | Within CONTRACT_STANDARDS, definition claims express legal or contractual meanings such as the MSA governing the overall relationship between Zeroth Agents and the client. | active | contextual | yes | |
| b40a83e763ee2d44… | The CONTRACT_STANDARDS set also includes AUP for Acceptable Use Policy and LICENSING for platform licensing terms and order forms so that policy and commercial terms are covered alongside agreements. | active | contextual | yes | |
| e92769617e8e7799… | The CONTRACT_STANDARDS set is sub-organized into MSA, SOW, TOS, SLA, NDA, AUP, and LICENSING categories so that each major contract artifact type has a dedicated namespace. | active | contextual | yes | |
| e77ca550c16806e1… | The CONTRACT_STANDARDS set contains all contractual templates, standard terms, clause libraries, and legal language patterns used in client agreements so that contract knowledge is organized in one domain. | active | contextual | yes | |
| cdbbc1dddc78f160… | The document defines a subsequent section titled CLIENTS Set with per-client sub-sets so that client-specific knowledge can be organized separately after the shared policy and contract sets. | active | contextual | yes | |
| 3f1e11a5d438e338… | The COMPANY_POLICIES set is expected to produce approximately 50 to 100 CXUs so that extraction scope is estimated for internal policy materials. | active | contextual | yes | |
| 5d9bd931b05950de… | The highest-priority COMPANY_POLICIES CXUs include core information security requirements, AI model usage guardrails, and BYOD device requirements so that extraction focuses first on the most critical internal controls. | active | contextual | yes | |
| 0ee5d31682c61bea… | The COMPANY_POLICIES extraction process must use four named policy documents covering information security, BYOD, AI model security and usage, and comprehensive security policy so that policy CXUs are sourced from official internal governance materials. | active | contextual | yes | |
| 5f35f02ca5ea297e… | The COMPANY_POLICIES set is almost exclusively prescribed knowledge so that extracted policy CXUs primarily represent official internal rules rather than observations or inferences. | active | contextual | yes | |
| 6819f303d6ec21ee… | The COMPANY_POLICIES set uses the CXU claim types requirement, procedure, and prescribed so that internal policy knowledge is expressed primarily as enforceable rules and operational instructions. | active | contextual | yes | |
| b680efa88730bb19… | The COMPANY_POLICIES set contains internal company policies governing employee conduct, security practices, technology usage, and operational standards so that internal policy knowledge is organized as a dedicated corpus. | active | contextual | yes | |
| 64626b516532ad9d… | The CONTRACT_STANDARDS set is expected to produce approximately 150 to 250 CXUs so that extraction scope and planning assumptions are defined for the contract corpus. | active | contextual | yes | |
| 405ae4f5ddcf111f… | The highest-priority CONTRACT_STANDARDS CXUs include standard payment terms, limitation of liability language, confidentiality obligations, IP ownership clauses, and required SOW structure or sections so that extraction emphasizes the most critical contract knowledge first. | active | contextual | yes | |
| 2a6b028bb6f71384… | The CONTRACT_STANDARDS extraction process must use eleven named source documents, including MSA, SOW, SLA, TOS, AUP, and enterprise terms templates so that contract CXUs are derived from approved legal artifacts. | active | contextual | yes | |
| f7c056bca54da7b6… | In CONTRACT_STANDARDS, derived knowledge consists of patterns observed across executed contracts so that recurring contractual practices can be captured separately from formal templates. | active | contextual | yes | |
| 7bf84fc3795baeb8… | In CONTRACT_STANDARDS, axiomatic knowledge covers legal definitions that do not change, exemplified by definitions such as Confidential Information means something fixed in legal language so that stable legal concepts are separated from negotiable terms. | active | contextual | yes | |
| 4827cb94d5732b73… | In CONTRACT_STANDARDS, prescribed knowledge is the dominant knowledge type and covers standard terms, approved language, and required clauses so that most extracted contract knowledge reflects official legal standards. | active | contextual | yes | |
| abd036d01d88cf43… | The CONTRACT_STANDARDS set uses the claim types definition, requirement, procedure, specification, and prescribed, each illustrated with a contract-focused example so that legal CXUs can be expressed in standardized forms. | active | contextual | yes | |
| fca549a162edcfe4… | Within CONTRACT_STANDARDS, the LICENSING subcategory refers to platform licensing terms and order forms so that commercial licensing artifacts are grouped together. | active | contextual | yes | |
| eaf83d2b01764f28… | Within CONTRACT_STANDARDS, the AUP subcategory refers to the Acceptable Use Policy so that acceptable-use rules are categorized as a distinct contractual standard. | active | contextual | yes | |
| 70572ac36be89460… | Within CONTRACT_STANDARDS, the NDA subcategory refers to mutual and one-way non-disclosure agreement templates so that confidentiality agreement variants are stored in one namespace. | active | contextual | yes | |
| 34c133545170579f… | Within CONTRACT_STANDARDS, the SLA subcategory refers to Service Level Agreement commitments and metrics so that service performance obligations are grouped together. | active | contextual | yes | |
| b209b16eb873855f… | Within CONTRACT_STANDARDS, the TOS subcategory refers to standard and enterprise Terms of Service so that service terms are organized under a dedicated contract class. | active | contextual | yes | |
| 5d0087f2cf4b195a… | Within CONTRACT_STANDARDS, the SOW subcategory refers to Statement of Work templates and standard deliverable language so that project-specific contractual content is grouped consistently. | active | contextual | yes | |
| 26ad617b2603f2a5… | Within CONTRACT_STANDARDS, the MSA subcategory refers to Master Services Agreement templates and standard clauses so that MSA-related legal language is grouped under a dedicated namespace. | active | contextual | yes | |
| 6a930aa2c6288e65… | The CONTRACT_STANDARDS set is subdivided into MSA, SOW, TOS, SLA, NDA, AUP, and LICENSING categories, each mapped to a specific contract artifact type so that contractual knowledge is organized by agreement form. | active | contextual | yes | |
| 77d93779bb8997cb… | The CONTRACT_STANDARDS set contains all contractual templates, standard terms, clause libraries, and legal language patterns used in client agreements so that contract knowledge is organized as a dedicated corpus. | active | contextual | yes | |
| 0a0e168545d5fec4… | The referenced architecture-related set is expected to yield approximately 300 to 500 CXUs when extracted so that planning and coverage expectations are established for that corpus. | active | contextual | yes | |
| 0766042b43bea032… | The extraction process for the referenced architecture-related set must use seven named source documents, including multiple CLAUDE.md files, architecture references, a frontend README, and two Drive-hosted presentation decks so that architectural CXUs are grounded in approved materials. | active | contextual | yes | |
| c61bc0d6349bffb8… | The specification defines three knowledge types for extraction: axiom for stable architectural facts, derived for conclusions inferred from implementation, and prescribed for design decisions and standards so that extracted knowledge can be categorized consistently. | active | contextual | yes | |
| 679eea4ae02633f8… | The document defines a subsequent section titled CLIENTS Set with per-client sub-sets so that client-specific knowledge can be organized separately after the shared company and contract domains. | active | contextual | yes | |
| ee6e6e1f512ec987… | The COMPANY_POLICIES set is expected to produce approximately 50 to 100 CXUs so that internal policy extraction remains narrower in scope than contract standards extraction. | active | contextual | yes | |
| 521f929d940d5b4a… | Rank 0 CXUs for COMPANY_POLICIES must prioritize core information security requirements, AI model usage guardrails, and BYOD device requirements so that the most critical internal policy controls are extracted first. | active | contextual | yes | |
| 17d06680578f0638… | Company policy extraction should use four named source documents covering information security, BYOD, AI model security and usage, and comprehensive security policy so that internal compliance knowledge comes from the listed policy corpus. | active | contextual | yes | |
| 563b6b1e86a89104… | The COMPANY_POLICIES set uses requirement, procedure, and prescribed claim types, and its knowledge is almost exclusively prescribed, so that extracted policy CXUs emphasize mandatory internal rules and operational instructions. | active | contextual | yes | |
| 7d95cfd35d3d7212… | The COMPANY_POLICIES set contains internal company policies governing employee conduct, security practices, technology usage, and operational standards so that internal rules are maintained as a separate policy knowledge domain. | active | contextual | yes | |
| a727edf5cd45434f… | The CONTRACT_STANDARDS set is expected to yield approximately 150 to 250 CXUs so that the extraction plan allocates substantial but bounded coverage to legal templates and standard clauses. | active | contextual | yes | |
| 60ab132a2e425317… | 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 so that the most critical contract knowledge is extracted first. | active | contextual | yes | |
| a134d5194a317741… | Contract standards extraction should use eleven named legal source documents, including MSA, SOW, SLA, TOS, AUP, and enterprise terms templates, so that CXUs are derived from the approved contract corpus. | active | contextual | yes | |
| eea7b9e3819adebd… | Within CONTRACT_STANDARDS, prescribed knowledge is dominant for standard terms and required clauses, axiomatic knowledge covers stable legal definitions, and empirical knowledge captures patterns observed across executed contracts so that legal CXUs reflect both standards and recurring practice. | active | contextual | yes | |
| a32271a17506005c… | The CONTRACT_STANDARDS set uses definition, requirement, procedure, specification, and prescribed claim types so that extracted legal CXUs can represent governing meanings, mandatory clauses, amendment processes, service metrics, and standard commercial terms. | active | contextual | yes | |
| 817a6e049929ca2b… | The CONTRACT_STANDARDS set also includes AUP for Acceptable Use Policy and LICENSING for platform licensing terms and order forms so that policy restrictions and commercial licensing terms are explicitly classified. | active | contextual | yes | |
| f4d992ab74355718… | The CONTRACT_STANDARDS set is subdivided into MSA, SOW, TOS, SLA, NDA, AUP, and LICENSING categories so that each major contract type and policy artifact has a dedicated sub-organization path. | active | contextual | yes | |
| e19bca6032520e87… | The CONTRACT_STANDARDS set contains all contractual templates, standard terms, clause libraries, and legal language patterns used in client agreements so that legal and commercial standards are organized as a dedicated knowledge domain. | active | contextual | yes | |