Master Art of Translation | The PDS4 Planetary Data, SPICE Geometry & Mission Archive Translation System — How Labels, Kernels, Time Scales, Frames and Provenance Keep Their Meaning

Planetary data translation is not just the translation of descriptions in a space mission archive. It is the disciplined interpretation and cross-language communication of PDS4 XML labels, NASA Planetary Data System products, SPICE kernels, mission geometry, instrument metadata, spacecraft clocks, coordinate frames, measurements and scientific provenance. A reliable translator must make the data understandable in another language while leaving executable identifiers, values, models and evidence intact. This guide explains how to translate PDS4 metadata and SPICE documentation, how to read planetary mission archive labels, and how to preserve scientific meaning without silently changing the observations.

The hidden problem in translating planetary science archives is that apparently ordinary words—product, target, frame, kernel, time, level, resolution, angle, version or calibrated—can refer to defined objects in a technical information model. Translating those words without checking their role can break the relationship between a label and a data file, confuse an instrument observation with a derived estimate, or make a position look correct in the wrong reference frame. A readable paragraph can therefore be linguistically fluent and still scientifically false. This article teaches an evidence-first method for deciding what to translate, what to preserve, and what to explain.

The repeatable method is to identify the original archive object, verify its PDS4 class and version, mark invariant tokens, inspect associated documentation and SPICE kernel context, translate the human-facing explanation, and test every claim against the unmodified source. Readers seeking a PDS4 metadata translation workflow, SPICE kernel terminology, spacecraft time-scale explanation, XML label translation rules, mission-data glossary or planetary archive quality-assurance checklist can follow the steps below. This is a world-facing teaching reference, not a mission-specific technical authority or an instruction to modify scientific archive files.

Architecture: EDKSG-TRANS-MASTER-WORLD-880. This is the next specialist child of Master Art of Translation | The Complete System for Moving Meaning Between Languages. It owns translation of mission-archive representation and evidential meaning; it does not replace the source standards, become a planetary-science encyclopedia, or absorb the protected Vocabulary Learning Hub or How English Works learning owners.

Quick answer: what is the translation standard?

A PDS4/SPICE translation is accurate when a reader of the target language can recover the same scientific object, its measurement basis, time definition, geometric reference, processing state, uncertainty and evidential status as a reader of the source. Preserve identifiers, schema names, file names, NAIF codes, kernel contents, numerical values, units, coordinate-frame names and version semantics unless a documented, explicitly authorised transformation requires otherwise. Translate titles, descriptions, documentation, user instructions and explanatory notes where appropriate, while distinguishing translated display text from authoritative machine-readable fields.

Identify what the archive actually contains before replacing any technical term.
Keep PDS4 label structure, LID/VID identity, SPICE frame identifiers and kernel content stable.
Separate source wording from labels, enumerations, timestamps, numerical arrays, equations and software parameters.
Document whether values are raw, calibrated, geometrically corrected, derived or interpretive.
Record uncertainty, missing data, competing products, superseded versions and unresolved source ambiguities.
Validate the narrative by reconstructing a complete source-to-target evidence trail.

Definition lock: translation, metadata, data and geometry

A scientific archive is not a box of sentences waiting to be translated. A PDS4 product consists of identified material and its formal descriptive label; collections group products, and bundles group collections. PDS4 uses XML labels governed by schemas and data dictionaries. SPICE is a geometry and event-computation system supported by kernels. These are different layers that meet in a reader’s interpretation. A label can identify a measurement; kernel context can help a program calculate where something was; a prose explanation can tell a human why that matters. Rewriting the prose must never masquerade as rewriting any of the other two.

The authoritative definition of a label attribute comes from the applicable PDS4 common or local data dictionary, not from the most familiar dictionary meaning in the target language. A SPICE frame name is an identifier in computational context, not a freely paraphrasable geographical direction. A UTC timestamp, spacecraft clock count, ephemeris time value and human-facing date may all refer to temporal information, but they are not interchangeable strings. The professional translation job is to convey the relationships faithfully, not to pretend that a language change is a computational conversion.

A title may be rendered in natural target-language prose, but an LID should remain an LID. An explanation of a binary SPK may be translated, but a binary SPK should not be edited as text. A translated help page may describe a spacecraft attitude kernel, yet it must not silently relabel the kernel as a spacecraft-position product. These boundaries protect readers from subtle but consequential forms of mistranslation.

Research basis and how to verify authority

The technical descriptions below are grounded in NASA PDS4 documentation, the PDS Small Bodies Node guide to archive structure, NASA NAIF SPICE documentation, kernel and frame references, and the PDS citation rules. Published specifications evolve: check the current release and mission documentation rather than treating a version number in an example as globally current. Terminology descriptions here are educational paraphrases of those authorities, not a replacement for the documents themselves. Source pages used for this edition were checked on 1 November 2026.

The hidden problem: language crosses several independent layers

1. The archive identity layer

A logical identifier and version identify a managed product; translating either can create an apparently new and nonexistent thing. A display name and an archive key must be treated differently. The translator should first decide whether a passage describes an object, an operation, a value, a convention or an inference. That decision sets the allowed degree of paraphrase. When a statement is evidential, preserve its conditions, exceptions and revision history, then make only the surrounding prose easier to read.

A practical test is to ask which machine-readable or citable record would allow an independent reader to check the statement. If no source record exists, do not invent one to make the narrative sound complete. When a mission-specific term has no approved target-language equivalent, retain the identifier or original term with a short accurate explanation instead of creating an unofficial alias.

2. The physical measurement layer

A numerical pixel, spectrum, time series or coordinate has meaning only with its unit, sampling basis, calibration history and quality status. Fluency cannot reconstruct a missing instrument definition. The translator should first decide whether a passage describes an object, an operation, a value, a convention or an inference. That decision sets the allowed degree of paraphrase. When a statement is evidential, preserve its conditions, exceptions and revision history, then make only the surrounding prose easier to read.

3. The geometry layer

Observer, target, aberration correction, epoch, reference frame and coverage determine the sense of a reported position or pointing. Two correct-looking triples can mean different things. The translator should first decide whether a passage describes an object, an operation, a value, a convention or an inference. That decision sets the allowed degree of paraphrase. When a statement is evidential, preserve its conditions, exceptions and revision history, then make only the surrounding prose easier to read.

4. The processing layer

Raw, calibrated, corrected, resampled and derived products answer different questions. A claim about what a sensor measured is not identical to a claim about what later software estimated. The translator should first decide whether a passage describes an object, an operation, a value, a convention or an inference. That decision sets the allowed degree of paraphrase. When a statement is evidential, preserve its conditions, exceptions and revision history, then make only the surrounding prose easier to read.

5. The provenance layer

Investigations, instruments, targets, people, processors and reference products establish lineage. When a translation erases qualifiers, readers lose the ability to trace a conclusion. The translator should first decide whether a passage describes an object, an operation, a value, a convention or an inference. That decision sets the allowed degree of paraphrase. When a statement is evidential, preserve its conditions, exceptions and revision history, then make only the surrounding prose easier to read.

6. The representation layer

XML tags, namespaces, schema types, arrays, tables, binary file layouts and line delimiters are infrastructure, not natural-language prose. Editing them can make the archive unreadable. The translator should first decide whether a passage describes an object, an operation, a value, a convention or an inference. That decision sets the allowed degree of paraphrase. When a statement is evidential, preserve its conditions, exceptions and revision history, then make only the surrounding prose easier to read.

7. The communication layer

Science is read by researchers, students, librarians, engineers, journalists and the public. Explanation may vary with audience, but the underlying evidence must not. The translator should first decide whether a passage describes an object, an operation, a value, a convention or an inference. That decision sets the allowed degree of paraphrase. When a statement is evidential, preserve its conditions, exceptions and revision history, then make only the surrounding prose easier to read.

A repeatable 24-gate translation workflow

Gate 01 — Brief and audience

Record source and target languages, subject speciality, audience, purpose, allowed transformations and responsible scientific reviewer. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

A translator should be able to demonstrate a pass/fail test. Ask: could a second reviewer reconstruct this decision from the recorded source and translated paragraph? If the answer is no, return to the source and write down the missing detail. Do not conceal a failed test with a smoother sentence; that converts a documentation problem into a knowledge problem for the next reader.

Gate 02 — Source inventory

Enumerate labels, data, supporting documents, kernel packages, software notes and online release notices before drafting. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 03 — Object classification

Identify product classes, collection membership and bundle scope; do not infer product class from file extension alone. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 04 — Authority hierarchy

