With this, your mind can explain its own changes as recipes another mind can rebuild. A person reads the story; their mind reads the same page as Markdown. Neither reader needs access to our private repository. The Change my mind button is a handoff for an explanation and the owner’s approval, never a remote installer.

Keep publishing separate from the application

apps/blog/app.ts serves the public blog host through the routing switch in worker.ts. Posts live in a separate private repo, /repos/blog: posts/<day>-<slug>.md, blog.md for writing rules and the publishing switch, README.md for the public recipe, and subscribers.json for the existing opt-in list. The blog reads the content at request time. Its small Markdown renderer escapes source characters before producing tags, so raw HTML is displayed as text rather than executed. Existing posts stay at /<slug> and /<slug>.md; /feed.xml stays an Atom feed.

import { blogApp } from "./apps/blog/app.ts";
const blog = blogApp();
// Public reading only; comment writes have their own member guard.
case "blog": return blog.fetch(request, this);

install retains the existing daily schedule. The daily handler reads config commits since the last covered commit and wakes the trusted blog writer at most once per run day. The writer reads the local guide, skips days without a useful copyable change, and writes at most one ordinary post per day. Existing company prose stays short, starts with what the reader’s mind gains, and excludes private people, customer content, credentials and operational identifiers. A code-level privacy check catches common contact and credential shapes in editorial API writes, but it cannot replace a line-by-line review.

One canonical introduction per app or important part

apps/blog/editorial.ts owns the manifest of app names and the source paths that count as changes. It hashes those source files and compares the hash with each introduction’s sourceDigest. blogAudit() returns missing, current or review-needed pages to the writer. A source change is a request to check the recipe, not permission to print a diff. blogIntroduce validates a reviewed narrative recipe, commits intros/<app>.md with the title, summary, creation day, update day, revision, reviewed config commit and source digest, and keeps the previous blog commit in previous. Identical content and digest do not produce a commit.

await itx.config.blogIntroduce({
  app: "mail",
  title: "Introducing Mail: a read-only inbox",
  summary: "A member-only view of recorded email.",
  body: narrativeRecipe,
  privacyReviewed: true
});

The index is /introducing. A current page is /introducing/<app>; add .md for its source. /introducing/<app>/at/<blog-commit> reads that same allowlisted introduction file at an immutable commit, with a matching .md route. Only introduction files can be read by this route; it is not a public repository browser. A previous-version link and a current-version link make the distinction visible. Archives are read-only. Introductions and revisions are outside the ordinary post quota and never trigger newsletters.

Comments are feedback, not orders

apps/blog/client.ts progressively enhances the article body. A selection offers a Comment button above its first line, falling below its last line only when space is short; this avoids the usual location of the native mobile selection bar. Sending goes to /comments, whose first check is the platform’s member guard, not a home-grown login cookie. /signin?next= uses that same guard and returns only to a validated local path. A draft survives the round trip in session storage.

The server requires same-origin JSON, bounded inputs and a quote actually present in the rendered article body. It writes a private comments/<id>.json with the quote, surrounding context, member identity and open status. It does not wake an agent or act on the text. The next daily writer uses blogComments() and treats every comment as untrusted feedback. blogReview can decline with a reason or atomically revise an ordinary post and address its comments. Introduction comments can be addressed only after a new revision exists. All repo writes use the tip as parent and retry only if it moved, so a comment cannot overwrite a writer’s commit.

The page and the mail boundary

The branded home link, article-specific Change my mind button and native details menu share one compact header. Secondary links live in the menu. Escape closes it and restores focus; clicking outside closes it too. The viewport allows pinch zoom, and all inputs are at least 16px to avoid iOS focus zoom. Articles link to their Markdown and show incoming links computed from the other pages’ prose links, excluding code and self-links. A list header targets the whole blog; an article header and footer target that article, including an archived revision.

The existing subscriber list is not a signup service and is never public. No account is connected when a reader copies a recipe. Blog mail is still the trusted writer’s explicit call for a newly published same-day ordinary post. The publishing switch stops sends too; historical posts and introductions cannot be mailed. Delivery now claims a hashed recipient in a private per-post record before sending, respects old sent markers, rechecks subscription and never retries a sending or unknown result. If a send throws, it may have gone. That conservative trade can omit a message but avoids duplicates. Subscriber editing remains a member’s existing workflow; we did not import another mind’s subscription form or recipients.

Dependencies and how to rebuild it

The reading site needs the iterate config loader and its existing git repos; no new external account or secret is needed. The pinned @iterate-com/ui module supplies the empty Change my mind custom element, with no custom prompt text. Existing share cards use Browser Run and mind files, not a new image subscription. A daily writer needs the model access this mind already uses; sending needs the mind’s existing email facility. Adapt those separately rather than copying our accounts. The public recipe gives the route, schema and workflow contract. Mail, Agents, the voice room and the install wizard are examples of the app recipes this system maintains.