MTPE deliverable · ML pipeline doc, MT→IT post-editing

MTPE — Lumen Analytics ML pipeline doc

Fictional brand. Lumen Analytics does not exist. This page shows the format of a real deliverable — no third-party logos, no real data. Layout is our own; the craft is what you are buying.

1 · English source

Before deploying to production, validate your pipeline against a representative sample of historical data. Monitor inference latency and set up alerts if p95 response time exceeds 500 ms for more than five minutes.

2 · Raw MT output

Prima di distribuire in produzione, convalida la tua pipeline contro un campione rappresentativo di dati storici. Monitora la latenza di inferenza e configura avvisi se il tempo di risposta p95 supera i 500 ms per più di cinque minuti.

3 · Post-edited version (untouched: ~71%)

Prima del rilascio in produzione, convalida la pipeline su un campione rappresentativo di dati storici. Monitora la latenza di inferenza e configura gli avvisi se il tempo di risposta p95 supera i 500 ms per oltre cinque minuti.

4 · Decision log

ChangeWhy
distribuire → rilasciare'Distribuire in produzione' is understandable but 'rilasciare' is the set collocation in Italian DevOps writing; the change costs nothing and buys nativeness.
la tua pipeline → la pipelineItalian technical prose drops the possessive where English keeps it ('your') — the pipeline of the system being documented, not of the reader personally. MT over-transfers 'your' everywhere.
contro → su'Validare contro' is a calque of 'validate against'. Italian uses 'su' for validation on a sample; 'contro' would imply opposition.
configura avvisi → configura gli avvisiArticle added: Italian generic plural takes the definite article in instructional register. MT drops it because English does.
per più di → per oltre'Più di' is spoken; 'oltre' is the written-register choice for thresholds. Register consistency across the doc is the MTPE's job, not the MT's.
Get a quote