# Welcome to the Policy as Code Forum! Get started here

**URL:** <https://forum.ansible.com/t/welcome-to-the-policy-as-code-forum-get-started-here/5265>\
**Category:** Project Discussions\
**Tags:** policy-as-code\
**Created:** [May 2, 2024, 2:49pm UTC](https://forum.ansible.com/t/welcome-to-the-policy-as-code-forum-get-started-here/5265 "2024-05-02T14:49:08Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\
**Post date:** [June 14, 2024, 3:07pm UTC](https://forum.ansible.com/t/welcome-to-the-policy-as-code-forum-get-started-here/5265/17 "2024-06-14T15:07:27Z")

</div>

I want to be excited by the whole PaC (Policy as Code) idea. But, I’m going to be “that guy” for a minute:

- I haven’t seen a rigorous definition of “policy”. It seems to me like it’s more of a mindset that’s somehow supposed to separate the actual “things we do” from the more lofty ideal of “the way we do things”. Somehow that doesn’t inform my fingers when I open my _Editor of Choice_ and start to type.

- Maybe I’ve hit my own personal ceiling on levels of abstraction, but I don’t see how – in actual practice – PaC differs from the same ol’ Ansible tasks we’ve been hacking on these last few years. If I really stretch credulity, I might comfortably claim that a set of tasks that truly is idempotent as a unit constitutes a chunk of PaC. But, honestly, I’d be more comfortable just claiming it’s a good set of tasks.

Truly I hope there’s more to it beyond aspirational hand waving. When I open a text file, what can I look for that clearly indicates it’s Policy as Code vs. mere code?

---

_[View the full topic](https://forum.ansible.com/t/welcome-to-the-policy-as-code-forum-get-started-here/5265)._