Developer Manual
Prerequisites
Confirm the current package set, runtime requirements, and host responsibilities.
Use the selected preview versions for this example. Find your packages, or try the package-free Lumber guided tour.
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.
Version history and scope
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.
Current package set
The current package tuple is Core 1.0.0-rc.1, Runtime 0.2.0-preview.5 and Actions 0.2.0-preview.8. The selected seven-archive private handoff also contains Retell adapter preview.3, Retell equipment example preview.4, Generic HTTP reference preview.4 and optional Trace Local preview.7. Core supports Node 20+ and CommonJS; use Node 22+ and ESM for the combined examples. Retell preview.1 declarations remain historical. Try the HTTP example.
Documentation, account creation and email-code sign-in are public. Google sign-in has been tested for a new account and a returning account, while other Google account-linking paths are not all independently verified. Microsoft personal-account sign-in remains unverified after a recorded Entra error. Account identity is separate from preview invitation, approval and package entitlement. The selected seven archives are supplied through approved private handoffs or protected Portal delivery after identity, invitation, agreement and active entitlement checks. They are not publicly available through a registry or unauthenticated download. If you have authorized access, follow the executable starting instructions.
Proven requirements
| Requirement | Current evidence |
|---|---|
| Core runtime | Node >=20, CommonJS |
| Runtime, Actions, Retell | Node >=22, ESM |
| Package imports | Package-root imports only |
| TypeScript examples | Consumer development-only typescript 5.8.3 and @types/node 22.15.30; use the quickstart's local tsc -p tsconfig.json npm script and exact compiler configuration |
| Operating system | No OS-specific requirement is established by the package authority |
| Provider access | Host supplies the provider integration and its credentials |
| Verifier access | Host supplies an independent read against the authoritative system |
| Identity and tenant scope | Host establishes requester, subject, tenant, account, and policy context |
| Persistence | Host-owned; no AnswerUp hosted database is supplied |
| Logging and retention | Host/operator responsibility; redact credentials and unnecessary personal data |
Provider SDKs, credentials, database engines, queues, hosted ingress, and production deployment are not package prerequisites established by the current portal authority. Treat them as integration decisions.
The example compiler and Node declarations are tooling for the consumer project only. They are not runtime dependencies of Core, Runtime, or Actions. The executable lumber quickstart supplies the minimal package.json, tsconfig.json, exact development-only tool versions, and package-local build command used by the quickstart, grounding diagnostics, and durable-recovery example.
Before production use
Decide how the host will persist lifecycle identities and evidence, coordinate multiple workers, handle process loss, rotate credentials, and schedule verifier-only reconciliation. The current process-local Runtime surface does not itself establish restart safety or exactly-once execution.