| 2b55e55f82d95b9c… | The architecture-related extraction set is expected to produce approximately 300 to 500 CXUs so that the knowledge graph captures broad coverage of platform and workflow architecture. | active | contextual | yes | |
| a2b03714be574889… | The architecture extraction effort should use seven named source documents, including CLAUDE files, architecture references, a frontend README, and two Drive presentations, so that architectural CXUs are grounded in the listed primary materials. | active | contextual | yes | |
| a73ea4743a17d770… | The specification defines three knowledge types for extraction: axiomatic facts are stable architectural truths, empirical knowledge is derived from implementation conclusions, and prescribed knowledge captures design decisions and standards so that extracted CXUs are categorized by source and certainty. | active | contextual | yes | |
| c51e3197d6d8322d… | The estimated CXU count for the PYRANA_PLATFORM set is 300 to 500 units so that extraction planning reflects the expected scale of platform knowledge coverage. | active | contextual | yes | |
| b49f31ba7cdc2ade… | Extraction for the PYRANA_PLATFORM set should use the Pyrana Overview - Core.pptx file from Drive as one of its source documents so that core overview presentation knowledge is included. | active | contextual | yes | |
| ccc5ff2f9a32ae09… | Extraction for the PYRANA_PLATFORM set should use the PYRANA Architecture.pptx file from Drive as one of its source documents so that presentation-based architecture knowledge is included. | active | contextual | yes | |
| 0b37fc9f594e20a4… | Extraction for the PYRANA_PLATFORM set should use PYRANA_PLATFORM_ARCHITECTURE_REFERENCE.md as one of its source documents so that architecture reference material is incorporated. | active | contextual | yes | |
| fede3c80d8966eec… | Extraction for the PYRANA_PLATFORM set should use zeroth-agents/pyrana-frontend-template/README.md as one of its source documents so that frontend template knowledge is included. | active | contextual | yes | |
| 5e426057bfd1c6df… | Extraction for the PYRANA_PLATFORM set should use zeroth-agents/pyrana-code-interpreter-tiered/docs/TIERED_ARCHITECTURE_DESIGN.md as one of its source documents so that tiered code interpreter architecture is covered. | active | contextual | yes | |
| 7404cb24b26c352f… | Extraction for the PYRANA_PLATFORM set should use zeroth-agents/pyrana-context-engine/CLAUDE.md as one of its source documents so that context engine knowledge is included in platform extraction. | active | contextual | yes | |
| 61fa17331c42496e… | Extraction for the PYRANA_PLATFORM set should use zeroth-agents/pyrana/CLAUDE.md as one of its source documents so that platform knowledge is grounded in that repository reference. | active | contextual | yes | |
| e35466216fbb83e4… | Knowledge types for the PYRANA_PLATFORM set include prescribed knowledge for design decisions and standards, such as requiring all tools to use the @tool() decorator with appropriate flags. | active | contextual | yes | |
| 8cb64e528d8f7b7c… | Knowledge types for the PYRANA_PLATFORM set include derived knowledge for conclusions drawn from implementation, such as the 3-strategy KAG retrieval pipeline providing fallback resilience when template queries return no results. | active | contextual | yes | |
| cf78de26bceee7f3… | Knowledge types for the PYRANA_PLATFORM set include axiom for stable architectural facts, such as PYRANA using Temporal for workflow orchestration. | active | contextual | yes | |
| 15ef356ca674a61f… | Within the PYRANA_PLATFORM set, the relationship claim form is used for statements such as PlannerDelegatorWorkflow delegating execution to GenericExecutorWorkflow, which dispatches execute_action_agent per DAG node. | active | contextual | yes | |
| 4ec4bc148b42148f… | Within the PYRANA_PLATFORM set, the requirement claim type is used for the rule that all new platform functionality must start as a library package before being promoted to an application. | active | contextual | yes | |
| 1589e0e8dc44d89e… | Within the PYRANA_PLATFORM set, the procedure claim type is used for the process where agent tools are registered via the @tool() decorator and discovered at startup through entry points, convention scan, and static manifest. | active | contextual | yes | |
| 11695ba97ebcda99… | Within the PYRANA_PLATFORM set, the specification claim type is used for statements such as Tier 1 execution using forked Python subprocesses with seccomp filtering and targeting P99 latency under 100 milliseconds. | active | contextual | yes | |
| 79e393da2063161c… | Within the PYRANA_PLATFORM set, the definition claim type is used for statements such as PyranaHarness being the core orchestration engine that implements native LLM tool calling via LiteLLM. | active | contextual | yes | |
| cd0341acf5be528d… | The PYRANA_PLATFORM set is sub-organized through named relationships, including PYRANA_PLATFORM:INFRASTRUCTURE for Azure, Kubernetes, CI/CD, and observability. | active | contextual | yes | |
| d8669af5095ef821… | The PYRANA_PLATFORM set is sub-organized through named relationships, including PYRANA_PLATFORM:FRONTEND for TypeScript libraries, @pyrana packages, and templates. | active | contextual | yes | |
| bcf1bb018157120d… | The PYRANA_PLATFORM set is sub-organized through named relationships, including PYRANA_PLATFORM:CODE_INTERPRETER for tiered execution, plans, and classification. | active | contextual | yes | |
| dc6f91fb81da8009… | The PYRANA_PLATFORM set is sub-organized through named relationships, including PYRANA_PLATFORM:CONTEXT_ENGINE for KAG, the CXU model, CORTEX agents, and retrieval. | active | contextual | yes | |
| 12a9c40d5b59033f… | The PYRANA_PLATFORM set is sub-organized through named relationships, including PYRANA_PLATFORM:CORE for Python libraries, agent orchestration, and PyranaHarness. | active | contextual | yes | |
| 6348301114624e19… | The purpose of the PYRANA_PLATFORM set is to contain complete technical knowledge of the PYRANA platform architecture, capabilities, and APIs so that platform-specific technical context is fully covered. | active | contextual | yes | |
| 26e85242a47a9010… | Rank 0 CXUs are always included and include the statement that PYRANA follows a libs-first philosophy in which all new functionality starts in library packages. | active | contextual | yes | |
| 4e7accfb6d3c3402… | Rank 0 CXUs are always included and include the statement that PYRANA is configuration-driven and multi-tenant, with client behavior driven by YAML configs rather than hardcoded logic. | active | contextual | yes | |
| 7756ee463dc2116e… | Rank 0 CXUs are always included and include the statement that Zeroth Agents builds PYRANA as an enterprise agentic application platform so that this foundational product identity is never omitted. | active | contextual | yes | |
| 32ababdbe69196bb… | Knowledge in the UNIVERSAL set is primarily classified as axiom for foundational truths and prescribed for approved self-description so that both factual identity and official positioning are represented. | active | contextual | yes | |
| c2a72aa7170aca00… | The UNIVERSAL set includes team structure and key roles so that foundational organizational knowledge is available in every query context. | active | contextual | yes | |
| 88a05c20f57cdd93… | The UNIVERSAL set includes key differentiators versus competitors so that comparative positioning knowledge is always available in foundational context. | active | contextual | yes | |
| b68ad993ba9f60fa… | The UNIVERSAL set includes brand identity knowledge specifying OAAX as a subsidiary or related brand. | active | contextual | yes | |
| 3ac5c52cbba23d0a… | The UNIVERSAL set includes product identity knowledge specifying that the product is the PYRANA Agentic Application Platform. | active | contextual | yes | |
| ae980bbc8fbe5666… | The UNIVERSAL set includes company identity knowledge stating that the company is Zeroth Agents Inc., founded by Ankur Tarnowski (Eric Tarnowski), and headquartered in New Jersey. | active | contextual | yes | |
| 621d3ac09271f367… | The purpose of the UNIVERSAL set is to hold foundational facts that should always be available regardless of query context so that baseline company and product knowledge is consistently accessible. | active | contextual | yes | |
| 18680708cade45af… | A CXU can belong to multiple sets when its knowledge is relevant to more than one bounded domain so that the same unit can be reused across contexts. | active | contextual | yes | |
| 02ad50fc71d2ad35… | CrossUnit Pricing & Licensing spans the Sales, Legal, and Client Delivery areas so that pricing and licensing knowledge can be managed across those multiple organizational domains. | active | contextual | yes | |
| b9519f41802cad6e… | CrossUnit Security spans the Corporate Operations and Platform Engineering pillars so that security knowledge that applies to both domains is organized across multiple pillars. | active | contextual | yes | |
| 84e5f0e4c101fc52… | CrossUnit AI Strategy spans the Platform Engineering, Client Delivery, and Sales pillars so that knowledge shared across those organizational areas can be grouped under one cross-unit. | active | contextual | yes | |
| aba22876fea68e0f… | The estimated CXU count for the PYRANA_PLATFORM set is 300 to 500 so that the expected extraction volume for this technical domain is explicitly scoped. | active | contextual | yes | |
| 9fe000187970fb40… | The PYRANA platform extraction sources include the Drive file Pyrana Overview - Core.pptx so that core platform overview knowledge can be drawn from that presentation. | active | contextual | yes | |
| dc07140ca6e004d4… | The PYRANA platform extraction sources include the Drive file PYRANA Architecture.pptx so that platform architecture knowledge can be drawn from that presentation. | active | contextual | yes | |
| 408ddc409436c6a6… | The PYRANA platform extraction sources include PYRANA_PLATFORM_ARCHITECTURE_REFERENCE.md so that architecture reference knowledge can be drawn from that specification document. | active | contextual | yes | |
| db058776ec65344f… | The PYRANA platform extraction sources include zeroth-agents/pyrana-frontend-template/README.md so that frontend template knowledge can be drawn from that repository readme. | active | contextual | yes | |
| 96d752bc246d499d… | The PYRANA platform extraction sources include zeroth-agents/pyrana-code-interpreter-tiered/docs/TIERED_ARCHITECTURE_DESIGN.md so that tiered code interpreter knowledge can be drawn from that design document. | active | contextual | yes | |
| 7cb1a4ceb5228505… | The PYRANA platform extraction sources include zeroth-agents/pyrana-context-engine/CLAUDE.md so that context-engine knowledge for this set can be drawn from that repository document. | active | contextual | yes | |
| 220a3f8621c859d3… | The PYRANA platform extraction sources include zeroth-agents/pyrana/CLAUDE.md so that technical knowledge for this set can be drawn from that repository document. | active | contextual | yes | |
| bccd4dc913e2710f… | Within the PYRANA_PLATFORM set, prescribed knowledge is defined as design decisions and standards, exemplified by requiring all tools to use the @tool() decorator with appropriate flags, so that mandated platform conventions are categorized consistently. | active | contextual | yes | |
| 4dacfad5565f49b3… | Within the PYRANA_PLATFORM set, derived knowledge is defined as conclusions drawn from implementation, exemplified by the 3-strategy KAG retrieval pipeline providing fallback resilience when template queries return no results, so that inferred technical conclusions are categorized consistently. | active | contextual | yes | |
| 72a3ecaa05b6f646… | Within the PYRANA_PLATFORM set, axiomatic knowledge is defined as stable architectural facts, exemplified by PYRANA using Temporal for workflow orchestration, so that enduring platform truths are categorized consistently. | active | contextual | yes | |