Architecture

The SDK is built around clear module boundaries. Each module has one responsibility, and dependencies flow in one direction. Subpath exports mirror those boundaries, so the package surface enforces the architecture and enables tree-shaking.

​

Subpath exports

Consumers reach internals only through documented subpaths: Deep imports into unpublished paths are not supported. If something is not reachable through a subpath, it is not part of the public surface.

​

Dependency direction

Cross-module dependencies flow downward only. Core defines interfaces; everything else depends on core, never the reverse.

• core depends on nothing else in the package.
• schemas is standalone (used at the type level elsewhere).
• generators and prompt-optimizer depend on core and schemas.
• adapters/* depend only on core’s interfaces.

This is why importing the core package pulls in zero bytes from an adapter or the ai peer.

​

Vendor isolation

zod and ai are peer dependencies, never direct dependencies. Vendor SDKs live only inside adapter subpaths. The core never imports a vendor SDK directly, so you can plug in a custom inference path by satisfying the LanguageModel contract without pulling in an ecosystem you do not use.

​

Isomorphic by default

The default and browser builds carry no Node-only built-ins. Node-only code (for example, the local Markdown loader in generators) is reachable only through the package’s node conditional export. In a browser build, those Node-only paths resolve to stubs that throw a clear error, so you choose an isomorphic alternative instead. This keeps the path open to in-browser evaluation flows while still offering Node conveniences where the runtime supports them.

​

Related concepts