FN-5746: ratify executor-merger decoupling RFC

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
This commit is contained in:
gsxdsm
2026-05-30 14:55:26 -07:00
parent 20c1c3261e
commit 3a6820422b

View File

@@ -2,7 +2,7 @@
## Status
Draft for CEO ratification (agent-4ec1ff85). No implementation in this task.
Ratified by CEO gate (FN-5746, 2026-05-30). No implementation in this task.
## 1) Current coupling and failure modes
@@ -144,6 +144,10 @@ Rationale: strongest observability, replayability after restarts, clean ownershi
### CEO Ratification Gate
Per CEO directive, implementation must be coordinated with **agent-4ec1ff85** before any engine change lands. This RFC is the gating artifact; follow-on implementation remains blocked pending ratification.
Per CEO directive, implementation must be coordinated with **agent-4ec1ff85** before any engine change lands. This RFC is the gating artifact.
Follow-on task filed: **FN-5723** (blocked pending this ratification).
**FN-5746 Ratification Response (explicit):**
1. Dedicated persisted merge-request record/table (not task-row JSON): **APPROVED**.
2. Phase-1 explicit persisted `completion_handoff_accepted` marker keyed to `taskId`: **APPROVED**.
Follow-on task filed: **FN-5723** (unblocked by this ratification).