Skip to content
B BYOAg
Menu

Relationship model

Personal agents.
Trusted service relationships.

BYOAg lets a person bring their own agent into a service relationship without requiring every provider to deploy a customer-facing agent or adopt the same internal harness.

This can give providers a more focused starting point: expose the capabilities, policies, and boundaries of their service, while the person retains continuity with the agent they chose. It does not remove the provider's responsibility for security, authorization, or reliable operation.

Standardize the boundary, not the mind.

01 · Interaction journey

From discovery to a useful, bounded relationship.

A provider can be agent-enabled without an always-on integration or disclosure of its private implementation.

  1. Discover

    Person

    Notices a signal that a provider works with their agent.

    Personal agent

    Recognizes a verified entry point without loading a permanent toolset.

    Provider

    Exposes minimal public metadata: identity, service category, and how to begin.

  2. Express intent

    Person

    Asks for an outcome.

    Personal agent

    Uses the active project, preferences, and constraints to find relevant services.

    Provider

    Does not receive the person’s full profile or private agent transcript.

  3. Connect

    Person

    Agrees only to what is required for the current relationship.

    Personal agent

    Checks whether it already has compatible capabilities.

    Provider

    Declares requirements, available actions, limits, and event options.

  4. Act

    Person

    Stays in control of consequential choices and approvals.

    Personal agent

    Composes authorized actions and applies user preferences.

    Provider

    Can use deterministic APIs, workflows, or internal agents. Its harness remains private.

  5. Close

    Person

    Gets a clear receipt, status, and revocation option.

    Personal agent

    Retains only approved, useful preferences and reusable capabilities.

    Provider

    Lets temporary authority expire.

02 · Account-linked agent delegation

A provider trusts an authorization, not an opaque intelligence.

The human account remains the provider’s source of accountability. The agent proves that it is the enrolled instance acting within a limited, revocable delegation.

Account-linked agent delegation sequence A sequence diagram showing sign-in, account approval, agent key enrollment, short-lived authority, and future proof of possession between a person, provider account, and personal agent. PersonProvider accountPersonal agent 01 · Normal provider sign-in02 · Show relationship and limits03 · Approve enrollment04 · One-time docking challenge05 · Public key and signature07 · Scoped delegated authority08 · Proof of key possession09 · Result, status, or consent event 06 · Bind account, agent key,scopes, and policy
Enrollment is account-linked: the provider authenticates the person, verifies the agent’s enrolled key, and issues bounded authority.

Human proof

The provider authenticates its own account holder using the assurance appropriate to its domain.

Agent proof

The agent holds a private key; the provider stores the public key and verifies a signature or proof of possession.

Delegation proof

Each authorization is scoped, time-bounded, auditable, and revocable by the person or the provider.

03 · Personal agent capability model

What an agent needs beyond tools.

A personal agent needs to discover relationships, establish trust, carry bounded authority, and manage the human experience across them.

Personal agent runtime capability map Nine capabilities radiate from a personal agent runtime, each paired with its expected relationship outcome. Personal agent runtimetrust, authority, and human context Discover service availabilityIdentity and key managementEnrollment and registryCapability matchingPolicy, limits, and consentSafe execution environmentEvent and notification handlingAudit, receipts, and revocationProject-scoped memory Minimal verified provider profileProof of possessionAccount-linked delegationsReuse or acquire compatible capabilityHuman approval for consequential actsNo unrestricted network or secret exposureAuthenticated status updatesExplain and disable any relationshipKeep context relevant to the human
Each relationship capability has a concrete outcome: discover only what is needed, prove enrollment, carry bounded authority, and keep context relevant to the person.