Hi Jeff, Thank you very much for offering to take a look.
I really appreciate it. I’ll prepare a concise technical review packet focused on the areas most relevant to the OAuth / identity boundary, rather than sending the full project. It will cover: - the authorization and one-use execution model; - the separation between the AI agent, policy/gateway layer, and external execution credential; - revocation vs. execution-start ordering; - RESULT_UNKNOWN and recovery semantics; - signed execution evidence and the independently supplied Trust Config; - the specific questions where I would most value critical feedback or references to existing OAuth/AuthZEN/WIMSE work. My goal is to identify anything we should reuse, align with, or change before considering a low-risk pilot—not to seek endorsement. Thank you again for your time. Best regards, Toshio Nakanishi Valora AI / Valora Proof On Mon, 28 Sep 2026 14:05:27 +0000, “Lombardo, Jeff” [email protected] wrote: Hi, I agree to take a look as a first step. Jeff Jean-François “Jeff” Lombardo | Amazon Web Services Principal Standards Specialist, Identity Services Montréal, Canada From: Valora AI [email protected] Sent: September 25, 2026 7:58 AM To: [email protected] Subject: [EXT] [OAUTH-WG] Review request: AI-agent authorization, one-use execution, and portable evidence prototype CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le contenu ne présente aucun risque. Hello OAuth Working Group, I am developing a small research prototype called Valora Proof and would appreciate technical feedback from participants working on OAuth / AI-agent authorization. I am not proposing a new OAuth standard, and I am specifically trying to avoid re-inventing existing authorization mechanisms. The v0.1 prototype explores a narrower end-to-end execution/evidence problem: - a human issues a narrowly scoped, one-use authorization; - the AI agent does not hold the external execution credential; - a separate policy/gateway layer enforces the authorization; - revocation vs execution-start ordering is explicit; - retries, response loss, restart, and RESULT_UNKNOWN are modeled; - external execution evidence is signed; - evidence is exported in a portable bundle; - a separate verifier evaluates claims using an independently supplied Trust Config. We already treat fine-grained authorization, PDP/PEP separation, OAuth-style delegated authority, and agent identity as areas where existing standards should be reused rather than claimed as Valora-specific novelty. I would value a focused review on: - which authorization semantics should be replaced by or aligned with OAuth/AuthZEN/WIMSE work; - whether the one-use authorization / execution-start boundary is clear; - whether our Trust Config assumptions are too proprietary or weak; - whether the evidence/recovery layer addresses a real gap, or duplicates existing work; - the smallest blocker you would require us to fix before a low-risk pilot. The prototype currently uses a mock merchant only: no real money, no production credentials, no blockchain requirement. The repository is private, so I can send a concise review packet and selected specification/source material directly to any volunteer reviewer. Critical feedback is preferred over endorsement. Thank you, Toshio Nakanishi Valora AI / Valora Proof
_______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
