Skip to main content

​
Decision: Reactivate wordis-bond (reverses 2026-06-10 sell-phase deferral, scoped)

  • Date: 2026-07-04
  • Status: ratified
  • Decider: adrper79 (founder), verbal approval 2026-07-04: “I approve the reversal and declaration update.”
  • Reverses (in part): 2026-06-10-sell-phase-action-plan.md — the line item “Touch wordis-bond, pricing experiments, or the AI-tokens SKU (all stay deferred per 2026-05-25).”
  • Supersedes: the WB portion of the 2026-05-25 alignment deferral.

​
Context

A 2026-07-04 audit found the governance record fully diverged from reality:
  • Factory docs recorded wordis-bond as an undeployed scaffold (cohesion 14/100 snapshot dated 2026-06-15, no service-registry entry, APP_SCOPE_REGISTRY “Planning / Not started”, LEGAL_OPS still showing the TCPA hold that was lifted 2026-06-08).
  • In reality the product is live in production: api.wordis-bond.com/health → 200 ({"status":"ok","worker":"wordis-bond","env":"production"}, verified by curl 2026-07-04), a React Studio SPA at wordis-bond.com (CF Pages project wordisbond), ~200 tests, a full CI/deploy pipeline with migration-drift gates, Sentry + PostHog server-side, six shipped feature waves (tenant isolation, analytics, reputation engine, voice personas, API keys, A/B testing), and a working Telnyx + Deepgram + Claude + ElevenLabs real-time voice engine.
  • What it lacks is everything commercial: no Stripe, no metering, no entitlements (the accounts.plan column is never read), an empty SPA shell for a homepage (no SEO/marketing/analytics), unverified free signup with real telephony COGS exposure, and a broken www. host (522).
Keeping WB “deferred” therefore preserves nothing — the build cost is already sunk and deployed. The remaining work is monetization, storefront, and abuse-gating.

​
Decision

  1. wordis-bond is reactivated for commercial buildout, scoped to Pillar A — Voice-AI Agent Testing (per wordis-bond/docs/POSITIONING.md): synthetic-caller testing, IVR assurance (Pillar B), and prompt validation (Pillar C) — use cases where the customer tests their own systems and the regulatory posture is clean.
  2. Pillars D (research/surveys) and E (dialer / spread-spectrum DID rotation) remain deferred and gated. Pillar E features stay out of public marketing, behind manual enterprise enablement only. The extraction plan’s TCPA/FDCPA/PII audit-and-abort discipline (docs/supervisor/plans/extract-from-wordis-bond.yml s2) carries over to all WB work.
  3. Execution is delegated to scheduled Opus cloud sessions working the phased plan at wordis-bond/docs/EXECUTION_PLAN_2026-07-04.md (Phase 0 hygiene → Phase 1 billing/metering → Phase 2 storefront → Phase 3 vending-machine ops).
  4. Stripe live-mode product/price creation for WB is authorized as part of Phase 1, after end-to-end verification in test mode. This is a recorded exception to the “pause on Stripe mutation” standing order, granted by the founder approval above.
  5. Governance records are corrected in this same change set: service-registry worker entry added, LEGAL_OPS stale-hold line fixed, APP_SCOPE_REGISTRY status updated, app-lifecycle entry filled in.

​
Non-goals

  • No change to the sell-phase plan’s other workstreams or the platform freeze as it applies to new packages/apps. WB reactivation spends effort on an already-deployed asset.
  • No AI-tokens SKU, no pricing experiments outside WB.
  • No outreach/campaign/blast marketing of WB features that dial third parties (Pillar E) — testing-your-own-systems only.

​
Review trigger

Revisit if: (a) Phase 1 not shipped within 30 days (2026-08-03), (b) any TCPA/consent question arises from a real customer use case, or (c) infra COGS for free-tier usage exceeds the configured spend ceiling two weeks running.