IP Library Granted Patent US 12675574
Granted Patent B1
US 12675574 · App. 19/536,124 · Granted Jul 7, 2026

Non-bypassable governance of partitioned contextual memory for conditioning execution

Inventors: Vedran Jukic (Trieste, IT); Harold Arkoff (Sudbury, MA)
Assignee: OneSource Solutions International, Inc.
G06F21/57G06F16/21G06F21/6227H04L41/0894
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12675574
App. No.
19/536,124
Granted
Jul 7, 2026
Kind
B1
Abstract

Computer systems and methods are disclosed for governing use of patient scoped contextual information during execution of reasoning models, agentic systems, and orchestration workflows operating over regulated data. A patient partitioned contextual memory stores memory atoms associated with provenance metadata, temporal validity metadata, and governance attributes. In response to a task request associated with a patient identity, a retrieval engine selects a candidate set of memory atoms for evaluation by a non-bypassable memory gate under an applicable policy snapshot identifier (or policy digest) and one or more integrity criteria. The memory gate determines admissibility and authorized transformation of memory atoms, and a governed context bundle is deterministically assembled from admitted memory atoms subject to a context capacity constraint. Execution is permitted only through a constrained execution interface requiring the governed context bundle and a gate produced governance artifact. In some embodiments, downstream reliance is conditioned on verification of a readiness artifact.

Claims (10)

1 . A computer-implemented method for governing use of patient scoped contextual information in execution of a governed execution component, the method comprising: retrieving, from a patient partitioned contextual memory storing memory atoms associated with a patient identity, a candidate set of memory atoms responsive to a task request associated with the patient identity; evaluating, by a non-bypassable memory-gating operation and prior to execution of the governed execution component, each memory atom in the candidate set under an applicable policy snapshot identifier and one or more integrity criteria; determining, by the memory-gating operation for each evaluated memory atom, an admissibility state comprising at least one of admission, denial, redaction, abstraction, or attenuation, and denying admission of, or admitting only in a non-data-bearing transformed form, each memory atom for which admissibility cannot be established; applying a completeness evaluation as part of the one or more integrity criteria by determining whether a completeness criterion for the task request is satisfied by confirming availability, within an admitted set of memory atoms determined by the memory-gating operation, of at least one admissible memory atom from each of one or more designated mandatory atom classes, and, responsive to determining that the completeness criterion is not satisfied, recording an integrity exception event comprising an omission event and denying or deferring execution of the governed execution component under a fail-closed policy; assembling, prior to execution of the governed execution component, a governed context bundle comprising an included set of memory atoms selected from the admitted set of memory atoms, the governed context bundle being associated with a bundle identifier bound to the applicable policy snapshot identifier; generating an execution governance artifact associated with the memory-gating operation and bound to the bundle identifier; conditioning execution of the governed execution component by invoking the governed execution component through a constrained execution interface that requires presentation of a governed execution package comprising the governed context bundle and the execution governance artifact, provides only the governed context bundle as patient scoped contextual input to the governed execution component, and programmatically rejects execution requests lacking the governed execution package or failing cryptographic or credential-based validation at the constrained execution interface; recording a governance record identifying at least the bundle identifier, the applicable policy snapshot identifier, and identifiers of the included set of memory atoms; and conditioning acceptance of a reliance event associated with output generated by the governed execution component on presentation of a readiness artifact bound to the bundle identifier and the applicable policy snapshot identifier.

2 . The method of claim 1 , wherein the constrained execution interface enforces non-bypassable execution by restricting invocation of the governed execution component to a credential-scoped network endpoint that denies direct access to the governed execution component absent presentation of the governed execution package.

3 . The method of claim 1 , wherein programmatically rejecting execution requests comprises validating a cryptographic binding between the execution governance artifact, the bundle identifier, and the applicable policy snapshot identifier.

4 . The method of claim 1 , wherein the completeness criterion corresponds to a completeness evaluation requiring inclusion of at least one memory atom from each of a predefined set of mandatory atom classes comprising at least one of contraindication data, medication data, or baseline condition data.

5 . The method of claim 1 , further comprising generating an insufficient-context state when the completeness criterion is not satisfied, and suppressing output generation or restricting downstream reliance based on the insufficient-context state.

6 . The method of claim 1 , wherein the governed context bundle is assembled using a deterministic ordering rule and a canonical serialization format recorded as governance metadata to enable deterministic replay.

7 . The method of claim 1 , wherein the bundle identifier is computed as a cryptographic hash over at least the included set of memory atoms and the applicable policy snapshot identifier.

8 . The method of claim 1 , wherein the readiness artifact comprises at least one of a signed bundle identifier, a signed policy snapshot identifier, or a signed evidence bundle digest, and is verified prior to acceptance of the reliance event.

9 . The method of claim 1 , wherein evaluating each memory atom under the one or more integrity criteria comprises performing at least one of provenance verification, temporal validity evaluation, or contradiction detection.

10 . The method of claim 1 , wherein admitting a memory atom in a non-data-bearing transformed form comprises generating an abstracted representation that constrains downstream execution without exposing underlying patient data.