Milestones
List view
Outcomes (draft) \- better consistency across policies \- reduce time spent in approval / review cycles \- shorten policy authoring times \- reduce complexity / domain expertise required for policy authoring
Due by September 30, 2026•0/25 issues closedThis milestone includes QA and docs related issues between the 3.7 RC and 3.7GA.
Overdue by 3 day(s)•Due by August 18, 2026•36/47 issues closedNative and third-party payment capabilities within Guardian — enabling policy-driven, on-chain, and off-chain payment flows tied to methodology and project workflows.
No due date•0/5 issues closed- No due date•0/10 issues closed
Create the technical layer for both localization and clear terminology * ability to change labels so that we can be flexible and adapt iteratively * propose a set of labels to change that will help users better grasp concepts building from established norms which we know from feedback have been confusing or are problematic * understand how such changes impact docs etc Problems The guardian terminology choices are a huge barrier for the user experience, here are some examples * policy * policy is actually a workflow * block is confusing * we work in a blockchain world * block is actually a step in a workflow * data source * in guardian a datasource is setting the endpoint you send data to which is the opposite of what this actually means
Due by January 1, 2027•0/4 issues closed- Due by January 1, 2027•0/4 issues closed
@[youtube](Ti0TOGZ_z8c)
Due by August 31, 2026•5/6 issues closed- Due by January 1, 2027•4/7 issues closed
- Due by November 30, 2026•0/10 issues closed
See the link below to learn more about the methodology bounty programme, https://www.dltearth.com/bounty-programme
Due by January 1, 2027•1/7 issues closed- Due by January 1, 2027•2/19 issues closed
- Due by January 1, 2027•1/20 issues closed
- Due by January 1, 2027•3/36 issues closed
- Due by January 1, 2027•4/33 issues closed