I don’t think this makes too much sense, when we require a service from a company we don’t ask for all the company internal receipts, we just receive the receipt of the service provided, which is already on the grant proposals, and the DAO as a customer accepts the budget or declines it. Of course, as a customer you can ask the reasoning for a budget to accept it or not, but as it’s said, this is already done before passing the proposal.
Is like if you go to repair your car, you are given a budget, you accept it, and then when you have to pay you ask for all the receipts of the car mechanic, rentals, materials, employees, … and if he doesn’t provide it, you don’t pay; It doesn’t make sense, right? Other matter is if the car is not repaired, in which case of course makes sense to don’t pay the service.
So, that is what I would just ask for, that the delivarables on the proposal are delivered and all preestablished conditions are met.
So, if someone thinks a proposal is not well justified, even accepted and with work delivered, what should be reveiwed is the acceptance process before enacting a grant (for example: Change threshold system to pass a proposal to the difference between YES and NO )
About being transaparents, well, we are as transparent as posible on our updates without entering in too many details to don’t make a TLDR text, others could make more text to make seem there is more work done, if someone is interested we can tell how many “git commits” we have in the code, how many hours and employees (except personal data that is not ours), how many pencils and office materials we bought, but this is optional on our side, we committed to deliver “something” in the accepted proposal, and that’s what is delivered.
In any case, if this proposal is accepted, I think it should never be retroactive, because the proposals are passed under established conditions, I don’t like if 1 part of a deal breaks an agreement between parts without the consent of the other part. It could work however for future proposals.