<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>lean4</title>
    <link rel="self" type="application/atom+xml" href="https://links.biapy.com/guest/tags/3535/feed"/>
    <updated>2026-09-08T10:39:12+00:00</updated>
    <id>https://links.biapy.com/guest/tags/3535/feed</id>
            <entry>
            <id>https://links.biapy.com/links/13820</id>
            <title type="text"><![CDATA[infra]]></title>
            <link rel="alternate" href="https://typednotes.github.io/infra/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/13820"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[infrastructure as code, in Lean 4.

 Terraform-style declarative infrastructure, written in the Lean programming language and proof assistant instead of a bespoke DSL. Target and observed cloud state are dependently-typed Lean values, so an unrealisable target is a compile error rather than a failed apply.

A dangling reference, a region a cloud is not in, an instance size that does not exist, a plaintext password in a committed file — none of these get as far as a plan. 

- [infra @ GitHub](https://github.com/typednotes/infra).

Related contents:

- [Terraform in Lean 4: If It Compiles, It Will Likely Deploy @ NGrislain](https://ngrislain.github.io/blog/2026-9-6-terraform-in-lean-4-if-it-compiles-it-will-likely-deploy/).]]>
            </summary>
            <updated>2026-09-07T12:28:42+00:00</updated>
        </entry>
    </feed>
