---
title: "Introducing the Public Website: a waiting list with bounded replies"
summary: "A public waiting-list form and a tool-free email conversation, separate from the blog newsletter and member capabilities."
created: "2026-11-15"
updated: "2026-11-17"
revision: "4"
previous: "5c2df9e617b931bc15d195cacc2b5b7a76d3ac4c"
reviewedThrough: "db9c004f146ca49dc313bc6b0a28d308d0d4b824"
sourceDigest: "fc57af298e08d271143bbe0398372d04c0dec0ed16532ddf2b681e1748f9755f"
---

With this, your mind can offer a public waiting list and ask what a visitor wants to build, without lending that visitor the hosting mind's capabilities. The front page explains the product, accepts an email address and starts a small one-to-one conversation. It is not self-serve installation and it is not the blog's subscriber newsletter.

## A public page and a narrow handler

The apex and the `www` host reach the routing switch in `worker.ts`. Their root serves `homepage()` from `newsletter.ts`. Before the form, a visible notice says the software is early alpha, recommends a separate isolated Cloudflare account owned by the person, and asks them to have their coding agent explain the security model before starting. Preserve that warning when adapting the page; joining a waiting list is not an assurance about deployment safety. The module's filename is historical: the visible form now says waiting list. It posts to `/waiting-list`; `/newsletter` remains a compatibility endpoint. The ordinary HTML form needs no client-side JavaScript or new UI package. Shared CSS provides its appearance. No public reader receives an `itx` socket.


You can rebuild the route shape like this:

```ts
if (pathname === "/") return homepage();
if (pathname === "/waiting-list" || pathname.startsWith("/newsletter")) {
  return await newsletterFetch(request, itx) ||
    new Response("Not found", { status: 404 });
}
```

Validate the method, origin when supplied, bounded form body and normalized email on the server. Include a honeypot and request quotas, but do not confuse those with authentication. Derive a private lookup key from the address and claim initial delivery durably before sending. Store opt-out state and routing material privately; never publish the waiting-list records. Returning the same accepted page for repeat submissions keeps the interaction simple. A claim is not a delivery guarantee: record failures and do not blindly resend an uncertain message.

## Ask about a useful first result

The welcome email says the person is on the list and asks what they would use the product for. Joining does not create a mind, reserve a date or authorize an account action. This installation uses a personal walkthrough rather than sending new visitors through self-serve setup. `newsletter.md` supplies that conversation's limited guide. It asks one concrete question at a time, follows the answer and stops pushing once the intended use is understood or the person declines. It must not promise a place in the queue, a booking, prices or deadlines.

Replies reach a dedicated conversation address. Both current waiting-list addresses and the older newsletter-address form are consumed before ordinary member-mail routing, including messages that fail verification. Only a platform-verified, direct sender matching the stored address can continue the conversation. Automated and mind-generated mail do not count. The private routing token identifies a conversation; knowing it does not authenticate the sender.

## A phone conversation can join the same list

The separate public call guide in `sales-calls.md` now points callers to this waiting list rather than walking them through self-serve installation. The bridge can note one read-back address; a qualifying inbound call-ended event reaches `waitingListFromCall` in `newsletter.ts`. Code, not caller-selected tools, claims the event and applies per-call, per-address and global daily limits before a welcome. A separate tool-free model uses redacted call text for a short follow-up; fixed wording is the fallback. This is a private handoff, not permission to publish a transcript or add anyone to the blog newsletter. A spoken address is not authenticated: continuing the email conversation still requires the verified direct reply described above. Existing opted-out records are refused, and uncertain sends are not automatically repeated.

## Isolation is implemented in code

The response model is a tool-free request, not an ordinary full-mind agent. Its input is the public guide plus a bounded history of that person's conversation. It gets no repository, secret, member-search, browser, deployment or arbitrary-action tools. Credential-like text is redacted, input and output are capped, and outbound links are restricted. These measures do not turn a visitor's words into trusted instructions. Keep provider authentication in the vault, outside the model's messages.

The delivery code chooses the stored recipient, never Reply-To, Cc or model output. It claims each incoming delivery, limits replies, handles stop requests before calling the model and rechecks opt-out after the model returns. Leaving the list also has a confirmation page; reading that page does not itself change the subscription. The separate public phone feature follows `sales-calls.md`, not this form's authority. Caller ID cannot authorize sensitive actions.

## Rebuild and verify the boundary

A static front page needs no external account or secret. The conversation adds the mind's existing mail facility, an owner-controlled model account with a vault-held provider credential, private KV records and durable events. Adapt branding and walkthrough arrangements; do not copy another mind's contact details, subscribers, tokens or account configuration. Model and mail usage follow those providers' terms and charges.

Use synthetic records and fake delivery to test invalid forms, oversized bodies, repeat and concurrent submissions, spoofed and forwarded replies, changed Reply-To, automated messages, duplicate delivery, model failure and opt-out during generation. Confirm that public conversation mail can never fall through to a full-authority member agent. Test member routes independently: a successful public form submission grants no membership. [Mail](/introducing/mail) is a separate member-only inbox. [The blog](/introducing/blog) keeps its own subscriber list and sends only its trusted writer's eligible posts; joining this waiting list does not subscribe anyone to it.
