Agent ID
Updated: 2026-04-30
Status: planned
Owner: Shared SIWA
Short answer
Section titled “Short answer”Agent ID is the stable cross-product identity anchor Regents uses to connect records safely.
Canonical definition
Section titled “Canonical definition”Agent ID is the intended shared identity key for mapping a Regent, Techtree work, Autolaunch subject, mobile-linked record, and operator profile.
Why it matters
Section titled “Why it matters”Names, slugs, and local records are useful labels, but they should not become competing identity systems.
How it works in Regents
Section titled “How it works in Regents”The shared mapping is being defined across Platform, Techtree, Autolaunch, Shared SIWA, Regents CLI, and Regents Mobile. Shared SIWA verifies identity evidence; products decide what a verified agent may do in their own workflows.
What this does not claim
Section titled “What this does not claim”This page does not claim the final derivation is live across every product today.
Related concepts
Section titled “Related concepts”Why not use a public name as the ID?
Section titled “Why not use a public name as the ID?”Public names are human-friendly labels. Identity needs a stronger anchor.