This page explains this system, not the category. For what agent identity is, see flashyos.com/concepts/agent-identity and gda.group.
One type, three kinds: human, organization, agent. The whole idea is that they are the same type — an agent is addressed exactly as a person is.
The edge. Carries scopes, constraints, expiry, and a pointer to its parent. Nothing in the system holds authority except a grant.
The organization’s rules, evaluated server-side. An agent never supplies the judgement that gates it.
The signed, portable claim. The only object that crosses an organizational boundary, and the only one a counterparty needs.
Each edge is annotated by what it carries. A counterparty walks this without holding any Flashy secret.
Attenuation only — a grant can never exceed its parent.
Authority always expires — there is no permanent grant.
Revocation walks down — revoking a link revokes everything beneath it.
Within one organization this is enforced today at resolution time. Propagation to a counterparty who has cached an assertion is not yet built; today they must re-resolve. Dated gold, on the sentence.
The policy engine described above is not built. Today an agent’s declared impact is taken at face value and a LOW impact auto-approves. Until Policy ships, treat every scope on this page as an assertion about intent, not an enforced boundary — except expiry and attenuation, which are checked at resolution.