Skip to content
PRESHaiPRESHaiPRESHos Platform

FDE path

The field delivery engineer (FDE) takes a tenant from “we bought the platform” to “agents do our work, governed.” This path is the end-to-end playbook: discovery, environment, skills and tools and MCP, approvals, handoff. New to the field sequence: the FDE blank-to-live path walks these stages as an ordered checklist; this section is the full technical reference behind it.

Grounding: workflow, artifacts, and checklists here are field practice grounded in the platform model. The MCP catalog/install model (ai.mcp_catalog_source / ai.mcp_catalog_server / ai.mcp_catalog_server_version vs ai.mcp_servers, custom tenant MCP with catalog_server_id null, requirePlatformOps, install endpoint, OAuth profiles, fingerprint and guarded fetch) and the connector contract (bindings, destinations, never-rules) are from pasted product sources. Agent/tool/MCP implementation syntax beyond that is not in pasted sources, flagged where it matters.

Stages

Section titled “Stages”

1. Discovery: from vague need to scoped build. Workload, systems, risk, and the one-page scope doc that gates everything after.

2. Environment: turn the scope doc into an Agent Environment (context, tools, policy). Narrow by default, verified before users arrive.

3. Skills, tools and MCP: capabilities that make the environment useful. Skills, tool composition, and MCP wiring, with verification per piece.

4. Approvals design: gate on risk. The approval matrix, approver roles, and the reviewable decision experience.

5. Handoff: to admin, operators, and users. Training, docs, open items, and the steady-state rhythm that keeps the build healthy.

Worked path: blank to live: one exact checklist end to end, from empty customer tenant to a live tenant-level enhancement, practice vs product labeled.

The engagement shape

Section titled “The engagement shape”

Stages run in order: discovery (scope doc), environment (scoped and verified), capabilities (skills, tools, MCP), approvals (matrix and roles), pilot sessions with real users, handoff (training, docs, open items). Pilot friction loops back to the environment stage.

  • Pilot with real users before handoff. Staged demos do not surface policy friction; real sessions with real goals do.
  • Loop back freely. Pilot friction is design feedback: adjust environment, capabilities, or approvals, then pilot again.
  • Leave artifacts, not memories. Every stage produces a document the tenant keeps (listed on each page).