Skip to content

epic: Phase 2 — Differentiate, go beyond #260

Open

Description

@amirkhan-ak-sf

Goal

The SDK does things no generic gateway SDK does, because it understands this
gateway's governance model — and it integrates with, never duplicates, what the
platform has already shipped.

Scope

Refusal handlers, classification registry, HITL normalisation, thin identity
helpers, in-repo scanner + GitHub Action, kill-switch awareness, MCP tool
discovery, a second adapter by demand, and A2A serve/expose/dev.

Exit criteria

  • At least one framework's official docs link to the SDK.
  • Evidence of production use — a customer or internal team running it with
    OTel attached.
  • Refusal handlers, registry, HITL and scanner all pass conformance against
    the simulator.

Standing constraint

Several features here are blocked on verification, and several deliberately
complement shipped platform capabilities rather than competing with them. Both
constraints are load-bearing, not caveats.

Activity

  1. added
    epicTracking issue spanning several child issues
    priority/p1Must-have: blocks a real adapter or CI gate
    size/xlMulti-week, its own workstream
    on Sep 4, 2026
  2. tbolis-at-mulesoft commented on Oct 12, 2026

    @tbolis-at-mulesoft
    Collaborator

    Related: #1102 — new GA-gated Phase 2 epic: publish agents and MCP servers through the Anypoint self-managed scanner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicTracking issue spanning several child issuespriority/p1Must-have: blocks a real adapter or CI gatesize/xlMulti-week, its own workstream

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions