HJS: A Judgment Event Protocol
draft-wang-hjs-judgment-event-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | yuqiang wang | ||
| Last updated | 2026-03-02 | ||
| Replaced by | draft-wang-jep-judgment-event-protocol | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-wang-jep-judgment-event-protocol | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines HJS, a specialized protocol for judgment attribution — determining who is responsible for AI decisions, when, and under what authority — and enables portable, verifiable judgment transfer across heterogeneous AI systems. HJS addresses one specific problem that complementary systems do not: binding decisions to accountable actors, tracking how responsibility transfers over time, and providing cryptographic credentials that allow AI agents to prove decision authority to external systems without requiring prior trust relationships. It works alongside provenance frameworks (VAP), security protocols (SEAT), monitoring platforms (Arize, WhyLabs), and governance systems (Fiddler), providing the attribution layer these systems complement. HJS contributes standardized judgment events, portable cryptographic Receipts that serve as verifiable credentials for cross-system delegation, and flexible verification modes for diverse deployment scenarios.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)