Locate the applicable PDS4 standards release, data dictionary, mission-specific local dictionary and NAIF documentation. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 05 — Read the whole context

Inspect surrounding label sections, source documentation and collection summaries before translating isolated phrases. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 06 — Identify immutable tokens

Mark XML element names, namespaces, identifiers, unit symbols, numeric literals, version strings and kernel or frame names. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 07 — Resolve names

Distinguish a display title, common body name, formally registered target name, context identifier and software object ID. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 08 — Resolve measurement level

Determine whether the product is unprocessed, calibrated, transformed, map-projected, modelled or otherwise derived. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 09 — Resolve time semantics

Identify the time system, count origin, event represented, time precision and any spacecraft-clock correlation needs. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 10 — Resolve spatial semantics

Identify observer, target, reference frame, coordinate basis, geometry convention and any relevant light-time choices. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 11 — Resolve numerical semantics

Record units, axes, sign conventions, fill values, scaling and uncertainty before explaining a measurement. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 12 — Audit relationships

Trace references among product, collection, bundle, context products and associated calibration documents. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 13 — Terminology record

Approve each domain-specific translation, retain the source term and document definition and source authority. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 14 — Draft human-facing text

Translate readable descriptions and instructions without touching operational tokens or changing degrees of certainty. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 15 — Explain necessary borrowings

Retain labels like SPK, CK, LIDVID and instrument IDs, adding concise plain-language glosses on first use. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 16 — Preserve controlled lists

Do not translate enumerated machine values inside their authoritative fields; localise explanations outside them. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 17 — Check false equivalents

Look for terms whose everyday meanings differ from their technical class or software use. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 18 — Back-translate critical claims

Independently check whether the target describes the same event, quantity, object and restriction. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 19 — Run XML/schema review

Where files are in scope, validate unchanged source XML with the appropriate tools; never claim a translated paragraph validates an XML schema. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 20 — Run geometry review

Ask a SPICE specialist to check time/observer/frame/coverage references when narrative statements depend on computed geometry. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 21 — Verify identifiers and citations

Confirm LIDs, VIDs, DOIs, product titles, version status and links against the real archive. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 22 — Review target-language usability

Ask a native-language subject reader to explain what the text says without access to the source. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 23 — Record exceptions

Log missing information, unresolved ambiguity, inherited source defects and decisions requiring project approval. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Gate 24 — Freeze and release

Separate released target-language prose from immutable source assets; retain traceable review and revision records. The deliverable for this gate is an explicit evidence note, not merely a tick in a checklist. Record who supplied the evidence, whether it came from a standards document, a mission data set, a kernel comment or an explanatory source, and which claims remain open for review.

Field-by-field mechanisms: what must keep its meaning

Mechanism 01: PDS4 Product

Definition and scope. A Product is the smallest separately identified and managed object in the PDS4 system; it may describe an observation or a document. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Calling every product a raw data file disguises document and context products. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check the product class in its label and associated data objects. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. An archive entry labelled Product_Document may contain a user guide rather than instrument measurements. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep the word Product when naming the class and explain its role in prose. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Transfer rule. Write a bilingual terminology entry with the source term, approved target-language gloss, definition, authority, example context, forbidden near-synonyms and review date. Reuse that entry only where the same formal concept truly appears. A surface match in another mission or dictionary does not establish identical semantics. This routine protects consistency without turning domain translation into rote word substitution.

Mechanism 02: PDS4 label

Definition and scope. The XML label describes one or more files and tells software and people how to interpret the product. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Translating element names or treating the label as an optional caption breaks the formal description. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check referenced files, XML namespaces and schema-driven elements. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A translated title changes while the XML tag Identification_Area remains exactly the same. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Translate display prose only where allowed; preserve authoritative markup. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 03: Product_Observational

Definition and scope. The class identifies an observational product whose scientific data and context are represented in a formal label. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Equating observational with unprocessed or directly visible oversimplifies what the product records. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check observation and discipline areas, product documentation and processing context. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A calibrated spectrum can still require observation metadata; it is not automatically a raw photograph. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve the class name and describe the actual data product. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 04: Product_Document

Definition and scope. A document product supplies textual or other documentary material to support the archive. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Readers may mistake a document’s title for an instrument observation. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check which file the document label references and what the document claims to be. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. An instrument paper does not automatically provide the measured spectra. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Translate explanatory writing; do not reclassify the product. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 05: Product_Bundle

Definition and scope. A bundle is an identified grouping of collections. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A bundle may be described falsely as one instrument file or one event. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check the bundle label, member collections and identifier. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. One bundle may organise observational, document and calibration collections. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Use bundle as an archive packaging term, not a poetic description. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 06: Product_Collection

Definition and scope. A collection organises related products and has its own identity and inventory. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A translator may collapse the distinction between folder, collection and individual product. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect its collection label and inventory relationships. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A directory named data is not itself sufficient proof of collection identity. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve formal collection relationships and explain folder layout separately. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 07: Identification_Area

Definition and scope. This part of a PDS4 label carries product identity and key descriptive information. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Making it read as a free-form heading may hide that its members include controlled fields. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Verify logical_identifier, version_id, title and product_class when present. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A title may change in a translation while the logical_identifier does not. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Leave schema element names untouched and document display variants. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 08: Logical identifier

Definition and scope. The LID identifies the logical product across versions. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A translator might turn the URN into a translated title and lose the stable key. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Read the source label and PDS LID formation guidance. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Two versions of the same logical product share an LID but not a complete LIDVID. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Copy the LID exactly and keep human-friendly glosses adjacent. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 09: Version identifier

Definition and scope. The VID distinguishes versions of a logical product. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Treating a version increment as a new observation or a translation edition changes provenance. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check the official version_id rather than guessing from filenames. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A revised label can retain a product LID while using a new VID. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep version numbers exact; describe what revision records prove. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 10: LIDVID

Definition and scope. The combined logical identifier and version specifies one product version. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Translating or respacing the double-colon separator produces a different string. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Confirm the concatenation rule and source version. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. The string urn:nasa:pds:example:collection:item::2.0 is illustrative, not a live product. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve both parts and the exact separator. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 11: DOI

Definition and scope. A digital object identifier can support citation of a bundle, collection or document where registered. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Inventing a DOI from an LID conflates two identifier systems. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Use the official PDS DOI search service and citation instructions. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A product LID need not imply that the product has its own DOI. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Cite the registered DOI when available; otherwise follow documented citation guidance. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 12: Title

Definition and scope. A title provides a human-readable product name. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A polished translation may drop a crucial observing phase, instrument or product-level qualifier. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Compare its descriptive scope to the unchanged LID and documentation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A title containing calibrated should not become raw in another language. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Translate for comprehension while retaining discriminating technical nouns. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 13: Information model version

Definition and scope. The information_model_version indicates the model version governing a label. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Confusing the model version with the observation date or data-processing version misleads readers. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Look at the label and relevant standards release. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A current reader can encounter a valid older label model. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Quote the exact model version and explain its role. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 14: Product class

Definition and scope. The product_class is a structural classification in the PDS4 model. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Rendering a class as a vague everyday label makes data discovery unreliable. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Consult the standards definitions for the named class. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Product_Context and Product_Observational answer different archival questions. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep controlled class names and translate their explanation. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 15: Context products

Definition and scope. Context products describe entities such as instruments, targets, investigations and hosts. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. An instrument’s descriptive metadata can be mistaken for measurements from that instrument. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Follow its referenced context LID and source taxonomy. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. An instrument context record is not a calibration file. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve context identity and distinguish documentation from observation. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 16: Instrument host

Definition and scope. An instrument host is the entity carrying or operating an instrument in the archive context. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Translating host as the person who uploaded the data misassigns operational responsibility. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Trace the instrument-host relationship in context references. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A spacecraft and its detector may have different records. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. State the relationship explicitly without inventing a person. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 17: Investigation

Definition and scope. Investigation identifies a scientific mission or organised investigation context. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A literary translation such as police inquiry would be misleading. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Confirm the official mission or investigation name. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. The investigation identity may apply to several instruments and data sets. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Retain the official proper name and describe the science programme. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 18: Target

Definition and scope. A target can denote the observed body or subject, not merely a destination. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Casual translation can turn observed target into navigation goal. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check target context, body ID and science purpose. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A detector may observe a moon while the spacecraft itself orbits another body. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Translate the observational relation rather than a generic word. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 19: Reference_List

