@absolutejs/voice 0.0.22-beta.236 → 0.0.22-beta.237
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +20 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -924,6 +924,26 @@ Use operations records instead of hosted call logs. A proof failure should link
|
|
|
924
924
|
|
|
925
925
|
Use simulation and contracts before live traffic. The simulation suite, tool contracts, outcome contracts, provider routing contracts, phone-agent smoke contracts, and production-readiness gates turn dashboard-only confidence into code-owned deploy evidence.
|
|
926
926
|
|
|
927
|
+
### Vapi Migration Checklist
|
|
928
|
+
|
|
929
|
+
Use this checklist when a buyer asks whether AbsoluteJS Voice covers the practical Vapi surface area without becoming a hosted platform:
|
|
930
|
+
|
|
931
|
+
| Vapi evaluation question | AbsoluteJS proof to show |
|
|
932
|
+
| --- | --- |
|
|
933
|
+
| Can I make a web voice assistant? | Framework page using `voice(...)`, then `/traces` and `/production-readiness` |
|
|
934
|
+
| Can I make phone calls? | `/phone-agent`, `/api/voice/phone/setup`, carrier matrix, and phone smoke proof |
|
|
935
|
+
| Can I use multiple assistants? | `createVoiceAgentSquad(...)`, `/agent-squad-contract`, current-specialist framework helpers, and handoff traces |
|
|
936
|
+
| Can I call tools/functions? | Tool definitions, `/tool-contracts`, audit events, integration events, and operations records |
|
|
937
|
+
| Can I debug a bad call? | `/voice-operations/:sessionId`, session replay, trace timeline, incident Markdown, delivery attempts, and provider decisions |
|
|
938
|
+
| Can I monitor production health? | `/production-readiness`, `/ops-recovery`, `/api/production-readiness/gate`, provider SLOs, and delivery runtime proof |
|
|
939
|
+
| Can I test before live traffic? | `/voice/simulations`, scenario fixtures, tool contracts, outcome contracts, provider routing contracts, and eval baselines |
|
|
940
|
+
| Can I run outbound campaigns? | `createVoiceCampaignRoutes(...)`, campaign readiness proof, carrier dry-run proof, retry/quiet-hours/rate-limit evidence |
|
|
941
|
+
| Can operators intervene? | Live-ops routes, action-center helpers, pause/resume/takeover runtime controls, and operator action audit history |
|
|
942
|
+
| Can I own compliance evidence? | `/data-control`, redacted audit export, retention dry-run/apply routes, provider-key recommendations, and customer-owned storage |
|
|
943
|
+
| Can I export logs to my infrastructure? | `/voice/observability-export`, delivery receipts, artifact index, replay proof, S3/SQLite/Postgres/file/webhook destinations |
|
|
944
|
+
|
|
945
|
+
The migration path should start by replacing hosted-dashboard concepts with mounted primitives and proof routes. Do not start by copying a hosted dashboard. Start with the voice route, operations record, readiness gate, provider contracts, and customer-owned observability export; then add campaigns, live-ops, or compliance controls only when the app needs those surfaces.
|
|
946
|
+
|
|
927
947
|
## Install
|
|
928
948
|
|
|
929
949
|
```bash
|