| 32bc75e1ecebf936… | Within the PYRANA_PLATFORM set, the relationship claim type is exemplified by PlannerDelegatorWorkflow delegating execution to GenericExecutorWorkflow, which dispatches execute_action_agent per DAG node, so that workflow relationships have a concrete example. | active | contextual | yes | |
| c945af7e0642cbc8… | Within the PYRANA_PLATFORM set, the requirement claim type is exemplified by requiring all new platform functionality to start as a library package before promotion to an application so that requirement-style knowledge has a concrete example. | active | contextual | yes | |
| 3e4d6da8926830bd… | Within the PYRANA_PLATFORM set, the procedure claim type is exemplified by registering agent tools via the @tool() decorator and discovering them at startup through entry points, convention scan, and static manifest so that procedural knowledge has a concrete example. | active | contextual | yes | |
| f6758368dc659f96… | Within the PYRANA_PLATFORM set, the specification claim type is exemplified by Tier 1 execution using forked Python subprocesses with seccomp filtering and targeting P99 latency under 100 milliseconds so that specification-style knowledge has a concrete example. | active | contextual | yes | |
| 6a5016902efd2fe8… | Within the PYRANA_PLATFORM set, the definition claim type is exemplified by describing PyranaHarness as the core orchestration engine implementing native LLM tool calling via LiteLLM so that definitional platform knowledge has a model example. | active | contextual | yes | |
| 675915651a8cbe18… | The named relationship PYRANA_PLATFORM:INFRASTRUCTURE is defined to cover Azure, Kubernetes, CI/CD, and observability so that infrastructure knowledge is grouped within the platform set. | active | contextual | yes | |
| 56288e882464781b… | The named relationship PYRANA_PLATFORM:FRONTEND is defined to cover TypeScript libraries, @pyrana packages, and templates so that frontend platform knowledge is grouped together. | active | contextual | yes | |
| 52ad6989a7e3571e… | The named relationship PYRANA_PLATFORM:CODE_INTERPRETER is defined to cover tiered execution, plans, and classification so that code interpreter knowledge is organized as a distinct platform subdomain. | active | contextual | yes | |
| 838ce04aef51319c… | The named relationship PYRANA_PLATFORM:CONTEXT_ENGINE is defined to cover KAG, the CXU model, CORTEX agents, and retrieval so that context-engine knowledge is grouped in one subdomain. | active | contextual | yes | |
| 0ec969aec7528010… | The named relationship PYRANA_PLATFORM:CORE is defined to cover Python libraries, agent orchestration, and PyranaHarness so that core backend platform knowledge is grouped together. | active | contextual | yes | |
| 2373f3c4e77b61b5… | The purpose of the PYRANA_PLATFORM set is to contain complete technical knowledge of PYRANA architecture, capabilities, and APIs so that platform-specific technical context is comprehensively organized. | active | contextual | yes | |
| 5fb59900f21c4217… | One Rank 0 CXU states that PYRANA follows a libs-first philosophy in which all new functionality starts in library packages so that platform development begins from reusable libraries. | active | contextual | yes | |
| 7d34e4dace125d01… | One Rank 0 CXU states that PYRANA is configuration-driven and multi-tenant, with client behavior driven by YAML configs rather than hardcoded logic, so that its architectural model is always available. | active | contextual | yes | |
| 27d64d1cca3bd17e… | One Rank 0 CXU states that Zeroth Agents builds PYRANA as an enterprise agentic application platform so that company-product identity is always included in core context. | active | contextual | yes | |
| 01a3b2c0e826c3ba… | Rank 0 CXUs are defined as context units that are always included so that the most essential foundational knowledge is guaranteed to appear in retrieval. | active | contextual | yes | |
| 275e387a7f363a24… | The UNIVERSAL set primarily uses axiomatic knowledge for foundational truths and prescribed knowledge for approved self-description so that both stable facts and official positioning are represented. | active | contextual | yes | |
| acafc4d2e8a16efe… | The UNIVERSAL set includes team structure and key roles so that organizational context about personnel and responsibilities is always available to queries. | active | contextual | yes | |
| 40a41f48b4f4ddc2… | The UNIVERSAL set includes key differentiators versus competitors so that competitive positioning knowledge is always available as foundational context. | active | contextual | yes | |
| 7bbc5374bceb817e… | The UNIVERSAL set includes the core value proposition that PYRANA is an enterprise-grade, configuration-driven, multi-tenant agentic AI platform so that the platform’s primary positioning is always retrievable. | active | contextual | yes | |
| 4cdb26d74e2e50e1… | The UNIVERSAL set includes brand identity knowledge stating that OAAX is a subsidiary or related brand so that brand relationships remain available in all query contexts. | active | contextual | yes | |
| 6defb6143faf3940… | The UNIVERSAL set includes product identity knowledge defining PYRANA as the Agentic Application Platform so that the core product name and category are always in scope. | active | contextual | yes | |
| c753f8a81584abff… | The UNIVERSAL set includes company identity knowledge specifying Zeroth Agents Inc., founded by Ankur Tarnowski (Eric Tarnowski), and headquartered in New Jersey so that core corporate identity is always available. | active | contextual | yes | |
| cf3a8fd848424fff… | 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 consistently accessible. | active | contextual | yes | |
| 62e225acf47db222… | The UNIVERSAL set is always in scope for every query so that foundational knowledge remains available regardless of the specific query context. | active | contextual | yes | |
| 2d47ba057c81d23b… | CXUs can belong to multiple sets at the same time so that a single context unit can be reused across more than one bounded knowledge domain. | active | contextual | yes | |
| c00265b01a93ce22… | Sets are defined as the primary organizational mechanism for CXUs, with each set defining a bounded knowledge domain so that extracted knowledge is structured within explicit scope boundaries. | active | contextual | yes | |
| 0fb2014ead3f5bd7… | CrossUnit Pricing & Licensing is defined as a cross-unit domain that spans Sales, Legal, and Client Delivery so that pricing and licensing knowledge across those functions can be managed together. | active | contextual | yes | |
| b532731d43c88574… | CrossUnit Security is defined as a cross-unit domain that spans Corporate Operations and Platform Engineering so that security knowledge crossing those two pillars is grouped in one organizational unit. | active | contextual | yes | |
| 02a8c34c412e59d1… | CrossUnit AI Strategy is defined as a cross-unit domain that spans Platform Engineering, Client Delivery, and Sales so that knowledge shared across those three pillars can be organized together. | active | contextual | yes | |
| 34fb44e0bee9877a… | The estimated CXU count for the PYRANA_PLATFORM set is 300 to 500 units, indicating the expected extraction volume for that technical knowledge domain. | active | contextual | yes | |
| e0f50a2ae22c5284… | The PYRANA_PLATFORM set draws extraction content from the Drive document Pyrana Overview - Core.pptx as one of its specified source documents. | active | contextual | yes | |
| 3c4507455cac8477… | The PYRANA_PLATFORM set draws extraction content from the Drive document PYRANA Architecture.pptx as one of its specified source documents. | active | contextual | yes | |
| b61daad56dae99a6… | The PYRANA_PLATFORM set draws extraction content from PYRANA_PLATFORM_ARCHITECTURE_REFERENCE.md as one of its specified source documents. | active | contextual | yes | |
| 06d538531afb50ab… | The PYRANA_PLATFORM set draws extraction content from zeroth-agents/pyrana-frontend-template/README.md as one of its specified source documents. | active | contextual | yes | |
| 6dd76b205c5f61ed… | The PYRANA_PLATFORM set draws extraction content from zeroth-agents/pyrana-code-interpreter-tiered/docs/TIERED_ARCHITECTURE_DESIGN.md as one of its specified source documents. | active | contextual | yes | |
| 3e0fd822c43dfd18… | The PYRANA_PLATFORM set draws extraction content from zeroth-agents/pyrana-context-engine/CLAUDE.md as one of its specified source documents. | active | contextual | yes | |
| 0220c0b07999241b… | The PYRANA_PLATFORM set draws extraction content from zeroth-agents/pyrana/CLAUDE.md as one of its specified source documents. | active | contextual | yes | |
| b1fc06e1ec662e5a… | Within the PYRANA_PLATFORM set, prescribed knowledge consists of design decisions and standards, such as requiring all tools to use the @tool() decorator with appropriate flags. | active | contextual | yes | |
| 2e8b3ec41de720f7… | Within the PYRANA_PLATFORM set, derived knowledge consists of conclusions drawn from implementation, such as the 3-strategy KAG retrieval pipeline providing fallback resilience when template queries return no results. | active | contextual | yes | |
| 6ca1d62aae42ff4b… | Within the PYRANA_PLATFORM set, axiomatic knowledge consists of stable architectural facts such as PYRANA using Temporal for workflow orchestration. | active | contextual | yes | |
| d40c59cde63e0527… | The PYRANA_PLATFORM set uses a relationship-style claim for statements such as PlannerDelegatorWorkflow delegating execution to GenericExecutorWorkflow, which dispatches execute_action_agent per DAG node. | active | contextual | yes | |
| fc3bc84a629fe3dd… | The PYRANA_PLATFORM set uses the claim type requirement for statements such as all new platform functionality having to start as a library package before promotion to an application. | active | contextual | yes | |
| 339ed626843f0d22… | The PYRANA_PLATFORM set uses the claim type procedure for statements such as agent tools being registered via the @tool() decorator and discovered at startup through entry points, convention scan, and static manifest. | active | contextual | yes | |
| 7e377fb82d359274… | The PYRANA_PLATFORM set uses the claim type specification for statements such as Tier 1 execution using forked Python subprocesses with seccomp filtering and targeting P99 latency under 100 milliseconds. | active | contextual | yes | |
| 96fb7b18318fddec… | The PYRANA_PLATFORM set uses the claim type definition for statements such as PyranaHarness being the core orchestration engine that implements native LLM tool calling via LiteLLM. | active | contextual | yes | |
| eb2a8cf30ee35a7b… | The named relationship PYRANA_PLATFORM:INFRASTRUCTURE covers Azure, Kubernetes, CI/CD, and observability within the PYRANA platform knowledge set. | active | contextual | yes | |
| cfafbb17f0a794f1… | The named relationship PYRANA_PLATFORM:FRONTEND covers TypeScript libraries, @pyrana/* packages, and templates within the PYRANA platform knowledge set. | active | contextual | yes | |
| c971ceeeefe42b19… | The named relationship PYRANA_PLATFORM:CODE_INTERPRETER covers tiered execution, plans, and classification within the PYRANA platform knowledge set. | active | contextual | yes | |
| a543e120b6938a9d… | The named relationship PYRANA_PLATFORM:CONTEXT_ENGINE covers KAG, the CXU model, CORTEX agents, and retrieval within the PYRANA platform knowledge set. | active | contextual | yes | |
| 4d546fc8572848bd… | The named relationship PYRANA_PLATFORM:CORE covers Python libraries, agent orchestration, and PyranaHarness within the PYRANA platform knowledge set. | active | contextual | yes | |