Ecosystem · graph position

Flashy ID is the layer underneath.

Flashy ID answers who may act. FlashyOS answers what is happening. Flashy Mind answers what is known. Each is the only writer of its own kind of truth, and each reads the others through an API.

Memory layer

Flashy Mind — what is known

In design

Coordination layer

FlashyOS — what is happening

Live

Identity layer

Flashy ID — who may act

Building · verifier live

One write rule — FlashyOS never writes an identity, Flashy ID never writes an event, Flashy Mind never writes either. Reads cross freely; writes never do.

Proof of scale, honestly framed

Flashy ID is not a protocol hoping for adoption — it is the identity layer of an operating estate. Here is what that means in numbers that exist, and what it does not mean.

Real, dated

✓ Per-person identity across properties — User, Session, Membership, in production✓ Organizations first-class, role-gated resolution✓ RS256 signer, tested, in service✓ Public JWKS, cached, unauthenticated

Not yet, and dated

★ Agent as an addressable entity — Q4 2026★ Delegation, mandates, spend limits — Q4 2026★ Policy engine, evaluated server-side — Q1 2027★ Cross-org revocation propagation — Q1 2027

Neither column is the headline. The difference between them is.

The protocol lens

Category vocabulary is defined at its canonical home and linked, never duplicated. Flashy ID holds primitives 02 and 03 in the PROTOCOL column alone — how authority is proven across an organizational boundary.

LensIdentity (02)Permissions (03)

Definitiongda.group/answers/what-is-agent-identitygda.group/answers/what-authority-should-an-ai-agent-hold

Softwareflashyos.com/concepts/agent-identityflashyos.com/concepts/agent-permissions

Networkflashygroup.com/learn/one-identity-nine-surfacesflashygroup.com/learn/ai-agent-security-and-permissions

Practiceflashy.academy — curriculum—

Protocolflashyid.com/spec — how it is provenflashyid.com/spec — how it is bounded