| 9c1510ea58fd284c… | The TEAM_NETWORK set is intended to capture team members, their roles, professional networks, and organizational relationships so that people-related knowledge can be represented in the graph. | active | contextual | yes | |
| fc70fea2c4a5bf27… | Section 4.1 introduces a Relationship Registry as the next component of the named-relationship framework so that relationship definitions can be formally organized. | active | contextual | yes | |
| ffe48292754b8931… | The context engine supports named relationships between sets with lifecycle management and usage tracking so that cross-set traversal during retrieval is enabled and governed. | active | contextual | yes | |
| 6e2a36341fa50e78… | The estimated CXU count for the TEAM_NETWORK set is 50 to 100 so that extraction planning reflects a moderate volume of team and relationship knowledge. | active | contextual | yes | |
| 64727ee0e4d36bea… | The TEAM_NETWORK extraction process should source material from Eric LinkedIn Connections.csv, team-related shared-drive documents, and Granola meeting notes so that personnel and network relationships are comprehensively captured. | active | contextual | yes | |
| 67ba719d31b16cb4… | Knowledge in the TEAM_NETWORK set should be classified as axiom so that team and network information is treated as factual organizational knowledge. | active | contextual | yes | |
| 968a781a326cdc25… | CXUs extracted for the TEAM_NETWORK set should use the claim types definition and relationship so that both entity descriptions and inter-person or organizational links are captured. | active | contextual | yes | |
| d058e75ba5ecd093… | The TEAM_NETWORK set is intended for team members, roles, professional networks, and organizational relationships so that people and relationship knowledge is organized in a dedicated set. | active | contextual | yes | |
| 7cca14818820516c… | The estimated CXU count for the FINANCIAL_OPS set is 30 to 80 so that financial extraction work is scoped for a medium-sized body of knowledge. | active | contextual | yes | |
| 6e190242d3eb4cbb… | Financial data CXUs for projections and models should be marked with is_assumption true and clear confidence scores so that forecasted financial content is explicitly identified as uncertain. | active | contextual | yes | |
| f1ba10c8ea6d2b97… | The FINANCIAL_OPS extraction process should source material from the listed spreadsheets and shared-drive folders so that expenses, census data, investment models, and valuation documents are all included. | active | contextual | yes | |
| 94e366c58c38240a… | Knowledge in the FINANCIAL_OPS set should be classified as axiom for financial facts and derived for projections so that actual financial data is distinguished from forecasted analysis. | active | contextual | yes | |
| 7b1bdf47e4130f8d… | CXUs extracted for the FINANCIAL_OPS set should use the claim types specification and definition so that financial knowledge is represented as structured facts and formal descriptions. | active | contextual | yes | |
| 64e9070489738f4b… | The FINANCIAL_OPS set is intended for financial models, expense tracking, investment projections, and operational metrics so that financial and operating data are grouped in one extraction domain. | active | contextual | yes | |
| a547f0435d49bdb4… | The estimated CXU count for the IP_PATENTS set is 20 to 50 so that patent extraction effort is planned for a relatively smaller body of knowledge. | active | contextual | yes | |
| a74f7ca18cb4baa6… | The IP_PATENTS extraction process should source material from the shared drive patent docs folder so that patent and IP knowledge is collected from the designated repository. | active | contextual | yes | |
| 1f51e82f383ffc5c… | Knowledge in the IP_PATENTS set should be classified as axiom for filed claims and derived for prior art analysis so that official filings are distinguished from analytical interpretation. | active | contextual | yes | |
| 6cc2a87bfa6d411c… | CXUs extracted for the IP_PATENTS set should use the claim types specification and definition so that patent-related knowledge is represented as formal descriptions and structured facts. | active | contextual | yes | |
| 7f052c362593ac8d… | The IP_PATENTS set is intended for patent filings, invention disclosures, prior art references, and IP strategy so that intellectual property materials are managed within a dedicated knowledge domain. | active | contextual | yes | |
| 5af623999a77deaf… | The estimated CXU count for the MARKETING_CONTENT set is 50 to 100 so that marketing extraction work is scoped for a moderate number of knowledge units. | active | contextual | yes | |
| a5916a97d657f640… | The MARKETING_CONTENT extraction process should use the listed shared-drive folders and named presentation and document sources so that marketing knowledge is collected from all designated repositories. | active | contextual | yes | |
| e6c4590d50429cb8… | Knowledge in the MARKETING_CONTENT set should be classified as prescribed and derived so that both approved content guidance and inferred marketing insights are represented. | active | contextual | yes | |
| d2fc4fedfda3d82b… | The MARKETING_CONTENT set should use claim types aligned to prescribed approved messaging and procedure content workflows so that both controlled messaging and execution processes are captured. | active | contextual | yes | |
| 1f573ce84e744b1d… | The MARKETING_CONTENT set is intended for blog posts, SEO strategies, content calendars, demo scripts, and brand guidelines so that marketing assets and content operations are organized together. | active | contextual | yes | |
| 9de83dd3e142a827… | The estimated CXU count for the SECURITY_COMPLIANCE set is 50 to 100 so that extraction scope for security and compliance materials is planned at a moderate volume. | active | contextual | yes | |
| 9ed5467722a609a3… | The SECURITY_COMPLIANCE extraction process should pull from the listed policy documents, presentations, spreadsheets, and shared-drive folders so that all relevant security and resilience evidence is included. | active | contextual | yes | |
| 666d1b38fb9f7ec5… | Knowledge in the SECURITY_COMPLIANCE set should be classified as prescribed for security standards and axiom for compliance facts so that normative controls are separated from factual compliance records. | active | contextual | yes | |
| 5956318935e0c704… | CXUs extracted for the SECURITY_COMPLIANCE set should use the claim types requirement, specification, and procedure so that security knowledge includes rules, detailed standards, and operational steps. | active | contextual | yes | |
| 64425f47f17d765c… | The SECURITY_COMPLIANCE set is intended for security assessments, DR/BCP plans, compliance certifications, risk matrices, and security architecture documentation so that security and compliance materials are grouped in one domain. | active | contextual | yes | |
| 7bfb7c03dfaa51e5… | The estimated CXU count for the PITCH_FRAMEWORKS set is 100 to 200 so that extraction planning reflects the expected volume of pitch-related knowledge units. | active | contextual | yes | |
| 8c851a33c0fc6c79… | Rank 0 CXUs for the PITCH_FRAMEWORKS set must include the target customer profile so that ideal-buyer knowledge is prioritized for retrieval and reuse. | active | contextual | yes | |
| 58d6b06035340ba6… | Rank 0 CXUs for the PITCH_FRAMEWORKS set must include standard pricing tiers so that core commercial positioning is available at the highest retrieval priority. | active | contextual | yes | |
| e0b87c1fe5a11241… | Rank 0 CXUs for the PITCH_FRAMEWORKS set must include core platform differentiators as 3 to 5 key points so that the platform’s main distinctions are consistently represented. | active | contextual | yes | |
| d8d52ee220753377… | Rank 0 CXUs for the PITCH_FRAMEWORKS set must include the PYRANA elevator pitch in approved language so that the highest-priority messaging asset is always captured. | active | contextual | yes | |
| 47dbc426f8c67fe5… | The PITCH_FRAMEWORKS extraction process should source content from the listed presentations, PDFs, and strategy documents so that pitch knowledge is gathered from all approved narrative materials. | active | contextual | yes | |
| bd4eb66d3384518a… | Knowledge extracted for the PITCH_FRAMEWORKS set is primarily prescribed approved messaging and derived market insights so that messaging assets and inferred market knowledge are both represented. | active | contextual | yes | |
| 8def1ca8f996b939… | CXUs extracted for the PITCH_FRAMEWORKS set should use the claim types definition, specification, and prescribed so that pitch-related knowledge is categorized according to approved schema options. | active | contextual | yes | |
| e141ce0e5daff7d1… | The NING:PITCH_FRAMEWORKS set contains reusable pitch deck structures and talking points so that approved sales and positioning narratives can be consistently reused across presentations. | active | contextual | yes | |
| 74119cc8eb3c96e6… | The TEAM_NETWORK set is expected to contain 50 to 100 CXUs so that extraction planning for team and relationship data has a defined scale. | active | contextual | yes | |
| 279925ebbb5dc32e… | The TEAM_NETWORK extraction sources include Eric LinkedIn Connections.csv, team-related shared-drive documents, and Granola meeting notes so that relationship CXUs are built from network and collaboration records. | active | contextual | yes | |
| e7322e4845221da0… | The TEAM_NETWORK set uses axiom knowledge so that team and network information is treated as factual organizational data. | active | contextual | yes | |
| 94e3fd9f0de7bf5e… | The TEAM_NETWORK set should use definition and relationship as CXU claim types so that both entity descriptions and inter-person or organizational links can be captured. | active | contextual | yes | |
| a825a402f6071552… | The TEAM_NETWORK set is defined as covering team members, roles, professional networks, and organizational relationships so that people and relationship knowledge is maintained in one set. | active | contextual | yes | |
| 3e54b2a9bcec6221… | The FINANCIAL_OPS set is expected to produce 30 to 80 CXUs so that the anticipated extraction volume for financial operations materials is documented. | active | contextual | yes | |
| dbeadb2b8481fcbe… | Financial data CXUs for projections and models should be marked with is_assumption true and clear confidence scores so that uncertain financial assumptions are explicitly identified. | active | contextual | yes | |
| 7e4e4bca0958b385… | The FINANCIAL_OPS extraction sources include named spreadsheets and shared folders for expenses, credit cards, and valuation documents so that financial CXUs are sourced from operational finance records and models. | active | contextual | yes | |
| 22d99365463e9e13… | The FINANCIAL_OPS set uses axiom knowledge for financial facts and derived knowledge for projections so that actual financial data is separated from modeled forecasts. | active | contextual | yes | |
| e8338b2e93d0572e… | The FINANCIAL_OPS set should use specification and definition as CXU claim types so that both formal financial details and conceptual finance terms can be represented. | active | contextual | yes | |
| cc690979b12446c9… | The FINANCIAL_OPS set is defined as including financial models, expense tracking, investment projections, and operational metrics so that finance and operating performance knowledge is centrally organized. | active | contextual | yes | |
| a1d391af44c4bd15… | The IP_PATENTS set is expected to contain 20 to 50 CXUs so that extraction effort for intellectual property materials is estimated before processing. | active | contextual | yes | |