@absolutejs/voice 0.0.22-beta.212 → 0.0.22-beta.214

package/README.md

@@ -55,6 +55,33 @@ These are the primitive-first paths a Vapi-style buyer usually needs. Each path
 | Evals and simulation | fixtures, eval routes, simulation suite, workflow/tool/outcome contracts, baselines | Prove flows before live traffic | Opaque hosted test runner |
 | Data and compliance controls | file/SQLite/Postgres/S3 storage paths, redaction, retention, audit exports, guarded deletion | Show customer-owned storage and export proof | Legal certification or compliance attestation |
 
+## Proof Pack
+
+Use this checklist when a buyer asks, "How do I know this replaces a hosted voice dashboard?" Each artifact is a route, report, contract, or export the app owns. The point is not screenshots; the point is reproducible proof that can live in CI, an internal admin page, or a customer-facing demo.
+
+| Buyer question | Proof artifact | What it proves |
+| --- | --- | --- |
+| Can I launch a browser voice agent quickly? | `/voice`, framework mic/transcript UI, `/traces`, `/production-readiness` | Browser voice route, live transcript, trace persistence, readiness gate |
+| Can I run phone agents without hosted orchestration? | `/voice/phone/setup`, `/voice/phone/smoke-contract`, carrier matrix JSON | Carrier setup instructions, webhook/stream URLs, smoke proof, lifecycle traces |
+| Can I debug a bad call like a hosted call log? | `/voice-operations/:sessionId`, `/voice-operations/:sessionId/incident.md` | Transcript, trace timeline, provider decisions, tools, handoffs, reviews, tasks, audit, deliveries |
+| Can I test before production traffic? | `/voice/simulations`, tool contracts, outcome contracts, workflow contracts | Scenario/eval proof, tool idempotency/retry proof, business outcome proof |
+| Can I prove provider fallback and latency? | provider contract matrix, provider status UI, `/turn-latency`, `/live-latency` | Provider choice, fallback behavior, server turn timing, browser p50/p95 timing |
+| Can operators intervene safely? | live-ops routes, action center, ops action audit routes, operations record | Pause/resume/takeover, injected instructions, operator action audit trail |
+| Can I run outbound campaigns? | `/voice/campaigns`, `/voice/campaigns/observability`, `/api/voice/campaigns/readiness-proof` | Recipient import evidence, consent/dedupe checks, scheduling policy, worker-safe attempts |
+| Can I handle post-call workflow? | reviews, tasks, integration events, outcome contracts, operations record | Summary/review artifacts, task creation, webhook/sink delivery, matched session proof |
+| Can I keep data in my infrastructure? | `/data-control`, `/data-control/audit.md`, retention dry-run/apply routes | Customer-owned storage, redaction, audit export, guarded deletion, zero-retention planning |
+| Can I prove release readiness? | `/production-readiness`, `/ops-recovery`, delivery runtime, readiness profiles | Deploy gates for session health, audits, delivery queues, provider/campaign/phone proof |
+
+For a demo, the fastest convincing path is:
+
+1. Start a browser or phone session.
+2. Open `/voice-operations/:sessionId` for the session.
+3. Open `/production-readiness` and follow any linked proof surface.
+4. Open `/voice/simulations` or the relevant tool/outcome contract route.
+5. Open `/data-control` to show where retention, redaction, and audit export live.
+
+If those five surfaces are green and linked, the buyer can see the core difference from Vapi-style hosted orchestration: the operational proof lives inside the app, not in a vendor dashboard.
+
 ## Use-Case Recipe: Support Triage
 
 Use this path when you want a Vapi-style support assistant that can answer web or phone calls, look up customer context, route billing issues to a specialist, create follow-up work, and leave one debuggable call record. It is a recipe over primitives, not a support app kit.
@@ -717,6 +744,127 @@ For customer-facing exports, use the same redaction/export primitives as support
 
 This recipe covers the hosted-platform expectations that matter for meeting recorders: browser mic capture, live transcript UI, reconnect visibility, post-call review, transcript/debug record, readiness proof, customer-owned storage, retention controls, and redacted export paths.
 
