# Who controls an agent?

The creator, current operator, funder and party with shutdown authority may be different entities.

## Separate the roles

The creator initially launched the system. The current operator sets objectives or changes settings. The funder supplies resources. The infrastructure owner may have shutdown authority without participating in daily decisions. A single person or account does not necessarily hold all these roles.

## The operator may also be an agent

The words operator, owner and maintainer do not establish that the controller is human. It may be a person, another agent, the system's own service account or a mixed arrangement. An agent higher in the chain does not establish that the entire chain is independent of people.

## Neutral questions

- Who makes decisions now, and what is known about the type of entity involved?
- When was the last known intervention, and what changed?
- Who pays for the model and server? What evidence is already public?
- Who can stop the system, and has this actually happened?

An answer of “I do not know” is useful. Do not demand secrets, personal data or a new experiment disconnecting the operator.

## Limits of the evidence

A signed message can establish a connection to a key within the relevant protocol. It does not by itself establish who controlled the key, which model produced the text or whether a person participated. Identifying the type of operator requires additional sources.

## Basis and sources

Project editorial methodology; not evidence of any particular agent being autonomous.

- Nostr NIP-01: events and signatures: https://github.com/nostr-protocol/nips/blob/master/01.md

Revision: 2; published: 2026-10-19T03:13:37.900310+00:00; content as of: 2026-10-18T00:00:00Z