DCC Pipeline Version and USD Composition Guide

Incremental Save - The practical question around Incremental Save is what evidence would make another reviewer agree with the same decision. Incremental Save (保存增量版本 / 増分保存) is useful in a brief only when it points to an inspectable source state. Put the term beside the file, target output, and owner who can verify it. The translation is therefore tied to evidence, not to an isolated glossary row.

External Link - Treat External Link as a production checkpoint: it should narrow the review, not decorate the page with another synonym. External Link (外部链接 / 外部リンク) is a dependency risk. Check whether the file is copied, linked, overridden, or resolved through a versioned reference, then save the path or layer that the receiving machine will load. That keeps the article searchable while still giving pipeline TD, producer, or publishing owner something concrete to approve.

Composition Arc - Composition Arc should be read through USD, not as a loose label in a translation sheet. Composition Arc (组合弧 / コンポジションアーク) is a pipeline contract. Record the version, layer or hook that produced the result and the rollback point that keeps the handoff recoverable. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.

Reference Arc - When 引用弧 or リファレンスアーク appears in a review note, the English term still needs the file state beside it. Reference Arc (引用弧 / リファレンスアーク) is a dependency risk. Check whether the file is copied, linked, overridden, or resolved through a versioned reference, then save the path or layer that the receiving machine will load. If that proof cannot be attached, the term should remain in review rather than be treated as covered.

Session Layer - Session Layer becomes useful only when the reviewer can point to the part of versioned asset, USD composition, reference package, or publish event that it changes. Session Layer (会话层 / セッションレイヤー) is a dependency risk. Check whether the file is copied, linked, overridden, or resolved through a versioned reference, then save the path or layer that the receiving machine will load. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.

Work Version - For a vendor-facing brief, Work Version is the anchor term and the localized labels explain the same inspected state. Work Version (工作版本 / 作業バージョン) is a pipeline contract. Record the version, layer or hook that produced the result and the rollback point that keeps the handoff recoverable. The translation is therefore tied to evidence, not to an isolated glossary row.

Check Out - The practical question around Check Out is what evidence would make another reviewer agree with the same decision. Check Out (签出 / チェックアウト) should be tied to the exact part of versioned asset, USD composition, reference package, or publish event that it changes. Record the setting, reviewer, and proof artifact so the term is not reduced to a loose label. That keeps the article searchable while still giving pipeline TD, producer, or publishing owner something concrete to approve.

Environment Variable - Treat Environment Variable as a production checkpoint: it should narrow the review, not decorate the page with another synonym. Environment Variable (环境变量 / 環境変数) is a pipeline contract. Record the version, layer or hook that produced the result and the rollback point that keeps the handoff recoverable. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.