What a merged pull request actually proves.

Keep the states separate

A session can be associated with a commit. A commit can be part of a pull request. A pull request can be merged. Production delivery requires additional evidence that the released revision reached an approved environment successfully.

The name of a default branch cannot establish that final step. Neither can an assumption that every merge is deployed immediately.

Inspect how the association was made

An observed repository and commit identity is different from an inference based on timing or a worktree. Both may help explain activity, but their methods and uncertainty need to remain visible.

Concurrent agents, branch changes, and rewritten history can introduce ambiguity. When an association cannot be resolved confidently, keeping it unresolved is more honest than filling the gap.

Do not erase work without a pull request

Incident response, code review, research, and experiments may be valuable without producing merged code. Open work may simply need more time. A delivery review should preserve those distinctions.

Classifying all unmerged consumption as waste would replace the uncertainty with an unsupported conclusion.

Business value needs its own evidence

A confirmed deployment is a useful signal that associated work shipped. It does not establish customer impact or return on expenditure. The team can explain why the work mattered.

Symentrio’s proposed chain is usage and cost, repository and branch, commits, merge into main, then observed deployment. Business value is a human judgment informed by that evidence.

A worked example to inspect

Synthetic alternative: two concurrent sessions share a repository and time window, but no commit identity was captured. Keep the session-to-commit link unresolved. A later merged PR does not repair that missing evidence or establish a business outcome.

Use the related worksheet or checklist.

Method and sources

Symentrio product perspective. Independent finance and engineering review pending; original publication date not established.

• GitHub documentation: About deployments

The proposed spending-to-delivery evidence method

Related reading

• The bill is not the token count.
• A better AI budget review starts with a decision.