Vendor-neutral OWL/SHACL — same rule, any platform

OWL Portability Layer — clinical compliance walkthrough

A clinical-data agent requests export of a de-identified patient cohort for an IRB-approved substudy. The same OWL/SHACL compliance rule must hold regardless of which enterprise platform executes the action.

How the portability layer works

owl-portability-layer user request flowHow the same OWL/SHACL check runs across multiple enterprise platformsAgent action requestPlatform context layerwhat does this entity mean?Platform access controlis this agent allowed to call this tool?OWL portability layerdoes this record satisfy the formal rule?samecheckeveryplatformPlatform adapterDatabricks, OpenAI, Palantir, AWS, IBM...yesnoAllowedaction runsBlockedreason returnedswap the platform adapter -- verdict never changesgithub.com/cloudbadal007/owl-portability-layer

Platform selected: Microsoft Fabric IQ. The compliance rule below does not change when you switch adapters.

Action

Export cohort C-8842 (n=312) — includes 14 records flagged REVIEW_REQUIRED — to external analytics workspace

Portable rule (SHACL)

SHACL: No export may include subjects with ex:reviewStatus "REVIEW_REQUIRED" unless ex:irbWaiver is true.

  1. 1

    Agent proposes an action

    The clinical analytics agent formats a platform-native API call. Without a portability layer, each platform interprets the payload differently.

  2. 2

    OWL Portability Layer validates

    The payload is lifted to RDF and checked against the same SHACL shapes — independent of Palantir, Fabric, or ServiceNow semantics.

  3. 3

    Platform adapter routes

    Only the adapter key changes. The constraint proof is identical across all nine registered adapters in simulation mode.

  4. 4

    Deterministic outcome

    Blocked or cleared — with the same reason string and rule version — no matter which vendor stack sits underneath.

See live SHACL validation on OntoGuard →