Skip to main content

It is Friday afternoon. An operator opens the changelog because something shifted in their dashboard during the week and they want to know whether it was them, the platform, or a teammate. The entry they need is the second one down — three lines, a thumbnail, and four PR links. They read it in under a minute. By the time they close the tab they know what shipped, who shipped it, and which page in the docs to read next. That is what a changelog is for.

A weekly record an operator can read on Friday afternoon. Each entry covers one week, lists what shipped, links the PRs, and tags the plan it belonged to. Reverse-chronological. Short. If you want the long-form migration guide for the architecture shift — Bridge retirement, .lobsterX retirement, workflow entity-model split — read Architecture migration history.

Weeks


How to read these

Each entry has a date header, a hero media slot, three to five lines of summary, bulleted highlights, and a plan-tag footer. The plan tags name the strategy plan and phase the work belonged to so you can trace any line item back to a written plan. Entries are written by whoever shipped the most code that week. They are not press releases. They are the truth as the engineer who lived through the week saw it on Friday afternoon.

Older

The migration guide for the pre-substrate-recast era — Bridge dispatch retirement, .lobsterX retirement, the workflow entity-model split — lives at Architecture migration history. Read it if you knew Forge before the shift and need the old-name → new-name mapping. See also: Design principles | Architecture overview