"an agent session for a particular namespace, different concept from the ROOT
host agent"
"The shared namespace agent, opted into"
"The Namespace agent is a common Agent of the Namespace it’s opted into. That
means the one who sets it up knows it’s shared amongst anyone who has REACH on
it."
It is an agent the node hosts, reached over A2A by its tenant, and the
tenant is its namespace. It stands in that namespace and nothing crosses
(ADR-026).
Who may see its Tasks is REACH on its namespace: A2A's "Project or workspace
membership (project-based authorization)" (§13.1).
A namespace opts into a model, and its agent is that model there: a
namespace's Sonnet and ROOT's Sonnet are two agents.
"The one who set’s it up does, they provide their own Subscription or API key"
Every model call it makes is on that credential, whoever with REACH spoke to
it.
"Namespaces shouldn’t be catalogued"
Its card is not at /.well-known/agent-card.json and is in no list. It is
given to who has REACH on its namespace, A2A's "Direct Configuration" (§8.2).
To who has no REACH, a namespace with an agent answers as one that does not
exist (§3.3.2).
Not done
The namespace agent: its own DID derived from the node's key for that
namespace and model, its own home, session and token, signed in through
claude login (ADR-051), a sandbox around the turn, and one test of the whole
claim: it fails to reach the node's environment, its config, another
namespace, the box's AWS role and its own credential file, and its model
call succeeds on its own sign-in. Its story is docs/stories.