<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.aravind-oauth-operator-of-record" target="https://datatracker.ietf.org/doc/html/draft-aravind-oauth-operator-of-record-00">
   <front>
      <title>Operator-of-Record: an Origination Marker for Agent-Operated Presentations and Decisions</title>
      <author initials="A. A." surname="Aravind" fullname="Anivar A Aravind">
         <organization>Independent Researcher</organization>
      </author>
      <date month="July" day="19" year="2026" />
      <abstract>
	 <t>   This document requests registration of opr, an OPTIONAL, descriptive
   JWT claim that marks the operator of record, that is, whether a human
   or an agent operated a credential presentation or drove a decision.
   Its purpose is record integrity.  Under agent operation a wallet key-
   binding proof is cryptographically indistinguishable from a human-
   operated one, and no presentation protocol marks the difference; opr
   records the distinction.  A Policy Decision Point MUST ignore opr for
   the allow/deny decision; interpretation and any resulting
   authorization behavior are deployment-local and out of scope.  This
   document defines representation only.  It defines no remedy,
   adjudication, obligation, or authorization mandate.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-aravind-oauth-operator-of-record-00" />
   
</reference>
