Packages and entry points

Five public packages, their root APIs, and the subpaths for specialized work.

Pick the smallest entry point that does the work. Each package root covers the common jobs; specialized APIs live on explicit subpaths.

Package	Root provides	Documented subpaths
`@varendo/core`	Contracts, typed parsers, `defineResource`, `compileIntent`, primary types	`app`, `agent`, `contracts`, `expressions`, `features`, `interaction`, `plot`, `presentation`, `query`, `schema`, `schemas/*`, `semantics`, `visualization`
`@varendo/runtime`	`createAeliqoRuntime` and runtime types	`actions`, `app`, `audit`, `data`, `evaluation`, `interaction`, `meaning`, `persistence`, `presentation`, `regions`, `results`, `scopes`, `surfaces`
`@varendo/web`	Element registration and recipe policy types	`app`, `server`, `region`, `recipes`, `register`, `events`, `styles`, `table`, `chart`, plus the family and component entries below
`@varendo/react`	Provider, Region, render and surface hooks, element registration	`app`, `surface`, `ssr`, `foundation`, `inputs`, `navigation`, `feedback`, `data`, `plot`, `visualization`, `compound`
`@varendo/agent`	`createAppToolEndpoint`, `createAppToolSession`, and host session types	`app`, `browser`, `capabilities`, `mcp`, `meaning`, `model`, `model/openai`, `model/responses`, `protocol`, `session`, `webmcp`

@varendo/web also publishes family entries: foundation, inputs, navigation, feedback, data, plot, visualization, and compound. Grouped entries cover visualization/temporal, visualization/cartesian, visualization/hierarchy, region/adaptation, foundation/manifest, and inputs/manifest. Each catalog component imports from its own subpath, such as @varendo/web/text-field or @varendo/web/search-results.

The dependency direction is core → runtime → web → react. agent may depend on core and runtime. The public site may consume all five packages; package code never imports the site.

Runtime boundaries

core has no browser, network, or application-state dependency.
runtime does not access the DOM. Supply data and business effects through host adapters.
web owns custom elements and browser registration. Its root is safe to import without the runtime package; call registration from a client boundary. The application facade is available from @varendo/web/app and requires @varendo/runtime.
react delegates rendering and behavior to web; import wrappers from the family subpaths. The package requires React 19 and the matching @varendo/runtime peer.
agent receives bounded host capabilities and cannot grant access or add a renderer.

Install all five packages on the same exact release when an application uses them together:

Shell example

npm install --save-exact \
  @varendo/core@0.1.0 \
  @varendo/runtime@0.1.0 \
  @varendo/web@0.1.0 \
  @varendo/react@0.1.0 \
  @varendo/agent@0.1.0

Component-only consumers can install only @varendo/web; skip @varendo/agent when no agent connects.

Varendo 0.1.0 is the published stable release. Install all Varendo packages at the same exact version.

The historical 0.5.0-rc.1 was published from an earlier source revision. It does not contain the React local data path documented here. Do not mix package versions or treat an earlier RC as evidence for the current source. Wire contract version "1" is independent of either npm version. See the 0.3 to 0.4 migration guide for older integrations and the 0.4 to 0.5 migration guide for that transition. Use release notes for changes after 0.5.

Runtime boundaries#

Runtime boundaries