Problem description
Existing Policy design and creation process in Guardian presents a challenge for practical use:
- it is too "technical" for Environmental industry subject matter experts
- Guardian provides no guidance for policy authors who are required to proceed by 'trial and error' which is time consuming
- constructing policies with strict verification of datatypes is not possible, thus values inputted by users during policy execution can frequently be wrong
- complex use-cases where there are, for example, multiple tokens and/or multiple MRV generators present in the policy are not visualized appropriately both at the policy design stage and policy execution stages (trust chain etc)
Furthermore policy definition language is required to evolve further, adding new elements (blocks) and their properties to enable more complex rules and dependencies. This is likely to further complicate the process of creating a real-world level complexity policies, and thus restrict adoption of Guardian in production.
Requirements
-
Continue working on enhancing policy definition language to enable new capabilities in policies
-
Re-engineer policy creation workflow to simplify the tooling for non-programmer users potentially using such approaches as
- wizard-based workflow
- data definition enhancements in schemas enabling more precise specification of expected data formats
- support for new data types (like 'spatial' etc) which are useful specifically in the Environmental domain.
- syntax highlighting of JSON policy definition view
-
Add new reference UI tools that would simplify comprehension of policy and its execution results for complex use-cases such as those with multi-benefit projects with multiple tokens and multiple MRV sources
Definition of done
- New functionality implemented to enhance policy engine capabilities
- Policy creation workflow simplified
- New functionality is documented
- Backward compatibility with existing policies is maintained
Acceptance criteria
See DOD above
Problem description
Existing Policy design and creation process in Guardian presents a challenge for practical use:
Furthermore policy definition language is required to evolve further, adding new elements (blocks) and their properties to enable more complex rules and dependencies. This is likely to further complicate the process of creating a real-world level complexity policies, and thus restrict adoption of Guardian in production.
Requirements
Continue working on enhancing policy definition language to enable new capabilities in policies
Re-engineer policy creation workflow to simplify the tooling for non-programmer users potentially using such approaches as
Add new reference UI tools that would simplify comprehension of policy and its execution results for complex use-cases such as those with multi-benefit projects with multiple tokens and multiple MRV sources
Definition of done
Acceptance criteria
See DOD above