The envelope is the single structured record an agent submits with every proposed action. It contains three classes of information:

Class

Contents

Action

Action type, scope, parameters

Action trace

The steps the agent actually executed: tool calls, data retrieved, checks performed

Context metadata

Agent identity, applicable mandate, account or system state, operative policy constraints

The envelope is agent-declared, so it can be fabricated in an internally consistent way by a sophisticated injection. The paper therefore treats it as a document to be authenticated against its origin, not simply as a report to be trusted.

Topics

Related terms

SAFR whitepaperp. 8

Action Trace

The steps an agent actually took to reach a proposal: tool calls, data retrieved, checks performed.

SAFR whitepaperp. 8

Context Metadata

Agent identity, applicable mandate, account or system state, and policy constraints attached to an envelope.

SAFR whitepaperp. 9

Agent Identity

The component that binds a proposed action to a verified, registered agent before any other evaluation.

Posts using this term

CommentaryGeneral

Introducing OpenSAFR

An open schema, conformance suite, and reference implementation for SAFR. What it is, why the schema comes first, and what it isn't.