# bookd: brand pivot and day-one BOOKD release plan

Decision draft, 3 October 2026. The requested deliverable remains a working website prototype with researched launch architecture. This update makes **$BOOKD critical from the first activated business**, superseding Voxraft and the optional-later-token approach. Contracts are tested references; no mainnet token, liquidity position, customer payment or commercial identity client has been deployed.

## What the associated thread decided

The shared conversation [Create 10 Voxraft Brand Concepts](https://chatgpt.com/s/cx_6ac18018847081918f1b4999c821acce) was retrieved and analyzed, including its visible user decisions and brand references. The user chose bookd while acknowledging existing names in the booking/receptionist category, preferred **bookd.bot** to .services, and selected **$BOOKD**. The resulting direction is lowercase bookd; lime **#cff75e** on ink **#151a18**, with warm paper **#f6f6ef**; the lowercase b/booking-check mark; proposed @BookdBot; **“Your next job, bookd.”**; and **“Real work. Onchain rails.”**

The prototype applies these cues rather than reopening naming. Fresh RDAP says bookd.bot was registered today at 21:59 UTC; account ownership was not verified. X returned no public @BookdBot profile, which does not establish claimability. No CoinGecko coins or Dexscreener pairs matched BOOKD. Cash App $BookD is already occupied and is distinct from the token symbol. [Identity evidence and launchpad constraints](bookd-brand.md).

## Preserve the product

The source is a US trades front office: 24/7 intake, returning-customer context, emergency human routing, business-approved services and answers, Google Calendar availability, least-busy technician assignment, booking before hangup, confirmation/cancellation/reschedule SMS, crew schedules and time blocks, late-arrival updates, lead-recovery context, owner settings, recordings/transcripts and review requests. Invoicing/customer job-payment collection was advertised as future work; estimated booked value is not cash revenue. Reschedule requests initially require team approval because the public source makes conflicting promises. The [full 37-row feature audit](source-audit.md) distinguishes publicly observed interfaces, advertised private capabilities and future scope.

The prototype retains those journeys in sample form and adds required token access. A token withdrawal or expired usage period blocks new demo bookings/calls but leaves records visible. All payments, texts, calls, grants, token deposits and withdrawals are device-local simulations. Browser speech is a sample voice, not a live phone/AI service.

## Day-one token utility

**Business bond:** every standard tenant deposits **2,500,000 BOOKD** into its opaque tenant escrow. A valid dollar-funded service grant is also required. A merchant can approve treasury sponsorship, keeping ordinary card/USDC onboarding wallet-free. A self-funded merchant supplies the same units. Only the original depositor can recover them; sponsored tokens return to the restricted sponsor reserve. Starting an exit disables new service immediately. The proposed seven-day cooldown can receive one bounded review extension; administrators cannot seize this business deposit. Neither token price nor a wallet balance alone activates service.

**Operator capacity:** qualified operators post **100,000,000 BOOKD per whole block of 100 assigned tenant slots, including assignments whose paid period has expired until they are removed**. Operator consent and tenant assignment are checked; token ownership alone cannot authorize access to customer recordings or calendar credentials. The activation adapter combines the tenant bond, funded service grant and assigned operator capacity. Token inventory is not a substitute for actual voice-service load testing.

**Funded benefits:** reserve 5% of collected service revenue: 2% for incidents, 2% for verified acquisition and 1% for budgeted trials. No APY, equity/cash-flow entitlement, rewards for fabricated bookings, permanent free minutes or guaranteed dollar redemption. A performance-slashing and appeal policy is specified separately and remains unimplemented; do not describe capacity collateral as audited automated compensation.

This creates a required product role for BOOKD, but tokens are not technically necessary to operate a centralized phone service. Treasury sponsorship does not guarantee outside buyers or price appreciation. Measure retained paying tenants, useful bookings, cost and independently funded collateral rather than treating wallet activity as adoption.

## Supply and funding

Native **Clanker V4 on Base** fixes origin supply at **100B BOOKD** with 18 decimals. It is not an arbitrary 1B-supply launch. The token includes restricted Superchain bridge mint/burn mechanisms; publish canonical chain/address and actual authorities.

| Proposed allocation | Share | BOOKD |
| --- | ---: | ---: |
| Launch pool | 25% | 25B |
| Sponsored business capacity | 25% | 25B |
| Operator reserve | 15% | 15B |
| Team/builders | 15% | 15B |
| Integrations | 10% | 10B |
| Operating treasury | 5% | 5B |
| Contributors | 5% | 5B |
| Total | 100% | 100B |

Team vesting is a 12-month cliff followed by 48 months linear, not a large accumulated cliff release. Integrations use a three-month cliff plus 36 months; treasury six months plus 36 months; contributor rewards are bounded and verified. Native Clanker only has one vault allocation/schedule and requires a seven-day lock; the native airdrop has a one-day lock. The candidate 75% distribution uses reviewed restricted reserve/vesting recipients through a compatible native path, whose authority and claim behavior must be simulated before approval. These proposed allocations are not deployed balances or completed vesting contracts.

Immediate 100-tenant enrollment needs **350M BOOKD** bootstrap inventory: 250M business collateral plus 100M operator collateral, acquired from the configured approved market/dev-buy path. Locked allocations cannot fund it on day zero. Token-pool allocation does not prove USDC liquidity; liquidity funding, slippage, custody, fee recipients and locker permissions need actual review. A 25B sponsored reserve supports 10,000 standard bonds; 15B operator reserve supports 15,000 tenants under the proposed blocks. No automatic emissions or discretionary inflation are part of the model. [Complete tokenomics and stress scenarios](bookd-tokenomics.md).

## Dollar unit economics

Proposal: **$199/month**, 500 voice minutes + 300 SMS segments; additional minutes **$0.35**, SMS **$0.03**. All operating features stay included. This deliberately changes the source's unlimited-usage price, rather than asserting that volatile token holdings pay unlimited costs. The initial trial proposal is 14 days with 150 voice minutes and 50 SMS segments, funded before activation. The source’s 60-day trial could return only with a separately approved cash allowance and enrollment cap.

Planning assumptions, not quotes: combined voice/AI cost $0.08/min baseline or $0.18 stress; SMS $0.013/segment; allocated support/hosting $24; card plus Billing collection 3.6%+$0.30; cash benefit reserve 5% of service revenue. At full included usage, contribution is **$113.69 / 57.1%** baseline and **$63.69 / 32.0%** stress, after that reserve, before acquisition, taxes and central payroll. At 100 full-allowance subscribers, $19,900 revenue budgets $995 for benefits and yields $6,368.60 stress contribution. Replace assumptions with actual provider contracts and cohort data before pricing commitments.

BOOKD can later be a payment input only through executable bounded swap/settlement; usage is credited from USDC actually received. Fiat and USDC are funded via one server entitlement ledger, with verified webhook/chain events, unique payment IDs, refunds, cancellation and reorg handling. The prototype records grants without live payments.

## Reference implementation and production integration

The bundled contracts use OpenZeppelin and separate registrar, billing, sponsor, operator and administration roles. The tenant escrow checks exact token receipts, sponsor consent, tenant isolation, entitlement replay/expiry, deposits and withdrawals. The operator registry and composite activation adapter enforce the capacity condition. The custom 100B reference ERC-20 is local-only; production uses **one verified Clanker BOOKD address**, not a second public token. [Contract reference](protocol-readme.md) and [download](bookd-protocol.zip).

Production additionally requires tenant-scoped authenticated APIs, provider-signed phone/SMS/payment webhooks, live Google OAuth availability/reservation/recheck, idempotent event writes, consent/STOP/HELP, emergency-transfer failure fallback, private expiring recording URLs and deletion/retention settings. Phone numbers, transcripts, calendars, addresses and private incidents stay offchain. Caller ID is context, not sufficient authority for account changes. Funded grants remain privileged, so role governance and billing reconciliation are disclosed trust assumptions.

ChatGPT identity is a real limited commercial trial, not an available unrestricted phone-usage subsidy. Shared-plan preview excludes audio/transcription; optional API BYOK bills the customer's provider account separately and needs encrypted server-side custody. [Sources and detailed chain/identity plan](chain-identity.md).

## Release gates

1. Confirm selected domain/handle control and preserve the accepted identity.
2. Freeze canonical token/factory/locker, roles, reserve/vesting recipients, budgets and exact launch transaction plan; independently review and simulate allocation claims and bootstrap buys.
3. Deploy and verify utility contracts and funded restricted inventory **before activating the first live business**; record verified contract addresses and reconciliation health.
4. Complete end-to-end calendar, SMS, emergency, billing and chain-failure tests; enroll only a funded pilot cohort.
5. Expand within measured cost, service concurrency, sponsor capacity and benefits budgets. Operator performance penalties require a reviewed incident/appeal mechanism before being advertised.

The previous optional-token launch order is superseded. The product and BOOKD utility launch together; production deployment remains a concrete gated release rather than an assertion that a sample dashboard is live.


## Current implementation

The launch site and authenticated pilot application now use server-backed D1 persistence. Tenant settings are scoped to their signed-in owner. Native Sites ChatGPT identity is implemented for account access; this is separate from commercial usage sharing. Billing/provider adapters and a separate guarded WebSocket gateway are prepared but not configured or live. Production flags remain disabled. OpenAI Platform rejected creation of the approved Bookd key without returning a reason or a key. No Stripe, Twilio or Google Cloud account exists yet.

The release package is explicitly **unfunded**: signer wallets, cash/LP commitments and pilot activation size stay unset. 32 local protocol/release tests passed; 10 simulated tenants exercised 77 setup transactions and exit scenarios. There is no public Sepolia or mainnet transaction. [Unfunded deployment instructions](token-deployment.md), [download package](bookd-release-unfunded.tar.gz), [provider setup](provider-setup.md), [voice gateway source](bookd-voice-reference.tar.gz).