The benchmark for AI-native Forward Deployed Engineering.
FDE is the operating model. AI-native deployment is the specialization this release examines first.
Synthetic illustration of the proposed sequence. No task has been administered and no record has been issued; the status register says exactly what exists.
Provisional editorial series · primary-source desk research
The line is intentionally rhetorical, not a measured prevalence claim. As employers stretch the label across software engineering, deployment, reinvention, and frontline delivery, the defensible question is what work a person can actually prove.
Training and certification establish access to knowledge. A stronger qualification record separates trained, certified, deployed, proven, and independently referenced evidence instead of collapsing them into one badge.
Forward deployment is not a one-way implementation handoff. The practitioner builds and runs inside the customer boundary, then turns field evidence into reusable product, evaluation, and research learning.
The hard part is not producing a polished demo. It is diagnosing the operating system around the model—data, controls, tools, workflows, people, acceptance conditions—and remaining accountable through production use.
Healthcare, legal, semiconductor, and other consequential deployments change the constraints that define competent work. A vendor-neutral core therefore needs separately governed domain packs—not one generic interview loop.
These field notes interpret first-party records to frame benchmark questions. They do not estimate how many people use the title, how many would qualify, or whether the proposed benchmark predicts performance.
Inspect the research programBrowse the AI-native FDE construct: a portable forward-deployed core, explicit AI-system delivery requirements, and separately versioned context packs. Each domain opens into its released capability families and proposed observable signals.
Open the full benchmark explorerDiscover, frame, prioritize, and contract consequential enterprise problems under ambiguity.
55families
Released families across the benchmark’s ten domains.
6levels
An ordinal path from assertion to independent field corroboration.
Claim strength increases only when the record changes.
E5v0.1release
Current, inspectable assets bundled with the public release.
Transparency belongs in the record—not on a victory scoreboard. Current absences remain inspectable below.
No admitted human-participant record supports a capability, hiring, ranking, tier, or credential interpretation.
No independent validation, accreditation, external-majority commission approval, or reproduction is represented.
Publication readiness is tracked separately from measurement validity; neither can be advanced by interface polish.
FIELD / PROOF
FIELD / PROOF
FIELD / PROOF
FIELD / PROOF
FIELD / PROOF