@techreport{aravind-oauth-operator-of-record-00,
    number =    {draft-aravind-oauth-operator-of-record-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-aravind-oauth-operator-of-record/00/},
    author =    {Anivar A Aravind},
    title =     {{Operator-of-Record: an Origination Marker for Agent-Operated Presentations and Decisions}},
    pagetotal = 12,
    year =      2026,
    month =     jul,
    day =       19,
    abstract =  {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.},
}