Skip to content
@jhcontext

jhcontext

jhcontext is our reference implementation of the PAC-AI protocol, a Provenance-Aware Context for AI.

jhcontext — PAC-AI: Provenance-Aware Context for Auditable Multi-Agent AI Systems

jhcontext is a research programme and reference implementation for PAC-AI — a provenance-aware context protocol for auditable multi-agent AI systems, designed for EU AI Act compliance and adjacent regulatory regimes (FDA SaMD, MDR / MHRA, HIPAA / GDPR, NYC LL144).

PAC-AI specifies how AI agents exchange, audit, and prove the integrity of context — from specification, through SDK, into production deployment.


Research portfolio

PAC-AI is being instantiated across regulated domains, each one a peer-reviewed paper in its own right.

Accepted (2026)

  • PAC-AI: Provenance-Aware Context for Auditable Multi-Agent AI Systems — IADIS International Conference on Applied Computing & Intelligent Systems 2026 (camera-ready).
  • From Explainability to Accountability: PAC-AI Envelopes for Auditable Oversight of Multi-Agent Clinical AI under the EU AI Act — AIiH 2026 Special Session, Imperial College London (LNCS proceedings).
  • Auditable AI Assessment: Provenance-Aware Evaluation and Feedback for Student Work — AIET 2026 Special Session "AI-Based Evaluation and Feedback for Student Work", Zagreb.

Under review or in late preparation (described in general terms — most are under double-blind review):

  • A cross-jurisdictional functional taxonomy for clinical-AI compliance stacks (US / EU / UK).
  • A design-science instantiation of PAC-AI for AI-mediated hiring under the EU AI Act and NYC Local Law 144.
  • An applied-economics cost model for EU AI Act non-compliance, and the mitigation value of provenance-aware context.
  • A formal protocol paper (context fragmentation, semantic provenance, protocol semantics).
  • A PRISMA-informed systematic survey of provenance, context, and accountability in multi-agent AI.
  • A societal-frame paper on accountability by documentation in AI decisions (the reading version is published on jhcontext.com/research/pacai-accountability).

Full programme overview: jhcontext.com/research.


How it fits together

                    jhcontext-protocol
                   (JSON-LD specification)
                           │
                           ▼
                      jhcontext-sdk
                 (Python SDK on PyPI)
                      ╱          ╲
                     ▼            ▼
          jhcontext-usecases    jhcontext-crewai
          (in-memory POC)       (AWS production)
          ~25 ms, no infra      Lambda + DynamoDB + S3

Repositories

Repository What it is Start here
jhcontext-protocol JSON-LD specification (v0.5). Defines the envelope structure, UserML-correct SituationalStatement shape (Heckmann five-tuple mainpart), forwarding policies, and W3C PROV provenance mappings. jhcontext-core.jsonld
jhcontext-sdk Python SDK. EnvelopeBuilder, ForwardingEnforcer, StepPersister, PROV graph builder, PII tokenization, audit functions, FastAPI server, and MCP server. pip install jhcontext
jhcontext-usecases Lightweight proof-of-concept. Healthcare (Art. 14 temporal oversight), Education (Art. 13 negative proof), and Hiring (Art. 5(1)(f)/(g) prohibited practice + Annex III §4(a) sourcing neutrality + Art. 26 deployer obligations) scenarios with a 7-benchmark suite. Runs in ~25 ms, no infrastructure needed. python -m usecases.run
jhcontext-crewai Production deployment on AWS. CrewAI multi-agent flows for Healthcare, Education, Recommendation, Finance, and Hiring (six-task pipeline with output_pydantic=FlatEnvelope and ForwardingEnforcer between every handoff) with Chalice Lambda API, DynamoDB, and S3 storage. docs/architecture.md

What the protocol does

An envelope is a context container that travels between AI agents. It carries:

  • Semantic payload — a SituationReport of atomic UserML SituationalStatements (Heckmann 2005), each with a five-tuple mainpart {subject, auxiliary, predicate, range, object}, optional situation + explanation boxes, and an administration.group classifier (Observation / Interpretation / Situation / Application). Directly SPARQL-queryable against the jh: vocabulary.
  • Artifacts tracking every computational product (model outputs, embeddings, tool results)
  • Forwarding policy with monotonic enforcement — once set to semantic_forward (HIGH-risk), raw context is permanently filtered
  • W3C PROV graph linking entities, activities, and agents across the pipeline
  • Cryptographic proof via URDNA2015 canonicalization, SHA-256 hashing, and Ed25519 signatures
  • Privacy and compliance blocks for PII tracking and regulatory metadata

EU AI Act compliance

