Alchemy lineage
The Alchemy repositories and patterns that shaped Distilled.
Distilled follows patterns learned from Alchemy’s real repositories, not a clean-room approximation. We inspected their current code, release workflows, source mirrors, and generated SDKs before extending the pattern to Jira, GitHub, and Slack.
Runtime compatibility is governed by ADR-001: the shared package targets Alchemy parity, while local deviations require an explicit, tested justification.
Core references
alchemy-run/distilled
Shared Effect-native runtime, traits, generators, and provider packages.
alchemy-run/distilled-spec-neon
A concrete example of isolating and curating an upstream API specification.
alchemy-run/distilled-neon
A generated provider SDK that pins its spec repository as an explicit input.
alchemy-run/actions
Shared CI and release conventions, including modern npm trusted publishing.
alchemy-run/node-utils
Dual Bun/Node package exports and TypeScript’s relative-import rewriting pattern.
Original architecture note
The initial study that motivated this standalone factory.
Patterns we retained
Separate the source from the implementation
A curated API source can evolve on its own without mixing generated code and upstream history.
Commit generated operations
Generator changes and source updates remain visible in normal code review.
Offer source-first and compiled exports
Bun consumes TypeScript directly while standard Node receives compiled ESM and declarations.
Publish with workload identity
GitHub Actions exchanges OIDC identity with npm; long-lived publish tokens are disabled.
Where this factory differs
Alchemy’s collection optimizes for its own provider fleet. This project uses standalone repositories under one account and applies a source decision rule per API: mirror maintained OpenAPI, extract a compact authoritative bundle when upstream history is too large, or generate from an official typed SDK when OpenAPI does not exist.