Skip to content

Expand Policy Comparison Tool to Support Calculation-Level Diff Across Standards #5563

@prernaadev01

Description

@prernaadev01

Problem description

The existing policy comparison (diff) feature compares Guardian policies at a high level, including schemas and workflow components. This ticket proposes an enhancement to extend the diff tool to support calculation-level comparisons, allowing users to compare how calculations are implemented across policies while excluding non-calculation components.
This is especially important for methodologies that are accepted by multiple Standards, such as AMS-III.F, where:
The calculation rules are derived from the same methodology document
But Project Description (PD) and Monitoring Report (MR) templates differ by Standard (e.g., Verra vs Gold Standard)
The feature should enable reviewers to confirm that calculation logic and required inputs are equivalent, even when schema structure and document templates differ.

Requirements

  • Enable policy comparison focused only on calculation components, including:
    - Calculation formulas and logic
    - Parameters and variables used in calculations
    - Input dependencies required for calculation execution
  • Explicitly exclude from the diff:
    - Schema components not used in calculations
    - Policy workflow blocks
    - PD / MR template structure
  • Support comparison of policies developed for different Standards (e.g., Verra vs Gold Standard)
  • Highlight:
    - Differences in calculation logic or formulas
    - Differences in required calculation inputs
    - Missing or extra parameters impacting calculation outcomes
    Example Use Case
  • Compare AMS-III.F (Verra) policy vs AMS-III.F (Gold Standard) policy
  • Ignore PD/MR template differences
  • Validate that:
    - Both policies collect the same calculation-relevant inputs

Definition of done

  • Users can run a policy comparison limited to calculation components only
  • Output clearly identifies:
    - Matching calculation logic
    - Meaningful differences affecting calculations
  • Schema and workflow differences unrelated to calculations are not surfaced

Acceptance criteria

As mentioned in DOD

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Epic.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions