| c2da5f1874a613c2… | Rank 0 CXUs for the SALES_POSITIONING set must include standard pricing tiers so that baseline commercial packaging can be retrieved quickly during sales and proposal work. | active | contextual | yes | |
| 346e681a3bc7aaa1… | Rank 0 CXUs for the SALES_POSITIONING set must include the core platform differentiators as 3 to 5 key points so that the primary reasons to choose the platform are immediately accessible. | active | contextual | yes | |
| 2ad06492df8bef46… | Rank 0 CXUs for the SALES_POSITIONING set must include the approved PYRANA elevator pitch so that the most important reusable sales language is prioritized for retrieval. | active | contextual | yes | |
| 42ab48740eea01c5… | Extraction for the SALES_POSITIONING set should draw from a defined corpus of decks, PDFs, notes, market sizing materials, integration presentations, and framework documents so that positioning knowledge is sourced from all approved commercial artifacts. | active | contextual | yes | |
| b1b31e3ee3a7a913… | The SALES_POSITIONING set should primarily contain prescribed knowledge for approved messaging and derived knowledge for market insights so that both official positioning and analytical conclusions are preserved. | active | contextual | yes | |
| 2a5e2475f94472c7… | The SALES_POSITIONING set should use definition, specification, and prescribed CXU claim types so that approved messaging and structured commercial knowledge can be represented consistently. | active | contextual | yes | |
| c9c2867c17bb1cd0… | The SALES_POSITIONING set should be sub-organized into VALUE_PROPS, PRICING, COMPETITIVE, MARKET, and PITCH_FRAMEWORKS so that reusable commercial knowledge is grouped by messaging and analysis function. | active | contextual | yes | |
| c4be555ffd7f23cf… | The SALES_POSITIONING set is intended to store sales materials, value propositions, competitive positioning, pricing strategies, market analysis, and pitch frameworks so that commercial messaging and go-to-market knowledge are centrally organized. | active | contextual | yes | |
| 6849bf40e5e0b6bd… | The estimated extraction volume for the PROJECTS set is 30 to 80 CXUs per project and 200 to 500 CXUs total so that implementation planning reflects expected project knowledge density. | active | contextual | yes | |
| 728e3cee87a60211… | The PROJECTS set should contain a mix of knowledge types including project facts as axioms, lessons learned as derived knowledge, and project standards as prescribed knowledge so that both descriptive and normative project knowledge are represented. | active | contextual | yes | |
| 6007935cdcdfa9ce… | Within the PROJECTS set, definition claims can establish project terminology such as Project Gateway meaning Patrick's AI infrastructure expansion initiative so that project references remain unambiguous. | active | contextual | yes | |
| 01faf87dfae38fe6… | Within the PROJECTS set, requirement claims can specify performance obligations such as processing SEC filings in under 30 seconds for the financial analysis solution so that measurable project standards are retained. | active | contextual | yes | |
| d35ad395fc694087… | Within the PROJECTS set, procedure claims can describe recurring execution processes such as delivering project status updates bi-weekly by email to the client project sponsor so that operational workflows are captured. | active | contextual | yes | |
| ff591170618598c3… | Within the PROJECTS set, specification claims can express scoped project facts such as SOW coverage for a phase and deliverable package so that contractual project boundaries are represented explicitly. | active | contextual | yes | |
| b212b32ee48fdd0d… | The PROJECTS set should be organized into project-specific sub-sets such as Patrick financial analysis, Patrick eCommerce, Patrick AI strategy, training workshops, J&J SDLC co-pilot, Tolmar document analysis, and Code3 agency operations so that each engagement is independently represented. | active | contextual | yes | |
| 2c6d62f53be5f029… | The PROJECTS set exists to track project-level knowledge about deliverables, timelines, decisions, risks, and outcomes for client-scoped work so that cross-project learning can occur while keeping projects separate from client records. | active | contextual | yes | |
| 1d33b05982e0e3aa… | The estimated extraction volume for client-level knowledge is 50 to 150 CXUs per client and 500 to 1000 CXUs total so that planning assumptions reflect the expected scale of graph population. | active | contextual | yes | |
| 495ccb3f45981a7d… | The Patrick client extraction scope includes a defined set of source files and meeting notes, including strategy decks, SOWs, MSAs, spreadsheets, research documents, and Granola-integrated notes, so that client knowledge is assembled from all major engagement artifacts. | active | contextual | yes | |
| 6b07f55bee5bc1bd… | Client extraction must capture prescribed client-specific requirements and preferences so that the knowledge graph preserves tailored constraints and expectations for each client. | active | contextual | yes | |
| 26f37d457c50263e… | Client extraction for the Patrick example should include project delivery insights about what worked and what did not so that experiential lessons are captured alongside formal client knowledge. | active | contextual | yes | |
| 4f9d094fcd957b9e… | The document identifies a subsequent section titled `3.8 SECURITY_COMPLIANCE Set`, indicating that security and compliance are treated as a separate knowledge set in the overall specification structure. | active | contextual | yes | |
| 78a326f5f9542450… | The estimated CXU count for the SALES_POSITIONING set is 100 to 200 so that extraction planning for sales-positioning knowledge has a defined expected volume. | active | contextual | yes | |
| ea428bd815630b6a… | Rank 0 CXUs for the SALES_POSITIONING set include the approved PYRANA elevator pitch, core platform differentiators, standard pricing tiers, and target customer profile so that the highest-priority sales knowledge is explicitly identified. | active | contextual | yes | |
| fe62d4d901ba9106… | Extraction sources for the SALES_POSITIONING set include overview decks, strategy frameworks, positioning documents, TAM-SAM-SOM analysis, integration materials, vertical-specific overviews, and platform framework documents so that sales knowledge is sourced from a broad set of positioning artifacts. | active | contextual | yes | |
| 1e1040ba14254c66… | The SALES_POSITIONING set is primarily composed of `prescribed` knowledge for approved messaging and `derived` knowledge for market insights so that both sanctioned positioning and analytical insights are represented. | active | contextual | yes | |
| 5cc52db98a984912… | The SALES_POSITIONING set uses `definition`, `specification`, and `prescribed` as CXU claim types so that sales-positioning knowledge can capture term meanings, detailed statements, and approved guidance. | active | contextual | yes | |
| 87ab9e224c0431c8… | The `SALES_POSITIONING:PITCH_FRAMEWORKS` sub-organization refers to reusable pitch deck structures and talking points so that repeatable sales presentation assets are organized in one subset. | active | contextual | yes | |
| e6aaea0f1d04d752… | The `SALES_POSITIONING:MARKET` sub-organization refers to TAM, SAM, and SOM analysis plus industry trends so that market-sizing and trend knowledge is grouped in a dedicated subset. | active | contextual | yes | |
| 539479e1ded9d609… | The `SALES_POSITIONING:COMPETITIVE` sub-organization refers to competitive landscape analysis so that competitor-related market intelligence is stored under a dedicated sales-positioning category. | active | contextual | yes | |
| d7526c27eb802967… | The `SALES_POSITIONING:PRICING` sub-organization refers to pricing models, tier structures, and licensing frameworks so that pricing-related sales knowledge is maintained in a dedicated subset. | active | contextual | yes | |
| 3fce8b946939cbf2… | The `SALES_POSITIONING:VALUE_PROPS` sub-organization refers to core platform value propositions and differentiators so that approved value messaging is grouped in a dedicated sales-positioning subset. | active | contextual | yes | |
| 13bd4a1740e3d5cb… | The SALES_POSITIONING set is intended for sales materials, value propositions, competitive positioning, pricing strategies, market analysis, and pitch frameworks so that commercial messaging and go-to-market knowledge are organized in one domain. | active | contextual | yes | |
| 94a1decc499efbf9… | The estimated CXU count for each project is 30 to 80, with a total estimated range of 200 to 500 CXUs, so that project-level extraction effort can be sized consistently. | active | contextual | yes | |
| 3db78428d46e3a9c… | The PROJECTS set uses a mix of knowledge types including `axiom` for project facts, `derived` for lessons learned, and `prescribed` for project standards so that multiple forms of project knowledge can coexist in the same set. | active | contextual | yes | |
| b764e5677fead714… | Within the PROJECTS set, a `definition` claim type can express term meanings such as Project Gateway referring to Patrick’s AI infrastructure expansion initiative so that project-specific terminology is formally captured. | active | contextual | yes | |
| a45cc9561e419425… | Within the PROJECTS set, a `requirement` claim type can express mandatory performance constraints such as requiring the financial analysis solution to process SEC filings in under 30 seconds so that enforceable project requirements are captured. | active | contextual | yes | |
| 3b2d0223492ae88f… | Within the PROJECTS set, a `procedure` claim type can express recurring operational actions such as delivering project status updates bi-weekly by email to the client project sponsor so that project communication processes are represented explicitly. | active | contextual | yes | |
| 47265c94869b4203… | Within the PROJECTS set, a `specification` claim type can express scope details such as SOW 002 covering Phase II design and planning workshop plus a financial analysis MVP so that project scope statements are captured in a structured form. | active | contextual | yes | |
| 61b3be438348207d… | The `PROJECTS:CODE3_AGENCY_OPS` subset refers to the Code3 agency operations proposal so that proposal-related project knowledge for Code3 is grouped under a dedicated project identifier. | active | contextual | yes | |
| e5d8de14a10d01dd… | The `PROJECTS:TOLMAR_DOC_ANALYSIS` subset refers to the Tolmar document analysis solution so that Tolmar’s document-analysis engagement is tracked as a separate project set. | active | contextual | yes | |
| 6327af314c9cea87… | The `PROJECTS:JNJ_SDLC_COPILOT` subset refers to the J&J SDLC co-pilot project so that this client engagement is represented as a distinct project knowledge grouping. | active | contextual | yes | |
| 4c0a2e97c97ad905… | The `PROJECTS:PATRICK_TRAINING_WORKSHOP` subset refers to AI training workshops so that workshop-based project work for Patrick is tracked separately from other engagements. | active | contextual | yes | |
| 854aeb85205ef1d1… | The `PROJECTS:PATRICK_AI_STRATEGY` subset refers to the board-level AI strategy engagement so that strategic advisory work for Patrick is tracked as its own project category. | active | contextual | yes | |
| d630bb5466152842… | The `PROJECTS:PATRICK_ECOMMERCE` subset refers to eCommerce platform work so that Patrick’s eCommerce-related project knowledge is organized under a dedicated project identifier. | active | contextual | yes | |
| 5602c16f5cca6a5d… | The `PROJECTS:PATRICK_FINANCIAL_ANALYSIS` subset refers to SOW I and II for the financial analysis solution so that this Patrick engagement is tracked as a distinct project knowledge area. | active | contextual | yes | |
| dbb8c448f57d0e61… | The PROJECTS set is intended for project-level knowledge tracking of deliverables, timelines, decisions, risks, and outcomes so that projects scoped to a client can still be tracked separately for cross-project learning. | active | contextual | yes | |
| ede2e84453c64c47… | The estimated CXU count for each client is 50 to 150, with a total estimated range of 500 to 1000 CXUs, so that extraction scope can be planned at both client and portfolio levels. | active | contextual | yes | |
| e01b274c4f75fd1d… | For the Patrick client example, extraction sources include presentation files, statements of work, master service agreements, spreadsheets, research documents, project documents, risk assessments, planning documents, proposal documents, order forms, and meeting notes via Granola integration so that client knowledge is gathered from a broad document set. | active | contextual | yes | |
| dc808589eb5c7026… | The `prescribed` knowledge type represents client-specific requirements and preferences so that client-tailored constraints and expectations can be captured as a distinct category of knowledge. | active | contextual | yes | |
| 2c40098b95eefa99… | The document identifies a SECURITY_COMPLIANCE set as section 3.8, indicating that security and compliance are recognized as a distinct knowledge area in the overall specification structure. | active | contextual | yes | |