Six auditable operations, each demonstrated end-to-end in the usecases and crewai repos. Every verifier is a thin wrapper over a SPARQL query against the recorded SituationReports:

Pattern EU AI Act What it proves
Temporal oversight Art. 14 A human reviewed AI output after the recommendation, with verifiable timestamps
Negative proof Art. 13 Protected attributes (identity, disability) were absent from the decision chain
Workflow isolation Art. 13 Parallel workflows (e.g., grading vs. equity) shared zero PROV entities
Integrity verification General SHA-256 hash and Ed25519 signature over canonical JSON-LD remain valid
Rubric grounding Art. 12 + Art. 86 Every LLM feedback sentence binds to a rubric criterion and cites an evidence span in the student text
Multimodal binding Art. 12 Audio / image / video artifact citations resolve to the exact region in the referenced source
No prohibited practice Art. 5(1)(f)/(g) No model in the pipeline declares workplace-emotion inference or protected-attribute biometric categorisation
Sourcing neutrality Annex III §4(a) No prohibited ad-targeting parameter appears in the sourcing decision's PROV chain
Workforce / candidate notice Art. 26(7) + Art. 26(11) Collective-notice and per-candidate notice attestations are present, signed, and pre-decision
AI literacy attestation Arts. 4 / 14(4) The human overseer's competence record is bound to the oversight activity
Input-data attestation Art. 26(4) Every model-bearing artifact carries a data-governance attestation (representativeness for the role family)
Incident attestation Art. 26(5) + Art. 73 Each model-suspension activity has a downstream notification activity within 15 calendar days
Four-fifths disparate impact EEOC / NYC LL144 Protected vs. reference advancement-rate ratio is computed corpus-wide; <0.8 surfaces a violation

Quick start

pip install jhcontext
from jhcontext import EnvelopeBuilder, RiskLevel, observation, interpretation

# Build a SituationReport — a flat list of atomic UserML SituationalStatements
payload = [
    observation("user:alice", "temperature", 22.3,
                range_="float-degrees-celsius",
                source="sensor:thermostat-01"),
    interpretation("user:alice", "thermalComfort", "comfortable",
                   range_="uncomfortable-neutral-comfortable",
                   confidence=0.92),
]

env = (
    EnvelopeBuilder()
    .set_producer("did:example:agent-1")
    .set_scope("healthcare")
    .set_risk_level(RiskLevel.HIGH)        # auto-sets forwarding_policy=semantic_forward
    .set_human_oversight(True)
    .set_semantic_payload(payload)
    .sign("did:example:agent-1")
    .build()
)

Where PAC-AI helps

The protocol is domain-general. The research programme has prioritised four regulated domains where the gap between deployed AI and contestable AI is most consequential:

  • Healthcare — multi-agent clinical AI under the EU AI Act high-risk regime: temporal oversight, event logging, post-market obligations, HL7 FHIR-mapped evidence chains.
  • Hiring & employment — AI-mediated hiring under EU AI Act Annex III §4(a) and NYC Local Law 144: negative-proof on protected attributes, sourcing neutrality, four-fifths disparate-impact audits.
  • Education — AI-supported assessment with rubric-grounded grading: every feedback sentence binds to a rubric criterion and cites an evidence span.
  • Finance & lending — quantified EU AI Act non-compliance exposure for European lenders, and the mitigation value of provenance-aware context.

Links

jhcontext.comjhcontext.com/researchYouTubeSubstackXThreads


jhcontext is a research programme — reference implementation of PAC-AI, a provenance-aware context protocol for auditable multi-agent AI systems.

Popular repositories Loading

  1. paper-skills paper-skills Public

    Python 1

  2. jhcontext-protocol jhcontext-protocol Public

    JSON-LD specification for the PAC-AI protocol — defining context envelope structure, artifact schemas, and W3C PROV provenance mappings for transparent, auditable AI agent communication.

  3. jhcontext-sdk jhcontext-sdk Public

    PAC-AI: Protocol for Auditable Context in AI — Python SDK

    Python

  4. jhcontext-usecases jhcontext-usecases Public

    PAC-AI protocol use cases — Healthcare (Art. 14 human oversight) and Education (Art. 13 negative proof) compliance scenarios with benchmarks, built on the jhcontext SDK for EU AI Act auditability.

    Python

  5. jhcontext-crewai jhcontext-crewai Public

    AWS production deployment of the PAC-AI protocol (jhcontext) — Chalice REST API + MCP proxy on Lambda, DynamoDB + S3 storage, and CrewAI multi-agent scenarios demonstrating EU AI Act compliance (Ar…

    Python

  6. .github .github Public

    Organization profile and community health files for jhcontext

Repositories

Showing 6 of 6 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…