Skip to content
FDEFDE Wiki

FDE glossary: one rendering per term

Twenty-two terms, one fixed translation each, and the three things this site will not let anyone rename.

Updated 2026-10-304 min read

A glossary earns its place only if it constrains what the rest of the site is allowed to say. Every term below has exactly one rendering, and every article here uses that rendering and no other, so a reader who learns 回灌 never has to work out later whether a stray 反馈闭环 meant the same thing. Some of these choices are arguable; the point is not that they are beyond argument, but that a definition on this page can be checked against a claim on another.

The role itself circulates under three Chinese names: 前沿部署工程师, 现场工程师 and 前线部署工程师. The first two read as "frontier deployment" and "on-site engineer"; this site uses 前线部署工程师 throughout, including in the titles of the articles that link here.

Chinese English One-sentence definition
前线部署工程师 Forward Deployed Engineer (FDE) An engineer stationed inside the client's environment who closes the gap between what the product can do and what the client actually needs, from investigation through delivery.
侦察 Reconnaissance The first stage, in which the client's description of the need is falsified into an executable judgement rather than collected as information.
定义 Definition The second stage, which locks terminology, data definitions, acceptance criteria and the fallback before any build starts.
交付 Delivery The third stage, in which something runs on the client's real data and the evidence reaches the business endpoint, not merely the system.
回灌 Feedback Loop The fourth stage, in which one client's solution becomes an asset the organisation can reuse on the next client rather than a one-off.
撤离 Extraction The fifth stage, in which the client keeps running without the FDE, with the exit conditions written down at the start.
三张图 Three Maps Money, power, and who loses — always in that order, because the third can only be drawn once the first two are done.
七问清单 Seven Questions The seven questions that must be answered in the first two weeks on site, including the ones the client cannot answer.
影子系统 Shadow System The spreadsheets, group chats and paper ledgers that carry the work the official system does not.
口径表 Metric Definition Table Five fixed columns — metric definition, data source, window, exclusion rules, arbiter — that turn a metric from a shared opinion into something a project can be judged against.
六段解剖 Six-Section Anatomy The fixed six-part write-up of a finished deployment, running from what the company earns to what died.
死因六型 Six Causes of Death The closed list of reasons a feature fails, kept closed so that "what died" cannot be answered with a story.
四周法则 Four-Week Rule A function counts as live only if it is still in use four consecutive weeks after go-live; a stop-use rate above 30% puts it on the not-live list.
日落条款 Sunset Clause The end conditions written into the project charter before work begins, including the trigger date and who may extend it.
席位 Seat The unit of staffing: one person plus one paired agent.
出环 Out-of-the-Loop Moving a task out of the conversation interface and into an API, so that the person leaves the loop.
魂与壳 Soul and Shell Two layers of a seat — judgement and memory versus tools and interface; the shell may be replaced, the soul must survive the move.
校准回路 Calibration Loop The cycle that sets a week-one judgement against what actually happened and feeds the gap into the next judgement.
判断日志 Judgement Log Four columns — the week-one judgement, what happened, the week and signal that revealed it, the transferable part — locked when written and only appended to.
影子工作法 Shadowing Spending a full working day beside a real user, watching for workarounds rather than the process as described.
证据分层 S1–S4 Evidence Ladder Four levels of proof that a delivery works: the system accepted the request, processed it, completed the action, and the business endpoint received the result; a 200 response proves only the first.
断奶 Weaning Reducing FDE involvement in order of risk, lowest first, until the client runs the system with nobody on the inside.

Three things this table forbids

Stage names may not be swapped for synonyms. Not 调研, 设计, 实施, 复盘, 退场, and not their English cousins either. A stage name is a pointer to a set of exit criteria and a set of known failure modes; a synonym detaches the criteria and leaves only the word. A page that writes "research phase" where it means 侦察 has quietly moved publication into a stage that has no rules attached.

The three maps keep their order: money, power, who loses. Who loses comes last because it is the map people skip, and because a losing list drawn before you know where the money flows and who approves it is a list of guesses.

The six-section anatomy may not be merged or reordered. Combining "what lived" and "what died" into one "results" section produces a section that reads as a single thing and buries every death inside its average. The order carries the argument; the headings alone do not.

Used as a lookup, the table settles arguments: if an article on this site uses a term in a way a row here does not allow, the row wins and the article gets fixed. A term you need and cannot find is missing on purpose — this site would rather hold twenty-two terms than publish sixty that drift.

Sources and further reading

  • fde.wiki 内容写作规范·术语口径——本页译名与三条红线以该规范为准
  • 《FDE 现场工程手册》 — CC BY-SA 4.0;阶段产出物、死因六型与席位的释义改写自该书

This article is original analysis by FDE Wiki. Frameworks and case material that originated elsewhere are credited below.

The weekly letter

One letter a week: what was added to the field manual

New articles, and the real demand and talent that came through the board. No drip sequence, no upsell.

Only used to send this letter. Unsubscribe in one click, any time.