Skip to main content

​
What’s Changed

This page is the derived narrative layer over Flux’s shipped changes. The authoritative record is always the chain PRD → RFC → Cycle → PR → code (see the AI-Native Manifesto §10); changelog entries here are summary narratives that link back to the authoritative artifacts for every claim they make.

​
Current state (April 2026)

The changelog page is scaffolded here as part of Cycle 214’s Mintlify foundation. The autonomous pipeline that will populate it is proposed in Cycle 451 but has not yet shipped. Until Cycle 451’s code PR merges, the operational release-communication surface is:
  • PR descriptions on the merged PR
  • Cycle 400’s /changelog Slack digest (daily cron, team-facing)
  • Cycle docs in docs/roadmap/cycles/ for the “why”

​
Planned (when Cycle 451 lands)

On every PR merged to main, a GitHub Action will run a three-pass Claude synthesis (Facts → Narrative → Verifier) grounded in the diff + cycle doc + Playwright screenshots, with a deterministic anti-slop guard. The resulting MDX entry will be committed here; Mintlify will auto-deploy. On verification failure a follow-up PR will open with a draft for human polish — the original merge is never blocked. Each entry will link back to:
  • The PR on GitHub (authoritative diff + review history)
  • The cycle doc that motivates it (authoritative “why”)
  • Specific file:line anchors on GitHub (authoritative “what”)
  • The preview or staging URL so you can try the feature
The changelog is secondary to those links — if an entry and the linked PR disagree, the PR wins.

​
For AI agents

Once the Mintlify site is live and the auth model for MCP / llms.txt access is confirmed (the site is gated by Google Workspace OAuth; MCP access for AI agents requires either a Mintlify API key or a public carve-out for /mcp and /llms.txt), this page and every future entry will be queryable via the auto-generated MCP server. Until then, agents should read the authoritative sources directly:
  • gh pr view <N> or gh pr list --state merged for what shipped
  • docs/roadmap/cycles/cycle<N>-*.md for the plan behind each merge
  • git log for raw history
The first autonomous entry will appear here when Cycle 451’s implementation lands and the next PR merges to main. Until then, this page describes the surface that will hold those entries.