Effect Office Hours 27: Alchemy, infrastructure as effects

Sam describes a workflow for coding agents from an empty project through deployment, tests, CI, and operations. An Effect describes work with typed failures36 and required services. A Layer describes how to build services and supply their dependencies. An Alchemy Stack is the infrastructure program that declares cloud resources.

Effects and Layers let the type system track the resource providers a Stack needs. Tests using real infrastructure check behavior after deployment. 03:38 07:01 16:01

He explains bindings23 as application capabilities that can inform least-privilege policies, which limit permissions to the application methods in use. The runtime and infrastructure stay related without bundling provider implementations into the application. 58:16 59:23 70:55

Sources

  1. Alchemy, Infrastructure as Effects | Office Hours 27 🔥 - YouTube. Sam Goodwin. Recording; used for Effect-native planning, testing, and deployment of infrastructure. Accessed 2026-10-01.

Last changed 2026-10-07 in 0e2d656. Source on GitHub. Change log.

Linked from

  1. Agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
    Link context

    Effect Office Hours 27: Alchemy, infrastructure as effects — Sam Goodwin presents Alchemy as a system built with Effect for planning, testing, and deploying infrastructure.

  2. Bindings. Sam Goodwin describes bindings as the place where runtime permissions and configuration meet infrastructure.

    See Happy Path 116 and Effect Office Hours 27.¶

  3. Change log. What changed in the files served here, newest first.

    Effect Office Hours 27: Alchemy, infrastructure as effects — edited: feat(learn): teach cards 23 to 42 with plain lines, diagrams and snippets

  4. Distilled. Sam Goodwin describes provider client libraries that return Effects and named error types under the Distilled name.

    See Effect Office Hours 27.¶

  5. Full agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
  6. Infrastructure as effects. Sam Goodwin relates application operations to infrastructure requirements in one typed program.

    The Stack declares cloud resources.¶

  7. Rat Stack lore | rat-stack. Short, source-grounded notes on the ideas and decisions behind rat-stack.
    Link context

    Effect Office Hours 27: Alchemy, infrastructure as effects — Sam Goodwin presents Alchemy as a system built with Effect for planning, testing, and deploying infrastructure.

  8. Source change history (log.md). The generated change log as Markdown.

    Effect Office Hours 27: Alchemy, infrastructure as effects — edited: feat(learn): teach cards 23 to 42 with plain lines, diagrams and snippets