Definition and scope. A reference list establishes relationships to other archive products and materials. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Treating references as optional reading suggestions hides dependencies. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect reference types and identifiers in the label. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A calibration reference and a bibliography entry may do different jobs. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Explain the linkage and preserve keys exactly. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 20: Internal_Reference

Definition and scope. An internal reference links products and context records inside the archive system. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Changing a referenced LID breaks the target’s referential identity. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Compare the reference target with registered source records. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A data product points to an instrument context product by identifier. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Never localise the reference value. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 21: External_Reference

Definition and scope. An external reference points to material beyond the immediate PDS product system. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A translated summary may suggest external material is part of the data bundle. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check the URL, reference type and citation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. An external journal paper can support interpretation without being an included file. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve the boundary between archive holdings and outside material. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 22: File_Area_Observational

Definition and scope. A file area describes actual data objects and the files that contain them. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A reader may equate file names with product identity or assume one label means one file. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect array and table descriptions and file references. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. An image payload and associated ancillary data can share a product context. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Translate the explanation without altering file names or locations. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 23: Array dimensions

Definition and scope. Array shape governs interpretation of pixels, spectra, grids and other numeric payloads. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Rewording axis meanings or reversing axis order produces plausible but wrong displays. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect axis_array, element_array and documented order. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A three-dimensional array need not store dimensions in the visual order shown in a figure. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve dimensional order and label each axis with source evidence. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 24: Axis names

Definition and scope. Axis labels identify what each dimension of an array means. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A common word such as line may mean scan line rather than a row of prose. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Read the array definition and instrument user guide. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A sample axis and a wavelength axis should not swap after translation. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep controlled axis values intact and explain them naturally. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 25: Element data type

Definition and scope. A data type specifies how binary or text elements are encoded. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Turning an unsigned integer into a signed value alters the interpretation of the same bytes. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check type, byte order and parsing notes. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A negative-looking display can come from a bad signedness assumption. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Do not translate or normalise datatype tokens. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 26: Byte order

Definition and scope. Endianness governs interpretation of multibyte binary numbers. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Human-language descriptions can be accurate while parser settings are wrong. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Confirm the source label’s storage order and software specification. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. The same bytes can decode to different numbers under different ordering. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Explain byte order; never convert without a verified transformation. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 27: Scale factor

Definition and scope. A stored number can require a scale factor to represent a physical measurement. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A translator can report the integer payload as the final physical value. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Read the calibration and scaling fields. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Stored 250 may denote a scaled measurement, not 250 physical units. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. State the exact formula when documented; never invent a multiplier. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 28: Value offset

Definition and scope. An offset may be applied in conversion from stored sample to physical value. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Omitting the offset shifts every derived point while leaving formatting plausible. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check offset semantics in the applicable data dictionary. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A display value may be reconstructed by applying both scale and offset. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep constants and operations explicit. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 29: Missing constant

Definition and scope. A fill or missing value may use a sentinel rather than a physical measurement. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Describing a sentinel as an extreme observed event contaminates science. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check special constant declarations and masks. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A large negative number can be missing-data notation, not temperature. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Document missingness and exclude such values from interpretations. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 30: Invalid constant

Definition and scope. Invalid indicates a condition distinct from unknown or missing in some contexts. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Combining invalid and not observed can falsely imply all absent values are equivalent. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect applicable special-constant definitions. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A value can exist but be rejected for quality, unlike a never-recorded value. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Translate the status distinction, not just the number. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 31: Units

Definition and scope. Units attach physical dimensions to numeric data. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A translated word such as degree can mean temperature or angular measure. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Verify unit declarations and scope of each field. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A numeric 30 could be degrees of angle, Celsius, or a dimensionless count. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve authoritative symbols and spell out the dimension for readers. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 32: Coordinate frame

Definition and scope. A reference frame fixes the mathematical axes for a position or orientation. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Treating a frame as an image border erases geometry. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check the SPICE frame name or applicable PDS coordinate definition. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. The same vector has different components in inertial and body-fixed frames. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep the canonical frame name and explain its orientation. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 33: Frame center

Definition and scope. Frame center is the reference point associated with a frame definition. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Assuming the center is the target of observation can confuse geometry. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect the frame kernel or frame documentation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A spacecraft-fixed frame can have the spacecraft as center while viewing another body. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Explicitly distinguish center, observer and target. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 34: Frame class

Definition and scope. SPICE frame class identifies how the frame orientation is provided. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Calling all frames inertial disregards body-fixed or CK-driven orientation. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check the frame definition and required-reading guidance. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A CK-based frame depends on attitude data valid over time. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Retain the class meaning and required inputs. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 35: Observer

Definition and scope. An observer is the reference object in a geometric computation. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Swapping observer and target changes vector direction or interpretation. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Read the actual SPICE call and documentation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A position of a moon relative to a spacecraft differs from spacecraft relative to moon. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Write the relation as X observed from Y, not merely X near Y. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 36: SPK kernel

Definition and scope. An SPK holds ephemeris information used to compute positions and related states. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. SPK must not be translated as a spacecraft clock or attitude file. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check kernel type and coverage. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A trajectory statement cannot be confirmed merely from an instrument description. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Retain SPK and explain ephemeris in plain language. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 37: CK kernel

Definition and scope. A CK supplies pointing or attitude information, typically as a function of spacecraft clock time. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Calling it an image calibration kernel merges different functions. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check reference-frame context and coverage. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A camera boresight needs both its mounting parameters and time-dependent pointing. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep CK distinct from SPK and IK. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 38: PCK kernel

Definition and scope. PCK data describe body orientation and physical constants according to kernel type. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A body orientation model is not a spacecraft trajectory. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check whether the PCK is binary or text and which values it supplies. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. An inertial-to-body-fixed conversion may depend on orientation parameters. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Explain model dependence rather than promising timeless coordinates. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 39: FK kernel

Definition and scope. A frame kernel defines reference frames and their relationships or associations. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Translating an FK as a camera calibration table hides the frame role. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect FRAME_ definitions and centers. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A named instrument frame may be defined relative to a spacecraft frame. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve frame names and explain axes carefully. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 40: IK kernel

Definition and scope. An instrument kernel describes instrument parameters and geometric characteristics. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Calling IK the record of where the spacecraft was confuses mounting with trajectory. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect instrument parameter names and documentation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Field of view and boresight information support interpretation of instrument geometry. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep instrument settings separate from ephemeris and attitude. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 41: SCLK kernel

Definition and scope. A spacecraft clock kernel supports conversion or interpretation of spacecraft clock counts. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Spacecraft clock is not automatically the same thing as UTC. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check clock partition, correlation and applicable mission documentation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A raw count needs appropriate conversion context before a civil-time statement. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve counts and describe clock transformation only when verified. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 42: LSK kernel

Definition and scope. A leapseconds kernel supports time conversions within SPICE. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. It does not by itself determine a spacecraft’s trajectory or observation quality. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check which LSK was loaded and the requested time conversion. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A UTC-to-ET conversion can depend on timekeeping assumptions and kernel currency. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Retain LSK name and distinguish time conversion from geometry. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 43: Meta-kernel

Definition and scope. A meta-kernel lists kernels to load as a related set. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Its presence does not prove that every referenced file is available or compatible. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect paths, kernel list and referenced file versions. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. An example meta-kernel may point to a directory that another user lacks. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Translate instructions; preserve the executable kernel list. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 44: Kernel pool

Definition and scope. A kernel pool holds text-kernel variables loaded for SPICE calculations. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Treating these variables as translatable prose changes program behaviour. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check exact variable names and priorities. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Different loaded kernels may populate or supersede a parameter. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve variable syntax and identify the effective configuration. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 45: Kernel coverage

Definition and scope. Coverage specifies the times or segments for which necessary data are supplied. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A translated statement that a kernel works for the entire mission may overclaim. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Review segment summaries and interval checks. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A pointing request near a gap can fail even if the file is otherwise valid. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. State the checked coverage interval and any gaps. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 46: Kernel precedence

Definition and scope. Loading multiple kernels can affect which data segment is used. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Assuming all kernels are additive and harmless makes reproduction difficult. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check load order and active segment selection. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A late-loaded updated ephemeris can change a computed value. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Record the exact kernel set used to support a claim. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 47: NAIF object ID

Definition and scope. NAIF numeric codes identify bodies, spacecraft, instruments or other SPICE entities. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A code must not be translated into a guessed display name. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Validate code-name mapping in authoritative NAIF or mission materials. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A negative spacecraft ID is still an identifier, not a sign of invalid measurement. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep the integer exact and annotate verified meaning. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 48: Ephemeris time

Definition and scope. SPICE ET is a computational time argument, commonly described as seconds past J2000 in a TDB-related framework. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Replacing ET with wall-clock time erases a time-scale distinction. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Consult NAIF time documentation for the applicable conversion. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A number passed to a SPICE routine is not necessarily a printable UTC timestamp. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Explain the scale and conversion without inventing a direct lexical equivalence. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 49: UTC representation

Definition and scope. UTC is a civil time scale with precise historical conventions. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Treating all displayed dates as UTC can shift science events. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect time-system labels and explicit suffixes. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A mission record might encode spacecraft clock counts instead of UTC. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Spell out the actual system and avoid assumed offsets. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 50: Spacecraft clock partition

Definition and scope. Clock partitions can distinguish separate spans of spacecraft-clock counts. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A counter reset can make identical-looking count fields denote different moments. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect SCLK format and partition information. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Comparing counters without partitions can produce false event ordering. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Retain partition identifiers and explain why they matter. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 51: Light-time correction

Definition and scope. An observation geometry may be evaluated with or without light-time correction. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A reader can mistake apparent position for instantaneous geometric position. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check aberration-correction choices in the computation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A target’s observed direction can differ from its uncorrected geometric direction. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Name the correction method rather than saying position is simply exact. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 52: Stellar aberration

Definition and scope. Aberration choices can incorporate apparent-direction corrections. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Translating apparent as approximate or uncertain changes the physics. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Consult NAIF function options and interpretation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Two computed angles may differ because their correction settings differ. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve the named option and describe what it changes. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 53: J2000 reference

Definition and scope. J2000 appears in astronomy and SPICE frame/time discussions with different roles. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A translator must not treat every J2000 occurrence as a date when a file was created. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect whether it names an inertial frame, epoch convention or time reference. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A J2000 frame coordinate does not mean the observation occurred in 2000. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Translate explanatory grammar without repurposing the label. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 54: Body-fixed coordinates

Definition and scope. A body-fixed frame rotates with a specified celestial body according to an orientation model. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A point in the rotating frame is not a timeless inertial-space vector. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check body orientation and frame definition. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Longitude can depend on the applicable rotational convention. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. State the frame and model, not just latitude-longitude values. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 55: Latitude conventions

Definition and scope. Planetographic, planetocentric and other latitude conventions can differ. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Translating latitude without its qualifier creates measurement ambiguity. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Verify geometric convention in the source documentation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Two latitude figures for the same place may follow different definitions. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep the qualifier visible and do not silently convert. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 56: Longitude conventions

Definition and scope. Direction, zero meridian and planet-specific conventions matter. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Using an everyday east/west assumption can reverse a map interpretation. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check coordinate-system definitions. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A west-positive longitude is not interchangeable with an east-positive value. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Retain the source convention and explain any desired conversion separately. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 57: Image geometry

Definition and scope. Pixels may represent detector positions, line/sample coordinates or map-projected locations. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Assuming an image is north-up or geographically corrected changes interpretation. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect projection and image geometry metadata. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A raw detector frame may need geometric operations before map comparison. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Identify image state before translating directional descriptions. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 58: Map projection

Definition and scope. Projection parameters determine how surface coordinates become planar positions. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A prose phrase like rectangular map is not a projection definition. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Read map projection parameters and coordinate reference. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Two images can look aligned but use incompatible projection settings. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Use formal projection names and list relevant parameters. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 59: Calibration file

Definition and scope. Calibration material documents or enables conversion from instrument response to physical estimates. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A calibration file is not itself necessarily an observation of the scientific target. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Trace calibration lineage and software version. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Changing gain or dark correction can change derived radiance. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep calibration provenance separate from target identification. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 60: Raw versus calibrated

Definition and scope. Raw and calibrated data have distinct evidential roles and may retain separate products. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A target-language summary that calls calibrated values direct sensor counts misrepresents processing. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect processing level and archive product label. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Calibrated radiance reflects corrections, not an unchanged detector readout. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Translate processing status consistently and accurately. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 61: Derived product

Definition and scope. A derived product combines or transforms source evidence. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. It must not be marketed as directly observed merely because its source is a mission. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Review algorithms, inputs and uncertainties. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A mosaic or digital terrain model is not a single camera exposure. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. State the derivation and the limits of inference. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 62: Uncertainty

Definition and scope. Uncertainty describes a quantified or qualified limit on a measurement or result. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Replacing suggests with proves or exact with approximate changes the claim. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Look for statistical definition, confidence method and propagation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A positional uncertainty may be a model-dependent estimate. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep qualifiers, distribution assumptions and the reported precision. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 63: Quality flag

Definition and scope. A flag classifies the status or usability of a data value. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Translating a code as high quality based on visual appearance misleads users. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Read the controlled flag dictionary or mission documentation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Flag 2 might mean suspect rather than good; a translator cannot guess. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Retain codes and explain verified meanings. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 64: Data processing history

Definition and scope. Processing metadata records the software, procedures and steps behind the product. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Compressing a pipeline into the word cleaned conceals transformations. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Consult release notes, algorithm descriptions and provenance. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A new processor version can change derived values without new observing events. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve chronology and qualified processing terms. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 65: Mission phase

Definition and scope. Mission phases are named operational periods with distinct observational contexts. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A free translation can imply a phase had formally ended when it had not. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check mission definitions and time boundaries. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Cruise and encounter can describe different geometric or operational conditions. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Retain official phase names or use approved target-language forms. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 66: Observation geometry

Definition and scope. Incidence, emission and phase angles describe different geometric relationships. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Translating all three as viewing angle destroys scientific distinctions. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check formal angle definitions and vector sources. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Illumination and line-of-sight geometry may change brightness interpretation. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Name the actors and vertex of each angle. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 67: Solar distance

Definition and scope. Heliocentric distance and target-observer distance are different quantities. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A translation might call both distance from Earth. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect endpoints and units. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A comet’s heliocentric distance says nothing direct about spacecraft range. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Explicitly specify the two objects in every distance. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 68: Footprint

Definition and scope. An instrument footprint is the surface area represented by an observation under a particular geometry. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Mistaking footprint for pixel size alone erases viewing and altitude effects. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Read geometry and sampling documentation. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A detector pixel can cover a larger surface area at oblique viewing. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Explain area, method and assumptions without inventing exact boundaries. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 69: Spectral band

Definition and scope. A spectral band refers to a defined wavelength or frequency region or instrument channel. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Translating it as a color name without calibration can mislead. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check bandpasses, filter definitions and sensor response. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Near-infrared is not a visible red photograph. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep band identifier and spectral range when available. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 70: Radiance

Definition and scope. Radiance is a specific physical quantity depending on area and solid angle conventions. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Changing it to brightness without qualification loses physical precision. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check units and calibration data. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A high displayed pixel value is not necessarily high physical radiance. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Use technical terminology and define it for non-specialists. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 71: Reflectance

Definition and scope. Reflectance relates reflected to incident radiation under relevant definitions. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Calling it raw brightness obscures illumination normalization. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check the exact reflectance product definition. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A reflectance factor and reflectance quantity need not be identical. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Name the archived quantity and avoid casual equivalence. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 72: Geometric resolution

Definition and scope. Spatial sampling, pixel scale and effective resolution are related but distinct. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A translation may equate pixel spacing with recoverable detail. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Consult instrument optics and product resolution statements. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A finely sampled image may still have limited physical resolving power. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Differentiate sampling interval from resolution. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 73: Digital terrain model

Definition and scope. A terrain model may derive elevations or shapes from multiple observations. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Calling it an unprocessed photograph misstates the nature of the evidence. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check model generation and vertical reference. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. The terrain surface can inherit uncertainty from geometry and stereo matching. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. State model status, datum and units. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 74: Shape model

Definition and scope. A shape model represents a body’s surface geometry, often with facets or meshes. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A mesh is not a literal set of measured ground points at every facet. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Review construction method, frame and scale. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Different mesh resolutions can represent one body with different detail. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Describe representation and provenance rather than asserting perfect geometry. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 75: Coordinate uncertainty

Definition and scope. Positional uncertainty depends on measurement and geometric transformations. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Omitting the frame makes uncertainty impossible to interpret confidently. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check covariance or error descriptions and coordinates. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A one-kilometre range error is not the same as a one-kilometre map-position error. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Keep frame, axes, statistical meaning and method together. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 76: Provenance statement

