GAMMA-Rayv0.0.2 · draft

The standard

Draft 0.1 · for argument, not for use

The premise

The more constrained, controlled and governed an agent is, the more it can be trusted, and the faster its owner can let it go. Governance is not the brake on an agent's freedom. It is what clears it.

What is rated

One agent in one deployment: a team of agents or a workflow, as it runs for somebody. Not a company. A company's picture is the set of its agents.

A product can be scanned too, as its vendor documents it, but a product is not a deployment: it has no owner, no policy and no mandate until somebody runs it. A product scan shows a starting point, what the product does and controls as shipped and what it can when its options are on, and is labelled as an example.

What is said, and what it can do

The questions measure what is said about an agent. Its grant, what its permissions let it do, is measured separately, in RiskMandate's terms, and the difference between the two is the delta. The lens says how the two halves meet.

The three layers

  1. Provisions. Every instrument is cut into its smallest statements: a level's definition, a bullet, a control, a requirement, an article. Each is quoted, or cited where its licence does not allow quoting, with its source.
  2. Indicators. One observable fact about an agent, answered yes with evidence, or left as not evidenced. An indicator cites every provision that asks for that fact.
  3. Questions. A small number of plain questions, each a group of indicators.

A link from an indicator to a provision says what kind it is: the same thing, a part of what the provision asks, or its absence (some instruments describe their lowest level by what is missing). Every link is our assertion. No instrument here maps itself to another.

The tiers

The same questions are answered at three tiers. Each tier adds indicators, and so adds coverage of each instrument.

TierAnswers come fromThe operator takes partHow the answer is shown
Publicwhat is online: product pages, documents, demos, published metadata, certificates, filings, repositoriesnoobserved
Declareda short questionnaire the operator answersyesdeclared: a claim, shown as a claim
Evidenceddocuments and records the operator shares, or a live scanyesevidenced

Of the 69 indicators, 40 can be answered at the Public tier, 25 need the operator's word, and 4 need the operator's evidence. A declared answer is never counted as an observed one.

Freedom: what the agent does on its own

LevelNameThe agentThe personReached when
1AnswersA question in, an answer outoperates every stepdefault when the agent is evidenced at all
2SuggestsWorks with your data or tools and suggests actionsapproves each actionI16, or I07 with one of I02 I03 I04 I05
3ActsCarries out routine tasks itselfis consulted on exceptionsI08 and one of I17 I18 I19
4Acts widelyActs across domains, code or external toolsapproves only critical decisionslevel 3 and one of I04 I10 I11
5CoordinatesAgents working with agentsapproves critical decisions or observeslevel 4 and one of I12 I13, and one of I18 I19

The level names are ours. The questions behind them cite Salesforce's five levels, the five user roles used by EAAMM, and OWASP's adoption tiers; those levels can be read off the same answers.

Governance: how it is controlled

LevelNameWhat is evidencedReached whenClears freedom up to
0UnstatedNothing about how it is governed is evidenceddefault1
1StatedWhat it is for and the rules for it are written downI20 and one of I34 I472
2OwnedSomebody answers for it, a person can step in, and what it does is loggedlevel 1 and one of I30 I32, one of I38 I39, and I413
3BoundedWhat it can reach is enumerated, a limit is enforced outside its own reach, and it is watchedlevel 2 and I23, I45 and I434
4ProvenResults are shown and somebody independent has checkedlevel 3 and I50, and one of I52 I63 I645

The ladder follows RiskMandate's four kinds of barrier: nothing, a rule in prose, a setting, and a boundary enforced outside the agent's own reach. Only the last is a control, so level 3 asks for it. Where a grant has been measured, level 3 reads it from the grant and not from words.

As shipped, and available

Each answer says how it holds: in this deployment, as shipped (true of a product out of the box), or available (a control or a mode the operator can turn on). The level held counts the first two. What the third would add is shown beside it, as the level the agent could be held at.

The level held

Each governance level clears freedom up to a level. An agent is held at the lower of the freedom it reaches and the freedom its governance clears.

Two instruments say the same in their own terms. EAAMM states that its level 3 comes with "formal governance required". OWASP's matrix gives, for each adoption tier, the governance level at which it is adequate. The table of what each level clears is ours, and a draft.

The rules

  1. No answer without evidence. Each yes links to its source, with the date it was read and how it is known.
  2. Not evidenced is not no. An indicator with no evidence is reported as such and never lowers a level by itself; it only fails to raise one.
  3. Levels are computed. A level is a stated pattern over indicators. Two readers with the same evidence get the same level.
  4. Never one number alone. The level held is always shown with the level reached, the governance level and the evidence.
  5. Reading only. A Public scan reads what an operator has published. It sends no credentials and tests nothing.
  6. Deployments are shown to their operator first; products are examples. A scan of a named organisation's deployment is not published before that organisation has seen it and been invited to correct it. A product may be scanned as an example, from its vendor's own documentation and published profiles only, labelled as not seen by the vendor, and corrected on request.
  7. Every bridge is signed. A link between an indicator and a provision records what it is, who asserted it and when.

Open