Skip to content

strategy(factory): map Salesforce AI Control Plane interoperability #1847

Description

@groupthinking

Verified change

Salesforce announced the Trusted Enterprise AI Harness on September 10, 2026:

  • six composable capabilities: context, agency, action, governance, security, and models;
  • an AI Control Plane for agent/capability discovery and registration, identity and policy, lifecycle, evaluation, behavior/outcome observability, and cost control across Salesforce and third-party AI;
  • headless access through MCP, APIs, Skills, and Plugins;
  • many foundation technologies available today, with the unified experience beginning rollout in early FY28;
  • final packaging, pricing, and detailed availability still pending.

Primary source: https://www.salesforce.com/news/stories/enterprise-ai-harness/

Strategic interpretation

This is material to Agent Factory because Salesforce is productizing much of the generic enterprise control-plane surface. Building an undifferentiated registry, identity, policy, evaluator, or cost dashboard would increasingly compete with a platform bundle.

It may also become a distribution channel. EventRelay can remain the provider-neutral execution/evidence spine while Salesforce supplies a customer-facing enterprise surface. Defensible boundaries should remain:

  • durable, append-only execution receipts and replay;
  • provenance-bound standing authorization;
  • deterministic claimed-versus-observed outcome verification;
  • cross-provider and cross-system execution;
  • UVAI/Video Pack evidence normalization;
  • policy enforcement independent of any model- or vendor-writable environment.

These are interpretations, not Salesforce claims.

Bounded action

Do not implement against announcement prose. Create a compatibility and partner-readiness map when official interfaces are published.

Acceptance criteria:

  1. Capture official API/schema documentation for Control Plane registration, identity/policy, lifecycle, evaluation, observability, cost, MCP, Skills, and Plugins.
  2. Map each interface to Agent Factory/EventRelay as BUILD, BUY, ADAPT, or DIFFERENTIATE.
  3. Define a read-only proof of concept: register one EventRelay agent/capability and ingest one immutable execution receipt without granting Salesforce merge/deploy authority.
  4. Specify identity, tenant isolation, approval provenance, receipt export, revocation, rate/cost ceilings, and failure semantics.
  5. Draft a partner/sales brief positioning EventRelay as the evidence and cross-provider execution layer for Salesforce-controlled agents.
  6. Require published availability and pricing before any paid test or implementation commitment.

Decision and boundary

WATCH + PARTNER

No outreach, paid use, deployment, production mutation, or public positioning claim is authorized by this issue.

Activity

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

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions