When handing the translation to a colleague, which checklist should be included in the zip file?

This paper uses synthetic samples to demonstrate the processing method. The code has been verified using examples in an isolated environment; this does not guarantee effectiveness for all real files or products. Before processing important files, please retain the original copies and verify them against the boundaries and acceptance criteria specified in the text. The delivery package contains only a few translation files, and the colleague does not know which source document they correspond to, what the target language is, or which pages require review. Adding a brief machine-readable checklist is often more reliable than sending ten additional explanations in the chat window. lists facts, without writing vague evaluations “Quality is very good” cannot be used for automated acceptance; input-output summaries, target language, task version, and unresolved issues can be. Record machine checks separately from human proofreading to avoid a single, generic passed: true is mistakenly interpreted as meaning that everything is correct. creates and reviews the contract delivery list import hashlib import json def sha(raw): return hashlib.sha256(raw).hexdigest() source = b"synthetic source" output = b"synthetic translated output" manifest = { "manifest_version": 1, "job_id": "demo-job-001", "source_sha256": sha(source), "output_sha256": sha(output), "target_language": "en", "policy_version": "demo-v1", "checks": {"file_present": True, "human_review": "pending"}, "open_issues": ["Review terminology on the example cover"] } encoded = json.dumps(manifest, ensure_ascii=False, sort_keys=True) restored = json.loads(encoded) assert restored["source_sha256"] == sha(source) assert restored["output_sha256"] == sha(output) assert restored["checks"]["human_review"] == "pending" assert restored["output_sha256"] != sha(output + b"changed") assert not {"token", "password", "api_key"} & restored.keys() The last assertion only checks a few top-level keys; it is not a general-purpose secret scanner. Before actual deployment, a strict field whitelist should be used, and nested structures and text comments should be reviewed—do not include the entire request object in the checklist as-is. How does the checklist serve the recipient? field What can the recipient do? should not infer output summary detected that the file has been modified file semantics must be correct target language routes to the appropriate reviewer All paragraphs have been translated rule version reproduction of processing conditions The results of the new and old versions must be identical Unresolved issues focuses on checking the position is not listed, which means there is no issue The list and the documents shall be versioned together If the translation is updated, the checklist must also be regenerated. Placing the new version of the file alongside the old summary can make the correct document appear to have been tampered with. One can use an immutable directory or version number for a single delivery to prevent recipients from downloading a mixed set of new and old files. makes the translation results easier to take over from OmniDoc (product entry point) After downloading the translation, the team can generate this checklist on their own delivery layer, documenting the source file, language, and proofreading status. It does not require the platform to adopt any specific internal technology; rather, it supplements the necessary collaboration context outside the files themselves, making the deliverables easier to transfer and review. Reference: Python json 。 - 1 -