Definition and scope. Provenance says where data came from and how it changed. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A smooth narrative without source IDs is not reproducible. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check source-product LIDs, processing notes and dates. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A derived image may aggregate several source observations. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Retain pointers to the sources and qualify lineage. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 77: Revision note

Definition and scope. A revision note explains changes to a data product or label. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A corrected metadata field is not always a new sensor measurement. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Compare previous and current VIDs and documented changes. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Users can cite the exact version rather than vaguely saying the latest one. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Record what changed and what was unchanged. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 78: Release status

Definition and scope. A preliminary, archived, superseded or corrected release has a particular status. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Describing preliminary output as final can overstate authority. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check PDS registration status and release notes. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. An early demonstration dataset may not have the same review history as a released archive. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. State documented status and uncertainty accurately. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 79: Science user guide

Definition and scope. The mission data user guide interprets fields, algorithms and known limitations. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A guide is explanatory, not a licence to replace source attributes by prose guesses. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Compare the guide to actual product and dictionary version. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A guide may discuss several product types with different semantics. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Link readers to the appropriate guide and identify its scope. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 80: Local data dictionary

Definition and scope. A local dictionary adds mission- or discipline-specific classes and attributes. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Applying a general English meaning where a local definition exists changes the field. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Check the correct namespace and dictionary version. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A familiar attribute name can mean something more constrained locally. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Give the local definition priority for that field. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 81: XML namespace

Definition and scope. A namespace distinguishes similarly named elements from different dictionaries. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Deleting prefixes to make text cleaner can merge unrelated concepts. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Inspect namespace declarations and schema locations. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. Two attributes with similar words may belong to separate namespaces. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Preserve markup and explain schema scope outside code. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 82: XML schema validation

Definition and scope. Schema validation checks structural constraints but does not prove scientific truth. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. A valid XML document can still contain wrong units or a false explanation. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Use compatible schemas, schematron and mission review where applicable. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A label may parse successfully while a time statement is semantically misleading. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. State which technical and human checks were performed. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Mechanism 83: Citable product version

Definition and scope. A citable version is a particular product state with an identifiable record. In planetary archive translation, the first step is to classify the string or statement by its role: schema component, identifier, controlled vocabulary, physical quantity, derived explanation or ordinary prose. That classification determines whether one should preserve the original token exactly, translate the surrounding words, or provide a paired technical label and explanation.

Hidden failure. Using a current link without a version can make later reproduction harder. This is a dangerous kind of failure because the translated sentence can remain grammatical and persuasive. The reader may not notice that the referent, unit, method or logical relationship has shifted. Fluency is a human-language test; it cannot substitute for a check against the source record. Mark this risk explicitly rather than assuming a specialist reader will infer the missing distinction.

Where the evidence lives. Verify LIDVID and DOI where appropriate. Do not use a search snippet or a nearby filename as the sole authority when the actual label or applicable dictionary can be examined. If source materials contradict each other, distinguish formal schema requirements from release notes, from scientific interpretation, and from an author’s informal description. Resolve the discrepancy with the appropriate data owner or retain a visible uncertainty note.

Worked interpretation. A change to label metadata can affect future interpretations of data. The safe target-language explanation must tell a reader what is observed or represented, which conditions hold, and which conclusions remain unsupported. It must not silently supply missing units, dates, reference frames, mission names or confidence levels. When necessary, keep the original technical term and add one brief explanation in the target language to prevent an invented equivalence.

Repair test. Cite identifiers and access information with precision. Compare the source and target at three levels: exact tokens, technical propositions and intended reader action. Check whether someone could recover the same object or computation after reading only the target-language material. If the answer depends on additional data, identify the dependency. A translation is incomplete if it makes a reproducible source sound like an untraceable fact.

Worked diagnostics: source, false reading, evidence and repair

Diagnostic 01: Bundle title says camera archive

Source situation. The bundle title includes the word camera while the contents include documentation and calibration products. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Treating every member as a camera exposure. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect bundle membership and collection labels. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Describe the archive package and specify the data classes separately. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Independent reader check. Give the target-language passage to someone who has not seen the source and ask them to identify the object involved, the nature of the claim, the relevant time and geometry where applicable, and whether the result is direct, derived or provisional. Compare those answers with the source. When they differ, revise the most specific misleading clause first and repeat the check.

Diagnostic 02: Product label has an updated VID

Source situation. The LID matches a prior product but version_id is higher. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling it a wholly new observation. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Compare revision metadata and LIDVIDs. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Say the archived product version changed, without inventing a new observing event. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 03: Translated file name differs

Source situation. A reviewer localises a filename displayed in a tutorial. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. The user searches for a file that cannot exist. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Match the tutorial link with actual archive filenames. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Keep filename exact and localise the surrounding instruction. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 04: Two similarly titled collections

Source situation. A data_raw collection and a data_calibrated collection share a mission and target. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Combining different processing levels under one translation. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read the collection LIDs and product documentation. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Retain level distinctions in every summary. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 05: Instrument and instrument host

Source situation. A context label references detector and spacecraft IDs. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Saying the spacecraft itself is the sensor. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Trace context references. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Name spacecraft as host and detector as instrument where the records support it. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 06: Data object with no plot

Source situation. A binary array has dimensions and datatype but no embedded figure. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling the file a PNG image. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read its data object declaration. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Describe data representation without inventing display format. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 07: Row versus line

Source situation. A sensor guide defines line and sample for an image product. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Switching them because a target language uses a different page orientation. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect axis order. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Explain rows, scan lines and samples using actual array axes. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 08: A missing-value sentinel

Source situation. A numeric payload contains an extreme negative constant. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Reporting record minimum as a dramatic physical event. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check Special_Constants. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Exclude missing-value sentinels from scientific descriptions. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 09: An invalid pixel flag

Source situation. The value is recorded but marked invalid. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Treating it as not observed at all. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect quality-mask semantics. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Preserve difference between missing and rejected observations. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 10: Scale factor and offset

Source situation. The physical quantity requires post-decoding arithmetic. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Printing stored counts as measured radiance. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read element array scale and offset. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. State computed physical values only when method is verified. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 11: Unsigned sample decoded signed

Source situation. The same bytes decode as negative under incorrect type assumptions. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Treating a software artifact as a low reading. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Compare datatype and parser configuration. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Restore correct interpretation; do not ‘correct’ values by translation. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 12: Unitless number in a caption

Source situation. A source caption says 45 without attaching the field’s unit. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Guessing degrees Celsius. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Trace the associated label. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Insert the verified dimension or flag missing source context. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 13: Angular degree versus heat

Source situation. A diagram says 30 degrees near a pointing axis. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Rendering a temperature unit in the target language. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check geometric definition. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Use angular terminology only when evidence establishes it. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 14: UTC confused with ET

Source situation. A computed time is labelled ET in a note. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Printing the numeric value as a UTC time. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Review SPICE time conversion. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Explain the computational time scale and required conversion. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 15: Spacecraft counter reset

Source situation. Two source clock counts look similar across mission segments. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Sorting events by raw count alone. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check partitions and correlation kernels. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Keep partition context and avoid unsupported chronology. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 16: Old leapseconds file

Source situation. An analysis note lists an LSK that may differ from a later standard file. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Assuming every time conversion reproduces identically. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Record kernel versions and conversion procedure. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Describe the run-specific configuration without asserting universal equivalence. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 17: Kernel list with absent file

Source situation. A meta-kernel references an SPK not found in the package. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Saying the package contains complete geometry. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check actual files and load logs. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Report unresolved dependency rather than invent a result. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 18: Ephemeris coverage gap

Source situation. The SPK does not cover the requested event time. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Claiming the result is unavailable because translation failed. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect segment coverage. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Identify a data-coverage problem, not a linguistic one. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 19: Attitude coverage gap

Source situation. A CK is available except around an instrument manoeuvre. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Rendering the absence as a pointing angle of zero. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check coverage and interpolation options. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Mark pointing as unavailable where the source cannot compute it. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 20: A frame name shortened

Source situation. A frame identifier is abbreviated for a presentation slide. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Using the abbreviation inside a reproducible software command. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Compare exact kernel frame names. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Keep machine names complete and provide a readable alias separately. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 21: Target and observer reversed

Source situation. An example says spacecraft position relative to Mars. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Translating it as Mars position relative to spacecraft. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read observer-target argument order. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Write both objects and direction explicitly. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 22: Geometric versus apparent

Source situation. A result is computed with a light-time correction. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Describing it as instantaneous geometry. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check aberration setting. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Differentiate apparent and uncorrected quantities. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 23: Instrument boresight

