Add the FN-5756 ratification addendum to the executor/merger decoupling RFC.
- Record approval for dual-run dependency satisfaction via in-review or completion_handoff_accepted marker
- Require audit diff logging when legacy and new dependency signals disagree during dual-run
- Record approval to make merge back-pressure branch-group aware by default with global safety caps retained
Files changed:
docs/rfcs/FN-5719-decouple-executor-merger.md | 4 ++++
1 file changed, 4 insertions(+)
Fusion-Task-Id: FN-5756
Fusion-Task-Lineage: 54077cc9-a4ae-4462-99b0-4c28d06652cc
Record CEO ratification outcomes in the decoupling RFC and unblock follow-on implementation.
- Update RFC status from draft to ratified with FN-5746/date context.
- Clarify the CEO ratification gate language as a completed gating artifact.
- Add explicit approval decisions for persisted merge-request record storage and Phase-1 completion handoff marker.
- Mark follow-on task FN-5723 as unblocked.
Files changed:
docs/rfcs/FN-5719-decouple-executor-merger.md | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
Fusion-Task-Id: FN-5746
Fusion-Task-Lineage: bb71138a-4d05-4224-a34e-213783e20a9f
Add an RFC that defines a merge-request handoff seam to decouple executor completion from merger orchestration.
- Document current executor/merger coupling points and failure modes across store, scheduler, self-healing, and merger paths.
- Propose a decoupled merge-request state machine with explicit handoff ownership, queueing, lease boundaries, and autoMerge true/false flows.
- Map reliability invariants (including FN-5147 and FN-5704) to preserved/modified behavior and define phased rollout plus follow-on test strategy.
Files changed:
docs/rfcs/FN-5719-decouple-executor-merger.md | 149 ++++++++++++++++++++++++++
1 file changed, 149 insertions(+)
Fusion-Task-Id: FN-5719
Fusion-Task-Lineage: 4a13c088-48a5-4b37-a969-a8602d82da4a