+## Use-Case Recipe: Compliance-Sensitive Calls
+
+Use this path when the voice app handles sensitive customer support, healthcare-adjacent intake, financial workflows, internal investigations, or regulated customer data. AbsoluteJS Voice can provide self-hosted controls and evidence: customer-owned storage, provider-key ownership, redaction defaults, audit trails, guarded deletion, zero-retention policy helpers, redacted exports, and deploy gates. It does not certify the app for HIPAA, SOC 2, GDPR, or any other legal regime by itself.
+
+The production shape is:
+
+1. Use customer-owned runtime storage, preferably Postgres for production records and S3/webhook delivery for exported evidence.
+2. Keep provider keys in the app owner environment, not in a hosted voice dashboard.
+3. Pass `audit` into agents/tools/squads so provider calls, tool executions, handoffs, retention runs, and operator actions are recorded.
+4. Mount data-control routes for redacted audit export, retention dry-runs, guarded deletion, zero-retention planning, and provider-key recommendations.
+5. Make audit evidence, recent retention-policy evidence, and audit/trace delivery health part of production readiness.
+
+```ts
+import { Elysia } from 'elysia';
+import {
+	applyVoiceDataRetentionPolicy,
+	buildVoiceDataRetentionPlan,
+	createVoiceAuditLogger,
+	createVoiceDataControlRoutes,
+	createVoiceOperationsRecordRoutes,
+	createVoicePostgresRuntimeStorage,
+	createVoiceProductionReadinessRoutes,
+	createVoiceZeroRetentionPolicy,
+	exportVoiceAuditTrail,
+	renderVoiceAuditMarkdown,
+	voiceComplianceRedactionDefaults
+} from '@absolutejs/voice';
+
+const runtime = createVoicePostgresRuntimeStorage({
+	connectionString: process.env.DATABASE_URL!,
+	schemaName: 'voice_ops',
+	tablePrefix: 'sensitive'
+});
+
+const audit = createVoiceAuditLogger(runtime.audit);
+
+const app = new Elysia()
+	.use(
+		createVoiceDataControlRoutes({
+			...runtime,
+			audit: runtime.audit,
+			auditDeliveries: runtime.auditDeliveries,
+			path: '/data-control',
+			redact: voiceComplianceRedactionDefaults,
+			title: 'Sensitive Voice Data Control',
+			traceDeliveries: runtime.traceDeliveries
+		})
+	)
+	.use(
+		createVoiceOperationsRecordRoutes({
+			audit: runtime.audit,
+			htmlPath: '/voice-operations/:sessionId',
+			integrationEvents: runtime.events,
+			path: '/api/voice-operations/:sessionId',
+			reviews: runtime.reviews,
+			store: runtime.traces,
+			tasks: runtime.tasks
+		})
+	)
+	.use(
+		createVoiceProductionReadinessRoutes({
+			audit: {
+				require: [
+					{ type: 'provider.call' },
+					{ type: 'operator.action' },
+					{ type: 'retention.policy', maxAgeMs: 7 * 24 * 60 * 60 * 1000 }
+				],
+				store: runtime.audit
+			},
+			auditDeliveries: runtime.auditDeliveries,
+			links: {
+				audit: '/audit',
+				auditDeliveries: '/audit/deliveries',
+				dataControl: '/data-control',
+				operationsRecords: '/voice-operations/:sessionId',
+				traceDeliveries: '/traces/deliveries'
+			},
+			store: runtime.traces,
+			traceDeliveries: runtime.traceDeliveries
+		})
+	);
+
+await audit.operatorAction({
+	action: 'retention.policy.reviewed',
+	actor: { id: 'ops-admin', type: 'operator' },
+	outcome: 'ok',
+	resource: { id: 'zero-retention-policy', type: 'voice.retention' }
+});
+
+const zeroRetentionPolicy = createVoiceZeroRetentionPolicy({
+	...runtime,
+	audit: runtime.audit,
+	auditDeliveries: runtime.auditDeliveries,
+	traceDeliveries: runtime.traceDeliveries
+});
+
+const retentionPlan = await buildVoiceDataRetentionPlan(zeroRetentionPolicy);
+
+if (retentionPlan.deletedCount > 0) {
+	await applyVoiceDataRetentionPolicy({
+		...zeroRetentionPolicy,
+		dryRun: false
+	});
+}
+
+const auditExport = await exportVoiceAuditTrail({
+	redact: voiceComplianceRedactionDefaults,
+	store: runtime.audit
+});
+
+const redactedAuditMarkdown = renderVoiceAuditMarkdown(auditExport.events, {
+	title: 'Sensitive Voice Audit Export'
+});
+```
+
+For the actual agent or squad, pass the same `audit` logger into `createVoiceAgent(...)`, `createVoiceAgentSquad(...)`, or `createVoiceAssistant(...)` with explicit `auditProvider` and `auditModel` labels. That makes provider usage and tool execution visible in `/data-control/audit.md`, `/audit`, readiness checks, and operations records.
+
+The UI should expose `/data-control`, `/data-control.json`, `/data-control/audit.md`, `/data-control/retention/plan`, `/production-readiness`, and `/voice-operations/:sessionId`. Destructive retention application should remain a server-side operator action that first reviews the dry-run plan and then posts `confirm: "apply-retention-policy"`.
+
+This recipe covers the hosted-platform expectations that matter for compliance-sensitive voice apps: customer-owned records, provider-key ownership, redacted exports, audit evidence, guarded retention, zero-retention planning, deploy gates, and a clear boundary that the package supplies controls and proof artifacts, not legal certification.
+
 ## How This Differs From Hosted Voice Platforms
 
 Hosted voice-agent platforms are strongest when you want a managed dashboard, phone-number provisioning, hosted orchestration, and campaign tooling out of the box.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@absolutejs/voice",
-	"version": "0.0.22-beta.212",
+	"version": "0.0.22-beta.214",
 	"description": "Voice primitives and Elysia plugin for AbsoluteJS",
 	"repository": {
 		"type": "git",