What an agent may do, and what it did.

Identity

Who is acting, and on whose behalf

Every agent has a passport: its name, its role, the team it belongs to and the person it acts for. The Writer in the Proposal team acts for Marram Advisory under Priya Nair's ownership. Every action is attributed to the agent, and every grant of authority is attributed to the person who made it.

Access

Which tools and documents are available

Access is granted per agent and per team, to named collections and named connector capabilities. The Reviewer can read the Oakhurst tender pack and comment on team documents. It cannot send email, share outside the team or change its own access. An access profile is proposed in plain language and reviewed by a person before the agent is activated.

Authority

What may run, and within which scope

Having access to a tool is not the same as being allowed to use it for a particular action. Authority is scoped: by action, by destination, by amount and by time. Agreeing a mission starts it within the team's existing authority. Anything outside that authority waits for approval or is refused.

Approval

Four classes, set by the owner

Every action an agent proposes falls into one of four classes.

• AutomaticInside the team's standing authority, such as reading its own collections. Runs and is recorded.
• DelegableEligible for the Steward to decide within limits the owner set, such as a read request inside the team's collections.
• Human onlyAlways waits for a named person, such as sending the proposal to Oakhurst. The Steward cannot take these.
• ProhibitedRefused regardless of who asks, such as an agent changing its own access.

The Steward works only inside the envelope an owner has granted it. It cannot expand that envelope, cannot take human-only decisions and cannot approve prohibited actions. A record of an owner granting the Steward an envelope is a record of that grant. It is not a fresh human approval of each later delegated action, and Avendrio does not present it as one.

Evidence

Decision record and execution outcome

Each agent action produces a record with the agent, the proposed action, the source of its authority, the decision, the time and the execution outcome. On this site we call that record a receipt. It is a readable entry in the mission's record, kept in the Provenance Vault, and it shows what was decided and what then happened.

Three things stay apart. Allowed records a decision. Executed records an event. Correct is a judgement a person makes about the work, and it is recorded separately. Allowed does not mean executed, and executed does not mean correct.

Revocation

How an owner stops or changes authority

An owner can pause an agent, remove a connector capability, narrow a Steward's limits or stop a mission. Changes take effect for the next proposed action, are attributed to the person who made them and appear in the record alongside the actions they affected.