Core + Runtime + Actions
core@1.0.0-rc.1 · runtime@0.2.0-preview.5 · actions@0.2.0-preview.8
Packages
Download the complete private-preview bundle, install the SDK packages and try your first local example.
Checking your downloads…
Downloads are available to approved preview participants. Need a hand? Contact Support.
Core, Runtime and Actions form the primary integration path. Keep your existing business functions and add AnswerUp’s execution and recovery controls.
Use Node 22 or newer. Extract the ZIP into a downloads folder inside your application. The seven archives, README and manifest will sit together in that folder.
Extract the ZIP once. Leave the .tgz files as they are. npm installs the SDK packages directly—there is no need to open or extract each archive.
From your application’s root folder, install Core, Runtime and Actions:
npm install --ignore-scripts --offline ./downloads/answerup-core-1.0.0-rc.1.tgz ./downloads/answerup-runtime-0.2.0-preview.5.tgz ./downloads/answerup-actions-0.2.0-preview.8.tgzRuntime and Actions use ESM. No registry credentials are needed. Use the selected versions together. The command above installs the SDKs into your application; running the supplied example is a separate step below.
Start with the Generic HTTP reference. Its first-action example runs locally and demonstrates governed execution, a lost response and recovery through independent verification. You can try it before integrating the SDKs into your own application.
This companion example runs from its own folder. From the extracted bundle folder (the one containing the archives), unpack only the HTTP reference into a separate example directory:
mkdir http-reference
tar -xzf answerup-generic-http-reference-0.2.0-preview.4.tgz -C http-reference
cd http-reference/package/try-answerup/01-first-action
npm install --ignore-scripts --offline
npm startOn Windows, use a terminal with tar, or follow the archive-extraction option in the bundle’s README.
The SDK archives stay intact. This extraction step is for running the companion example, not for installing packages into your application.
Open the Generic HTTP first-action guide → for expected output and recovery steps. The bundle’s README contains the same runnable starting point.
All seven archives below are selected for this private preview. Use these exact versions together. This is not a public registry release or production-support commitment.
@answerup/runtime0.2.0-preview.5Execution lifecycle, identities, claim control and host-authorized recovery@answerup/actions0.2.0-preview.8High-level facade, outcome-aware plans, diagnostics, and reconciliation@answerup/generic-http-reference0.2.0-preview.4Recommended first example: local HTTP execution and recovery.Executable HTTP guide@answerup/retell-equipment-example0.2.0-preview.4Additional example: a local equipment reservation using Retell.Equipment example guide@answerup/trace-local0.1.0-preview.7Optional evidence viewer distribution; follow its guide rather than installing it with npm.Trace Local guideDiagnostics & Logging explains optional file logging and evidence inspection.
The ZIP is a convenient container for the original package files. Individual downloads are available under Your download. Check SHA-256 values if you want to confirm file integrity; manual verification is optional.
A checksum helps confirm a download matches the published manifest. Manual checksum verification is optional; it is not required to install the packages. If you choose to check and find a mismatch, download the file again before using it.
Save MANIFEST.sha256 alongside the archives. Compare against the manifest supplied by AnswerUp.
Get-FileHash .\answerup-core-1.0.0-rc.1.tgz -Algorithm SHA256Compare the displayed hash with that file's line in the manifest. Repeat for any other file you want to check.
sha256sum -c MANIFEST.sha256shasum -a 256 -c MANIFEST.sha256These checks compare files with a trusted manifest; they do not authenticate an unknown sender or prove that a business action occurred.
Current package set: Core rc.1, Runtime preview.5 and Actions preview.8. Try HTTP reference preview.4 or Retell adapter preview.3 with equipment example preview.4.
Retell preview.1 declarations describe the older Runtime preview.1 / Actions preview.2 line. Retell preview.2 uses a mock facade; HTTP preview.1 simulates bookkeeping. The older private HTTP source uses Runtime preview.3 / Actions preview.4. These are separate from the current runnable examples.
Examples use local test systems. They do not validate live providers, arbitrary crashes or distributed durability. Approved participants can use protected downloads.
Compatibility and references
core@1.0.0-rc.1 · runtime@0.2.0-preview.5 · actions@0.2.0-preview.8
@answerup/retell@0.2.0-preview.1 records a separate historical compatibility line with @answerup/runtime@0.2.0-preview.1 and @answerup/actions@0.2.0-preview.2.
Historical HTTP preview.1 simulates bookkeeping. A separate older host-owned reference implementation is pinned to @answerup/core@1.0.0-rc.1, @answerup/runtime@0.2.0-preview.3, @answerup/actions@0.2.0-preview.4, separate from the current package set.
Verify archives
Exact artifact, source, inventory, metadata, and declaration identities for independent verification.
The extracted-member inventory digest is SHA-256 of a UTF-8 manifest covering every regular file in the supplied .tgz. Members use their package/-prefixed POSIX paths in ascending raw UTF-8 byte order; each line is <member SHA-256><two spaces><member path>\n, including the final newline.
@answerup/core@1.0.0-rc.1 provenanceabc625dd0a68eabbf8044b9251fa797828b6a621ba20e2b71fd0336505b01c63664c4aade4f023bd77fd9108d773d8bb2546d62b · 43,232 bytes417378f5b858228f1d614376a8e4bf9939bd6c504a065a0736892242068c70b3c1298da88bf011c33d96025485ca7831f59a86e0df5131098a3e6477d22ab520b8d43e1dd306737f4979e65cb0f5a3a3391738c38571b8f4af712d3290cc8eea@answerup/runtime@0.2.0-preview.5 provenanceb800ccf3057332c8bae999d1a3c6e506b56a73af3d1f805f30199c498653a5cdd69d0b9df7bd2563ac79f87bdcb8d2ddda8a9336 · 27,856 bytesa1ce024d4adfdfe9c78645f79a1ea776cde5501f83bc7d0a8d86961786a5648023b3518689dded9b3ab38b9f00d2231552745c4489b7334bd286c9483db9b174edb2c11f3a16e73b173f1fdeff4c36b14acc962e543aff50149512b15b6d0963@answerup/actions@0.2.0-preview.8 provenance158c48c2acfb97337fb8b21016a43e19fc10bd762f0023f4ada2086e4d52f52149ac9061c5d1f99d4eda82c22ae88f7b46aebc30 · 22,347 bytes5438dd2231e3f41a8d84414f7749e0dc2223993fafc6e930f01056abdf53c41a0bca75bbda79565c58b299912a21c9bf36a06ddd324d35a4cb810bd32d812549a1e1ef1295ea740084b8cd9e1385a8694dfcfa7894247643be49122dcedc1052Retell: the preview.1 declarations describe an older package set. Use adapter preview.3 with Core rc.1 / Runtime preview.5 / Actions preview.8. The retained preview.2 mock example remains historical. The older package versions have not been validated with the current package set and remain reference-only.
Older private HTTP reference: source evidence at commit 839489149ee8ed9843f80133ae1838f492bf98b4 pins the private application-local implementation to Actions preview.4. That historical Core rc.1 / Runtime preview.3 / Actions preview.4 source has no established preview.8 compatibility. This does not describe the current HTTP reference preview.4 archive.