Developer Manual
Package guide
Choose the package surface and import boundary for your integration.
Use the smallest package surface that matches the integration. Exact exports and signatures remain in the API Reference.
| Package | Use it for | Depends on | Status |
|---|---|---|---|
@answerup/core 1.0.0-rc.1 | Core grounding, authorization, identities, effect resolution, and claim contracts | None | Private Preview |
@answerup/runtime 0.2.0-preview.1 | Process-local lifecycle orchestration, execution, reconciliation, and projection | Core 1.0.0-rc.1 | Private Preview |
@answerup/actions 0.2.0-preview.2 | Protected-action façade and bounded Actions results | Runtime 0.2.0-preview.1 | Private Preview |
@answerup/retell 0.2.0-preview.1 | Offline Actions-only translation at the Retell tool boundary | Actions 0.2.0-preview.2, Runtime 0.2.0-preview.1 | Private Preview |
Import boundary
Use supported package-root imports only:
import * as Core from '@answerup/core';
import * as Runtime from '@answerup/runtime';
import * as Actions from '@answerup/actions';
import { createRetellAdapter } from '@answerup/retell';Do not import workspace paths, declaration snapshots, test helpers, or package internals. The declarations used by this portal are authoritative evidence for the API pages, not an installation channel.
Selection guidance
Start with Core when you need direct lifecycle control. Add Runtime for process-local orchestration and reconciliation. Add Actions for the protected-action façade. Add Retell only when translating a Retell custom-tool boundary into bounded Actions calls. None of these packages supplies hosted persistence, provider credentials, a provider SDK, or a general framework adapter.