| 4e999deeaeedb2d4… | Mainstream RAG deployments lack a closed learning loop because the corpus does not systematically learn from useful outcomes, failures, contradictions, or identified knowledge gaps. | active | contextual | yes | |
| 3d4b00b440cfb277… | Mainstream RAG deployments suffer from loss of governance because mandatory constraints, policies, and speculative observations are flattened into the same retrieval substrate. | active | contextual | yes | |
| e90b1b75b669bcc3… | Mainstream RAG deployments suffer from loss of atomicity because retrieved chunks often combine multiple claims, making provenance, contradiction detection, and approval workflows difficult. | active | contextual | yes | |
| 8a908bd75a35d4d0… | Mainstream retrieval-augmented generation systems typically index text in chunks, retrieve by similarity, and pass results to a model without distinguishing whether retrieved statements are policy, guidance, outdated knowledge, or contradictions, which is inadequate in regulated or operational settings. | active | contextual | yes | |
| f5c5b355b447399a… | In this structured form, a CXU can be surfaced as a mandatory requirement, compared against related procedural CXUs, linked to equipment and process entities, and protected from silent modification without approval. | active | contextual | yes | |
| de80708cfe54d763… | In the example CXU, the source scope is SOP-EBR-014, revision 7, specifying the governing source context from which the claim is derived. | active | contextual | yes | |
| cc60ea1ec5b8c84c… | In the example CXU, the lifecycle state is ACTIVE, indicating that the claim is currently in force rather than draft or inactive. | active | contextual | yes | |
| f12c772d4b8a0f41… | In the example CXU, the hash value is shown as 1220b7f2..., illustrating that each claim has a content-addressable identifier for durable identity across systems and revisions. | active | contextual | yes | |
| 066491fb3f0ae4da… | In the example CXU, the claim type is REQUIREMENT, indicating that the claim is expressed as a mandatory obligation rather than as a definition, observation, or procedure. | active | contextual | yes | |
| 1bcf1aeb8bb3ef37… | In the example CXU, the classification is REGULATED, indicating that the claim belongs to a governance tier associated with regulated handling and lifecycle controls. | active | contextual | yes | |
| 4f3a77dbd07edda0… | In the example CXU, the knowledge type is PRESCRIBED, indicating that the claim is treated as an official rule or mandated requirement rather than an observation or empirical finding. | active | contextual | yes | |
| 101c7dc83bcd6898… | In the example CXU, the supporting quote states that any change to a batch production record shall be attributable, time-stamped, and retained for review, providing evidence for the audit-trail requirement. | active | contextual | yes | |
| a3955ebddacabd4b… | In the example CXU, the claim states that electronic batch record changes must preserve a complete, time-stamped audit trail, defining a mandatory requirement in a pharmaceutical manufacturing context. | active | contextual | yes | |
| 5cd127e0bf9467a5… | Atomicity makes governance tractable because when a retrievable unit contains one claim instead of several loosely related statements, the system can independently score, approve, suppress, contradict, promote, or retire that claim. | active | contextual | yes | |
| 95219efa17299b6a… | Each CXU may carry an optional rank-0 designation for claims that must always surface under governed conditions so that mandatory claims are never omitted when those conditions apply. | active | contextual | yes | |
| af9dee94e7fd4237… | Each CXU carries a lifecycle state such as draft, active, or inactive so that the claim’s current status is explicitly governed over time. | active | contextual | yes | |
| e1cbd73f42959bf9… | Each CXU carries a claim type such as definition, requirement, procedure, observation, specification, or finding so that the form of the claim is explicitly identified. | active | contextual | yes | |
| 28eec60b039f1921… | Each CXU carries a derived classification tier that influences governance and lifecycle so that the claim can be managed according to its regulatory or operational significance. | active | contextual | yes | |
| ac3588038946245c… | Each CXU carries a knowledge type such as axiomatic, empirical, prescribed, or procedural so that the nature of the claim is explicitly categorized. | active | contextual | yes | |
| 182e1886a2da5d85… | Each CXU carries one or more supporting contexts, typically including verbatim source quotes, rationale, examples, or scope constraints, so that the claim is evidentially grounded. | active | contextual | yes | |
| 96f231edbc2ba584… | Each CXU carries a canonical claim expressed as one atomic assertion so that the unit represents exactly one governable statement. | active | contextual | yes | |
| 1667377198e965d0… | The Context Unit, abbreviated CXU, is the foundational object in the Pyrana Context Engine and is defined as a single claim linked to supporting evidence, structured metadata, and explicit governance semantics. | active | contextual | yes | |
| e1195736215a703e… | Pyrana treats enterprise knowledge as a governed system of claims, relationships, and policies rather than as a pile of vectorized text so that knowledge remains governable and semantically structured. | active | contextual | yes | |
| 1425ebbd1571922f… | The Pyrana Context Engine includes a CORTEX agent layer that observes retrieval outcomes and proposes policy-aware improvements so that the system can learn and adapt under governance constraints. | active | contextual | yes | |
| 1ceee7cb96b77927… | The Pyrana Context Engine uses strategy-aware retrieval rather than similarity-only retrieval so that retrieval behavior can reflect governance and context instead of pure semantic proximity. | active | contextual | yes | |
| 7f86e9ce3cc91c5f… | The Pyrana Context Engine attaches CXUs to a governed entity graph rather than relying only on a vector index so that retrieval and governance operate over structured relationships. | active | contextual | yes | |
| 3b9f3a591ae49981… | The Pyrana Context Engine addresses mainstream RAG problems by decomposing knowledge into atomic Context Units, or CXUs, so that knowledge can be managed at the level of single governed claims. | active | contextual | yes | |
| 8c85699905698691… | A structural problem in mainstream RAG deployments is the absence of a closed learning loop, because the corpus does not systematically learn from useful outcomes, failures, contradictions, or knowledge gaps. | active | contextual | yes | |
| 964cbdea53e2663b… | A structural problem in mainstream RAG deployments is loss of governance, because mandatory constraints, policies, and speculative observations are flattened into the same retrieval substrate. | active | contextual | yes | |
| ceebeb5dc32da6ee… | A structural problem in mainstream RAG deployments is loss of atomicity, because retrieved chunks often combine multiple claims, making provenance, contradiction detection, and approval workflows difficult. | active | contextual | yes | |
| dbb149f862a69fad… | Mainstream retrieval-augmented generation implementations typically index text in chunks, retrieve by similarity, and pass results to a model without distinguishing whether retrieved statements are policy, provisional guidance, outdated knowledge, or contradictions, which limits reliability in sensitive contexts. | active | contextual | yes | |
| 770236c270372e96… | In the structured CXU form, the claim can be surfaced as a mandatory requirement, compared against related procedural CXUs, linked to equipment and process entities, and protected from silent modification without approval. | active | contextual | yes | |
| 9c0c41ce5b313abc… | In the example CXU, the source scope is SOP-EBR-014, revision 7, specifying the governing source context for the claim. | active | contextual | yes | |
| 5e48d7fe83719d54… | In the example CXU, Rank-0 is set to Yes, indicating that the claim must always surface under governed conditions. | active | contextual | yes | |
| a8b538208cda5490… | In the example CXU, the lifecycle state is ACTIVE, indicating that the claim is currently in force within the system. | active | contextual | yes | |
| b4f476e6af0cd818… | In the example CXU, the content-addressable hash is shown as 1220b7f2..., demonstrating how a claim is assigned a durable identifier. | active | contextual | yes | |
| bd2c4fbd606b460f… | In the example CXU, the claim type is REQUIREMENT, indicating that the claim is expressed as an obligatory rule. | active | contextual | yes | |
| 17967531526f88cc… | In the example CXU, the classification is REGULATED, indicating that the claim belongs to a regulated governance tier. | active | contextual | yes | |
| 130b005fb88d4525… | In the example CXU, the knowledge type is PRESCRIBED, indicating that the claim is treated as a mandated rule rather than an observation or empirical finding. | active | contextual | yes | |
| 0d6c6ac004847dd1… | In the example CXU, the supporting quote states that any change to a batch production record shall be attributable, time-stamped, and retained for review, providing the evidentiary basis for the audit-trail requirement. | active | contextual | yes | |
| e6743e29463f192b… | In the example CXU, the claim states that electronic batch record changes must preserve a complete, time-stamped audit trail, expressing a mandatory requirement for record-change handling. | active | contextual | yes | |
| dced81465e48d2bb… | The whitepaper provides a stylized example of a CXU in a pharmaceutical manufacturing context to illustrate the structure and fields of a Context Unit. | active | contextual | yes | |
| d8b219a2807f2d04… | Atomic claims enable high-quality provenance because the system can point not only to the source document but also to the exact supporting language that justified adding the claim to the corpus. | active | contextual | yes | |
| 5383cf98e6dccecc… | Atomicity makes governance tractable because when a retrievable unit contains one claim instead of several loosely related statements, the system can score, approve, suppress, contradict, promote, or retire that claim without affecting unrelated text. | active | contextual | yes | |
| 9ef07918aee87ce3… | Each CXU may carry an optional rank-0 designation for claims that must always surface under governed conditions, enabling mandatory prominence for critical claims. | active | contextual | yes | |
| 7ab0ceb6ea3fefe5… | Each CXU carries a lifecycle state such as draft, active, or inactive so that the system can track the operational status of the claim over time. | active | contextual | yes | |
| 68aa36eaacddd9c3… | Each CXU carries a content-addressable hash so that the claim has a durable identity across systems and revisions. | active | contextual | yes | |
| c198b8e6e76c8901… | Each CXU carries a claim type such as definition, requirement, procedure, observation, specification, or finding so that the form of the claim is explicitly represented in the knowledge model. | active | contextual | yes | |
| 700a825d21d1562b… | Each CXU carries a derived classification tier that influences governance and lifecycle, allowing the system to manage claims differently based on their classification status. | active | contextual | yes | |
| 0b30538e573ab222… | Each CXU carries a knowledge type such as axiomatic, empirical, prescribed, or procedural so that the system can distinguish different kinds of knowledge for governance and retrieval. | active | contextual | yes | |