docs(blog): announcement - Agents as Effects (vision draft)#350
Closed
sam-goodwin wants to merge 3 commits into
Closed
docs(blog): announcement - Agents as Effects (vision draft)#350sam-goodwin wants to merge 3 commits into
sam-goodwin wants to merge 3 commits into
Conversation
Draft post that frames Alchemy as three layers (IaC, IaE, Agents as Effects) and lays out the autonomous-organization vision: agents whose prompts splice typed Output references via Output.interpolate, that modify themselves by editing code rather than calling imperative infra APIs. Grounds the shape in PR #293's ChatAgent DO and shows the bootstrap (coding agent pointed at Alchemy itself, Slack-shaped service of channels + people + agents).
Contributor
|
Install the packages built from this commit: alchemy bun add alchemy@https://pkg.ing/alchemy/167b169@alchemy.run/better-auth bun add @alchemy.run/better-auth@https://pkg.ing/@alchemy.run/better-auth/167b169@alchemy.run/pr-package bun add @alchemy.run/pr-package@https://pkg.ing/@alchemy.run/pr-package/167b169 |
Replace the technical-walkthrough draft with a conversational vision post organized around the three layers Alchemy stacks: Infrastructure-as-Code, Infrastructure-as-Effects, Agents-as-Effects. The narrative weaves the layers together (stack to worker to agent in one program) and lands on the unifying claim: source code is the only state the author manages, for human and agent alike.
…ergy Rewrite the announcement so the unifying principle - "as Effects" - is the spine of the narrative, not a side note. New section after the opening names Effect as the common substrate that lets the three floors actually stack. Each floor's prose now leans into how Effect-the-abstraction makes that floor possible: the seam between infra and runtime collapses because both are Effects; the agent moves in because it is one too. The "author no longer manages state. they declare it. the engine reconciles" sentence repeats deliberately, once per floor, as the central claim. Trimmed throughout for punch.
Contributor
Website Preview DeployedURL: https://alchemyeffectwebsite-worker-pr-350-uvzhxmw5wx72sdw7.testing-2b2.workers.dev Built from commit This comment updates automatically with each push. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft post that frames Alchemy as three layers (IaC, IaE, Agents as
Effects) and lays out the autonomous-organization vision: agents whose
prompts splice typed Output references via Output.interpolate, that
modify themselves by editing code rather than calling imperative infra
APIs. Grounds the shape in PR #293's ChatAgent DO and shows the
bootstrap (coding agent pointed at Alchemy itself, Slack-shaped service
of channels + people + agents).