163
edits
Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!
Changes
Jump to navigation
Jump to search
no edit summary
Line 2:
Line 2:
==Business Brief==
==Business Brief==
+Rules as Code is an approach to create and publish regulations, legislation and policies as machine and human readable.
+The approach involves creating rules in government that are better suited for digital service delivery, creating software tools to write the rules into code, and then using that code as a basis for service delivery and decision making.
+
+Coded rules can automate certain decision-making in government. They are particularly well-suited to yes/no and if-this-then-that decisions, such as eligibility for benefits or obligations to pay tax.
+
+Making rules machine readable helps both civil servants and citizens clearly understand their intent, and execute them.
+
+'''Why It Matters'''
+
+Rules developed in the government are complex and often ambiguous. When rules require amendments, it becomes a challenge to make changes without introducing unintended consequences.
+
+When software developers and system administrators implement IT systems based on these rules, the complexity and ambiguity can often lead to a confusing user experience and worse, broken processes.
==Technical Brief==
==Technical Brief==
Line 18:
Line 30:
==Sources==
==Sources==
−Four things you should know about Rules as Code | GovInsider
+[https://govinsider.asia/inclusive-gov/four-things-you-should-know-about-rules-as-code/ Four things you should know about Rules as Code | GovInsider]
−Emerging Technology Guide: Rules as Code | Digital.NSW
+[https://www.digital.nsw.gov.au/digital-transformation/policy-lab/rules-code Emerging Technology Guide: Rules as Code | Digital.NSW]
−Why Policy as Code? (hashicorp.com)
+[https://www.hashicorp.com/blog/why-policy-as-code Why Policy as Code? (hashicorp.com)]
[[Category:Architecture]]
[[Category:Architecture]]
[[Category:Technology]]
[[Category:Technology]]
