B14 · platform · Platform depth & replacement

Platform-Native Agent

Status

planned

Weeks

13–15

Permission gate

none

Depends on

B10 · B11 · B12

Page depth

outline

This is an outline, not a result.
Nothing here has been built. It states what the block is for, what it has to produce and what would make it a failure, so that the claim can be checked against the result later. Written 2026-09-01, and it will change.

Why this block exists

Scheduled here because it comes this is the single most specific posting match in the plan. Salesforce is hiring a Senior PM for LLM Fleet Management who "will write code, build automation pipelines, and instrument systems." Platform depth inside a permission system you don't control is a differentiator, not a detour.

What it has to produce

Build an agent that lives inside an enterprise platform's data model and permission system rather than calling its API from outside. Convert your Salesforce background from a footnote into an asset.

01What it has to teach me

topicplatform object models and relationships

topicpermission systems as constraints

topicApex

topicHosted MCP Servers

topicnative action primitives

02Evidence this page will carry

emptyPrimary artifact

emptyMeasured result

emptyRejection record

2026-09-01Outline created from the AI Operations Roadmap (B10-B27).

← B13 Adversarial Robustness + Cost GatingB15 Portability + Registry Bootstrap →