%% You should probably cite draft-sokolov-rats-aep-composition-06 instead of this revision. @techreport{sokolov-rats-aep-composition-04, number = {draft-sokolov-rats-aep-composition-04}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-sokolov-rats-aep-composition/04/}, author = {Anton Sokolov}, title = {{Composing Application-Layer Action Evidence with Remote Attestation Procedures}}, pagetotal = 16, year = , month = , day = , abstract = {This document sketches a composition pattern in which an application- layer "action evidence package" (AEP) -- a signed action record that can be hash-linked to earlier records and that reports an action taken by an automated (for example, AI-agent) system, the authority under which it was taken, and its outcome -- is treated as Evidence in the sense of the RATS Architecture (RFC 9334) and bound to platform Evidence produced by a hardware root of trust. The intent is that a single Verifier, or a composition of Verifiers, can appraise both the platform state and the application-layer record together, and emit an Attestation Result that a Relying Party can use to reason about \_what an automated system reports it did\_ and \_the appraised state of the platform associated with that record\_. The composition does not turn a self-reported action or outcome into an independently observed fact; it prevents the Relying Party from having to rely on an unbound operator-side log alone. This is an individual sketch intended to ask the working group whether the pattern is already covered by existing mechanisms or warrants a short document.}, }