| 8149325fab4f8373… | Sets are defined as the primary organizational mechanism for CXUs, with each set defining a bounded knowledge domain. | active | contextual | yes | |
| fe1fb981d5f61542… | The Pricing & Licensing cross-unit spans Sales, Legal, and Client Delivery within the internal graph. | active | contextual | yes | |
| db63408546817137… | The Security cross-unit spans Corporate Operations and Platform Engineering within the internal graph. | active | contextual | yes | |
| 0ccfa784844947e3… | The AI Strategy cross-unit spans Platform Engineering, Client Delivery, and Sales within the internal graph. | active | contextual | yes | |
| ab9e96474d6c440a… | Cross-units are defined as organizational units that span multiple pillars, enabling knowledge domains that cut across the primary hierarchy. | active | contextual | yes | |
| 6e2fb4690ec8a928… | The Marketing & Brand pillar contains the groups Content & SEO, Demos & Showcase, and Intellectual Property within the graph hierarchy. | active | contextual | yes | |
| 72e80a7f4782ce1c… | The Corporate Operations pillar contains the groups Legal & Compliance, Finance & Accounting, Human Resources, and Security & Risk within the graph hierarchy. | active | contextual | yes | |
| 497b11397eee82dc… | The Sales & Growth pillar contains the groups Positioning & Messaging, Proposals & Deal Management, and Market Analysis within the graph hierarchy. | active | contextual | yes | |
| 7fd3316f159bda2c… | Within Client Delivery, the Tolmar group contains the Document Analysis business unit. | active | contextual | yes | |
| d601632e8ebc8885… | Within Client Delivery, the Johnson & Johnson group, labeled JNJ, contains the SDLC Co-Pilot business unit. | active | contextual | yes | |
| f818e30ba3d94a5e… | Within Client Delivery, the Patrick Industries group contains the business units Financial Analysis, eCommerce, and AI Strategy. | active | contextual | yes | |
| c9a7345803ee2023… | The Client Delivery pillar contains groups for Patrick Industries, Johnson & Johnson, Tolmar, EY, Hunter Onsite, Lastmile, Assurea, Celldex, Profitero, Zenda, and Life Sciences within the graph hierarchy. | active | contextual | yes | |
| 6d715199ba6ddf0d… | The Platform Engineering pillar contains the groups Core Platform, Context Engine, Code Interpreter, Frontend Framework, and Infrastructure & DevOps within the internal graph hierarchy. | active | contextual | yes | |
| dec4af9db9ad841c… | Within the graph hierarchy, the top-level company node is Zeroth Agents, under which all pillars and subordinate organizational nodes are arranged. | active | contextual | yes | |
| c37abbae86672f71… | The context engine's Neo4j graph is defined as using a hierarchical node structure for Zeroth Agents' internal deployment so that company knowledge is organized by company, pillar, group, business unit, and cross-unit relationships. | active | contextual | yes | |
| 18bfdbc264dd6935… | The knowledge graph should support daily research analysis by enriching the daily AI research pipeline with deep platform context so that relevance scoring becomes more precise. | active | contextual | yes | |
| 89feeac89e2a5ac2… | The knowledge graph should support onboarding new team members by providing instant access to company policies, platform architecture, client context, and operational procedures. | active | contextual | yes | |
| 0415deb84cc502ee… | The knowledge graph should 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 | |
| 62aa8484b7c24029… | The knowledge graph should 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 | |
| c03513ba1fedcb12… | The knowledge graph should support creating presentations by sourcing platform capabilities, positioning language, client-specific talking points, and strategy frameworks for pitch decks and board presentations. | active | contextual | yes | |
| f23a020ee2f05642… | The knowledge graph should support preparing client quotes and proposals by retrieving contract templates, pricing models, client history, and past SOW language so that new proposals can be drafted in minutes. | active | contextual | yes | |
| 0e2a8110851960cd… | The purpose of the internal PYRANA knowledge graph is to provide every agent-assisted workflow, including Cowork sessions, Claude Code, and internal tools, with authoritative structured context about the company, platform, clients, and standards. | active | contextual | yes | |
| ef7a63321a1881e8… | The PYRANA internal knowledge graph is defined as a self-hosted instance of the PYRANA Context Engine loaded with Zeroth Agents' institutional knowledge so that agent-assisted workflows can access authoritative, structured company context. | active | contextual | yes | |
| e912c7946441d294… | The purpose of the UNIVERSAL set is to hold foundational facts that should always be available regardless of query context. | active | contextual | yes | |
| 0d7a6dbdf85f43db… | The UNIVERSAL set is always in scope for every query so that foundational context remains available regardless of the specific query context. | active | contextual | yes | |
| 4a6147b719ac2f2a… | A CXU may belong to multiple sets at the same time so that knowledge can be organized across more than one bounded domain. | active | contextual | yes | |
| 01e42d19af7c8ee4… | Sets are defined as the primary organizational mechanism for CXUs, with each set establishing a bounded knowledge domain for organizing extracted context. | active | contextual | yes | |
| 87560c642bc58fc5… | The graph defines a cross-unit named Pricing & Licensing that spans Sales, Legal, and Client Delivery so that pricing and licensing knowledge can connect commercial, legal, and delivery domains. | active | contextual | yes | |
| 2f5a12284d307401… | The graph defines a cross-unit named Security that spans Corporate Operations and Platform Engineering so that security knowledge can connect those two pillars. | active | contextual | yes | |
| 5f933f2a67e72356… | The graph defines a cross-unit named AI Strategy that spans Platform Engineering, Client Delivery, and Sales so that knowledge crossing those pillars can be represented together. | active | contextual | yes | |
| 591bc974ec408d31… | The Marketing & Brand pillar contains the groups Content & SEO, Demos & Showcase, and Intellectual Property as its organizational subdivisions. | active | contextual | yes | |
| 55422232de37f60a… | The Corporate Operations pillar contains the groups Legal & Compliance, Finance & Accounting, Human Resources, and Security & Risk as its organizational subdivisions. | active | contextual | yes | |
| abcc171e5b9aa877… | The Sales & Growth pillar contains the groups Positioning & Messaging, Proposals & Deal Management, and Market Analysis as its organizational subdivisions. | active | contextual | yes | |
| 8676490aa3fdee7b… | Within Client Delivery, the Tolmar group includes a single listed business unit named Document Analysis. | active | contextual | yes | |
| d72f63712a4a0645… | Within Client Delivery, the Johnson & Johnson group includes a single listed business unit named SDLC Co-Pilot. | active | contextual | yes | |
| 16db26ae9ca67cc6… | Within Client Delivery, the Patrick Industries group contains the business units Financial Analysis, eCommerce, and AI Strategy as subordinate nodes. | active | contextual | yes | |
| b10250c2036b8788… | The Client Delivery pillar contains groups for Patrick Industries, Johnson & Johnson (JNJ), Tolmar, EY, Hunter Onsite, Lastmile, Assurea, Celldex, Profitero, Zenda, and Life Sciences as a vertical grouping. | active | contextual | yes | |
| 1254e6baf17a1ea1… | Within the Platform Engineering pillar, the Core Platform group corresponds to the pyrana monorepo, the Context Engine group corresponds to pyrana-context-engine, the Code Interpreter group corresponds to pyrana-code-interpreter-tiered, and the Frontend Framework group corresponds to pyrana-frontend-template. | active | contextual | yes | |
| 41cbe377bfd04de5… | The Platform Engineering pillar contains the groups Core Platform, Context Engine, Code Interpreter, Frontend Framework, and Infrastructure & DevOps as its primary organizational subdivisions. | active | contextual | yes | |
| 51ff61ee577dc313… | At the top of the hierarchy, the company node is defined as Zeroth Agents so that all subordinate pillars, groups, and business units are organized under a single company root. | active | contextual | yes | |
| a9f83dbcb11b7aca… | The internal context engine uses a Neo4j graph with a hierarchical node structure, and the Zeroth Agents deployment maps that hierarchy to company, pillar, group, business unit, and cross-unit levels. | active | contextual | yes | |
| 556db2c7765646d4… | One target use case for the internal knowledge graph is powering daily research analysis by enriching the daily AI research pipeline with deep platform context so that relevance scoring becomes more precise. | active | contextual | yes | |
| 6df7c511c2bd19ca… | One target use case for the internal knowledge graph is onboarding new team members by providing instant access to company policies, platform architecture, client context, and operational procedures. | active | contextual | yes | |
| 55892cec8523588b… | One target use case for the internal knowledge graph is authoring contractual documents by accessing MSA templates, standard terms, SLA commitments, acceptable use policies, and NDA language with proper versioning. | active | contextual | yes | |
| 3460bd6beca12a63… | One target use case for the internal knowledge graph is 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 | |
| e725bcc824db8da8… | One target use case for the internal knowledge graph is creating presentations by sourcing platform capabilities, positioning language, client-specific talking points, and strategy frameworks for pitch decks and board presentations. | active | contextual | yes | |
| 7ecd4c9591cf4eef… | One target use case for the internal knowledge graph is 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 | |
| 37616d8757b8a621… | The specification is titled as a Zeroth Agents internal context engine deployment document and is identified as version 1.0 Draft dated April 1, 2026, authored by Ankur Tarnowski and Claude. | active | contextual | yes | |
| cff540b24df16846… | This document specifies a self-hosted internal PYRANA knowledge graph for Zeroth Agents that loads the company’s institutional knowledge so that agent-assisted workflows can access authoritative, structured context about the company, platform, clients, and standards. | active | contextual | yes | |
| f82ce10676bc3596… | Configuration-over-code is defined as agent or workflow behavior being driven by versioned YAML so that new use cases can be shipped without platform changes. | active | contextual | yes | |