Git Submodule

Outcome: Use Git Submodule to release or recover the change safely, with a clear record. User context: An app repository uses firmware kept in its own repository. The parent project records one reviewed firmware commit and setup steps load it. Pulling the submodule's newest branch does not update the parent pointer by itself. Delivery concept or operation: Git Submodule. Why it fits: Use this term when one repository must lock another independently managed repository to an exact commit. Do not use it when: Avoid submodules when a released package or copied snapshot gives simpler ownership and updates. Delivery requirements: Name the code repository and target. List preconditions, changes, review and CI checks, conflict and data-loss risks, release order, and the rollback or recovery command. Repository safeguards: Keep unpublished work and a clear history. Do not run destructive steps without an explicit backup. Check the exact code diff and remote target before publishing. Acceptance criteria: Review the intended diff and pass all required checks. Keep the target version traceable. Practice failure recovery and keep published history clear. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Repository, branch, team activity, release environment, approval owner, protected checks, and rollback target.