WHY
Developers need document extraction to return structured, traceable artefacts that can feed a product workflow without sending sensitive files to a third-party model.

WHAT
This edit shows a source PDF attached in the actual File extraction UI, a job submitted, a workbook and linked pickup returned, and the product's shared CMS handoff completed.

HOW
The fictional PDF was processed once by the real in-house extractor, then its exact fresh result was replayed through the unchanged frontend with deterministic local APIs. The UI exposes in-house EU hosting and keeps the source, status and downstream artefacts in one session. No production system is contacted.