Happy Path 116: Infrastructure as effects

Sam argues that infrastructure tools can retain ordinary application-code properties such as debugging and tests. Effect gives Alchemy a pure program: it describes work before execution and can be planned first. The program carries resource requirements in its context. 03:50 12:22 24:52

He shows how runtime operations relate to explicit infrastructure policies and deployed resources. The compiler can check those relationships before deployment. 28:00 30:31 34:03

Sources

  1. #116 Infrastructure as Effects with Sam Goodwin - YouTube. Sam Goodwin. Recording; used for the relationship between Effect requirements, policies, and runtime behavior. Accessed 2026-10-01.

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

Linked from

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

    Happy Path 116: Infrastructure as effects — Sam Goodwin connects Effect requirements, infrastructure policies, and runtime behavior.

  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.

    Happy Path 116: Infrastructure as effects — edited: feat(learn): teach cards 43 to 62 with plain lines, diagrams and snippets

  4. Full agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
  5. Infrastructure as effects. Sam Goodwin relates application operations to infrastructure requirements in one typed program.
  6. Rat Stack lore | rat-stack. Short, source-grounded notes on the ideas and decisions behind rat-stack.

    Happy Path 116: Infrastructure as effects — Sam Goodwin connects Effect requirements, infrastructure policies, and runtime behavior.

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

    Happy Path 116: Infrastructure as effects — edited: feat(learn): teach cards 43 to 62 with plain lines, diagrams and snippets

  8. The plan model. Sam Goodwin describes Alchemy's plan outputs as a way to inspect infrastructure before deployment.

    See Sam Goodwin on Alchemy and Happy Path 116.¶