The plan model

A plan model describes infrastructure changes before they are applied.

Sam contrasts Alchemy’s earlier await-based model with a plan model. He says Alchemy v2 adopted output values that can connect to other resources before deployment. The engine can show the plan before those values become readable at deployment. Sam Goodwin on Alchemy, 26:00.

He also connects Effect purity with a reviewable plan and a concrete deployment result. Happy Path 116, 12:22.

See Sam Goodwin on Alchemy10 and Happy Path 1168.

Sources

  1. Sam Goodwin - Alchemy - YouTube. Sam Goodwin. Output-value discussion; used for connecting resources before deployment. Accessed 2026-10-01.
  2. #116 Infrastructure as Effects with Sam Goodwin - YouTube. Sam Goodwin. Pure-program discussion; used for a reviewable plan and concrete deployment. 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.

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

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

    The plan model — edited: feat(learn): teach cards 63 to 82 with plain lines, diagrams and snippets

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

    A plan model describes infrastructure changes before they apply.

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

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

  6. Sam Goodwin on Alchemy. Sam Goodwin explains Alchemy's Effect model, plans, bindings, and cloud-library idea.

    He compares Alchemy’s earlier await-based model with a plan model, which describes infrastructure changes before applying them.

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

    The plan model — edited: feat(learn): teach cards 63 to 82 with plain lines, diagrams and snippets