expose the "comment" an approver made inside the Approval Policy payload

Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.

Thanks for raising this—really valuable discussion.

To clarify, the reason field entered during approval isn’t currently passed into policy evaluation. That’s not a deliberate design exclusion, but we’ve also been cautious about introducing it. Here’s why:

That field is unstructured. It’s free-text, unauthenticated, and unconstrained. If we allow policies to depend on its content, we introduce a subtle but serious risk: letting arbitrary human input influence policy logic.

It’s easy to imagine policies that check for certain phrases (“risk accepted”, “urgent fix”)—but those checks would be fragile, unenforceable, and invisible to review. The decision logic would live in human convention, not in code. That’s the concern.

We want to make sure we don’t accidentally create a second, implicit policy system—one where behavior depends on who writes what into a text box.

If there’s a real need to evaluate structured human input as part of an approval, that’s a different conversation—and probably a different mechanism.

Would love to understand more about the use case if this is a blocker or a pattern you’re relying on.