Machine-Executable Policy

# Machine-Executable Policy **Entity class:** Legal, policy, or governance instrument **Domain:** Austin Research / Concepts **Doc Type:** Corpus analysis **Source basis:** Supplied research cluster with linked references; see the [[wiki/Austin Research Evidence Map|evidence map]] for verification scope. **Machine-Executable Policy** represents handling or decision rules in a form software can evaluate and apply. The [[wiki/IC ITE|IC ITE]] data strategy provides a concrete institutional example through machine-interpretable conditions for access, sharing, and use. The mechanism joins data markings with requesting identities, relevant attributes, and an enforcement service. A rule becomes consequential when systems actually evaluate it on a request and record the result. Its originating authority remains distinct from the machinery applying it. The Austin succession reading concerns a reduced need for humans to mediate every routine transaction. Policy execution, policy authorship, and authority to change policy remain separate functions. ## Connected entries [[wiki/IC ITE|IC ITE]] · [[wiki/Unified Identity Attribute Set|Unified Identity Attribute Set]] · [[wiki/Attribute-Based Access Control|Attribute-Based Access Control]] · [[wiki/Trusted Data Format|Trusted Data Format]] · [[wiki/Algorithmic Governance|Algorithmic Governance]] · [[wiki/Digital Administrative Infrastructure|Digital Administrative Infrastructure]] · [[wiki/Intelligence Community Cloud Architecture|Intelligence Community Cloud Architecture]] ## Simple Reminders, Quotations, and Thoughts > "When I think about the machines that can think, i.e. the AI, I think of them as technology that needs to be developed with similar (if not greater!) care." > **— Jaan Tallinn**, *2015, Edge annual question “What Do You Think About Machines That Think?”* [[reminders/AI Control/AI Must Be Developed With Greater Care by Jaan Tallinn|AI Must Be Developed With Greater Care by Jaan Tallinn]] > "Artificial Intelligence (AI) is commonly used as a tool to augment our own thinking." > **— Gary Klein**, *2015, Edge annual question “What Do You Think About Machines That Think?”* [[reminders/AI Control/Artificial Intelligence Augments Human Thinking by Gary Klein|Artificial Intelligence Augments Human Thinking by Gary Klein]] > "Iron law approaches to artificial and biological intelligence reveal a different set of engineering problems." > **— John Tooby**, *2015, Edge annual question “What Do You Think About Machines That Think?”* [[reminders/AI Control/Artificial and Biological Intelligence Share Engineering Problems by John Tooby|Artificial and Biological Intelligence Share Engineering Problems by John Tooby]] > "Machines that think make it possible for more people to celebrate the joy of human intuitive insight, and to cultivate the equanimity that is unique to the self-controlled human mind." > **— Nina Jablonski**, *2015, Edge annual question “What Do You Think About Machines That Think?”* [[reminders/AI Control/Thinking Machines Could Deepen Human Intuition by Nina Jablonski|Thinking Machines Could Deepen Human Intuition by Nina Jablonski]] > "In order to achieve the dream for thinking machines, they will have to understand and question values, suffer internal conflicts, and experience intimacy." > **— Andrés Roemer**, *2015, Edge annual question “What Do You Think About Machines That Think?”* [[reminders/AI Control/Thinking Machines Must Experience Values and Intimacy by Andrés Roemer|Thinking Machines Must Experience Values and Intimacy by Andrés Roemer]] ## Sources and corpus context - [[research/IC ITE - Intelligence Community Information Technology Enterprise|IC ITE - Intelligence Community Information Technology Enterprise]] - [[research/The Austin Executable Loop|The Austin Executable Loop — master document]] - [Intelligence Community Data Strategy 2017–2021](https://www.odni.gov/files/documents/CIO/Data-Strategy_2017-2021_Final.pdf) - [IC Technical Specification — Unified Identity Attribute Set](https://www.odni.gov/files/documents/CIO/ICEA/IC_Tech_Spec_Attributes_V2_Final_PUBLIC.pdf) - [Vision for the IC Information Environment — May 2024](https://www.odni.gov/files/documents/CIO/IC-IT-Roadmap-Vision-For-the-IC-Info-Environment-May2024.pdf) **Cluster:** [[wiki/Austin Executable Loop|Austin Executable Loop]] · [[wiki/Austin Research Evidence Map|Austin Research Evidence Map]]  ## Agreements expressed through access controls The LEAP agreement assigns gateway control, security review, audit, and suspension to NCTCOG. The DHS LEIS briefing specifies the service and data-exchange layer. Together they identify where human-authored participation rules meet technical enforcement. The actual LEAP rule engine or attribute policy is not described by the reviewed documents, so it should not be assumed identical to IC ITE’s. Provider transitions raise a further question: which permissions, correction duties, and restrictions remain enforceable when the operator changes? **Follow:** [[wiki/Interlocal Information Sharing|Interlocal Information Sharing]] · [[wiki/LEAP Provider Transition|LEAP Provider Transition]] · [[wiki/DHS Law Enforcement Information Sharing Service|DHS Law Enforcement Information Sharing Service]] **Source:** [[research/The Austin Surveillance Field|The Austin Surveillance Field]]; [City of Austin — LEAP interlocal agreement, recitals and §§2–7](https://services.austintexas.gov/edims/document.cfm?id=176641); [DHS — Law Enforcement Information Sharing Service briefing, slides 4–16; existing MOUs on slide 15](https://info.publicintelligence.net/DHS-LEISS.pdf).  ## Relationships  This entry's documented connections are expressed in its definition and related-work routes, with provenance retained in the source-linked material.