The "Writing a Gatekeeper Config" section of this doc may help explain how this json format is expected to translate into concrete rules:
https://docs.google.com/document/d/1rJtHbQCxLiWbxg4vWAhi62o3ALTO2dvxe1e2Nu1pkVk/edit#heading=h.z9q7lswy8iio

One way to test for compatibility/regressions would be to implement gatekeeper_ng.py's "flatten" operation in go. Then diff the go version's output with the original gatekeeper_ng.py's --flatten output, using the same gatekeeper.json input file.

@martiniss, you called it correctly :P

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot