Home / Articles / Your own newsroom / Versions / v1.2.0
Your own newsroom: what changed in v1.2.0
From v1.1.0 (2026-10-15, b4d872995) to v1.2.0 (2026-10-16, 62d7d61bb), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 67 unchanged. About 30 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
25 unchanged paragraphs, under In short {#in-short}, Why a founder needs one {#why}, What you need {#need}…
1. Create the repository and turn on Pages. A new public repository, a README, and in Settings, Pages, choose GitHub Actions as the source. GitHub's guide covers it in five steps.
2. Add a workflow that validates before it publishes. This site's deploy workflow is the pattern: validate, then tag the release, then deploy. A small version is below. The rule that matters is that a failed check stops the release.
3. Write the house rules. One file at the root, CLAUDE.md, which Claude Code reads at the start of every session. A template is below. This is where your voice, your verification rules and your release steps live, and it grows by one line every time you correct the agent.
4. Connect a cloud session to the repository. At claude.ai/code, connect GitHub, choose the repository, and start a session. From then on you can do the same from your phone.
5. Give it the first brief. Paste the brief below. The agent sets up the folders, the article template, a small build script that turns Markdown into pages, and a validator, and publishes a first page about you.
6. Record, paste, review. Record a memo, paste the transcript into the session, and read what comes back on your phone. Correct it by voice. The agent changes it, rebuilds, validates, pushes, and checks the live page.
7. Add the meter. When there is something worth paying for, add the reader meter (next section).
8. Keep the record. Every article ends with what it does not claim and where it comes from; correctionsa arecorrection addedis ina new version of the open,article, dated;with its diff, not a note about the old one; every release gets a version and a one-line note.
9 unchanged paragraphs, under The house rules {#rules}, Who I am [Two paragraphs: your field, your years in it, what you are building and for whom.], The voice - Write as me, in the first person, from my voice memos, keeping my order and my phrases. - Plain words. British spelling. No em-dashes. Never overstate.…
Every article
- A title, a summary, "In short", the argument in sections,
"What this does not claim", and "Where this comes from".
- CorrectionsA arecorrection addedis ata new version: republish the end,article dated.as it should read now, and let the version history and its diff show what changed. Nothing is silently changed.
33 unchanged paragraphs, under Every release 1. Build and validate. Stop on any failure. 2. Bump the version and add a one-line release note. 3. Commit, push, and check the live page loads. ```, Readers who pay a little {#meter}, A behaviour policy for your agents {#policy}…