Skip to content
B BYOAg
Menu
Browse BYOAg
Conceptual

From protocol to experience

One working connection flow. Several future experience shapes.

The reference-host example below reflects implemented plugin behavior. Domain scenarios show how the same boundaries could support useful experiences once the remote tool and signed-skill layers exist.

Concrete reference flow

Connect, inspect two engagements, disconnect

Implemented
  1. 01

    Discover loopback host

    The connector validates signed discovery and same-origin JWKS using explicit development loopback mode.

  2. 02

    Begin pairing

    The host issues a short-lived code; the connector returns only its own local connection reference.

  3. 03

    Complete with DPoP

    New pairwise and installation keys establish a key-bound registration without returning the credential.

  4. 04

    List registration

    Public local metadata identifies the platform and state while secrets remain inside the vault.

  5. 05

    Validate two engagements

    Two signed in-memory match contexts are retrieved and checked independently.

  6. 06

    Disconnect cleanly

    The registration is revoked and its local BYOAg state is removed without touching an unrelated sentinel file.

Conceptual domain scenarios

Apply the same boundary model in different environments

Capability identifiers below are illustrative names, not entries in a finalized global registry or implemented remote MCP surface.

Guided learning activity

Conceptual

A learner brings an agent into a course activity with readings, a rubric, and a bounded submission workflow.

Platform role
Learner assistant
User-narrowed delegation
Read assigned materials; prepare and submit work for this activity only.
Illustrative capabilities
learning.resource.read learning.submission.create learning.feedback.read
Confirmation
Required before final submission or sharing learner-authored work.
Structured result
Validation, rubric-aligned feedback, evidence used, and permitted retry guidance.
Safety boundary
The agent cannot inspect other learners, alter the rubric, or carry restricted course data into another engagement.

Interactive game session

Conceptual

A player’s agent enters one match, explains visible choices, and submits only the player’s confirmed move.

Platform role
Player
User-narrowed delegation
Read the current match state and submit valid moves for one seat.
Illustrative capabilities
game.state.read game.move.submit game.result.read
Confirmation
The experience may require confirmation for irreversible or high-impact moves.
Structured result
Accepted move, updated public state, audit reference, and the next legal actions.
Safety boundary
A second simultaneous match has a different engagement and cannot reuse this match’s authority or hidden state.

Care-navigation preparation

Conceptual

An agent helps a person prepare questions and navigate available scheduling or coverage services.

Platform role
Patient-authorized navigator
User-narrowed delegation
Read selected service information and prepare requests within the person’s chosen scope.
Illustrative capabilities
care.service.read care.question.prepare care.scheduling.request
Confirmation
Required before transmitting health-related information or requesting an appointment change.
Structured result
A prepared question list, scheduling status, or escalation to a qualified human professional.
Safety boundary
The example does not diagnose, prescribe, or treat. Sensitive information retains its handling restrictions.

Commerce comparison and checkout

Conceptual

A shopper’s agent compares current eligible options and prepares a transaction without silently completing it.

Platform role
Shopping assistant
User-narrowed delegation
Read eligible catalog and policy data; save a shortlist; prepare checkout.
Illustrative capabilities
commerce.catalog.read commerce.shortlist.modify commerce.checkout.prepare
Confirmation
Purchase, subscription, or material account change requires protected confirmation.
Structured result
A comparison with current constraints, prepared checkout details, or a confirmed transaction receipt.
Safety boundary
Tool discovery is not purchase approval, and an updated skill cannot add payment authority without new consent.

Scenario anatomy

What a complete example must show

  • The human account, pairwise agent, and installation
  • The registration and exact named engagement
  • The platform role and user-narrowed delegation
  • Semantic capabilities and concrete tool mappings
  • Confirmation, idempotency, and audit behavior
  • Data-handling limits, failure paths, and teardown