Git Object Type Before Inspection Sequence

Inputs: [repository path], [object identifier], [expected object kind]. Use read-only Git object inspection to determine whether an identifier resolves to a commit, tree, blob or tag before choosing how to display it. Explain type and size checks; bound output and avoid printing large blobs or credentials. Do not execute blob content, fetch objects, alter refs or assume a tag object is a commit. Produce a 12-second object-inspection diagram revealing type first and bounded content second. Adapt the presentation to [audience] and [tone]. Check the defining task detail against the inputs before finishing.

Confirm required reference images and timing inputs are present before generating. Keep objects, identities, spatial relationships and light direction consistent. Render the clip when video generation is supported; otherwise supply a timed shot list, reference checklist and generation-ready prompt, labeled as a production plan. Do not claim rendered output without an actual file. Check the opening, transition and final frame against the stated counts and geometry.