| 37eab12522eea40f… | The example CXU has lifecycle status ACTIVE so that the claim is treated as currently in force within the system. | active | contextual | yes | |
| d51ffb2e643308d9… | The example CXU includes a hash value, shown as 1220b7f2..., so that the unit can be uniquely identified and tracked. | active | contextual | yes | |
| f21442b2bf24b42d… | The example identifies the audit-trail claim type as REQUIREMENT so that the unit is interpreted as a mandatory obligation rather than descriptive information. | active | contextual | yes | |
| c16b486749b3efb1… | The example classifies the audit-trail claim as REGULATED so that it is recognized as subject to regulatory governance constraints. | active | contextual | yes | |
| 5d8ea89ed186b867… | The example classifies the electronic batch record audit-trail claim as PRESCRIBED knowledge so that the system treats it as an official rule rather than an inferred observation. | active | contextual | yes | |
| d19466ac1520c644… | In the example CXU, the supporting evidence is the statement that any batch production record change must be attributable, time-stamped, and retained for review so that the requirement is explicitly justified. | active | contextual | yes | |
| 7fdd3e14ff0ef6b0… | Electronic batch record changes must preserve a complete, time-stamped audit trail when modifications occur so that the record remains attributable and reviewable. | active | contextual | yes | |
| 7bbd11d61b770360… | The whitepaper presents a stylized pharmaceutical manufacturing example to show what a CXU looks like in practice so that readers can understand the structure of a Context Unit. | active | contextual | yes | |
| c31fd8805f5381bd… | A Context Unit can point not only to its source document but also to the exact supporting language that justified the claim entering the corpus so that provenance is preserved at the evidence level. | active | contextual | yes | |
| 0aa4e155c41aac03… | Scope relationships express membership in sets, domains, or operating boundaries so that the graph can represent where knowledge applies. | active | contextual | yes | |
| 794cb05b257b7426… | Knowledge relationships include dependency, contradiction, specification, or governance links so that the graph can represent interactions among knowledge units. | active | contextual | yes | |
| 8dc2af6548d8be87… | Context relationships link a CXU to the entity or entities it concerns so that claims are connected to their subject matter. | active | contextual | yes | |
| 2ef85175a0d4201e… | At a high level, the graph distinguishes three classes of relationships: context relationships, knowledge relationships, and scope relationships. | active | contextual | yes | |
| 031d6a90eb74bd41… | Scoped sets provide a practical path to multi-tenant knowledge management because shared foundational knowledge can coexist with tenant- or department-specific corpora while preserving scoped retrieval and governance. | active | contextual | yes | |
| 3f31b8385bd27eba… | Sets create scoped subgraphs that let the system answer the same question differently depending on the active domain, tenant, or policy frame. | active | contextual | yes | |
| eee2029a8e500084… | A CXU may belong to multiple sets, including universal sets and sets representing a regulatory regime, business unit, customer environment, region, or internal operating boundary. | active | contextual | yes | |
| 9aac4eb6f413ceb0… | Graph attachment makes relational enterprise questions first-class so that the system can directly support those question types. | active | contextual | yes | |
| ab100d2b7f587d3b… | The whitepaper gives example relational enterprise questions about which procedures govern equipment, what changed for a process after a policy update, which requirements apply to one department but not another, and what evidence supports a workflow instruction. | active | contextual | yes | |
| 5d69d4a5b3230b96… | Enterprise questions are usually relational rather than simple similarity searches, meaning users are not only asking for a paragraph similar to their query. | active | contextual | yes | |
| 007e0a0559f88fd4… | CXUs attach to entities through explicit relationships so that retrieval can reason over what knowledge is about rather than only the words it contains. | active | contextual | yes | |
| a194f210fb686400… | The graph model provides a stable representation of real-world organizational objects including products, facilities, SOPs, regulations, systems, departments, controls, vendors, and process steps. | active | contextual | yes | |
| 43c28b94bd149b60… | The graph is the second foundation of the system, and CXUs do not exist in isolation because they attach to canonical entities and scoped knowledge sets that define where, how, and for whom a claim applies. | active | contextual | yes | |
| fb7afb20c31b5959… | The CXU is presented as the reason the rest of the architecture works because without atomic claims, provenance, policy, contradiction handling, and learning become much harder to govern. | active | contextual | yes | |
| 1693bed03771d9ad… | Pyrana differs centrally from conventional retrieval pipelines because most RAG systems apply governance after retrieval as an application-layer patch, whereas Pyrana begins governance at the unit of knowledge itself. | active | contextual | yes | |
| 684ac7ada7281f65… | Contextual, tribal, and derived claims can evolve more freely when conflict checks and evidence thresholds are satisfied so that less critical knowledge remains adaptable. | active | contextual | yes | |
| c99dfbc144f51a95… | Regulated claims can require approval for lifecycle changes so that changes to governed knowledge receive explicit authorization. | active | contextual | yes | |
| 9e2a279ecd36f47a… | Foundational or policy-critical claims can be protected from autonomous modification so that highly sensitive knowledge is not changed automatically. | active | contextual | yes | |
| fc368000950022fc… | The classification model determines what the system may do with a claim so that system behavior is governed by claim classification. | active | contextual | yes | |
| bdd5e06f590358cc… | In this CXU form, a claim can be surfaced as a mandatory requirement, compared with related procedural CXUs, linked to equipment and process entities, and protected from silent modification without approval. | active | contextual | yes | |
| 7f881ebc81c86663… | The example CXU includes governance metadata showing hash 1220b7f2..., lifecycle ACTIVE, Rank-0 Yes, and source scope SOP-EBR-014 revision 7 so that the claim is traceable and managed. | active | contextual | yes | |
| e5ec201cfdd5726f… | The example CXU classifies the batch-record audit-trail claim as prescribed knowledge with a regulated classification and a requirement claim type. | active | contextual | yes | |
| d71f510c10d5952f… | In the example CXU, electronic batch record changes must preserve a complete, time-stamped audit trail so that modifications remain attributable and reviewable. | active | contextual | yes | |
| 0782b0866a395186… | The whitepaper presents a stylized CXU example in a pharmaceutical manufacturing context to illustrate what a CXU looks like in practice. | active | contextual | yes | |
| 0024e19330523eb0… | A CXU can reference not only its source document but also the exact supporting language that justified adding the claim to the corpus so that provenance is preserved at the evidence level. | active | contextual | yes | |
| 88608b26f00e0d92… | In the example CXU, the hash value is shown as 1220b7f2..., indicating that the claim is assigned a durable identifier. | active | contextual | yes | |
| 4a7d4dc3c970558a… | In the example CXU, the knowledge type is PRESCRIBED, the classification is REGULATED, the claim type is REQUIREMENT, the lifecycle is ACTIVE, rank-0 is Yes, and the source scope is SOP-EBR-014 revision 7. | active | contextual | yes | |
| dff7f8b3701b2191… | In the example CXU, the supporting quote requires that any change to a batch production record be attributable, time-stamped, and retained for review. | active | contextual | yes | |
| e5eadf3d34af460a… | In the example CXU, the claim states that electronic batch record changes must preserve a complete, time-stamped audit trail so that changes remain fully traceable. | active | contextual | yes | |
| ff8e75962298a0a0… | Atomic CXUs enable high-quality provenance because the system can point not only to the source document but also to the exact supporting language that justified the claim entering the corpus. | active | contextual | yes | |
| 94ccf153a2f8a459… | Each CXU can include an optional rank-0 designation for claims that must always surface under governed conditions. | active | contextual | yes | |
| 68a6cfed50a1697e… | Each CXU includes a lifecycle state such as draft, active, or inactive so that the system can manage the claim through its operational status. | active | contextual | yes | |
| e298ebf7ecf6f22f… | Each CXU includes a content-addressable hash so that the claim has a durable identity across systems and revisions. | active | contextual | yes | |
| bdeba13caecffa73… | Each CXU includes a claim type such as definition, requirement, procedure, observation, specification, or finding so that the form of the claim is explicitly categorized. | active | contextual | yes | |
| b777c2d8bbf6b6d1… | Each CXU includes a derived classification tier that influences governance and lifecycle so that the claim can be managed according to its regulatory or operational status. | active | contextual | yes | |
| d1fffe72c4fbe6cb… | Each CXU includes a knowledge type such as axiomatic, empirical, prescribed, or procedural so that the system can distinguish the nature of the knowledge. | active | contextual | yes | |
| c1bf3ddd71447a5d… | Each CXU includes one or more supporting contexts, typically verbatim source quotes, rationale, examples, or scope constraints, so that the claim is evidentially grounded. | active | contextual | yes | |
| 1551b3883a56ae95… | Each CXU includes a canonical claim expressed as one atomic assertion so that the unit preserves a single governed statement. | active | contextual | yes | |
| fece40e057c59bc3… | The Context Unit (CXU) is the foundational object in the Pyrana Context Engine and represents a single claim linked to supporting evidence, structured metadata, and explicit governance semantics rather than a document chunk or undifferentiated embedding payload. | active | contextual | yes | |
| 5465046db610448e… | Pyrana models enterprise knowledge as a governed system of claims, relationships, and policies rather than as a collection of vectorized text. | active | contextual | yes | |
| 76b7bbad64a60a63… | The Pyrana Context Engine addresses mainstream RAG limitations by decomposing knowledge into atomic Context Units, attaching them to a governed entity graph, using strategy-aware retrieval, and adding a CORTEX agent layer that proposes policy-aware improvements. | active | contextual | yes | |