guardian
guardian copied to clipboard
hashgraph
Emissions Reduction/Removals (ERRs)Calculation Pre-Calculator in Guardian
Problem description
The current process does not make it clear to stakeholders the estimated ERR's in Guardian
Requirements
Based on input data a estimated ERRs should be able to be queried in project development.
Definition of done
ER calculation should be visible in the Guardian in real time based on input data by all parties
Acceptance criteria
The ERR calculation should be consistent with defined formula by the methodology/registry from baseline through issuance.
@dubgeis Could you please clarify - what is the context of this requirement, is it for policy development or is it the situation where policy is running and when project data is being submitted users can preview some of the results for the data they are providing?
If it's the former there is a 'dry-run' function which allows to view the results without actually executing the policy. Is what required here a preview for a specific formula rather than the end-to-end?
If it's for the latter context, I think this requirement can be re-phrased as 'dry-run for projects' on published policies. Is this an accurate understanding?
This should work similar to a Nerd Wallet like quick calculator, effectively for key inputs (1-2 levels lower in the schema tree) to manually bypass all data entry to determine projected credits. For example in a forestry (ARR/IFM/REDD+) methodology a project proponent may want to determine their carbon yield with key assumptions (not manually entering each data point for a monitoring report. This could bypass to an output of calculations that feed the higher order methodology formula leading to a projected credit issuance. @prernaadev01
Ideally it could use a similar interface for bottom up attributes to allow PP to click into a schema tree UI and determine which level of detail would enable a pre-issuance calculator for a published methodology. Instead of creating an attribute (tag) for a production scenario, this would determine an output in dry run. For clarity this feature would be on published policies in dry run, it should be enabled to allow project proponents to save and ideally export this to add more details later (maybe in excel if that's easily feasible).