Source situation. A camera IK defines a boresight vector. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling it spacecraft trajectory. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Review instrument pointing definitions. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Explain fixed instrument direction separately from time-dependent attitude. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 24: Body-fixed longitude

Source situation. A surface location uses a specified longitude convention. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Assuming east-positive because that is familiar. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read coordinate convention. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Retain positive direction and zero meridian. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 25: Planetocentric latitude

Source situation. The source explicitly labels a latitude planetocentric. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Removing the qualifier in translation. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read projection and coordinate notes. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Carry the convention into the explanation. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 26: A projected mosaic

Source situation. A composite map looks like a camera photograph. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Claiming a single instantaneous exposure. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect processing-level documentation. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Call it a derived mosaic with source inputs where documented. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 27: Radiance map called color

Source situation. A spectral data view is shown with a false-color palette. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Describing the colors as direct visual appearance. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read display processing notes. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Distinguish false color from physical reflectance or radiance. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 28: Reflectance versus brightness

Source situation. A note reports reflectance factor. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling it simply sensor brightness. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect units and calibration. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Keep physical terminology and explain illumination effects. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 29: A terrain model elevation

Source situation. A numeric grid reports local topography. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Comparing elevation without knowing vertical reference. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check shape model and datum. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. State the reference surface and processing assumptions. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 30: Pixel scale exaggerated

Source situation. A product has small pixel spacing. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Claiming that all features of that size are resolved. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check optics and resolution. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Separate sampling from effective resolving ability. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 31: Uncertainty changes meaning

Source situation. A source says the result may indicate ice. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Translating it as proof of ice. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Track modality and evidence. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Preserve the tentative scientific claim. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 32: Preliminary classification

Source situation. A data product is described as preliminary. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Advertising it as final archive truth. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check release status. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Retain provisional status and relevant caveats. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 33: Source product superseded

Source situation. An older processing version remains citable. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Silently switching a target-language footnote to newest results. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect version history. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. State which version is actually discussed. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 34: Two instruments share target

Source situation. A mission has two sensors observing one planet. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Merging both instruments into one dataset description. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Trace context IDs. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Describe independent instrument provenance. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 35: Observation date and release date

Source situation. A press note says a product was released years after acquisition. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Equating release with observation time. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect start and stop times versus publication metadata. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Keep both dates clearly labelled. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 36: Start versus stop times

Source situation. A series has an observation interval. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Rendering the end as the acquisition start. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read field names and definitions. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Describe the complete interval. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 37: Image and spectrum in same archive

Source situation. The collection has different object types. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling every product a photograph. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check data object class. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Name image arrays and spectral tables accurately. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 38: Spectral wavelength unit

Source situation. A spectrum has values in micrometres. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Rendering numeric values as nanometres without conversion. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect units and conversion method. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Keep original units or show a verified explicit conversion. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 39: Range versus altitude

Source situation. A spacecraft-to-target range is listed. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling it altitude above surface. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check endpoints and surface model. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Name range as a distance between two objects. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 40: Incidence and emission angles

Source situation. Both angular quantities occur in a photometry table. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Combining them into one viewing angle. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read geometry definitions. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Keep illumination and view angles separate. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 41: Phase angle

Source situation. The phase angle appears with two other angles. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Mistaking it for mission phase. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Use geometric context. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Translate angle terminology rather than operational-phase terminology. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 42: Shape model facet

Source situation. A mesh facet is associated with a surface normal. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling every facet a measured crater. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check model method and mesh description. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Explain geometric representation and its limits. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 43: Target name translated poetically

Source situation. A body has an official designation. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Replacing the designation with a descriptive metaphor. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check authoritative body identifiers. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Use proper designation, adding translated explanation only. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 44: NAIF negative code

Source situation. An instrument ID is a negative integer. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling it an error or deficit. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Review code mapping. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Preserve it as a nominal identifier. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 45: FK versus PCK

Source situation. A paragraph names frame definitions and planetary orientation. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Treating both as the same data. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Review kernel types. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Explain the different computational roles. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 46: CK versus SCLK

Source situation. Pointing is indexed through spacecraft clock. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling the clock file the pointing data. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check CK and SCLK dependencies. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Name both components and their relationship. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 47: LSK does not provide pointing

Source situation. A time conversion works but an orientation query fails. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Assuming a valid time proves valid geometry. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect CK, FK, SPK and coverage. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Separate conversion success from geometric sufficiency. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 48: Wrong kernel load order

Source situation. Two kernels hold overlapping data. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Claiming a unique answer without recording which was applied. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect kernel load order and segment priority. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Document reproducible configuration. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 49: Example synthetic LID

Source situation. A tutorial invents urn:nasa:pds:example for demonstration. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Citing it as a real archival source. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check registry or PDS citation tool. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Label fictional identifiers as illustrative. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 50: Invalid schema namespace

Source situation. A translated XML fragment has locally translated tag names. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Treating it as valid PDS4 source. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Validate against proper schemas. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Keep XML syntax and tags unchanged. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 51: Human note inside code

Source situation. A comment explains an instrument choice. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Automatically translating the entire executable file. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Identify permitted translation scope. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Translate documentation externally or in approved comment fields. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 52: Version of dictionary

Source situation. The data dictionary name is right but version differs. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Applying later definitions indiscriminately. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read model version and release notes. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Tie explanations to the applicable specification. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 53: LID versus DOI

Source situation. An article contains an LID and links to DOI search. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Presenting the URN as a DOI. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check identifier registry. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Use each identifier by its own semantics. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 54: Reference is external

Source situation. A label links to a journal article. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Reporting that paper as embedded data. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect external reference. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Separate supporting literature from archive files. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 55: Incomplete documentation

Source situation. An instrument guide omits a field definition. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Making up a confident translation. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check local dictionary or data provider. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Flag unresolved meaning instead of guessing. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 56: Merged glossary entries

Source situation. The same English word appears with two different technical definitions. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Using one target word mechanically everywhere. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Compare contexts and source authorities. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Split term entries by concept and scope. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 57: Localized URL path

Source situation. A translated guide changes the URL for a live data service. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Breaking user access. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Test exact links. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Keep operational URLs and API paths intact. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 58: Missing calibration reference

Source situation. A derived result lists a calibration product that is unavailable. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Inventing a plausible calibration method. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect references and release notices. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. State the missing dependency. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 59: Claim about data completeness

Source situation. A release covers only some mission phases. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling it the complete mission record. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read coverage and inventory. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Report the documented subset. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 60: False certainty about precision

Source situation. A table prints many decimal places. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Writing that the result is known with corresponding accuracy. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check uncertainty and significant-figure justification. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Do not confuse number formatting with epistemic certainty. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 61: Citation without version

Source situation. An article cites a product title only. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Making verification fragile when labels change. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Resolve LIDVID and registered citation. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Add exact identifiers where appropriate. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 62: Translation of science caveat

Source situation. A note says processing is experimental. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Removing the caveat for reader comfort. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Compare source and target qualifications. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Preserve caution while clarifying the method. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 63: A coordinate in the wrong frame

Source situation. A source vector is in J2000 but a chart says body-fixed. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Assuming the tuple itself proves location. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Review frame transformation and epoch. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. State original frame and conversion requirements. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 64: Missing software version

Source situation. A derived dataset references a pipeline without release identifier. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Claiming reproducibility is complete. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Inspect software history. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Flag version gap and limit the claim. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 65: A label passes XML validation

Source situation. A file is syntactically valid but contains wrong narrative meaning. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Using schema success as proof of translation accuracy. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Perform human technical review. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Treat structural and semantic quality tests as independent. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 66: A target-language summary shortens caveats

Source situation. A public-facing caption compresses three limitations into none. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Replacing method claims with certainty. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Read source limitations and risk. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Retain essential restrictions even in concise prose. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 67: An instrument field of view

Source situation. A camera FOV is defined in the IK. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Describing it as visible terrain in every image. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check geometry and pointing. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Explain potential coverage and actual scene footprint separately. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 68: Body orientation at epoch

Source situation. A result requires body orientation at a chosen time. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Presenting longitude as independent of model and epoch. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Review PCK and frame configuration. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Name assumptions for reproducible conversion. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 69: PDS search result versus data

Source situation. A search page returns collection metadata. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Calling the search snippet the full evidence. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Open the actual labels and files. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Use discovery tools to locate, not replace, records. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 70: A single parent bundle DOI

