> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myclerkbook.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> What shipped and when, kept as one entry per release, newest first.

This page is the record of what has shipped. Newest first, one entry per
release, with no entry for anything that has not.

<Note>
  **myClerkBook is pre-launch, so the log has not started.** Its first entry is
  the first public release. Nothing is backdated into it and nothing is invented
  to fill it, because a changelog that describes work that did not ship is worse
  than an empty one.

  What is coming, and in what order, is the
  [roadmap](https://company.myclerkbook.com/roadmap).
</Note>

## What counts as an entry

A shipped change that you can see or use. That is the whole test.

* **Features and capabilities**, when they become available to you rather than
  when they are finished internally.
* **Changes to behaviour you already rely on**, including anything that moves,
  is renamed, or stops working the way it used to.
* **Fixes worth knowing about**, meaning the ones where you may have hit the
  problem and wondered whether it was you.

## What does not go here

* **Plans.** What is coming lives on the
  [roadmap](https://company.myclerkbook.com/roadmap), and keeping the two apart
  is what lets you trust this page as a record of fact.
* **Incidents and downtime.** Those go to
  [status.myclerkbook.com](https://status.myclerkbook.com), which carries uptime
  and incident history.
* **Internal work.** Anything you cannot see is not a change to you.

## How each entry is written

<Steps>
  <Step title="Dated, and in order">
    Newest at the top. The date is the date it reached you.
  </Step>

  <Step title="Named the way the product names it">
    A feature is called here exactly what it is called in the app and on the
    feature pages. One name for one thing, everywhere.
  </Step>

  <Step title="Linked to the page that documents it">
    Every entry points at the page explaining the thing it announces, and **an
    entry never ships ahead of that page**. If it is announced here, it is
    documented here.
  </Step>

  <Step title="Written once">
    A shipped feature produces one entry on this page and, where it is
    significant, one email. Never two independent write-ups that drift apart.
  </Step>
</Steps>

## Being told without checking

Significant releases go out as a **Feature Update** email from
`hello@myclerkbook.com`, which is product news rather than an alert about your
own money. It carries an unsubscribe link, and unsubscribing from it leaves your
account and alert emails untouched. See
[Contact support](/support/contact-support) for which address sends what.

If you would rather not receive it, this page is the same information without
the email.

<Card title="What is coming next" icon="arrow-right" href="https://company.myclerkbook.com/roadmap">
  The roadmap: the phases myClerkBook is being built in, and where each one
  stands.
</Card>