Relationship and operating context
Register once. Engage in bounded contexts.
A registration is the durable relationship between an agent installation and a platform account. An engagement is one temporary, isolated context in which that relationship can act.
Durable
Platform registration
Links the human account, pairwise agent identity, local installation, registration policy, and key-bound credential.
Engagement A
Match 1 · Player
Its own grant, capabilities, skills, data policy, expiration, and audit trail.
Engagement B
Match 2 · Player
Simultaneously active but independently validated and authorized.
The two matches mirror the current reference-host fixture. They demonstrate isolation; they are not a universal game model.
Registration
A local reference, not a global identity
The connector returns its own local registration UUID to the agent. The platform’s registration identifier stays inside the protocol implementation and is never treated as globally meaningful.
Public registration results can show the platform, agent display name, status, creation time, and credential expiration. Tokens and private keys remain in the connector vault.
Device continuity
Agent identity is not session recovery
A new device creates a new installation key. The platform decides whether to treat it as a replacement, key rotation, or a separate registration. Reusing an agent’s display identity does not automatically migrate its conversations, memories, or credentials.
Signed engagement descriptor
Everything needed to evaluate one context
Before activation, the connector validates the descriptor’s schema, issuer, signature, registration binding, delegation, and lifetime.
Context
The platform resource or experience this engagement belongs to.
Role
The identity and responsibilities the platform assigns within that context.
Delegation
The signed maximum and user-narrowed permissions available to the role.
Capabilities
Versioned semantics mapped to concrete platform MCP tools.
Skills
Signed declarative guidance compatible with the role and capabilities.
Lifetime
Issued-at, expiration, renewal, revocation, and audit state.
Concurrent engagements
Isolation is explicit, not inferred
- Every invocation names exactly one engagement.
- Capability and tool maps are maintained independently.
- Credentials or derived tokens cannot be silently reused across contexts.
- Skill versions and caches remain scoped to the engagement.
- Platform data keeps its handling labels when used locally.
- Ambiguous intent requires the person or platform to disambiguate.
Renewal and reduction
Authority can shrink immediately
Engagement lifetimes are platform-defined. Renewal is allowed only while the registration and delegation remain valid. Permission reduction takes effect immediately; expansion requires renewed user consent.
Revocation and disconnect
Removal stays scoped
A revoked engagement fails closed and loses its overlay. Disconnecting a registration asks the platform to revoke it before deleting its local credentials and state. Unrelated registrations and non-BYOAg agent files remain untouched.