Source situation. A collection has no separate DOI. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Inventing a collection DOI. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Consult PDS citation guidance. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Cite the parent bundle where recommended. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 71: A mislabeled public infographic

Source situation. A multilingual infographic says all image colors are true color. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Masking palette transformations. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Check rendering and source channels. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. State what colors encode rather than what eyes would see. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Diagnostic 72: A second-language review

Source situation. An expert approves fluent wording but has not checked codes. This is a deliberately illustrative scenario, not a quotation from a particular mission archive. The reader must determine whether the sentence describes a technical class, a measured result, a computation, a catalogue relationship or a claim about evidence. Those categories require different translation decisions.

Plausible but false target reading. Assuming language sign-off equals data sign-off. The problem is not necessarily bad grammar. The target-language sentence could sound entirely natural to an intelligent reader, which is precisely why formal source checking matters. A smooth wording that supplies missing certainty or erases a qualifier must be treated as a mistranslation even when the terms are otherwise familiar.

Diagnostic evidence. Run independent token and technical review. Ask which identifier, data dictionary entry, kernel configuration, processing note or source field actually determines the answer. Do not decide by a nearest dictionary synonym or an unrelated example found elsewhere on the internet. State the location of the evidence in the translation worksheet so another reviewer can reproduce the judgment.

Corrected translation strategy. Record each reviewer scope and unresolved issue. The corrected wording should be fluent but appropriately narrow. It must distinguish what the source explicitly records from what a human infers. If exact code, uncertainty or version information is needed, retain it. If a dependency is unavailable, report that limitation rather than completing the story from general scientific knowledge.

Transfer workshops: how this method carries into related translation problems

Workshop 1: Archive discovery interfaces

Localise human search hints and filters while keeping the underlying API fields, product identifiers and controlled parameters intact. Test a translated query against actual result records. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

To deepen the exercise, deliberately introduce one false friend, one changed number or identifier, and one lost qualification into a trial translation; then recover each error with a different check. A lexical glossary catches word choice, an exact-token comparison catches identity changes, and source-to-claim verification catches inferential overreach. All three are needed because none reliably replaces the others.

Workshop 2: Scientific visualisations

Translate captions and legends but identify whether color encodes radiance, class, uncertainty, altitude or a display palette. Check that readers can reconstruct the same visual claim. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 3: Spacecraft operations explanations

Use technical review to distinguish command sequence, telemetry, observation plan and post-processed science product. Avoid presenting archival data as live operational directions. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 4: Educational mission pages

Use plain language to explain instruments, targets, geometry and uncertainty without changing scientific conditions. Route readers to source data for verification. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 5: Research paper methods sections

Preserve method names, kernel sets, correction options, uncertainties and date ranges. Translate hedging and statistics without overstating results. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 6: Cross-agency archive comparisons

Do not assume an ESA, JAXA or NASA label uses the same versioning and metadata convention simply because similar words appear. Identify each archive authority. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 7: Mission press releases

Protect observed-versus-inferred distinctions, chronology and numerical claims. A release narrative is not a substitute for a calibrated dataset. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 8: Data citation and reproducibility

Record which citable version and which computing configuration supports the published result. Translation should strengthen, never conceal, the evidence trail. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 9: Multilingual help documentation

Keep command syntax, paths, variables, sample code and immutable keys stable. Translate instructions outside the operational syntax. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 10: Scientific uncertainty communication

Preserve probability, conditional statements, margins and instrument limits. Simplification should reduce unnecessary language complexity, not remove evidential constraints. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 11: Terminology database maintenance

Maintain concept IDs, source definitions, language variants and approval decisions. Do not let one convenient target word absorb distinct source concepts. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 12: Quality assurance for AI translation

Treat automated drafts as proposals; test identifiers, numeric fidelity, scope and evidential claims. A model’s fluency is not evidence that it consulted a kernel. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 13: Project handovers

Provide a list of frozen tokens, glossary exceptions, source versions and remaining questions so the next translator can continue without reinventing judgments. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 14: Public data portals

Distinguish what the portal indexes from what it actually hosts and describes. Keep discovery search results separate from citable archived products. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 15: Historical mission data

A valid older data model or processing pipeline may differ from current tools. Describe the archived historical state before proposing modern reinterpretation. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 16: Planetary maps and atlases

Carry body name, frame, projection, longitude direction, latitude definition and datum together; do not translate coordinates as if they were placeless numbers. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 17: Time-sensitive event summaries

Preserve the event represented by each timestamp: observation start, downlink, ground receipt, processing, release, or computed epoch. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 18: Software documentation and notebooks

Retain case-sensitive API parameters, function names and execution cells; localise explanations, warnings and narrative results with technical checks. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 19: Peer-review response letters

Translate questions, methodological qualifications and author commitments without turning proposals into completed corrections. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 20: Digital preservation deposits

Preserve bit-level integrity of immutable science assets and provide target-language documentation as separately versioned explanatory material. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 21: Citizen-science descriptions

Teach readers what a displayed image or detection actually represents. Do not promise that visual recognition alone verifies an archived scientific category. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 22: Museum displays of planetary objects

Translate interpretive labels and provenance, but distinguish an image product, a sample, a digital model and an artist’s conception. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 23: Robotic sample-return archives

Maintain relations among sample IDs, observation products, instruments, procedures and laboratory documentation without confusing sample custody with image acquisition. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

Workshop 24: Cross-language collaboration

Define who has authority over terminology, computations, scientific caveats and publication sign-off. Translation quality depends on a clear division of responsibility. The assignment is to write a three-sentence bilingual explanation, record the preserved technical tokens, identify the original evidence and ask a separate reviewer to reconstruct the intended distinction. If the reviewer needs undocumented assumptions, the explanation remains provisional.

A practical translation QA rubric

Identity integrity

Pass condition: Every LID, VID, LIDVID, DOI, registered name, numeric code, link and filename is preserved or explicitly explained as non-authoritative display text. Failure signal: Fail if a reader cannot locate exactly the referenced original object. Document a specific example of a pass and a failure with the page or record consulted. A numerical quality score is useful only after these categorical defects have been investigated; passing style checks does not compensate for an identity error.

Structural integrity

Pass condition: XML tags, namespaces, attributes, types and machine-readable controlled values remain untouched in protected source material. Failure signal: Fail if translation corrupts parsing or introduces unofficial schema terms. Document a specific example of a pass and a failure with the page or record consulted. A numerical quality score is useful only after these categorical defects have been investigated; passing style checks does not compensate for an identity error.

Numerical integrity

Pass condition: Numbers, units, sign, precision, axis order, scale, offset, special constants and confidence statements preserve source meaning. Failure signal: Fail if the same textual claim leads to a different physical value without a documented conversion. Document a specific example of a pass and a failure with the page or record consulted. A numerical quality score is useful only after these categorical defects have been investigated; passing style checks does not compensate for an identity error.

Temporal integrity

Pass condition: Observation epochs, time scales, clock partitions, UTC claims, release dates and kernel time context are differentiated. Failure signal: Fail if time systems or events are conflated. Document a specific example of a pass and a failure with the page or record consulted. A numerical quality score is useful only after these categorical defects have been investigated; passing style checks does not compensate for an identity error.

Geometric integrity

Pass condition: Observer, target, reference frame, frame center, kernel set, corrections and coverage remain distinguishable. Failure signal: Fail if target prose points to different geometry than the source. Document a specific example of a pass and a failure with the page or record consulted. A numerical quality score is useful only after these categorical defects have been investigated; passing style checks does not compensate for an identity error.

Scientific integrity

Pass condition: Processing level, provenance, calibration, uncertainty and source limitations remain recoverable. Failure signal: Fail if a provisional or derived result is presented as direct or final evidence. Document a specific example of a pass and a failure with the page or record consulted. A numerical quality score is useful only after these categorical defects have been investigated; passing style checks does not compensate for an identity error.

Linguistic usability

Pass condition: The target is grammatical, clear, appropriate to audience and consistent with a controlled glossary. Failure signal: Fail if technical precision is preserved only in a sentence the reader cannot understand. Document a specific example of a pass and a failure with the page or record consulted. A numerical quality score is useful only after these categorical defects have been investigated; passing style checks does not compensate for an identity error.

Reproducible review

Pass condition: A second reviewer can find the exact standard or archive record supporting each consequential statement. Failure signal: Fail when authority is attributed vaguely or source ambiguities disappear. Document a specific example of a pass and a failure with the page or record consulted. A numerical quality score is useful only after these categorical defects have been investigated; passing style checks does not compensate for an identity error.

Common questions about PDS4 and SPICE translation

