What is an FDE?
Define the role through the outcome chain and delivery evidence.
FDE WHITEPAPER / BETA 0.1
The FDE Field Delivery Handbook
A living bilingual handbook for turning AI capability into an operable, adopted, and transferable business outcome.
The first release ships five usable assets
Start with accountability, process, evidence, and two working templates, then expand into technology, organizations, jobs, and field cases.
01Published05Published12PublishedAPublishedBPublished
What is an FDE?
Where accountability begins and ends
The 10-step delivery loop
How a project moves from field discovery to transfer
Project evidence standards
How to prove launch, adoption, and outcomes
Project evidence card
Record stage claims, five evidence layers, gates, and publication controls
10-step delivery canvas
Use it for kickoff, weekly review, stage gates, and transfer
Full outline
Cases, playbooks, templates, jobs, and community feedback live inside the relevant chapters instead of becoming disconnected top-level channels.
Definition, boundaries, and accountability
Chapters 1-4Published
Why now
Why AI products have renewed the need for high-touch delivery.
Role boundaries
Compare product, solutions, implementation, customer success, and Applied AI roles.
Global and China contexts
How procurement, governance, private deployment, and organizations change delivery.
The 10-step delivery loop
Chapters 5-11The 10-step FDE delivery loop
From entering the field and defining the problem to operations and transfer.
Enterprise constraints
Data, permissions, legacy systems, procurement, compliance, and adoption friction.
Agents
When autonomy helps and when a deterministic workflow is enough.
RAG and enterprise knowledge
Knowledge boundaries, permissions, freshness, citations, and retrieval evals.
Evals
Replace demo impressions with failure modes, datasets, thresholds, and regression.
Permissions, security, and accountability
Least privilege, human approval, audit, and high-risk actions.
Integration, launch, and operations
Interfaces, rollback, SLOs, incidents, adoption, and transfer.
Evidence, people, and organizations
Chapters 12-16Project evidence standards
Prove completion through problem, solution, quality, operations, outcomes, and transfer.
The FDE competency model
Map capability to artifacts, project evidence, and observable behavior.
Transition paths
Move from engineering, data, product, solutions, consulting, or internal IT into FDE work.
Companies, roles, and opportunities
Read the real accountability, not only the job title.
Organization and business models
Create product feedback without falling into unlimited custom services.
Failure, cases, and peer review
Chapters 17-19The failure atlas
Explain why demos fail to become durable outcomes.
The field casebook
Compare projects with a shared evidence card instead of packaging success stories.
Peer review in practice
Keep cases, methods, templates, and role maps correct through real field feedback.
Five layers of delivery evidence
Every important claim in the handbook should eventually resolve to reviewable material.
01Problem evidence
Real users, workflow, baseline, and loss
02Solution evidence
Constraints, architecture decisions, assumptions, and alternatives
03Quality evidence
Evals, failure modes, safety, and launch thresholds
04Operational evidence
Release, adoption, reliability, cost, and incidents
05Outcome and transfer
Business results, confirmed ownership, and operating capability
Appendices A-H
Put the handbook to work
The project evidence card and 10-step delivery canvas are ready for kickoff, review, and retrospectives. Later appendices will add evals, permissions, launch gates, capability models, job maps, and correction logs.