本页以 FDE FAN 的第一视角讲解知识：先讲概念，再讲方法、图表、训练任务。底部保留参考来源，方便继续阅读。 This page teaches in FDE FAN's own voice: concepts first, then methods, visuals, and practice tasks. References are kept at the bottom for further reading.
知识结构地图Knowledge Structure Map
| 知识层级Knowledge Layer | 我们要掌握什么What We Need to Master | 训练产物Training Artifact |
|---|---|---|
| 核心论点Core thesis | 企业正在重新思考 FDE，因为现场知识不能长期停留在少数人的脑子里。Companies are rethinking FDEs because field knowledge cannot remain inside a few individuals' heads. | 把个人经验变成上下文资产。Turn individual experience into context assets. |
| 平台化方向Platform direction | 上下文、权限、工具、评估和组件需要被平台承载，而不是每次项目重做。Context, permissions, tools, evals, and components must be carried by platforms rather than rebuilt each time. | 课程要训练上下文工程。Train context engineering. |
| FDE 新职责New FDE responsibility | FDE 不只是客户现场解决问题，还要把解决方案产品化、模板化、可复用化。FDEs do not only solve problems in the field; they productize, templatize, and reuse solutions. | 每个作业必须产出可移交资产。Every assignment must produce transferable assets. |
| 组织风险Organizational risk | 如果没有平台化，FDE 成为昂贵瓶颈；如果过度平台化，又可能丢失客户现场判断。Without platforms, FDEs become expensive bottlenecks; with excessive platformization, teams may lose field judgment. | 训练“平台 + 人”的边界。Train the boundary between platform and human. |
核心观点Key Takeaways
FDE 不能只做项目英雄，要把现场知识结构化成团队可复用资产。FDEs cannot remain project heroes; they must structure field knowledge into reusable team assets.
上下文工程会成为核心技能：知道给模型什么、不该给什么、如何保持更新。Context engineering becomes a core skill: what to give the model, what to withhold, and how to keep it current.
交付标准应从“能跑”升级到“可维护、可审计、可移交”。Delivery standards must move from 'it works' to maintainable, auditable, and transferable.
从人肉部署到上下文平台From Manual Deployment to Context Platform
| 层级Layer | 含义Meaning | FDE 产物FDE Artifact |
|---|---|---|
| 过去Before | 个人经验、现场救火、重复定制Individual memory, field firefighting, repeated custom work | 交付不可复制Delivery cannot scale |
| 过渡Transition | 模板、Prompt、脚手架、组件库Templates, prompts, scaffolds, component libraries | 效率提高但仍依赖个人Faster but still person-dependent |
| 目标Target | 上下文平台、权限、评估、可观测Context platform, access control, evals, observability | 组织级 FDE 能力Organization-level FDE capability |
深度讲义Deep Study Notes
1. 上下文是 FDE 的核心资产1. Context is the core FDE asset
FDE 的现场价值往往来自对客户系统、流程、隐性规则和组织政治的理解。问题是，这些理解如果只存在于个人脑中，就无法规模化。FDE 要把现场知识转换成结构化上下文，包括数据来源、字段定义、业务规则、权限边界、异常样本、验收口径和维护说明。FDE value often comes from understanding customer systems, workflows, implicit rules, and organizational dynamics. The problem is that this understanding does not scale if it lives only inside an individual. We convert field knowledge into structured context: data sources, field definitions, business rules, access boundaries, failure samples, acceptance definitions, and maintenance notes.
2. 平台不是替代 FDE，而是减少重复劳动2. Platforms do not replace FDEs; they remove repeated work
当上下文被平台化，FDE 不需要每次从零开始理解客户资料、拼接 API、写相同的工具说明或重复创建测试清单。平台负责保存和调用上下文，FDE 负责判断上下文是否完整、是否过期、是否越权、是否足以支持上线。课程中应把“资料结构化”设为必修任务。When context is platformized, FDEs do not need to repeatedly understand customer materials from scratch, stitch APIs, write the same tool descriptions, or recreate test checklists. The platform stores and retrieves context; the FDE judges whether it is complete, outdated, over-permissioned, or sufficient for launch. We make source structuring a required task.
3. 从项目英雄到组织能力3. From project hero to organizational capability
传统 FDE 容易变成项目英雄：某个人很懂客户、能快速救火、能把系统跑起来。但这类能力很难复制。新的 FDE 训练应该要求学员每做一次项目，都把经验沉淀成模板、组件、Prompt、测试样本、权限说明和操作手册，让下一位同学或下一位企业同事可以接手。Traditional FDEs can become project heroes: someone understands the customer, fixes fires quickly, and gets the system running. But that ability is hard to reproduce. New FDE training should require learners to turn every project into templates, components, prompts, test samples, permission notes, and runbooks so another student or colleague can take over.
4. 课程升级要求4. Curriculum upgrade requirement
我们要把课程从“会做 Demo”升级到“会沉淀组织资产”。每个案例页应该要求学员提交资料结构图、上下文选择理由、敏感信息处理方式、Prompt 版本记录、测试清单和移交说明。这样学员学到的不是一个页面，而是 FDE 的工作系统。We push the course from 'can build a demo' to 'can create organizational assets'. Every case should require learners to submit a source-structure map, context selection rationale, sensitive-data handling plan, prompt version history, test checklist, and handoff note. Learners then study an FDE operating system, not merely a page.
本课训练目标Training Goal
我们需要增加“上下文资产化”训练：每个案例必须交付资料结构、Prompt 版本、权限边界和维护说明。We need context-asset training: every case must ship source structure, prompt versions, access boundaries, and maintenance notes.
课堂任务Classroom Assignments
把一个客户资料包整理成上下文目录：哪些给模型、哪些不给、哪些需要脱敏。Turn a customer source pack into a context directory: what goes to the model, what does not, and what must be masked.
为一个 Agent 项目写 Prompt 版本记录和权限说明。Write prompt version history and permission notes for an agent project.
把一次人工救火过程改写成可复用的 runbook。Convert one manual firefighting process into a reusable runbook.
引用Citation
Unframe. Why companies are rethinking the role of Forward Deployed Engineers. https://www.unframe.ai/blog/why-companies-are-rethinking-the-role-of-forward-deployed-engineers. Accessed 2026-06-28.