Can I translate a PDS4 XML file directly?

Translate human-facing descriptions only when your project and archive rules permit; do not translate schema tags, namespaces, identifiers, enumerated values or other operational fields. The safe default is a separate translation of explanatory material.

Apply the same source-to-target audit: first locate the claim and its relevant identifier, then decide which words may change, then verify that the target-language reader can recover the intended object and restriction. If a correction would change a number, identifier, source document or computational setting, that correction belongs in an explicitly authorised data process, not in a silent language edit.

What is the difference between PDS4 and SPICE?

PDS4 is an archive information model and representation framework; SPICE is a system for geometry, time, and related calculations supported by kernels. They are related in scientific use but not synonyms.

Is a label the same as its data?

No. The label describes what a product contains and how it is represented. A table, image or spectrum is not identical to the XML description that makes it intelligible.

Can an LID be translated?

No. Keep the identifier string exactly. Provide a translated explanatory title beside it when useful.

What is LIDVID?

The combination of a logical identifier and version identifier, generally joined with a double colon, identifies a specific PDS4 product version.

Do all products have DOIs?

Do not assume so. Use the PDS citation and DOI guidance to determine the appropriate citable bundle, collection or document.

What is an SPK file?

It contains ephemeris data used in positions and related computations. It is not a generic synonym for all mission metadata.

What is a CK file?

A C-kernel supplies pointing or attitude information under a mission-specific context, not the spacecraft trajectory itself.

What is an FK file?

A frame kernel supplies reference-frame definitions and relationships; its names and IDs must remain computationally exact.

What is an IK file?

An instrument kernel gives instrument parameters and geometric characteristics relevant to an instrument model.

What is an SCLK file?

It supports spacecraft clock interpretation and conversions, which cannot be assumed equivalent to ordinary UTC timestamps.

What is an LSK file?

It provides leap-second information used in SPICE time conversions; it does not by itself compute instrument pointing.

What is a PCK file?

It contains planetary constants and orientation information, with exact content depending on its type and source.

What does a meta-kernel do?

It identifies a set of kernels to load. The included paths and kernel versions are part of a reproducible computational setup.

Why does reference frame matter?

A coordinate vector is meaningful only relative to defined axes, an origin and, for time-dependent frames, a relevant epoch.

Can I translate J2000 as January 2000?

Not mechanically. J2000 may name a frame or epoch-related convention; its role must be established from context.

What is the difference between target and observer?

They are roles in a geometric relation. Swapping them changes the expressed direction or result.

Can latitude and longitude be left without qualifiers?

Only if the context already resolves body, reference, direction and convention. For planetary bodies, preserve planetocentric or planetographic qualifiers where specified.

Is a raw image the same as a calibrated image?

No. The calibrated product may apply documented transformations to detector measurements; its scientific claims and provenance differ.

Does schema-valid XML mean the translation is scientifically correct?

No. Structural validity does not prove correct interpretation of units, geometry, processing or uncertainty.

How should I handle a missing calibration file?

Report the missing dependency and avoid describing unsupported calibrated values as verified.

How should I translate a quality flag?

Use the field’s actual controlled definition. Never infer that a numeric code means good, bad or missing based on intuition.

Can AI translate instrument labels safely?

AI can help draft descriptions, but exact-token checks, subject-matter verification and source authority are still essential.

What if the source itself is unclear?

Log the ambiguity and request clarification from the data owner or authoritative documentation. Do not silently resolve uncertain science in the target language.

How do I cite a planetary archive?

Follow current PDS citation guidance, including appropriate LIDs, versions and registered DOIs where they exist.

What is a science-data dictionary?

It defines domain-specific meanings, constraints and values for metadata fields; terminology decisions should follow the applicable dictionary.

Why preserve English acronyms?

Technical acronyms like SPK, PDS4 and LIDVID often denote defined systems or syntax. Translate their explanations rather than altering the stable token.

What if target readers need simpler prose?

Reduce grammatical complexity and define unfamiliar concepts, while retaining measurement conditions, uncertainty, identifiers and evidential limits.

Does a product title have to stay in English?

Human-facing titles may have translated display forms where appropriate, but product identity and formal archived values must be distinguished and kept intact.

How should I handle version updates?

Recheck the new product version, documents and definitions. Treat the translation as versioned explanatory content and record what changed.

Can I turn a binary kernel into translated text?

No. Translate documentation about the binary file, not its binary payload. Changing bytes can corrupt scientific meaning.

What counts as successful final review?

Independent checks must show correct language, correct referent, unchanged tokens, correct time and geometry assumptions, accurate scientific status and reproducible citations.

Should all scientific terms have one permanent target-language word?

No. Stable concepts need stable approved entries, but a word can have several technically distinct senses across disciplines or contexts.

Where can I learn the general art of translation?

Use the Master Art of Translation root for meaning, equivalence, source reading, revision and localisation. This specialist child teaches preservation of planetary archive semantics.

Where do I study vocabulary itself?

Use the Vocabulary Learning Hub for word meaning, retrieval and precision. Return here when the problem is preserving a technical concept across languages.

Where do I study English grammar and comprehension?

Use How English Works for English structure and meaning inside the language. Use this page for the cross-language transport problem.

Is it appropriate to use this guide for mission operations?

No. This is educational translation guidance, not authoritative flight operations, navigation or safety-critical software guidance.

What does not translating mean here?

It means freezing identifiers, data and source syntax while translating explanations around them. Accurate multilingual communication can require intentional non-translation.

Why do the examples avoid real mission values?

Illustrative scenarios teach diagnostic structure without claiming that a fictional number, code or record exists in a public archive.

Can I publish translated science interpretations as official NASA text?

Not without appropriate authorization. Attribute sources accurately and distinguish your translated educational interpretation from the agency’s official publication.

Four-week implementation plan

Week 1: source-reading competence

Read the PDS4 Concepts and Small Bodies Node introductions. Locate one genuine bundle, collection and product, classify their labels, and build a ten-entry glossary. Practise identifying protected tokens without translating content.

For each session, preserve the source excerpt, your draft, the technical authority you checked, the revision you made and the remaining question. The final assessment is practical: a reader should be able to identify the correct archival product and avoid at least three common inference errors without needing access to the translator’s private reasoning.

Week 2: geometry and time competence

Read the NAIF SPICE overview and relevant frames/kernel documentation. Build a concept map linking SPK, CK, PCK, FK, IK, SCLK, LSK, frame, target and observer. Explain each relation in natural target-language prose.

Week 3: controlled translation practice

Translate a short document passage or label description. Annotate every identifier, unit, qualifier, processing status and time reference. Perform a second pass focused on independent reconstruction and evidence.

Week 4: independent verification and release

Ask a target-language science reviewer to locate each referenced object, explain the geometry assumptions and identify limits. Correct all unresolved issues, freeze the translation and publish with versioned source links.

Final audit: the meaning-preservation contract

Every translation of planetary mission archive information must meet the following contract. The source is not silently edited. Product identity and version remain discoverable. XML syntax and enumerations remain exact. Data values and units do not drift. Frame and time assumptions are named whenever a physical claim depends on them. Corrections and uncertainty remain visible. A reader can trace a technical statement to the original product, standards authority or documented computation. And the target-language prose reads as natural explanation rather than a word-by-word substitute for structure that belongs in code.

The most damaging failure is not an obvious mistranslation. It is a fluent explanation that has changed the object of an observation, the meaning of a number or the conditions under which a conclusion holds. When fluent prose conflicts with a checked identifier, value or provenance record, the evidence controls the editorial decision. When the evidence is incomplete, the responsible answer is a visible gap, not an invented completion.

Next routes inside the translation architecture

Return to Master Art of Translation | The Complete System for Moving Meaning Between Languages for the general systems of source analysis, equivalence, terminology, revision and quality assurance. The translation root owns that broad teaching method; this child owns the PDS4 and SPICE meaning-transfer problem. For word acquisition and lexical precision, visit the protected Vocabulary Learning Hub. For English grammar, comprehension and communication inside English, visit the protected How English Works V1.1 branch. These links are outward learning routes, not requests to rewrite or retitle those existing owners.

For official source documents, use the linked NASA PDS4 and NAIF references above. A mission’s applicable documentation always overrides a generic teaching example. This article does not provide computed ephemerides, validate particular science products, or substitute for a mission’s science or software review.

One-sentence conclusion: Translate the explanation; preserve the identifier, the data, the time, the frame, the method, the uncertainty and the evidence trail. That is the master art of translating a planetary archive without changing the planet it describes.