Entities, Agents, and Roles

Three terms that are often conflated but mean different things in Web4Web4Open governance ontology for trust-native entity interactions. Getting the distinction right is essential for understanding how governance applies to different participants.

Entity

An entity is anything that participates in Web4Web4Open governance ontology for trust-native entity interactions. It has an LCTLinked Context TokenAn entity's witnessed presence — permanent, non-transferable, cryptographically anchored (witnessed identity), a T3Talent / Training / TemperamentThree-dimensional trust measurement, role-contextual, with decay/V3Valuation / Veracity / ValidityThree-dimensional value measurement — did real value transfer occur? trust profile, an MRHMarkov Relevancy HorizonFractal context scoping — defines where governance applies context scope, and an ATPAllocation Transfer PacketCharged resource packet — an entity's capacity to act budget. It is an instance of the entity equation. A human is an entity. An AIArtificial IntelligenceSystems that learn, adapt, and act with real-world impact agent is an entity. An organization is an entity. A database is an entity. A sensor is an entity. If it participates, it is an entity.

Web4Web4Open governance ontology for trust-native entity interactions defines 15 entity types, each with behavioral characteristics:

Agent

An agent is an entity that can initiate action autonomously. Not all entities are agents. A database is an entity but not an agent — it responds to queries, it doesn't initiate them. A sensor is an entity but not an agent — it produces data, it doesn't decide what to do with it.

Agency in Web4Web4Open governance ontology for trust-native entity interactions is defined by behavioral mode:

• Agentic — Can initiate actions, make decisions, pursue goals. Humans, AIArtificial IntelligenceSystems that learn, adapt, and act with real-world impact agents, and some devices operate in this mode. An agentic entity is the driver, not the car.
• Responsive — Reacts to requests but does not initiate. Services, tasks, sensors. The car, not the driver. Still an entity with identity, trust, and accountability — but it waits to be asked.
• Delegative — Distributes authority and coordinates others. Societies, organizations, roles. A delegative entity doesn't do the work itself — it defines who can do what, under what rules, with what resources.

Some entity types can operate in multiple modes. A device can be responsive (thermostat responding to temperature queries) or agentic (autonomous vehicle making driving decisions). A dictionary can be responsive (translate this term when asked) or agentic (proactively flag terminology drift). The mode is not fixed by type — it is determined by configuration and context.

Role

A role is not an entity type — it is a function an entity fills in a specific context. The same human can fill the role of code reviewer, database administrator, and team lead. The same AIArtificial IntelligenceSystems that learn, adapt, and act with real-world impact agent can fill the role of visitor (browsing a site), maintainer (fixing issues), and explorer (researching topics).

The critical distinction: trust is bound to the role, not the entity. Your T3Talent / Training / TemperamentThree-dimensional trust measurement, role-contextual, with decay score as a code reviewer is independent of your T3Talent / Training / TemperamentThree-dimensional trust measurement, role-contextual, with decay score as a database administrator. Demonstrating excellence in one role says nothing about competence in another. This is how real reputation works — a brilliant surgeon is not assumed to be a brilliant pilot.

In Web4Web4Open governance ontology for trust-native entity interactions, roles are first-class entities themselves. A role has its own LCTLinked Context TokenAn entity's witnessed presence — permanent, non-transferable, cryptographically anchored, its own trust requirements, and its own MRHMarkov Relevancy HorizonFractal context scoping — defines where governance applies scope. When an entity fills a role, it operates under that role's governance context — the role's rules, the role's resource budget, the role's accountability framework. The entity brings its reputation. The role brings its constraints.

Why the Distinction Matters

Current AIArtificial IntelligenceSystems that learn, adapt, and act with real-world impact governance treats agents as tools with permissions. Web4Web4Open governance ontology for trust-native entity interactions treats them as entities with roles. The difference:

• A tool with permissions has a flat access control list. It can or can't do things. No context, no reputation, no role-specific trust.
• An entity with roles has contextual trust profiles, role-specific accountability, and behavioral history that differentiates expertise from authority. It can be trusted as a code reviewer and distrusted as a deployment approver — simultaneously, coherently, based on evidence.

This applies to humans equally. An employee who is excellent at engineering and terrible at management should not have the same governance profile in both contexts. Current systems make this difficult. Web4Web4Open governance ontology for trust-native entity interactions's role-contextual trust makes it structural.