# Roadmap
FeatureRelease monthDevelop branch?Released?Release Version
Development of AMS-I.E and Mass Comparison on CookstoveJuly 2024YesYes2.27
Indexer APIJuly 2024YesYes2.27
Development of VMR0006July 2024YesYes2.27
Filtering data for blocks is stateful API, introduce stateless data filters for API usage.July 2024YesYes2.27
Auto-testing community submitted policiesOctober 2024YesYes3.0
Code audit: support and resolution of issuesOctober 2024YesYes3.0
GHG Scorecards ResearchOctober 2024YesYes3.0
Token action block to work with token templatesOctober 2024YesYes3.0
Different token IDs for different projects by the same policyOctober 2024YesYes3.0
Enhance MongoDB IntegrationOctober 2024YesYes3.0
Leverage the pre-built images as the default way to start Guardian locallyOctober 2024YesYes3.0
Global Carbon Council (GCC) GCCM001October 2024YesYes3.0
Default values for schema-defined fieldsOctober 2024YesYes3.0
Rationalize API and UI return error codesOctober 2024YesYes3.0
Simplify default SR schema to take out optional propertiesOctober 2024YesYes3.0
Guardian analytics: bottom-up data traceabilityOctober 2024YesYes3.0
API versioning and support/deprecation scheduleOctober 2024YesYes3.0
Data Parameterization and Conditional Review LogicOctober 2024YesYes3.0
Calculation logic for values in 'automatic fields' in schemasOctober 2024YesYes3.0
Verify and Fix the features that got affected by Mirror node changesOctober 2024YesYes3.0
Climate Action Reserve's U.S. Landfill ProtocolJanuary 2025YesYes3.1
Scope 3/PCF Referencing Demo (Methodology Breakdown)January 2025YesYes3.1
Development of AMS-I.CJanuary 2025YesYes3.1
API facilities to retrieve unique references (IDs) of results for API-triggered operationsJanuary 2025YesYes3.1
Guardian analytics: labels and top down data way pointsJanuary 2025YesYes3.1
Trustchain support for contract-based issuance and retirement implementationJanuary 2025YesYes3.1
GHGP Version 3January 2025YesYes3.1
Enhancements and Bugs of IndexerJanuary 2025YesYes3.1
Formula Linked Definitions & Schema Tree EnhancementJanuary 2025YesYes3.1
Dry-run policy execution 'savepoints' - restart policy dry-run from the list of 'saved' placesJanuary 2025YesYes3.1
Standardize UI on Angular Material, remove/replace PrimeNGJanuary 2025YesYes3.1
Enhancing Research on Indexer and Analytics Use CasesJanuary 2025YesYes3.1
Add policy support for more than one external data blockMay 2025YesYes3.2
Firing external event when minting process is finishedMay 2025YesYes3.2
Establish deprecation policy for architectural APIsMay 2025YesYes3.2
Cross-context (API+UI) refresh token invalidation (regression from v2.18.0)May 2025YesYes3.2
Business UseCase for Emissions Reduction/Removals (ERRs)Calculation Pre-Calculator in GuardianMay 2025YesYes3.2
Add capabilities to display complex geoJSON shapes superimposed on mapsMay 2025YesYes3.2
Weak Default configurationMay 2025YesYes3.2
System Logs Accessible by All RegistriesMay 2025YesYes3.2
Development of VM0042 v2.1: Improved Agricultural Land ManagementMay 2025YesYes3.2
Manual trigger of re-indexing for specific policy, SR, tokenMay 2025YesYes3.2
Article 6.4 Forms ResearchMay 2025YesYes3.2
Session Token in URLMay 2025YesYes3.2
Accessing a Guardian policy from a Guardian instance other than the publishing instanceMay 2025YesYes3.2
Exporting Project Data in CSV formatJuly 2025YesYes3.3
Missing Authentication between ServicesJuly 2025YesYes3.3
Server-Side Request Forgery (SSRF) in Request Data moduleJuly 2025YesYes3.3
No Password PolicyJuly 2025YesYes3.3
Development of VM0033July 2025YesYes3.3
Detailed Research on Indexer EnhancementsJuly 2025YesYes3.3
Guardian policy embedded code testing/debugging facility for Custom Logic, Calculate, etc blocksJuly 2025YesYes3.3
Substitute Google maps API in Guardian UI with an OSS alternativeJuly 2025YesYes3.3
Outdated Software/LibrariesJuly 2025YesYes3.3
Identifying, Implementing and Integrating 3rd Party data resourcesJuly 2025YesYes3.3
Authorization Headers Potentially Leaked through IPFS in Request Data ModuleJuly 2025YesYes3.3
Facilities to use specialist math tooling (such as R language) for calculations in Guardian Policies .July 2025YesYes3.3
Payload Shapefile IngestionAugust 2025YesYes3.4
Improvement in the error handling for excel schema exportsAugust 2025YesYes3.4
Dry-run savepoint[s] to survive exit and policy editingAugust 2025YesYes3.4
Locations Data Field enhancementAugust 2025YesYes3.4
SLA Ticket Import and Policy Publish Performance in GuardianAugust 2025YesYes3.4
Validation for project data submissionSeptember 2025YesYes3.4
Guardian Form UI ImprovementsSeptember 2025YesYes3.4
Add an option to hide some buttons in case the policy is discontinuedSeptember 2025YesYes3.4
Make testing easier for subflowsSeptember 2025YesYes3.4
Complex iterative review and approval workflows​October 2025YesYes3.4
Policy warningsOctober 2025YesYes3.4
Import Excel to check for duplicates by schema name​October 2025YesYes3.4
Project (Relayer) Account (ex:Project Developer or Accountable Impact Organization)October 2025YesYes3.4
Nested schemas for complex conditionsOctober 2025YesYes3.4
Need to implement best practices on Schema CycleOctober 2025YesYes3.4
Update Walkthroughs in DocumentationOctober 2025YesYes3.4
Schema deletion with child schemasOctober 2025YesYes3.4
Capability to retire tokens by serial numberOctober 2025YesYes3.4
Option to delete all schemas for a particular policy in Draft stage​October 2025YesYes3.4
Next phase of 'Tools' evolution in Guardian PoliciesNovember 2025YesYes3.5
Implementing Artifacts such as Schemas/Policies/tokens Deletion all at once​November 2025YesYes3.5
Graphical View of formula linked definitionsNovember 2025YesYes3.5
Capture/replay and compare data of published policiesNovember 2025YesYes3.5
Formula-linked definitions enhancements​November 2025YesYes3.5
Guardian as a multi-workflow engine for independent data streams​December 2025YesYes3.5
Tamper-resistant Policy and Module export/importDecember 2025YesYes3.5
Data Entry UpdatabilityDecember 2025YesYes3.5
Fine grained Policy workflow certification labels​January 2026YesYes3.5
Extend Policy definition language to include a Formula calculations block​January 2026YesYes3.5
Deterministic CompressionJanuary 2026YesYes3.5
Add API endpoint to generate example payloads matching UI auto-fill logicJanuary 2026YesYes3.5
Add Support for Synchronous Event ExecutionJanuary 2026YesYes3.5
Implement Form View for Image TagsJanuary 2026YesYes3.5
Improve schema version handlingJanuary 2026YesYes3.5
Enable the "Publish" button only when the policy version is correctJanuary 2026YesYes3.5
UI Ticket — Pop-Up Window Size Too Small for Data EntryFebruary 2026YesYes3.5
UI Ticket — Add Tables to Improve Data EntryFebruary 2026YesYes3.5
UI Ticket — ERR Table Display: No Ability to See Tables for Summarized InformationFebruary 2026YesYes3.5
Main Framework Schema Design for GHGP v3February 2026Yes
Improvements for Data Migration Tool – Progress Tracking & Large Load ReliabilityFebruary 2026Yes
UI Ticket — Add Navigation Panel to Jump Between SectionsFebruary 2026Yes
Redesign of the Hedera network configurationFebruary 2026Yes
Embed gitbook documentation assistant into GuardianFebruary 2026Yes
Disconnect functionality for Decentralized featureFebruary 2026Yes
Improving Naming Conventions of the Features in DocumentationMarch 2026
Guardian UI improvementsMarch 2026
API documentation improvementsMarch 2026
Guardian Policy Development for VM0047 (Afforestation, Reforestation, and Revegetation v1.1)March 2026
DR: policy state 'save points' capability to be restarted from for restore operationsMarch 2026
Revised documentation on Formula linked definitions featureMarch 2026
Initial Toolbox Schema Design for GHGP v3March 2026
Top-level (generic) API calls for common tasksApril 2026
Create Guardian UI terminology 'dictionary'April 2026
Review the list of Blocks documentationApril 2026
Add filter/search option in schemas with their IDApril 2026
Configurable rounding strategy for the token minting processApril 2026
feat: user managed credentials for external servicesApril 2026
Create external event for "token failed"April 2026
VM0049 Carbon Capture and Storage, v1.0*May 2026
Enhance diff and search to be less (ideally in-) sensitive to the order of schemas/fieldsMay 2026
feat: dry-run external servicesMay 2026
Not able to revert back after selecting a role in the policy workflow​May 2026
Impossible to change policy binding for schemasMay 2026
Creating and assigning sub schemasMay 2026
Disabling the option to rebind the policy in created schemaMay 2026
Manual input of additional data for inclusion into the VC documentMay 2026
Add the ability to create any type of user in production environment using Guardian UIMay 2026
Export Schema Tree and Tree Diagrams in editable UML format such as Plant UMLMay 2026
Use {cid} as a placeholder for IPFS_PUBLIC_GATEWAY environment variable instead of ${cid}May 2026
Support the Development of GHGP v3June 2026
Make the build process of docker images fasterJune 2026
Extend the Python libraries supported by GuardianJune 2026
Review the current list of supported Python librariesJune 2026
Granular global search/diff matching arbitrary policy block subtreesJune 2026
Multi-Factor Authentication Not SupportedJune 2026
Need a placeholder code to write expressions within Schema UI on importJune 2026
Confusing 'not working' button - grey it out until the action is possibleJune 2026
Refreshing of available filter state on Guardian (Potential Caching Issue)​June 2026
Add Worker Tasks to the permission modalJune 2026
Development of AMS-II.J.: Demand-side activities for efficient lighting technologies --- Version 8.0*June 2026
Duplicate validation during ImportJuly 2026
Support for Multi-Strata Schema Fields, Auto-Calculation Enhancements, and Improved Schema–UI IntegrationJuly 2026
UI/UX enhancementsJuly 2026
Testing and Piloting GHGP v3July 2026
Development of VM0050: Energy Efficiency and Fuel-Switch Measures in Cookstoves, v1.0*
Development of AMS-II.C: Demand-side energy efficiency activities for specific technologies*
Development of VM0045: Improved Forest Management Using Dynamic Matched Baselines from National Forest Inventories, v1.2*
Development of AR-ACM0003 : Afforestation and reforestation of lands except wetlands - Version 2.0*
Development of VM0051 : Improved Management in Rice Production Systems, v1.0*
Development of ACM0022: Alternative waste treatment processes --- Version 3.0*
Development of AMS-III.C.: Emission reductions by electric and hybrid vehicles --- Version 16.0*
Development of AMS-III.F.: Avoidance of methane emissions through controlled biological treatment of biomass --- Version 8.0*
Development of VM0008 Weatherization of Single Family and Multi-Family Buildings, v1.2*
Development of VM0043 CO2 Utilization in Concrete Production, v1.1*
Development of VM0041 Methodology for the Reduction of Enteric Methane Emissions from Ruminants through the Use of Feed Ingredients, v2.0*
Development of VM0044 Biochar Utilization in Soil and Non-Soil Applications, v1.2*
Development of ACM0008: Abatement of methane from coal mines --- Version 8.0*
Development of ACM0009: Fuel switching from coal or petroleum fuel to natural gas --- Version 5.0*
**Note: The above items marked as "\*"are subject to change.** {% tabs %} {% tab title="Upcoming Releases" %} **---February 2026---** **Improvements for Data Migration Tool – Progress Tracking & Large Load Reliability** Improved Progress Tracking: * Show real-time migration progress (e.g., 30/50 VCs migrated, with percentage). Recovery Path After Failure : * Implement the ability to resume migration from the last completed point after a failure. Large Dataset Reliability: * Optimize migration process to handle large datasets (20k+ VCs) without frequent failures. Referral Link: Documentation Link: **UI Ticket — Add Navigation Panel to Jump Between Sections** * A navigation panel should appear on the left or top, allowing users to jump to: * Major template sections Referral Link: **Redesign of the Hedera network configuration** The developer should be able to clearly set all configurations for the network used by Guardian. In particular, there should be four initial **base configurations**: 1. Mainnet 2. Testnet 3. Previewnet 4. Local Node The base configurations are applied using the default SDK configurations. No custom attributes or parameters have been applied yet. Please note the SDK uses the following names for the networks: `mainnet`, `testnet`, `previewnet`, `local-node` In addition to the base configuration, developers can set overriding parameters for each aspect of the network, such as consensus nodes, mirror nodes, ports, and API endpoints. These overriding configurations are applied on top of the initial choice. For example, if developers set "Testnet" and then specify an alternate list of mirror nodes, the current default list of mirror node servers provided by the Hiero SDK will be overridden by that configuration. Referral Link: Documentation Link: **Embed gitbook documentation assistant into Guardian** 1. Embed Guardian gitbook assistant into Guardian builds giving users instance access to Guardian knowledge base whenever they need it. See [Gitbook docs ](https://gitbook.com/docs/publishing-documentation/gitbook-ai-assistant/embedding)for instructions. 2. Ensure Guardian documentation is utilising new features and improvements delivered in the [November 2025 release](https://www.gitbook.com/blog/new-in-gitbook-november-2025). Referral Link: **Disconnect functionality for Decentralized feature** 1. UI Enhancements — Add Disconnect Button * A “Disconnect” button must be displayed for each connected public policy in the External Policies page. * Button visibility is role-based:\ \- Visible only to PP users.\ \- Not visible to SR or other user types. * The button should be placed near the existing policy card controls (e.g., near “Open” or “View Details”). 2. Initiation of Disconnect Request * When a PP clicks the “Disconnect” button: * A confirmation modal should appear (optional but recommended). * After confirmation, the system should:\ \- Create a Disconnect Request tied to the PP user, policy ID, and SR.\ \- Mark the policy’s status as “Disconnect Pending” for that user. * The PP should receive a visual acknowledgment that the request was submitted. 3. Disconnect requests must appear in the SR’s Requests / Approvals dashboard under a new category or the existing list. 4. Policy Disconnect Logic After SR Approval * Once the SR approves the disconnect request: * The system must remove the policy from the PP user’s:\ \- External policy list\ \- Access controls\ \- UI modules\ \- Policy-based dashboards or workflows * All temporary or cached policy artifacts tied to that PP must be deleted or unlinked. * The PP should no longer be able to access or view any part of that policy. * A success notification should be displayed to both PP and SR. Referral Link: Documentation Link: **---March 2026---** **Improving Naming Conventions of the Features in Documentation** * Evaluate current documentation and identify areas that are overly technical or unclear for business users. * Review naming conventions across UI, APIs, and documentation for consistency and business relevance. * Map out the “first-time user” journey from a business perspective and highlight pain points. * Recommend improved terminology and documentation structure that separates business concepts from technical details. * Provide a draft style guide for naming and terminology (business-facing vs. technical) Referral Link: **Guardian UI improvements** * of the retirement of the tokens. * Tools * Modules Introduce the usability enhancements to the UI: Referral Link: **API documentation improvements** 1. Improve clarity of API documentation throughout 2. Implement and document more descriptive error logs would significantly improve the debugging experience Referral Link: **Guardian Policy Development for VM0047 (Afforestation, Reforestation, and Revegetation v1.1)** * Build the full workflow following Verra’s process. * Add all required PD, monitoring, and verification templates. * Implement baseline and monitoring parameters for both approaches. * Ensure all user inputs map 1:1 to Project Hub for future transformation code. * Development of the methodology Referral Link: **DR: policy state 'save points' capability to be restarted from for restore operations** Introduce a new capability into Guardian policies to have 'restore points' at a particular stage of the policy execution, which would mark the point from which the execution of the policy can be restarted following the restore operation. The author of the policy would then be able to select an appropriate stage for restart by introducing a 'save state' block at the corresponding points, which for example could be: * just after project registration, at the beginning of the 'MRV receive' loop * submission of the new yearly emissions user report Referral Link: **Revised documentation on Formula linked definitions feature** Need to revise the existing documentation which would focus on VM0042 methodology showing * how this feature would be used * how the formulas can be configured * Adding screenshots of the formula configuration Referral Link: **---April 2026---** **Top-level (generic) API calls for common tasks** Propose and implement a set of 'top-level' API call for generic tasks such as finding an artifact, or messageID, or other information related to the policy. Referral Link: **Create Guardian UI terminology 'dictionary'** * Refactor Guardian UI to as much as possible 'externalise' words/phrases/text into a separate file or module which we can then automatically run through a syntax checker. * Design this in such a way that it would be possible in the future to introduce 'language' choice feature and display translated text from this file/module in the UI. (note: the actual implementation of this functionality is not required for this ticket, this to ensure that its **design** is compatible with this vision). * Introduce an automated syntax checker running on every build or merge (whatever is easier) Referral Link: **Review the list of Blocks documentation** 1. Review the current list of blocks in the documentation. 2. List out all the missing blocks, which are already present in Guardian but not in the documentation. 3. Create a detailed block documentation for the missing blocks. 4. Update the gitbook documentation on the missing ones. Referral Link: **Add filter/search option in schemas with their ID** It would be much easier to debug in this case if we have a filter/search options by schema ID so when looking at the error we dont have to open each schema and check if the schema ID matches with the one shown in the error. Referral Link: **Configurable rounding strategy for the token minting process** Developers can choose the rounding behavior for the token minting process when defining the policy. The **rounding** option can be set to: * **nearest** (default): round up to the nearest integer, with .5 rounded down to 0. Examples: `0.3 -> 0`, `0.5 -> 0`, `0.51 -> 1` * **floor**: Round down to integer only, decimal part is stripped. Examples: `0.3 -> 0`, `0.9 -> 0` * **ceiling**: Round up to the next integer value.) Examples: `0.3 -> 1`, `0.9 -> 1` The rounding behaviors apply only to positive numbers. Negative numbers are always considered invalid. Referral Link: **feat: user managed credentials for external services** Core * Differentiate external services credentials *by-user* and *by-policy-instance*, in addition to the existing *by-Guardian-instance* feature * Allow SRs to set credentials for every imported policy * Allow any user (SR, VVB, normal users, etc.) to set their own credentials for all the policies they interact with * Allow any user (SR, VVB, normal users, etc.) to set their own credentials for a single policy instance * Allow any user (SR, VVB, normal users, etc.) to set different credentials for dry-run and for production executions * Implement precedence logic for credentials to be used during policy execution, such as the first credentials found will be used: 1. User-defined policy level. "Users" here means any user type: SR, VVB, normal, etc. 2. User-defined global level. "Users" here means any user type: SR, VVB, normal, etc. 3. SR-defined policy level 4. Guardian instance level UI * Offer a UI to set the above mentioned credentials globally at user level * Offer a UI to set the above mentioned credentials at policy instance level * Offer a UI to set the above mentioned credentials at Standard Registry level (all policies imported by that SR will use those credentials) * Offer a UI to the SR to check the global overriding levels currently configured for its policies (all levels). The SR will be able for example to see if a user overrides the credentials at policy or instance level, but it will not be able to see the actual credentials. * Highlight when a policy allows setting custom credentials (i.e. contains blocks requiring credentials). * Highlight when a policy is using custom credentials instead of the Guardian instance level. API * Extend the existing APIs to allow users to set the above mentioned credentials Referral Link: **Create external event for "token failed"** Create a new external event for when the token(s) minting fails. Referral Link: {% endtab %} {% tab title="Previous Releases" %} **---- January 2025----** **Climate Action Reserve's U.S. Landfill Protocol** 1. Creating Schema design for this methodology. 2. Development of the schema and policy. 3. Testing the policy development through Guardian UI and configurator. Referral Link: Documentation Link: **Scope 3/PCF Referencing Demo (Methodology Breakdown)** Once the approach has been approved, we can update the GHGP policy and run the example data, publish the PCFs to the Hedera Network, and demonstrate how another guardian policy (of a supply chain partner) can reference a dynamic PCF to support scope 3 calculations. I believe Wes was interested in having this be a methodology breakdown. Referral Link: **API facilities to retrieve unique references (IDs) of results for API-triggered operations** * Design a generic approach to the 'traceability' of API calls such that for each API call a chain of events and actions within Guardian policy and especially to outside systems can be established via the unique IDs culminating in: * Hedera transactions * Hedera topics messages * Hedera contract calls * Artifacts published on IPFS * Introduce a corresponding UI where users can visually observe the same information * Consider packaging this into Interactions Resilience Module (see related [Hedera interactions resilience module #2905](https://github.com/hashgraph/guardian/issues/2905)) Referral Link: Documentation Link: **Guardian analytics: labels and top down data way points** * Introduce 2 new workflows into Guardian, which include the corresponding roles and access permissions: * labels author, for users to be able to create the 'rulesets' for evaluating data for their compliance with the chosen 'label', * auditor workflow, for users which would use these 'rulesets' to apply to data. * Introduce the concept of labels, which can be specified to combine multiple statistics (introduced in [Guardian analytics: bottom-up data traceability #3336](https://github.com/hashgraph/guardian/issues/3336)) to create 'higher-order' statistics which themselves can be combined further essentially enabling the creation of 'data transformation' trees which, when applied to data, would ultimately get resolved into binary compliant/non-compliant answers. The top-level 'nodes' in these trees are 'Labels'. * Enhance the current capability of qualitative evaluations in Statistics to support the ability for users to attach external evidence and add textual comments/explanations whenever a human input is enabled. The evidence would then become part of the 'evaluation trust-chain', i.e. it should be hashed and stored verifiably. Evidence in the image formats should be viewable in the browser, archives (zip files), pdfs, csv files should be supported for attachment and then download. * Enable Auditors to apply 'label rulesets' to tokens, Guardian would then automatically traverse the token trust-chain to find and evaluate the required data to produce the label conclusion, i.e. the compliant/non-compliant results. These results can optionally be published to IPFS/topics by Auditors that generated them. * Enable ordinary users to search for statistics, label ruleset, and label conclusions that have been published. Referral Link: Documentation Link: **Trustchain support for contract-based issuance and retirement implementation** Extend/modify trustchain implementation to support new contract-based issuance and retirement functionality such that users have visibility to the entire lifecycle of the token and have access to all significant artifacts produced as a result. Referral Link: Documentation Link: **American Carbon Registry (ACR) ACR Methodology for Quantifying, Monitoring, Reporting, and Verifying Greenhouse Gas Emissions Reductions and Removals from Landfill Gas Destruction and Beneficial Use Projects** 1. Creating Schema design for this methodology. 2. Development of the schema and policy. 3. Testing the policy development through Guardian UI and configurator. Referral Link: Documentation Link: **GHGP Version 3** Some items that could help take this policy to the next level would be to build out scope 3 and PCF referencing capabilities, build out SEC compliance aspects, and pursue a “Built on GHGP Mark” of approval. I believe this will help drive the policy to be attractive to real world users and ready for adoption. Referral Link: **Enhancements and Bugs of Indexer** We need to enhance Indexer feature by implementing following: 1. Progress Bar to show the data loading to DB. 2. Token and search data should be sortable by time Referral Link: Documentation Link: **Formula Linked Definitions & Schema Tree Enhancement** 1. Introduce a UI component, or 2 separate but compatible components, into the Guardian which can display mathematical formulas in a format familiar to the user (like formulas in a LaTex documents of PDFs). These formulas should be interactive, i.e.: * at the viewing time individual elements of the formulas should be clickable so users can drill into the variables and see corresponding schemas/documents. * users should be able to input formulas (in a formula editor) of sufficient complexity to cover all VCM cases * users should be able to copy/paste entire formulas or parts thereof 2. Enable policy authors to map schema tree structures to formulas, linking the fields and variables so Guardian UI can display them as per point above 3. Enhance Guardian schema, policy and VC/VPs views to display the formulas whenever they are available. 4. Introduce the ability to attach a PDF file to the schemas/formulas at the policy/schema creation time, and specify the (external) 'origin' link so the original source of the math can be traced to the original paper. 5. Enhance schema tree view to display the formulas alongside schemas. Referral Link: Documentation Link: **Dry-run policy execution 'savepoints' - restart policy dry-run from the list of 'saved' places** * Introduce a new functionality for users to 'save' dry-run execution status at arbitrary points by clicking 'save state' button. * The system should support the creation of multiple save points for the same execution workflow * Next time the (draft) policy is executed in the dry-run mode users should be given a choice whether to restart from the beginning or continue execution from any of the 'save points'. * Starting execution from a 'save point' invalidates and removes all the other save points that logically followed it * It should be possible to delete some or all save points manually Referral Link: Documentation Link: **Standardize UI on Angular Material, remove/replace PrimeNG** * Standardize Guardian UI to be Material-based * Remove/Replace all PrimeNG with Material without changing the look feel Referral Link: **Enhancing Research on Indexer and Analytics Use Cases** Identify and map out potential uses cases for the indexer and what type of analytics if could be used for. Referral Link: **Development of AMS-I.C.: Thermal Energy Production with or Without Electricity** 1. Designing the Schema for the methodology 2. Development of the policy 3. Development of all the tools involved in this policy * Tool 03- Tool to calculate project or leakage CO2 emissions from fossil fuel combustion * Tool 05- Baseline, project and/or leakage emissions from electricity consumption and monitoring of electricity generation * Tool 06- Project emissions from flaring * Tool 07- Tool to calculate the emission factor for an electricity system * Tool 09- Determining the baseline efficiency of thermal or electric energy generation systems * Tool 12- Project and leakage emissions from transportation of freight * Tool 16- Project and leakage emissions from biomass * Tool 19- Demonstration of additionality of microscale project activities * Tool 21- Demonstration of additionality of small-scale project activities  * Tool 22- Leakage in biomass small-scale project activities Referral Link : Documentation Link : **---- February 2025----** **Add policy support for more than one external data block** Allow more than one external data block per policy. Each external data block should be able to handle a different schema, enabling multiple types of data to be sent from external sources as needed. Referral Link: Documentation Link: **Firing external event when minting process is finished** * Add another external event when the minting process is completed (i.e. external-events.token\_minting\_process\_completed) * Include in the event payload, among other details like tokenID, minted tokens, etc, the consensus timestamp of the last mint transaction Referral Link: Documentation Link: **Establish deprecation policy for architectural APIs** * Identify and enumerate all architectural APIs significant to end users * Extend API deprecation policy coverage to include the above APIs Referral Link: Documentation Link: **Cross-context (API+UI) refresh token invalidation (regression from v2.18.0)** Looking into the code, it seems that the refresh token should last for a year, this is fine as it is configurable, but losing login context (or a user potentially feeling they lost all their data) isn't great UX. In terms of code behaviour, I would presume that this change would fix the issue: ``` const user = await new DataBaseHelper(User).findOne({refreshToken: decryptedToken.id, username: decryptedToken.name}); ``` to ``` const user = await new DataBaseHelper(User).findOne({username: decryptedToken.name}); ``` The reason why this ***might*** be okay, is that the *expire at* decoding happens on the line above, so a refresh token, would last for the period of time by default. As this is authentication related, it requires review from more people. Referral Link: **Business UseCase for Emissions Reduction/Removals (ERRs)Calculation Pre-Calculator in Guardian** We are in the process of creating a few approaches to this ticket from the business use case perspective. One is essentially an “estimator” with a simplified workflow that can be used to estimate emission reductions, token issuance, etc. upfront to help the user better anticipate issuance and the impacts of various project activities and methodological choices. The other is more of a “summary preview” of the actual calculation results, that can be implemented just before validation (or anytime thereafter) to see summary KPIs based on the actual inputs and methodological choices made by the user, and they can then interact with the data like the Nerd Wallet retirement calculator to see how changes to the project activities could impact issuance. To be discussed further with the team. Referral Link: **Add capabilities to display complex geoJSON shapes superimposed on maps** * Introduce capability for geometric shapes display for geoJSON in Guardian UI (both Indexer and Guardian itself). * Shapes display must be correctly superimposed on maps wherever possible Referral Link: Documentation Link: **---- March 2025----** **Weak Default configuration** Change the password to a strong, random value, or create additional setup steps were the deployer is required to set this secrets. Additionally, set the most secure configuration as the default in the repository. This ensures that any user deploying the repository will benefit from enhanced security by default. In addition, as highlighted on the issue finding "Lack of Security Hardening Guides", a security guideline is recommended so that users can configure securely their environment before deploying it. Referral Link: **System Logs Accessible by All Registries** It is recommended to separate the system functionality from the registry functionality specifically for log management. Additionally, it would be appropriate to restrict access to system logs to a different admin role, who would only review the system logs. For registry logs, it is recommended to ensure that one registry can only view its logs, without seeing the logs of other registry users. Referral Link: Documentation Link: **Development of VM0042 v2.1: Improved Agricultural Land Management** 1. Flexible Quantification Approaches: 2. Support for three primary quantification approaches:\ \- Measure and Model\ \- Measure and Remeasure\ \- Default Factors 3. Document and Template Integration: 4. Capture key documents/templates:\ \- Project Description Template, v4.4\ \- Monitoring Report Template, v4.4\ \- Validation Report Template, v4.4\ \- Verification Report Template, v4.4\ \- User Registration Forms\ \- Emission Calculation Form 5. CDM Tools and Modules Integration: 6. AR-TOOL14: Tool for Testing Significance of GHG Emissions in A/R CDM Project Activities 7. A/R Methodological Tool for the Identification of Degraded or Degrading Lands in CDM A/R Project Activities 8. VMD0053 Module: This module will be treated as a tool within Guardian. Referral Link: Documentation Link: **Manual trigger of re-indexing for specific policy, SR, token** * Introduce a new capability into the indexer to trigger manual re-indexing for a specific 'vertical', starting at a specific topic and navigating (only) down the hierarchy for immediate availability of data. * Develop a UI for users to provide a Topic ID for one of the specific items below as an entry point into the 'vertical': * Policy * Standard registry * Token * When manual re-indexing is scheduled it must take priority, or the rest should gets postponed until the manually-triggered update is finished. * The user who triggered the update must be notified when the update is finished. Referral Link: Documentation Link: **Article 6.4 Forms Research** o Identify the additional requirements of Article 6 in comparison to one (or more) of the main voluntary standards. o Determine functionality requirements to implement a “label-type” feature discussed above Referral Link: **---- April 2025----** **Session Token in URL** The application should use an alternative mechanism for transmitting session tokens, for example, the Authorization header, as it is done by the rest of the web application.22 Referral Link: **Accessing a Guardian policy from a Guardian instance other than the publishing instance** A Guardian user should be able to access a policy published by another Guardian instance from their own Guardian instance. This access should be based on a request-grant model. Referral Link: Documentation Link: **---- May 2025----** **Server-Side Request Forgery (SSRF) in Request Data module** If the functionality is important enough to keep despite the risk, then all URLs should be requested through a secure proxy server. This is a significant effort, and to be secure the proxy must ensure that: 1. The URL does not resolve to a private or local IP address 2. Redirects are not followed 2. Only HTTP(S) protocol schemes are supported\ Additionally, the application server should define and enforce rate limits to discourage abuse of the functionality as a web scanner.\ If the application is hosted on AWS servers, enforce usage of AWS “Instance Metadata Service Version 2” with token usage required. This is a new AWS metadata API which severely curtails the ability of attackers to abuse SSRF to access the AWS metadata API. However, this will not prevent attacks against other internal services. Referral Link: **Exporting Project Data in CSV format** 1. We should be able to export the complete project data of any policy in CSV format through Guardian. 2. We should also be able to apply filters to the project data, which should be included in the export file. 3. When we export the data in csv format, it should follow proper naming convention such as saving the exported file by its respective policy name\_version.csv Referral Link: Documentation Link: **Missing Authentication between Services** It is recommended to implement mutual authentication for all internal microservice communications to ensure that each service can verify the identity of the other. It is recommended to ensure that each service is properly authenticated, using authorization roles and permissions to ensure that each service can only publish or consume messages in the queues relevant to its designated function. Moreover, messages could be digitally signed, ensuring they originate from the correct service. At each step in the process, the signatures can be verified to ensure that the message has not been tampered with. Where applicable, integrate these recommendations into the security hardening guide to ensure organizations deploying the application can implement these best practices effectively. Referral Link: Documentation Link: **No Password Policy** It is recommended to create a password policy, that can be configured by the organizations using the application. It should also be noted that recent guidance from NCSC promotes password policies which are designed to decrease the burden on the user. This can include relaxing controls requiring users to change their passwords at regular intervals in favor of the use of suitably complex passwords. The NCSC password guidance21 should be reviewed to determine if this new guidance can be applied to the environment reviewed. Referral Link: Documentation Link: **---- June 2025----** **Development of VM0033** 1. Creating Schema Design. 2. Review the design 3. Development of the methodology 4. Testing the methodology 5. Documenting the methodology user guide. Referral Link: Documentation Link: **Detailed Research on Indexer Enhancements** Identify and implement indexer enhancements based on example use cases and community feedback. Referral Link: **Guardian policy embedded code testing/debugging facility for Custom Logic, Calculate, etc blocks** * Introduce the 'Test' button to all places where **source** or **math** code can be inputted in Guardian policy which would trigger the 'in place' execution of the code based on the execution context and defined inputs/outputs of the block. This tool could prompt the user for input data when required. * Add ability to 'print' (i.e. log) data and variable values somewhere when test-running policy (e.g. in Dry-run mode). This way policy authors would be able to examine the data structures passed into the functions and identify unexpected behaviour in this area. * Add recommendations to the documentation wrt running this code in an separate developer environment, i.e. all the needed execution context such as imported libraries etc so those developers who prefer to use their code editors can replicate the execution of the code there. Referral Link: Documentation Link: **Outdated Software/Libraries** Ensure the Guardian code is covered by an effective patching policy that allows the latest server software upgrades, updates, or patches to be tested and applied within a short time frame following their release by the vendor. Referral Link: **Substitute Google maps API in Guardian UI with an OSS alternative** Substitute currently used Google Maps for the same open maps as used in the Indexer. Referral Link: Documentation Link: **---- July 2025----** **Identifying, Implementing and Integrating 3rd Party data resources** * Identify and shortlist 2-3 key Environmental-related data sources to be used as reference data and/or * Implement integration with these 3rd party data providers (may be similar to IPFS/Hedera integration), such as: * policy can easily add such 'integration' to their policy - potentially using the new policy modules functionality [Linkable policy modules for constructing end-to-end Policy workflows #1657](https://github.com/hashgraph/guardian/issues/1657) * the data can be defined as mandatory or optional (by the policy author) * data imported into Policy artifacts is stored and displayed in its native format, preserving 'mime type' and/or any other indication of the nature of the data as well as the identity/credentials of the source, time/date and other identifying information as appropriate Referral Link: Documentation Link: **Authorization Headers Potentially Leaked through IPFS in Request Data Module** Implement a secure method to handle secrets in the Request Data module that ensures sensitive information, such as authorization headers, is not published with the policy. A possibility may be to include encrypted headers with the public key that only the private key of the policy owner can decrypt. Other possibility may be to store the secrets headers in the vault and fetch them at runtime using appropriate access controls. Update the documentation to explicitly warn policy creators about the risks of including sensitive information in the policies and recommend using the module only for public HTTP methods. Provide guidelines on securely configuring policies to avoid the leakage of sensitive data. Referral Link: **Facilities to use specialist math tooling (such as R language) for calculations in Guardian Policies** 1. Introduce support for Python language **in** Policies such that Python code can be embedded into Policies and enable them to perform complex calculations in the course their execution by users 2. Bundle Python interpreter and a standard (curated) set of libraries into Guardian distros 3. Add 'Guardian version' parameter to the documents so any complex calculations can be replicated by knowing versions of libraries and interpreters used by the Policy at the document production time. Referral Link: Documentation Link: **--— August 2025 ----** **Payload Shapefile Ingestion** Make the payload ingest shapefiles, KML etc. Referral Link: Documentation Link: **Improvement in the error handling for excel schema imports​** To have better validation when excel is imported into guardian which will help prevent all the points I mentioned above and some more that I probably missed while working on methodology digitization Referral Link: **Dry-run savepoint\[s] to survive exit and policy editing** 1. Make savepoints 'survive' multiple "exit dry-run -> edit policy -> execute dry-run" cycles such that policy authors would not have to enter values in fields again on subsequent dry-runs. 2. Enable to existence of multiple 'savepoints' per policy 3. Enable policy authors to choose when savepoint to apply on each policy dry-run session. 4. Users can clean-up savepoints by deleting them individually, or choosing to 'Delete All' Referral Link: Documentation Link: **Locations Data Field enhancement** Validation Check: Implement a validation step to confirm that location data being passed to the policy is in polygon format (e.g., Polygon or MultiPolygon in GeoJSON). Data Format Enforcement: Ensure that only valid polygon geometry types are accepted. Reject or flag submissions that use unsupported formats (e.g., Point, LineString, or malformed geometries). GeoJSON Handling (Optional Enhancement): Explore and, if feasible, implement a conversion method to extract the location GeoJSON and convert it into a downloadable file format (e.g., .geojson or .json). Referral Link: **SLA Ticket Import and Policy Publish Performance in Guardian** Investigate bottlenecks in the SLA Ticket Import process: * File parsing and validation * Schema mapping and VC generation * Backend processing queues Optimize the policy publishing process: * Reduce the time to publish policies with SLA blocks * Improve processing time for VC issuance and anchor creation on Hedera * Implement batch processing or lazy loading where applicable Evaluate and optimize: * MongoDB write operations * Hedera anchoring transaction handling * Large file buffer management * Provide loading indicators and progress status updates to the user Add backend logs/metrics to measure: * SLA import time * VC issuance time * Total policy publishing duration Referral Link: **--— September 2025----** **Validation for project data submission** Validation Rules Enhancement\ Implement robust validation for schema fields in both UI-level form inputs and backend processing logic for key field types: * GeoJSON: Ensure that the data is a valid FeatureCollection or Geometry object following RFC 7946 standards. * IPFS Links: Ensure that the link is not empty and follows proper CID or ipfs\:// format. Error Handling and Feedback * Inform the user with clear error messages during submission if data fails validation. * Prevent submission if any required or format-sensitive fields are invalid. Backward Compatibility Handling * Optionally, mark or flag previously submitted documents with invalid data for review or correction. Unit and Integration Tests * Add test cases to ensure all validations work across various scenarios and edge cases Referral Link: **Add an option to hide some buttons in case the policy is discontinued** * Policy developers can flag a button as available only if the policy is not discontinued. * Buttons flagged as *hide/WhenDiscontinued* won't be displayed in the webUI when the policy is discontinued Referral Link: Documentation Link: **Guardian Form UI Improvements** These four can be made into their individual issues as well. Let me know, I'd be happy to submit four separate ones. 1. Support a table input(and csv import) field for multi-year data fields. Often methodologies require multi-year inputs(think 10 or 100 year) and it's not the easiest to visualize or input them with a typical form UI. It'd be good to have a way to have tabular inputs and a way to specify how they will be read within calculations code. 2. Support attachments to a field (justifications, report). Corresponding to a submitted field, a VVB or SR may ask for justification report which is usually a file. A similar issue is already there - [Manual input of additional data for inclusion into the VC document #2076](https://github.com/hashgraph/guardian/issues/2076) 3. For large documents for example PDD, it'd be good to divide them into sections when user is submitting. We must allow draft saves and make dry-run testing feasible. Such a feature already exists(tabbed/navigation UI), but if document is too big, policy developer needs to click test data button multiple times to fill the entire form. 4. GeoJSON/Shapefiles rendering - Allow file uploads of such types and they should be rendered with maps in best way in form UI. Referral Link: Documentation Link: **Make testing easier for subflows** There should be a way to test the sub-flows similar to unit test paradigm we have in programming. Each unit should be individually runnable and testable. Following the entire workflow for testing takes up \~50-60% of time of policy development. Referral Link: **--— October 2025----** **Complex iterative review and approval workflows​** Introduce `reviewVcDocumentBlock` as a complement to the `requestVcDocumentBlock` into Policy definition language and corresponding Guardian UI tools which would facilitate complex iterative document review workflows supporting rich communications, namely the ability to: * send messages/descriptions associated with actions * conduct stand-alone (not action-linked) message exchanges (questions, responses, general comms) * send requests for providing additional documents/evidence, and provide facilities to upload/receive them * ability to edit/correct previously submitted (but rejected) document and resubmit again * forward messages to another user * involve other users into 'conversations' These actions, steps, message exchanges have to be verifiably traceable, i.e. recorded and published as VC/VP documents alongside the usual data-containing documents produce by the policy workflows. Referral Link: Documentation Link: **Policy warnings** * Introduce the generic capability to highlight blocks, elements within them, and groups of blocks * Introduce the generic capability to produce and display warning/error/info messages, their numbers and ability to disable/resolve: * ignore (this one) * ignore all like this * Add the corresponding API capability to access and manage the warnings etc via API Referral Link: Documentation Link: **Schema deletion with child schemas** Implement a safe way to delete all schemas embedded into the parent schema in one operation such that: * the system check whether the schemas embedded into the parent schema being deleted are used anywhere else, and if so prevents the delete operation * users can select whether to delete all embedded schema together with the parent one or not before the deletion Referral Link: Documentation Link: **Project (Relayer) Account (ex:Project Developer or Accountable Impact Organization)** * Each new Project must have a unique wallet address generated/associated upon creation. * The Project wallet must support: * Receiving funds (Hedera tokens/HBAR) * Sending funds (to users, vendors, or community members) * Holding and managing tokens (if applicable) * Transactions must be traceable back to the Project wallet for reporting/financial audit. Referral Link: Documentation Link: **Need to implement best practices on Schema Cycle** We need to implement and document best practices covering the following aspects of the schema lifecycle: Schema Design & Format Guidance * Explain how to design schemas that align with Guardian requirements. * Describe valid formats and structure (e.g., JSON Schema). * Outline file format expectations for importing into Guardian. Manual Schema Creation in Guardian * Step-by-step process to create schemas directly in the Guardian UI. * Include tips for defining required fields, types, and constraints. * Emphasize validation logic to reduce submission errors. Schema Mapping * When and why to map schemas. * Best practices for setting up mapping relationships (if applicable). * Examples of mapped vs. unmapped use cases. Referral Link: Documentation Link: **Update Walkthroughs in Documentation** A clear and concise description of what you expected to happen. Referral Link: Documentation Link: **Option to delete all schemas for a particular policy in Draft stage​** There may be another solution/improvement to the excel where it checks for duplicates and provides with an option to replace. Similar to the file system in macOS for example where it doesn't allow 2 folders with the same name at a particular destination. Issue for that created here: [#4754](https://github.com/hashgraph/guardian/issues/4754) Referral Link: Documentation Link: **Import Excel to check for duplicates by schema name​** But I believe there is one more check which the guardian can do when the excel is imported and that is to check for duplicates and provide the user with an option to either replace the schema or keep both the files. Referral Link: **Nested schemas for complex conditions** * Cross-sub-schema referencing:\ \- Conditions should be able to reference fields located in other sub-schemas or sections.\ \- Example: A “Parameters for Validation” field’s visibility or requirement should depend on the “Application of Methodology” field located in a different sub-schema. * Multi-field logic:\ \- A single condition should support evaluation of multiple fields simultaneously.\ \- Example: A field becomes visible or required only when both “GHG Sources/Carbon Pools” and “Temporal Boundary” fields meet specific values. * Chained conditional logic (presentation order):\ \- Conditional fields should be able to reference other conditional fields, allowing a sequential display order.\ \- Example:\ \- If Field 1 is true → show Field 2.\ \- If Field 2 is true → show Field 3. * Dynamic updates:\ \- When a user changes a field value, all dependent conditions across the entire schema should re-evaluate in real time.\ \- This ensures immediate UI updates for visibility and requirement changes. * Automatic data reset:\ \- If a field becomes hidden due to a condition change, all data previously entered in that field should automatically clear.\ \- This avoids invalid or inconsistent state retention. * User guidance and clarity:\ \- Sequential logic and real-time updates should create a natural flow for users.\ \- Only relevant questions are displayed based on prior responses, improving data accuracy and reducing confusion. Referral Link: \ Documentation Link: **---November 2025---** **Implementing Artifacts such as Schemas/Policies/tokens Deletion all at once​** 1. Create a checkbox at the top of the schema/policy/token table, which will allow to select all the artifacts. 2. Once, all the schemas/policies/tokens are selected, and clicked on delete, we should be able to delete all the schemas/policies/tokens at once Referral Link: Documentation Link: **Graphical View of formula linked definitions** * Add the capability to display dependencies and relationships of data feeding into Formula definitions as a diagram similar to 'schema tree view' or 'statistics'. * Color code (or in other way identify) the data points based on: * their values (missing/default/as suggested/not-null) * type (data structure/scalar value) * in the future other criteria (e.g. "outside of 'normal' range") Referral Link: Documentation Link: **Capture/replay and compare data of published policies** Introduce the capability to record and publish 'runs' of the policy for published policies such that it would be possible to replay these runs locally (in dry-run mode) and compare the results. Additionally the runs need to be secured as a certified artifact which can be undeniably attributed to an instance of the Guardian and Standard Registry in it. Thus it would provides additional execution environment verification tool for auditors etc potentially other interested parties. Make the recording of the runs for published policies executions 'on' by default (which can be disabled by the user), with an option to publish the final 'runs' artifact on IPFS which is also 'on' by default. Referral Link: Documentation Link: **Formula-linked definitions enhancements** 1. "Name" column in formula records table should be wider. Now it's unreadable 2. After creating a formula record I need to find it in a list to edit. It's quite difficult according to point 1 3. On the top of a formula edit page I see button "Back to policies" but button redirects me to list of formulas 4. I cannot move a formula item when I'm scrolling the page. Drag-n-drop works only in visible part of screen and it's impossible to add const/variable and move it to the top of a long list 5. I cannot re-use constants which are defined in another formula in relationships. It makes me to define same constants in different formula records Referral Link: **---December 2025---** **Guardian as a multi-workflow engine for independent data streams** Guardian should be able to inject machine-readable product data and process them simultaneously in multiple independent Policy processing streams, each with an independent ruleset, however with the possibility to coordinate and cross reference the artifacts produced by these streams, all while maintaining and referencing the single original instance of the 'master' data. 1. Extend and adapt the topics architecture to support multi-workflow processing of the master data (from a topic) 2. Develop a multi-streams Guardian policy coordination mechanisms which were in a single instance and across different Guardian instances, which include * trigger workflow execution based on an event such as NFT issuance, data events. * pause and wait for the availability of specific data 3. Introduce additional (to token issuance) Guardian policy actions to enable 'final' stages of policy streams executions, such as: * payment execution * certificate (invoice, bill of lading, etc) issuance Referral Link: Documentation Link: **Tamper-resistant Policy and Module export/import** * Introduce the signing of Policies and Policy Modules such that on import their authenticity is evaluated - which proves that they have not been tampered with. * In an indicator into the Policy grid (or other appropriate place) which would show whether the Policies (and/or their elements such as schemas, modules etc) that have been imported (whether from the file system or IPFS) have been modified from their original state. * Introduce the ability to compare all Policies which have been 'created' in the particular instance by import with their original 'just after import' state. Referral Link: Documentation Link: **Data Entry Updatability** An ability to make schema data that is non-material to calculations updatable, while not changing the token issuance in flight. Referral Link: Documentation Link: **---January 2026---** **Fine grained Policy workflow certification labels** Introduce the capability to select arbitrary sections of Policy workflows and then assign tags to them, which should result in these tags being visible whenever the policy sections or any artifacts produced in these sections are viewed by users such that: * Policy sections can be selected and assessed/tagged after the policy is published * Assessment/tagging can be done by users who are not policy authors * Tags then applied retrospectively to artefacts produced by the 'target' section of the Policy (where the tag has been applied) * Tags are visible whenever users view artefacts and/or policy in Guardian and Indexer, including trustchain view Referral Link: Documentation Link: **Extend Policy definition language to include a Formula calculations block​** Introduce a Formula calculation block which would: * Allow Policy authors to input mathematical formulas directly into the policy (using Guardian UI formula editor) in the standard mathematical notation () * Enable policy authors to bind variables/parameters in these formulas to data (fields in schemas) for inputs/outputs to integrate the block into the Policy workflow * At Policy run time perform the calculations directly without any additional input etc from users () Extend Guardian UI to: * Whenever the result of such calculation is shown to the user to also display the formula definition in the standard math notation * Also display the values of the variables/parameters in the formula which were used to calculate these results * Enable users to navigate to the data sources of these values (used for the calculations) by providing links to the required levels dept. Referral Link: Documentation Link: **Deterministic compression** Implement deterministic compression for all cases in which compression is applied by Guardian. Referral Link: **Add API endpoint to generate example payloads matching UI auto-fill logic** * Add an API endpoint that generates an example payload based on the same logic currently used by the UI "Test" button in Dry Run mode. * The example payload generation must follow this exact priority order: * If a field has an `example` defined, use that. * If no example exists, use the corresponding preset value (if available). * If neither an example nor preset exists, generate a value based on the field's data type. * The generated payload must fully match the structure defined by the JSON schema, including nested fields. * Ensure feature parity between UI "Test" button logic and API-generated examples. * Preserve existing performance expectations even for very large schemas. Referral Link: Documentation Link: **Add Support for Synchronous Event Execution** * Introduce a configurable event type: synchronous or asynchronous. * New events must be synchronous by default. * When an event is synchronous, the API must wait until the entire chain of event-triggered blocks completes before returning the response. * In synchronous mode, errors from related blocks must propagate back to the API response rather than going only to logs. * Synchronous events must not allow the creation of cycles. Implement cycle detection and validation. * Asynchronous events must preserve current behavior. Referral Link: Documentation Link: **Implement Form View for Image Tags** * Implement a Form View for VC documents that renders uploaded images in their proper visual format rather than as plain text links. * Provide the ability for users to toggle between Document View (text view) and the new Form View. * Ensure the Form View properly displays all supported media types, with images rendered inline. Referral Link: **Improve schema version handling** * Improve the UX such that it is immediately apparent that some schemas (published or not) are new versions of other schemas. This can be done via drop down list of schema versions, with the most recent (draft or published) displayed at the top * Enforce linear progression of schema versions such that only the most recent published schema can be the source/basis of new versions * Always display the version of the schema documents * for draft new versions of the existing schemas display in italic the suggested version, which is also pre-populated in the schema dialogue but can be overwritten by the user * for imported versions of the schema display the version as imported, no italic or any other formatting Referral Link: **Enable the "Publish" button only when the policy version is correct** The "Publish Policy" popup window should: * Inform the user about the current policy version * Enable the publish button only if the selected version passes the verifications that the server will apply later (i.e., the version number should be greater than the current one). Referral Link: **UI Ticket — Pop-Up Window Size Too Small for Data Entry** Pop-up windows should automatically resize to utilize more of the screen area or allow manual resizing. Referral Link: **UI Ticket — ERR Table Display: No Ability to See Tables for Summarized Information** Users should be able to see data in table format (rows + columns), consistent with Verra Project Hub. Referral Link: **UI Ticket — Add Tables to Improve Data Entry** The UI should support true tables where users can: * Add/delete rows * Input data column-by-column Referral Link: {% endtab %} {% endtabs %}