| 40ca53591546486c… | The PYRANA_PLATFORM set is sub-organized through named relationships so that technical knowledge can be partitioned into specific platform domains. | active | contextual | yes | |
| d9f8d9aafceaae0c… | The purpose of the PYRANA_PLATFORM set is to contain complete technical knowledge of the PYRANA platform architecture, capabilities, and APIs. | active | contextual | yes | |
| 708b6b12bab974fe… | A Rank 0 CXU states that PYRANA follows a libs-first philosophy in which all new functionality starts in library packages before any later promotion. | active | contextual | yes | |
| bb661203f5638680… | A Rank 0 CXU states that PYRANA is configuration-driven and multi-tenant, with client behavior driven by YAML configurations rather than hardcoded logic. | active | contextual | yes | |
| c48d893f989b9fdf… | A Rank 0 CXU states that Zeroth Agents builds PYRANA, which is an enterprise agentic application platform. | active | contextual | yes | |
| 28f4434a1ae826f3… | Rank 0 CXUs are always included so that the most foundational PYRANA and company facts remain present in every retrieval context. | active | contextual | yes | |
| f1125334bd1cbb75… | Knowledge in the UNIVERSAL set is primarily classified as axiomatic for foundational truths and prescribed for approved self-description practices. | active | contextual | yes | |
| 6ed65cd2c6f925b9… | The UNIVERSAL set includes team structure and key roles as foundational organizational knowledge for all query contexts. | active | contextual | yes | |
| b4c02805f5ab9238… | The UNIVERSAL set includes key differentiators versus competitors as part of the foundational knowledge that should always be available. | active | contextual | yes | |
| 030e63ef1cb26356… | The UNIVERSAL set includes the core value proposition that PYRANA is an enterprise-grade, configuration-driven, multi-tenant agentic AI platform. | active | contextual | yes | |
| 8500df6888dd6edf… | The UNIVERSAL set includes brand identity knowledge stating that OAAX is a subsidiary or related brand. | active | contextual | yes | |
| 1e76c1fc7a477f96… | The UNIVERSAL set includes product identity knowledge stating that the product is the PYRANA Agentic Application Platform. | active | contextual | yes | |
| d5ad337206c561ef… | The UNIVERSAL set includes company identity facts stating that the company is Zeroth Agents Inc., was founded by Ankur Tarnowski (Eric Tarnowski), and is headquartered in New Jersey. | active | contextual | yes | |
| 1248f0b4f9b72825… | The purpose of the UNIVERSAL set is to hold foundational facts that should always be available regardless of query context so that core company and product knowledge is never omitted. | active | contextual | yes | |
| fe2ec208a907e318… | A CXU can belong to multiple sets when knowledge overlaps more than one bounded domain so that the same unit can be reused across contexts. | active | contextual | yes | |
| 7d8c3413837e2770… | Sets are the primary organizational mechanism for CXUs because each set defines a bounded knowledge domain for organizing extracted knowledge. | active | contextual | yes | |
| d6c05721b7c60121… | CrossUnit Pricing & Licensing spans the Sales, Legal, and Client Delivery areas so that pricing and licensing knowledge can be managed across commercial, legal, and delivery functions. | active | contextual | yes | |
| 49afedb1bbc75b66… | CrossUnit Security spans the Corporate Operations and Platform Engineering pillars so that security knowledge can be organized across both operational and technical domains. | active | contextual | yes | |
| 4da7b4fe663acefb… | CrossUnit AI Strategy spans the Platform Engineering, Client Delivery, and Sales pillars so that knowledge shared across those three organizational areas can be grouped as a single cross-unit domain. | active | contextual | yes | |
| 2108a03c14197204… | The purpose of the UNIVERSAL set is to hold foundational facts that should always be available regardless of query context so that baseline company knowledge is consistently accessible. | active | contextual | yes | |
| 16ac37663d08195a… | The UNIVERSAL set is always in scope for every query so that foundational knowledge remains available regardless of the active query context. | active | contextual | yes | |
| 0b496d9fba245c5e… | A CXU can belong to multiple sets so that one knowledge unit may be reused across more than one bounded domain when relevant. | active | contextual | yes | |
| fe5c160fa3df5792… | Sets are defined as the primary organizational mechanism for CXUs, with each set representing a bounded knowledge domain so that extracted knowledge can be grouped by scope. | active | contextual | yes | |
| 83f9670c714c6052… | The Pricing & Licensing cross-unit spans Sales, Legal, and Client Delivery so that pricing and licensing knowledge can connect commercial, legal, and delivery domains. | active | contextual | yes | |
| 7056527b5b9e6761… | The Security cross-unit spans Corporate Operations and Platform Engineering so that security knowledge can connect operational and engineering domains. | active | contextual | yes | |
| f64dce564c9ae0d3… | The AI Strategy cross-unit spans Platform Engineering, Client Delivery, and Sales so that AI strategy knowledge can connect those three organizational domains. | active | contextual | yes | |
| bb56deda40953ad8… | The graph includes cross-units for knowledge that spans multiple pillars so that multi-domain topics can be represented outside a single pillar hierarchy. | active | contextual | yes | |
| e2d85d35eaee1674… | The Marketing & Brand pillar contains the groups Content & SEO, Demos & Showcase, and Intellectual Property so that marketing and brand knowledge is organized into content, demo, and IP domains. | active | contextual | yes | |
| eb57af8366c58486… | The Corporate Operations pillar contains the groups Legal & Compliance, Finance & Accounting, Human Resources, and Security & Risk so that operational governance knowledge is organized by function. | active | contextual | yes | |
| b9b7da8ce6f0f44e… | The Sales & Growth pillar contains the groups Positioning & Messaging, Proposals & Deal Management, and Market Analysis so that sales-related knowledge is organized into messaging, deal, and market domains. | active | contextual | yes | |
| 94db707c6acf0b3c… | Within the Client Delivery pillar, the Tolmar group includes the Document Analysis business unit so that Tolmar delivery knowledge is organized under that specific business unit. | active | contextual | yes | |
| 86fa7f859f053b57… | Within the Client Delivery pillar, the Johnson & Johnson group includes the SDLC Co-Pilot business unit so that JNJ delivery knowledge is organized under that specific business unit. | active | contextual | yes | |
| fd5a4930b860d7b9… | Within the Client Delivery pillar, the Patrick Industries group contains the business units Financial Analysis, eCommerce, and AI Strategy so that Patrick Industries knowledge is subdivided by business function. | active | contextual | yes | |
| 81a177e8967875b8… | The Client Delivery pillar contains client and vertical groups including Patrick Industries, Johnson & Johnson, Tolmar, EY, Hunter Onsite, Lastmile, Assurea, Celldex, Profitero, Zenda, and Life Sciences so that delivery knowledge is organized by account or vertical. | active | contextual | yes | |
| 6f15db79e713c425… | Within the Platform Engineering pillar, the Frontend Framework group corresponds to pyrana-frontend-template so that frontend framework knowledge is categorized under that specific group. | active | contextual | yes | |
| 00b6d52d8252526a… | Within the Platform Engineering pillar, the Code Interpreter group corresponds to pyrana-code-interpreter-tiered so that code interpreter knowledge is categorized under that specific group. | active | contextual | yes | |
| 9cddc7d855ccfde3… | Within the Platform Engineering pillar, the Context Engine group corresponds to pyrana-context-engine so that context engine knowledge is categorized under that specific group. | active | contextual | yes | |
| 501661b0d675a0bc… | Within the Platform Engineering pillar, the Core Platform group corresponds to the pyrana monorepo so that monorepo knowledge is categorized under that specific group. | active | contextual | yes | |
| f1c11b642bbc126f… | The Platform Engineering pillar contains the groups Core Platform, Context Engine, Code Interpreter, Frontend Framework, and Infrastructure & DevOps so that platform-related knowledge is grouped under one engineering domain. | active | contextual | yes | |
| 0a9d0047e5e14336… | At the top of the graph hierarchy, the company node is defined as Zeroth Agents so that all lower-level pillars and groups are organized under a single company root. | active | contextual | yes | |
| ef36dcc8ba8fed12… | The context engine’s Neo4j graph uses a hierarchical node structure for Zeroth Agents’ internal deployment so that company knowledge is organized into mapped levels such as company, pillar, group, and business unit. | active | contextual | yes | |
| 5b8555a233e82804… | The internal knowledge graph is intended to power daily research analysis by enriching the daily AI research pipeline with deep platform context so that relevance scoring becomes more precise. | active | contextual | yes | |
| 6795b3d2085d11bf… | The internal knowledge graph is intended to support onboarding new team members by providing instant access to company policies, platform architecture, client context, and operational procedures. | active | contextual | yes | |
| 4f556b07a47732e8… | The internal knowledge graph is intended to support authoring contractual documents by providing access to MSA templates, standard terms, SLA commitments, acceptable use policies, and NDA language with proper versioning. | active | contextual | yes | |
| defad432a3f747b6… | The internal knowledge graph is intended to support building client prototypes by retrieving platform architecture, API surfaces, component libraries, and client configuration patterns so that new deployments can be scaffolded. | active | contextual | yes | |
| 0a448ac8a568ec72… | The internal knowledge graph is intended to support presentation creation by sourcing platform capabilities, positioning language, client-specific talking points, and strategy frameworks for pitch decks and board presentations. | active | contextual | yes | |
| a58ed78ffd2f4783… | The internal knowledge graph is intended to support preparing client quotes and proposals by retrieving contract templates, pricing models, client history, and prior SOW language so that new proposals can be drafted in minutes. | active | contextual | yes | |
| dab8956aa6176f4c… | This specification defines a self-hosted PYRANA Context Engine deployment for Zeroth Agents that loads the company’s institutional knowledge so that agent-assisted workflows can access authoritative, structured company context. | active | contextual | yes | |
| 4c12f460ed3ba47c… | The UNIVERSAL set is always in scope for every query within the PYRANA internal knowledge graph. | active | contextual | yes | |
| 006f71dbf25f620f… | A CXU can belong to multiple sets within the PYRANA internal knowledge graph so that knowledge can be organized across more than one bounded domain. | active | contextual | yes | |