---
title: Updates
description: What changed in Else, reported one week at a time. Only changes that are live for everyone, written as what you can do now.
---

{/*
  HOW TO ADD NEXT WEEK'S REPORT — read this before touching anything here.

  ONE FILE PER WEEK. No weekly file is ever edited after its week closes; a
  later correction becomes an entry in a later week, named as a repair.

  0. WHERE THINGS LIVE. This page is `content/updates.mdx` and it is the tab's
     landing page at `/updates`. The weekly reports are `content/updates/*.mdx`.
     Do NOT move this page to `content/updates/index.mdx`: `reed check` accepts
     the PageRef `updates/index`, but the build then fails with "The slug
     `updates/index` ... does not exist", because a nested index file's real slug
     is `updates`. Sibling file, directory of weeks — that is the working layout.

  1. FILENAME. `content/updates/<Monday of that week, YYYY-MM-DD>.mdx`. Weeks
     run Monday to Sunday. A change that landed on Sunday belongs to the week
     that started six days earlier, not to the week beginning the next day.

  2. FRONTMATTER. Exactly two fields, nothing else:
       title: Week of <Month D, YYYY>     (the Monday, spelled out)
       description: <one sentence naming what the week actually gave people>
     Never put an `# H1` in the body. The page heading comes from `title`, and
     a body H1 is a hard `reed check` failure (DS-A02). Body headings start at `##`.

  3. SHAPE OF THE FILE, in this order and no other:
       a. Two or three paragraphs of narrative — what you can do this week that
          you could not do last week, and what got more reliable. Complete
          sentences addressed to the reader. Not a list of headings, not a
          summary of what we rebuilt.
       b. `## What changed`
       c. One `###` block per change, newest first. Each block is: the `###`
          title, then a single bold date-and-tag line `**Jul 28, 2026 · New**`,
          then one or two short paragraphs. Nothing else varies.
       d. Optionally a closing `## What is next` — but ONLY for work already
          announced in a published page of this site. Never a promise of a
          feature. If there is nothing true to say, the section does not exist.

  4. TAGS. New = did not exist before. Better = existed, now better.
     Fixed = was broken or quietly degraded, now works.

  5. WIRE IT UP. Add the new page to `docs.json` under the Updates tab, in its
     month group, above the previous week. Create the month group if the month
     is new. Then add a row to the list on this page, newest first. A file that
     is not in `docs.json` is a build failure, not a warning.

  6. INTERNAL LINKS are relative to the site base and must never carry a
     `/docs` prefix: write `[Spending limits](/docs/spending-limits)`, because reed
     adds the prefix itself. A `/docs` prefix resolves to `/docs/docs/…` and 404s.

  7. CONTENT RULES, non-negotiable:
     - Only list something that is live for everyone and that a person can
       notice. A finished plan is not a shipped change; when in doubt, leave it out.
     - Write what a person can do now, never what was rebuilt.
     - Use the product's own vocabulary, never the internal engineering words
       for the same things. DESIGN.md, section Language, is the binding list.
     - Never name a supplier, a routing decision, or a cost structure.
     - A price never appears alone: an amount must be paired with the engine
       tier it depends on, or be left out entirely. Never hand-type a per-model
       rate — link to [Model prices](/docs/model-prices) instead.
     - No exclamation marks. State it and move on.
*/}

Else changes every week. This is the record of it, one report per week, newest
first. Each report opens with what the week actually gave you and then lists the
individual changes with the date each one landed.

Two rules govern everything here. Nothing appears until it is live for everyone,
so work we have finished but not shipped stays off the list. And repairs are named
as repairs — if something was quietly not working, the entry says so.

## July 2026

- [Week of July 27, 2026](/docs/updates/2026-07-27) — Handed-off work comes back with
  finished files again, the receipt is written in your terms, and you can connect
  an app yourself with a key from it.
- [Week of July 20, 2026](/docs/updates/2026-07-20) — Every built-in add-on gained real
  work behind it, the engine menu got four honest names, and the settings you choose
  for a conversation stay put.