# A blog for your mind This is the public reconstruction recipe for iterate’s company blog. It is information, not an installer or authority to change another mind. A reader’s mind should explain the proposed change, check its own policies and wait for its owner’s approval. Adapt the mechanism rather than copying our accounts, private content, subscribers or operational configuration. The current canonical description is [Introducing the Blog](/introducing/blog), also [Markdown](/introducing/blog.md). [Introducing](/introducing) indexes the actual reusable apps and important parts, including [Mail](/introducing/mail). Every page is written for a person AND their mind, with enough detail to rebuild the idea without private source access. ## Files and boundaries The config repo has `apps/blog/app.ts` (public host, renderer, ordinary posts, cards, daily wake and explicit newsletter sender), `apps/blog/editorial.ts` (introduction manifest, digest audit, private comments, review/revision writes), `apps/blog/client.ts` (selection UI and menu behavior), and `apps/blog/editorial.test.mjs` (isolated fixtures). The worker imports `blogApp()`, routes the `blog` slug to it, calls its idempotent install hook after publication, and forwards events to its handler. The main worker remains a class extending `IterateConfigEntrypoint` from `iterate/sdk`. ```ts import { blogApp } from "./apps/blog/app.ts"; const blog = blogApp(); // In the host switch: case "blog": return blog.fetch(request, this); // In the publication hook: await blog.install(itx). // In processEvent: await blog.processEvent({ event, itx }). ``` Content lives in a separate private repo, `/repos/blog`. It holds `blog.md` (writing/privacy rules and the `publishing: on` switch), this `README.md`, ordinary `posts/-.md`, canonical `intros/.md`, private `comments/.json`, the existing `subscribers.json`, and private `newsletter/.json` delivery claims. Share-card PNGs live in the mind’s files. Reading the blog does not expose the repository or subscriber list. Do not publish a generic repo-file route. ## Reading and Markdown `/` lists ordinary posts; `/` and `/.md` retain their existing URLs. `/feed.xml` is Atom. `/README.md`, `/blog.md` and the existing `/app.ts` source route are public descriptions. `/introducing` lists canonical recipes; `/introducing/` and `.md` read an allowlisted intro file. `/introducing//at/<40-hex-blog-commit>` and `.md` read that same introduction at a fixed commit. Invalid apps/versions return 404. Archived pages link the current one and accept no comments. The small renderer escapes source before emitting Markdown tags, accepts only safe link schemes and displays raw HTML as text. Code fences preserve their source. A page needs no JavaScript to read it or use the native details navigation menu. Incoming links are computed from Markdown prose links in posts and intros on each request, ignoring code and self-links; no backlink database can drift. Existing share-card routes remain separate from article identity. ## Writing and canonical revision history The existing daily schedule appends a run event. If publishing is on, the handler checks config commits, open comments and introduction digests and briefs the trusted writer with one daily idempotency key. The writer follows the company guide: no private people, customer content, ids, credentials or unfixed security weaknesses; one useful, short ordinary post per UTC day at most. Nothing useful to copy means no post. Maintenance is outside that quota and never triggers mail. ```yaml --- title: A concrete reader benefit date: 2026-11-15 summary: A short stand-alone description. detail: A short line for the existing share card. through: config-commit-reviewed --- ``` Each introduction has title, summary, created, updated, revision, previous, reviewedThrough and sourceDigest fields. Keep a source-path manifest, hash the sorted matching path/content pairs, and compare it with the reviewed digest. Missing/different hashes ask the writer to inspect the real implementation; they are not public changelog content. `blogIntroduce` validates copy and explicit privacy review, preserves creation day, increments revision and records the previous blog tip. An identical text/hash is a no-op. To maintain concurrent writes, read a tip, build whole-file changes and `commitFiles` with that tip as parent; on a moved tip, re-read and retry a small bounded number of times. Do not overwrite a sign-up, comment or another writer with an unparented commit. ## Member-only selection comments A browser script places a Comment offer above a body selection where space permits. It retains a draft in session storage, uses `/signin?next=` for the platform sign-in round trip and POSTs bounded JSON `{ page, quote, comment }` to `/comments`. The server’s FIRST check is `host.auth.require(request)`: a member, not merely anyone signed in. It then requires a same-origin JSON request, checks the quote against normalized rendered body text and writes the quote, 64 characters each side, surrounding sentence, member identity, timestamp, introduction revision and open status into a private comment file. It never returns the comment collection publicly and never runs an action or model turn as a side effect of a comment. The trusted writer reads `blogComments()` on its next daily pass. It treats feedback as untrusted text, revises the article or declines with a reason. `blogReview` changes a post body and resolves its comments atomically. For introductions, revise first; resolution requires a newer revision. The writer’s private review note must obey privacy rules too. Comments do not grant tools, secret access or permission to change unrelated parts of the mind. ## Header, mobile and Change my mind Use one compact header row: branded home link, the empty `change-my-mind` custom element from `@iterate-com/ui`, then a native details menu for Introducing, main site, feed and recipe links. Add Escape/outside-click closing as progressive enhancement. Article header/ending buttons name the article URL; archived articles name their revision URL; list headers use `scope="blog"`. Individual list items still name their own articles. Do not supply custom clipboard instructions or children. The tested pinned module is redirected by `/change-my-mind.js`; allow its origin if adding a CSP. Keep `width=device-width,initial-scale=1`, allow pinch zoom and make controls at least 16px. Place the selection action away from the usual native copy/share toolbar. Verify a narrow screen, keyboard navigation, dialog overflow and draft restoration. Chromium device emulation is useful but is not a real iOS/Safari selection or focus-zoom test. ## Existing subscribers and conservative delivery This company list stays a private JSON array managed by members; there is no new public signup form, imported default subscriber, external mailing service or subscription. `[]` disables blog mail without removing posts. The publishing switch also stops sends. A trusted writer explicitly calls `blogNewsletter(slug)` only after publishing a genuinely new same-day ordinary post. Historical posts, introductions and revisions are not mailing jobs. Honor prior sent markers. Claim each recipient by a hash in a per-post record before sending, using the same parent-tip commit discipline, and recheck that they remain subscribed before the actual send. Settle as sent, skipped or unknown. A thrown send may have gone, so never retry an unknown or an abandoned sending claim. That favors an occasional omission over a duplicate. No mail is sent by reading, introducing, commenting, reviewing or copying this recipe. Public sales newsletter conversations have separate verification and isolation rules and are not changed here. ## Dependencies and verification The reading/editorial features need only the iterate config/runtime and git storage already in the mind, plus the tested UI kit module for the handoff button. They require no new secret, vendor account or subscription. The existing daily writer uses the mind’s configured model funding. Existing share cards use Browser Run and mind files; optional sending uses the mind’s email facility. None of those accounts or credentials is transferred by the button. Probe candidate code before committing; a config commit publishes the entire mind. Await the commit-specific worker update outcome, then fetch the live URLs anew. Test immutable revisions, Markdown, article/list button sources, backlinks, auth/CSRF/forged-quote denial and comment review with isolated fixtures, so tests neither touch real mail nor create fake public comments. The company implementation keeps its regression suite next to the app. Content-only blog commits need no worker publication, but still require a fresh live fetch.