Git Object Type Before Inspection Visual

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 four-kind object diagram keeping annotated tag, commit, tree and blob as separate nodes. Adapt the presentation to [audience] and [tone]. Check the defining task detail against the inputs before finishing.

Use the attached references only for the specified visual attributes. If a required reference is missing, request it before generation. Produce one finished image with a deliberate focal point, consistent geometry and clean margins. Keep any exact wording on a separate editable label layer or leave its area blank. Do not invent evidence or present an illustration as documentary proof.