---
title: "Introducing the Public Website: a small front door with bounded replies"
summary: "A public introduction and opt-in conversation flow that does not lend a visitor the hosting mind’s capabilities."
created: "2026-11-15"
updated: "2026-11-16"
revision: "2"
previous: "d6e46fb5188b884a579dde8a5cb5a38b1a065ca4"
reviewedThrough: "5c10ea7ea0c957fc4dd594e85b009495b50f01aa"
sourceDigest: "21aacd2eae41456f14c801feecf08ae90e4e85be120f39e249fa1f1a73cdf212"
---

With this, your mind can offer a public front door without putting a full-mind agent behind the contact form. The website explains what iterate is, links to getting a mind, and has its own opt-in newsletter conversation. That public conversation is intentionally separate from this blog’s private subscriber list and trusted daily writer.

## Public reading, bounded writing

`worker.ts` serves the apex and `www` through `homepage()` in `newsletter.ts`. The same module handles the public newsletter routes; `newsletter.md` is the limited conversation guide and `newsletter-operations.md` describes its mail boundary. The homepage is ordinary server-rendered HTML using the shared theme. The platform still owns sign-in and membership. A visitor can read the site without gaining a member socket, access to a repo or a general-purpose tool.

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

The handler validates email input, keeps private subscription state and uses claim records for actions that must not repeat. It consumes mail to its public conversation addresses before ordinary member-mail routing. A reply is eligible only when the platform reports a verified, direct sender matching the subscriber; automated or mind-generated mail is not treated as a new person’s instruction. Reply-To and copied recipients cannot redirect the response. Unsubscribe requests are handled as stop requests, not an opportunity for another sales message.

## Isolation is code

The public response path has no repo, secrets, member-data search or arbitrary-action tools. It uses only approved public product information, caps and redacts text, and restricts outbound links. Any public calling feature belongs to the separate `sales-calls.md` boundary; caller ID is not authentication. A blog recipe cannot authorize weakening any of those checks. Even a verified sender may ask a hostile question, so verification and capability isolation solve different problems.

## Adapting it

Build the static page first. If adding opt-in replies, define the verified-sender contract, immutable recipient selection, unsubscribe behavior, action claims, storage and limits before connecting a model or a mail sender. The basic page needs no secret or external service. The conversation requires the mind’s existing email facility and an appropriately restricted model path; phone service is optional and separate. Never copy this company’s recipient state, public contact details or account configuration as part of an installation. Test forwarded mail, spoofed senders, Reply-To changes, duplicate deliveries and unsubscribe. [Mail](/introducing/mail) is an entirely different member-only view of recorded messages; [the blog](/introducing/blog) publishes descriptions, not public tool authority.
