| 45902aa8d60df209… | The IP_PATENTS extraction source is the shared drive patent docs folder so that patent-related CXUs are drawn from the designated IP repository. | active | contextual | yes | |
| 8e0c184918a7da04… | The IP_PATENTS set uses axiom knowledge for filed claims and derived knowledge for prior art analysis so that official filings are distinguished from analytical comparisons. | active | contextual | yes | |
| 4fd32417f3a7ffc4… | The IP_PATENTS set should use specification and definition as CXU claim types so that both formal patent details and conceptual IP descriptions can be extracted. | active | contextual | yes | |
| b99c0c4cdb649895… | The IP_PATENTS set is defined as covering patent filings, invention disclosures, prior art references, and IP strategy so that intellectual property knowledge is grouped into a dedicated set. | active | contextual | yes | |
| d966f1ff2480ff02… | The MARKETING_CONTENT set is expected to yield 50 to 100 CXUs so that the projected extraction volume for marketing materials is explicitly bounded. | active | contextual | yes | |
| 0422623314ff6e8f… | The MARKETING_CONTENT extraction sources include shared-drive marketing folders, the AI Executive 101 presentation series, and a named efficiency document so that content CXUs come from both repositories and authored assets. | active | contextual | yes | |
| e02a4f062203f019… | The MARKETING_CONTENT set uses prescribed and derived knowledge types so that official marketing guidance and analytically developed content insights can both be represented. | active | contextual | yes | |
| 34d64c8d002d087c… | The MARKETING_CONTENT set should use prescribed claim types for approved messaging and procedure claim types for content workflows so that both controlled language and process guidance are captured. | active | contextual | yes | |
| f71a580284934f4b… | The MARKETING_CONTENT set is defined as including blog posts, SEO strategies, content calendars, demo scripts, and brand guidelines so that marketing knowledge assets are organized within one content set. | active | contextual | yes | |
| 2c0a613e26d9468e… | The SECURITY_COMPLIANCE set is expected to contain 50 to 100 CXUs so that extraction scope for security and compliance materials is estimated in advance. | active | contextual | yes | |
| 12d4bca35eef1d0d… | The SECURITY_COMPLIANCE extraction sources are the listed policy, presentation, spreadsheet, and shared-drive folders so that security CXUs are sourced from formal security and continuity documentation. | active | contextual | yes | |
| 3787ef449e7591e7… | The SECURITY_COMPLIANCE set uses prescribed knowledge for security standards and axiom knowledge for compliance facts so that normative controls are separated from factual compliance status. | active | contextual | yes | |
| e676f6742d919aa1… | The SECURITY_COMPLIANCE set should use requirement, specification, and procedure as CXU claim types so that security content can represent standards, detailed controls, and operational processes. | active | contextual | yes | |
| 006ee88333ee235b… | The SECURITY_COMPLIANCE set is defined as covering security assessments, DR/BCP plans, compliance certifications, risk matrices, and security architecture documentation so that security and compliance knowledge is grouped in one domain. | active | contextual | yes | |
| 1c0beca4bbc7411b… | The PITCH_FRAMEWORKS set is expected to produce an estimated 100 to 200 CXUs so that extraction planning reflects the anticipated volume of pitch knowledge. | active | contextual | yes | |
| 88e37e9f5e8b9346… | The PITCH_FRAMEWORKS set designates Rank 0 CXUs as the PYRANA elevator pitch, core platform differentiators, standard pricing tiers, and target customer profile so that the most important pitch knowledge is prioritized. | active | contextual | yes | |
| f5d8af3972c5e97f… | The PITCH_FRAMEWORKS extraction sources include thirteen specified presentation, PDF, and document files so that pitch-related CXUs are derived from the approved source corpus. | active | contextual | yes | |
| 9c27fbdf53794f0a… | The PITCH_FRAMEWORKS set primarily uses prescribed knowledge for approved messaging and derived knowledge for market insights so that pitch content distinguishes official language from analytical interpretation. | active | contextual | yes | |
| 079f82b1a4e7bbd0… | The PITCH_FRAMEWORKS set should use CXU claim types definition, specification, and prescribed so that extracted pitch knowledge is categorized according to approved messaging and structural content. | active | contextual | yes | |
| fa176c9f7daf0277… | The NING:PITCH_FRAMEWORKS set is defined as a collection of reusable pitch deck structures and talking points so that approved sales and positioning knowledge can be consistently reused. | active | contextual | yes | |
| ce14fac443478306… | Section 4.1 is titled Relationship Registry, indicating that the named relationships capability includes a registry component for managing set relationships. | active | contextual | yes | |
| 08d986c63ae6e0d0… | The context engine supports named relationships between sets with lifecycle management and usage tracking so that cross-set traversal can be enabled during retrieval. | active | contextual | yes | |
| a31fe3831dbc2bba… | The TEAM_NETWORK set is expected to contain approximately 50 to 100 CXUs so that the extraction workload for team and relationship data can be estimated. | active | contextual | yes | |
| 6c099e2f9296784e… | The TEAM_NETWORK set should extract from LinkedIn connection data, team-related shared drive documents, and Granola meeting notes so that personnel and network information is broadly sourced. | active | contextual | yes | |
| 835848e5acc763dc… | The TEAM_NETWORK set uses definition and relationship as CXU claim types so that both entity descriptions and connections between people or organizations can be captured. | active | contextual | yes | |
| 507e14af7737413d… | The TEAM_NETWORK set covers team members, roles, professional networks, and organizational relationships so that people and relationship knowledge is represented in a dedicated set. | active | contextual | yes | |
| 2667743beed9357d… | The FINANCIAL_OPS set is expected to yield approximately 30 to 80 CXUs so that extraction planning reflects the projected size of the financial corpus. | active | contextual | yes | |
| 10b5fc137344f389… | Financial data CXUs for projections and models should be marked with is_assumption set to true and should include clear confidence scores so that uncertainty in forward-looking financial information is explicit. | active | contextual | yes | |
| a80e9196c33b2bd1… | The FINANCIAL_OPS set should extract from named spreadsheets and shared drive folders covering expenses, credit cards, and valuation documents so that operational finance sources are comprehensively included. | active | contextual | yes | |
| 45afdf8dd64942c7… | The FINANCIAL_OPS set uses specification and definition as CXU claim types so that both structured financial details and descriptive financial concepts can be represented. | active | contextual | yes | |
| a69411dece595f7f… | The FINANCIAL_OPS set includes financial models, expense tracking, investment projections, and operational metrics so that financial and operating knowledge is grouped in one set. | active | contextual | yes | |
| a78a021504d49e1a… | The IP_PATENTS set is expected to contain roughly 20 to 50 CXUs so that the anticipated extraction volume for patent materials is bounded. | active | contextual | yes | |
| 374cf5b1bbf788bd… | The IP_PATENTS set should extract from the shared drive patent docs folder so that patent-related source material is centralized for CXU generation. | active | contextual | yes | |
| 04d2e35272d49cc1… | The IP_PATENTS set uses specification and definition as its CXU claim types so that both formal patent details and conceptual IP descriptions can be extracted. | active | contextual | yes | |
| a754bb2aac1737b5… | The IP_PATENTS set covers patent filings, invention disclosures, prior art references, and IP strategy so that intellectual property knowledge is maintained as a dedicated domain. | active | contextual | yes | |
| dd3423530e8bd983… | The MARKETING_CONTENT set is expected to produce approximately 50 to 100 CXUs so that extraction effort can be sized for marketing materials. | active | contextual | yes | |
| 9f1c7486a1dcdf21… | The MARKETING_CONTENT set should extract from shared drive marketing folders and named presentations and documents so that campaign, SEO, demo, and executive education materials are included. | active | contextual | yes | |
| 13812f9082d6b243… | The MARKETING_CONTENT set uses prescribed claim types for approved messaging and procedure claim types for content workflows so that both messaging standards and execution processes can be represented. | active | contextual | yes | |
| 086451790ba269d5… | The MARKETING_CONTENT set includes blog posts, SEO strategies, content calendars, demo scripts, and brand guidelines so that marketing knowledge and messaging assets are grouped together. | active | contextual | yes | |
| 1b13695036a526f9… | The SECURITY_COMPLIANCE set is expected to contain about 50 to 100 CXUs so that extraction scope and workload can be estimated in advance. | active | contextual | yes | |
| 6b25a3d5bb48b0be… | The SECURITY_COMPLIANCE set should extract from named security documents and shared drive folders, including Security and DR/BCP directories, so that compliance and resilience materials are comprehensively covered. | active | contextual | yes | |
| f2468b9588703ccb… | The SECURITY_COMPLIANCE set uses requirement, specification, and procedure as CXU claim types so that security knowledge can represent standards, detailed controls, and operational steps. | active | contextual | yes | |
| 6b4358f73872fc1d… | The SECURITY_COMPLIANCE set covers security assessments, DR/BCP plans, compliance certifications, risk matrices, and security architecture documentation so that security and compliance knowledge is organized in one domain. | active | contextual | yes | |
| c256737b759fbd7f… | The NING:PITCH_FRAMEWORKS set is expected to yield approximately 100 to 200 CXUs so that extraction planning reflects the anticipated knowledge volume. | active | contextual | yes | |
| b9a8202418b19c99… | The highest-priority Rank 0 CXUs for the NING:PITCH_FRAMEWORKS set are the approved PYRANA elevator pitch, core platform differentiators, standard pricing tiers, and target customer profile so that essential pitch knowledge is captured first. | active | contextual | yes | |
| adacef097cb445a6… | The NING:PITCH_FRAMEWORKS set should extract CXUs from specified presentation, PDF, and document sources so that pitch-related knowledge is captured from all approved materials. | active | contextual | yes | |
| 8422393d9c1aa196… | The NING:PITCH_FRAMEWORKS set contains reusable pitch deck structures and talking points so that approved messaging assets can be extracted and reused consistently. | active | contextual | yes | |
| 28844bb1f9bd20d3… | The document introduces a subsequent section named SECURITY_COMPLIANCE Set after SALES_POSITIONING, indicating that security and compliance are treated as a separate top-level knowledge set in the specification. | active | contextual | yes | |
| 42640277305ed61d… | The estimated extraction volume for the SALES_POSITIONING set is 100 to 200 CXUs so that the expected scope of commercial knowledge extraction is bounded for planning purposes. | active | contextual | yes | |
| 3b9c176020da7f55… | Rank 0 CXUs for the SALES_POSITIONING set must include the target customer profile so that ideal buyer characteristics are prioritized in the knowledge graph. | active | contextual | yes | |