Skip to content

Post-Release Patch Pattern

The invariant that governs FCC's UAT hand-off, mirrored from the ecosystem convention and codified alongside the release cycle (../developer/release-cycle.md).

Invariant

The patch fixes FCC's own findings before the operator sees the build. The manual UAT that follows a hand-off is a confirmation pass over an already-corrected surface, not a discovery pass.

Concretely, before writing manual_uat_handoff.md:

  1. Run the executable probe contract (make uat-probe) against the live stack.
  2. Run the journey streams (make uat-streams) and the perf model (make uat-perf).
  3. Run the advisory vision pass (make uat-vision) where captures exist.
  4. Fix everything those surface that is in-scope for the patch.
  5. Only then write the hand-off — and honestly carry forward (with rationale) anything deliberately not fixed (advisory items, by-design behavior, deferred work).

What this is not

  • It is not a promise that nothing is imperfect — advisory findings (e.g. the v1.10.0 admin cold-start latency) are carried forward openly in §E of the hand-off, not hidden.
  • It does not gate on the advisory vision pass — vision is always advisory.

Cadence

Per the release cycle, from v1.10.0 onward every minor/major is followed by a hardening patch that re-runs and extends this UAT machinery, then produces a fresh manual_uat_handoff.md for the operator. v1.10.0 is the build-out that established the machinery and produced the first hand-off.

Current as of v1.10.0.