FN-5756: document ratified dependency and merge back-pressure decisions

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
This commit is contained in:
gsxdsm
2026-05-30 15:23:16 -07:00
parent cf88bab2cc
commit 784c58f5c3

View File

@@ -150,4 +150,8 @@ Per CEO directive, implementation must be coordinated with **agent-4ec1ff85** be
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**.
**FN-5756 Ratification Addendum (explicit, 2026-05-30):**
1. Q1 dual-run dependency signal: **APPROVED** to treat dependency as satisfied when **either** (`dep.column === "in-review"`) **or** a persisted `completion_handoff_accepted` marker is present; require audit diff logging whenever old/new signals disagree during dual-run.
2. Q4 merge back-pressure default scope: **APPROVED** as **branch-group aware by default** (instead of global), with global throttles retained only as safety caps.
Follow-on task filed: **FN-5723** (unblocked by this ratification).