Every deploy writes its own changelog entry
A deploy to Giant Context finishes and the platform files a changelog entry for it. Nobody writes it, nobody approves it, nobody edits it. It is public at giantcontext.com/en/changelog.
How an entry gets made
The deploy succeeds
Every service that changed reports success.
CI records what shipped
The services that went out, the deployed commit, and the build number.
Brain resolves the range
It reads the commit the last entry ended on and takes everything since.
Commits are enriched
Each one is resolved to its pull request, and that request's body comes with it.
The model drafts
One pass for a short range, parallel chunks joined by a second pass for a long one.
The entry is filed
Against the build number, so it points back at the run that produced it.
Brain is never told what to write about. It asks the changelog where the last entry stopped and drafts everything between that commit and the one just deployed, so two entries cannot leave a commit between them.
A commit subject is written for whoever runs git log. Brain resolves each commit to the pull request that carried it and reads that request's body, which is where the change was already explained. The entries are drafted from the explanation rather than from the label, which is why they read as descriptions of features.
Thirty commits or fewer draft in a single pass. A longer range is cut into chunks of twenty that draft in parallel and are joined by a second pass, so a deploy carrying two hundred commits does not have to fit into one request.
The version is not semantic. It is the number of the build that deployed, so 1.108.0 names a specific CI run rather than a release somebody chose to call a minor. The entry is filed against that number, and a redraft of the same deploy updates it in place.
What reaches the page
If a deploy contains nothing a customer would notice, no entry appears. That follows from the content rather than from anyone's decision, so the page cannot be padded and cannot describe work that was not done.
Customers can follow progress as it is made, and anyone curious can see that Giant Context is real.
Building something like this
I'm Jesse. I build platforms end to end, and I'm open to work. If this is the kind of engineering you need, get in touch.