Good point that a product name is not enough to identify the security model; a fork can change the practical answer. For a parts inventory that feeds purchasing or production, I’d add a reconciliation check tying each stock adjustment to a role, API client, reason, and source event (receipt, issue, or count). Then test a disabled API user and a normal user against both read and write paths, and confirm the audit trail preserves the before/after quantity. That makes the permission review measurable against the workflow, not just the account list.