| 9cfcb429b7738acd… | The TEAM_NETWORK set is intended to capture team members, their roles, professional networks, and organizational relationships so that the knowledge graph can represent internal people and relationship context. | active | contextual | yes | |
| a5ad5a8c0a32a9b7… | The estimated CXU count for the financial data extraction section is 30 to 80 so that extraction planning reflects the expected volume of financial knowledge units. | active | contextual | yes | |
| 9f018743ed2a5f72… | Financial data CXUs should include clear confidence scores when they represent projections and models so that uncertainty is explicitly communicated. | active | contextual | yes | |
| dbe3cea41fa5efd0… | Financial data CXUs should set is_assumption to true for projections and models so that modeled financial information is explicitly marked as assumptive. | active | contextual | yes | |
| 058ecd010ef21024… | Financial data extraction should use Zeroth Expenses.xlsx, Zeroth Technology census NJ 2025.xlsx, Patrick AI Investment Model.xlsx, the Expense Details folder, the Credit Card folder, and the Valuation Docs folder as source materials. | active | contextual | yes | |
| d7827e0f7d0abe49… | Every CXU stored in the graph follows a defined structure, as introduced by the CXU Anatomy recap section. | active | contextual | yes | |
| b63a5abc9126ca85… | A query to draft an NDA for a new biotech prospect should traverse from the NDA template to past biotech client customizations and then to company policies that constrain required content. | active | contextual | yes | |
| 48d3aea1ad3af81c… | A query about the Patrick financial analysis project’s platform capabilities should traverse from PROJECTS:PATRICK_FINANCIAL_ANALYSIS through IMPLEMENTS to PYRANA_PLATFORM:CORE and PYRANA_PLATFORM:CODE_INTERPRETER. | active | contextual | yes | |
| 19898c318c4c87e3… | Cross-set relationships support multi-hop querying for proposal preparation by traversing from sales positioning value propositions to life sciences clients, then to past pharma projects, and finally to SOW templates. | active | contextual | yes | |
| 49ca14a50bb6b4d6… | The BASED_ON relationship links PROJECTS:deliverables to PYRANA_PLATFORM with many:many cardinality when deliverables are based on platform components. | active | contextual | yes | |
| 2af2a559cd1c08c1… | The EVOLVED_FROM relationship links SALES_POSITIONING version 2 to SALES_POSITIONING version 1 with 1:1 cardinality when positioning evolves over time. | active | contextual | yes | |
| c800fbe0fa4a0a84… | The CUSTOMIZED_FROM relationship links CLIENTS:*:contracts to CONTRACT_STANDARDS with many:1 cardinality when client contracts are customized from templates. | active | contextual | yes | |
| 9d5ffb693e4803be… | The FUNDS relationship links FINANCIAL_OPS to PROJECTS with 1:many cardinality when financial allocations fund projects. | active | contextual | yes | |
| 03ebadec5fa73fc6… | The PROTECTS relationship links IP_PATENTS to PYRANA_PLATFORM with many:many cardinality when patents protect platform innovations. | active | contextual | yes | |
| 99c1aa791b560356… | The DEMONSTRATES relationship links MARKETING_CONTENT to PYRANA_PLATFORM with many:many cardinality when content demonstrates platform capabilities. | active | contextual | yes | |
| 42624527b8745063… | The POSITIONS_FOR relationship links SALES_POSITIONING to CLIENTS with many:many cardinality when positioning materials target client segments. | active | contextual | yes | |
| b997e77ffc71b238… | The CONSTRAINS relationship also links SECURITY_COMPLIANCE to PROJECTS with 1:many cardinality when security requirements constrain delivery. | active | contextual | yes | |
| d0a3276fb493592e… | The CONSTRAINS relationship links COMPANY_POLICIES to PROJECTS with 1:many cardinality when policies constrain project execution. | active | contextual | yes | |
| a27e76d2f60bedba… | The IMPLEMENTS relationship links PROJECTS to PYRANA_PLATFORM with many:many cardinality when projects implement platform capabilities. | active | contextual | yes | |
| 0ff7b81e1519981f… | The DELIVERED_UNDER relationship links PROJECTS to CONTRACT_STANDARDS:SOW with 1:1 cardinality when a project is delivered under a specific statement of work. | active | contextual | yes | |
| e27afdd389bb3cb8… | The SCOPED_BY relationship links PROJECTS to CLIENTS with many:1 cardinality when a project belongs to a client. | active | contextual | yes | |
| a884c0893a7a2ef6… | The GOVERNS relationship links CONTRACT_STANDARDS to CLIENTS with 1:many cardinality when an MSA or TOS governs a client relationship. | active | contextual | yes | |
| bee4addde7ac0683… | The estimated CXU count for the TEAM_NETWORK set is 50 to 100 so that extraction planning reflects the expected volume of team-network knowledge units. | active | contextual | yes | |
| 50b25b4b5bb4d63a… | TEAM_NETWORK extraction should source information from Eric LinkedIn Connections.csv, shared drive team-related documents, and Granola meeting notes so that team-network CXUs are grounded in those materials. | active | contextual | yes | |
| 8d66e08d2db0f56c… | Knowledge extracted for the TEAM_NETWORK set should be classified as axiomatic so that team-network facts are treated as foundational graph knowledge. | active | contextual | yes | |
| a767ae394535535b… | CXUs extracted for the TEAM_NETWORK set should use the claim types definition and relationship so that team-network knowledge is expressed in the intended forms. | active | contextual | yes | |
| 5d858a147bd51632… | The TEAM_NETWORK set is defined to capture team members, their roles, professional networks, and organizational relationships so that team-related knowledge can be represented within the knowledge graph. | active | contextual | yes | |
| 900a43a74af1bf2b… | Section 5.1 introduces a recap of CXU anatomy and states that every CXU stored in the graph follows a defined structure so that subsequent content can specify the standard CXU schema. | active | contextual | yes | |
| 1ecd91b23fe4659a… | To draft an NDA for a new biotech prospect, the graph should traverse from CONTRACT_STANDARDS:NDA through CUSTOMIZED_FROM to CLIENTS:CELLDEX and then through CONSTRAINS to COMPANY_POLICIES so that prior biotech customizations and required policy content are incorporated. | active | contextual | yes | |
| f74e1ac279d95236… | To determine what platform capabilities the Patrick financial analysis project uses, the graph should traverse from PROJECTS:PATRICK_FINANCIAL_ANALYSIS through IMPLEMENTS to PYRANA_PLATFORM:CORE and PYRANA_PLATFORM:CODE_INTERPRETER. | active | contextual | yes | |
| f4b082910aaa9459… | To prepare a proposal for a new pharma client, the graph should traverse from SALES_POSITIONING:VALUE_PROPS through POSITIONS_FOR to CLIENTS:LIFE_SCIENCES, then through SCOPED_BY to PROJECTS:TOLMAR_* and PROJECTS:JNJ_*, and then through DELIVERED_UNDER to CONTRACT_STANDARDS:SOW templates. | active | contextual | yes | |
| 3cee29d7a8c86988… | Cross-set relationships support multi-hop query patterns so that the system can answer compound retrieval requests spanning several sets and relationship types. | active | contextual | yes | |
| a23ae73b689eb8e4… | The BASED_ON relationship links PROJECTS:deliverables to PYRANA_PLATFORM with many:many cardinality when deliverables are based on platform components so that deliverable artifacts can reference reusable platform elements. | active | contextual | yes | |
| f6537f9da36679dd… | The EVOLVED_FROM relationship links SALES_POSITIONING version 2 to SALES_POSITIONING version 1 with 1:1 cardinality when positioning evolves over time so that version lineage is explicitly tracked. | active | contextual | yes | |
| dbdb8b16417031e5… | The CUSTOMIZED_FROM relationship links CLIENTS:*:contracts to CONTRACT_STANDARDS with many:1 cardinality when client contracts are customized from templates so that many client-specific contracts can derive from one standard template. | active | contextual | yes | |
| 64f7984d452e2c1e… | The FUNDS relationship links FINANCIAL_OPS to PROJECTS with 1:many cardinality when financial allocations fund projects so that one financial source can support multiple projects. | active | contextual | yes | |
| 45c84ad014cfa046… | The PROTECTS relationship links IP_PATENTS to PYRANA_PLATFORM with many:many cardinality when patents protect platform innovations so that intellectual property can cover multiple innovations. | active | contextual | yes | |
| f5818c7cd0f34331… | The DEMONSTRATES relationship links MARKETING_CONTENT to PYRANA_PLATFORM with many:many cardinality when content demonstrates platform capabilities so that marketing assets can showcase multiple platform features. | active | contextual | yes | |
| 6a8966d197fe564f… | The POSITIONS_FOR relationship links SALES_POSITIONING to CLIENTS with many:many cardinality when positioning materials target client segments so that multiple positioning assets can serve multiple client groups. | active | contextual | yes | |
| 88f0959de1072ea3… | The CONSTRAINS relationship also links SECURITY_COMPLIANCE to PROJECTS with 1:many cardinality when security requirements constrain delivery so that compliance rules can govern multiple project deliveries. | active | contextual | yes | |
| 664d15b22b484cfe… | The CONSTRAINS relationship links COMPANY_POLICIES to PROJECTS with 1:many cardinality when policies constrain project execution so that one policy can affect multiple projects. | active | contextual | yes | |
| 6cfccf806fbddd72… | The IMPLEMENTS relationship links PROJECTS to PYRANA_PLATFORM with many:many cardinality when projects implement platform capabilities so that platform features can be reused across multiple projects. | active | contextual | yes | |
| 4901beea9fa0d51e… | The DELIVERED_UNDER relationship links PROJECTS to CONTRACT_STANDARDS:SOW with 1:1 cardinality when a project is delivered under a specific SOW so that each project maps to one governing statement of work. | active | contextual | yes | |
| f6dc63665485c962… | The SCOPED_BY relationship links PROJECTS to CLIENTS with many:1 cardinality when a project belongs to a client so that multiple projects can map to one client. | active | contextual | yes | |
| bfad75364a5e2733… | The GOVERNS relationship links CONTRACT_STANDARDS to CLIENTS with 1:many cardinality when an MSA or TOS governs a client relationship so that one standard can apply across multiple clients. | active | contextual | yes | |
| ec0610dd0363ee03… | The context engine supports named relationships between sets with lifecycle management and usage tracking so that cross-set traversal can be performed during retrieval. | active | contextual | yes | |
| b3db9df5f263d139… | The expected extraction volume for the TEAM_NETWORK set is approximately 50 to 100 CXUs so that planning reflects the anticipated amount of team-network knowledge. | active | contextual | yes | |
| b0e1118e8c3a1326… | TEAM_NETWORK extraction should use Eric LinkedIn Connections.csv, shared drive team-related documents, and Granola meeting notes as source materials so that team relationship knowledge is grounded in documented evidence. | active | contextual | yes | |
| 0927ecbe6415c439… | Knowledge in the TEAM_NETWORK set should be treated as axiomatic knowledge so that the graph classifies team-network facts as foundational rather than inferred. | active | contextual | yes | |
| a58ebe68a90339fc… | CXUs extracted for the TEAM_NETWORK set should use the claim types definition and relationship so that team-network knowledge is consistently structured. | active | contextual | yes | |