root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-4813): complete Step 6 — document mutex handoff and runtime scope

Browse Source 
Fusion-Task-Id: FN-4813
Fusion-Task-Lineage: 846893a5-2afa-4817-8f64-8c444d2fd713
This commit is contained in:
Fusion (runfusion.ai)
2026-05-16 17:13:46 -07:00
committed by gsxdsm
parent b81bfacf07
commit 7a5739faea
2 changed files with 39 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/shared-mesh-protocol.md
View File

@@ -13,10 +13,12 @@ This document is the canonical contract for Fusion multi-leader mesh replication
- Support deterministic replay/reconciliation after recovery.
- Expose read staleness so clients can decide whether to trust last-known global state.
### Non-goals (for v1)
- Full runtime scheduler failover.
- Full live-process state migration.
- Immediate global consistency for every data class.
### Runtime scope and non-goals (v1, updated for FN-4772/FN-4813)
- `HybridExecutor` is the canonical multi-project/multi-node runtime orchestration path.
- Scheduler failover (a peer node taking over another node's live scheduler tick loop) is an explicit non-goal.
- Live-process state migration (moving in-memory executor/session state between nodes mid-task) is an explicit non-goal.
- Supported alternative: lease handoff under `OwningNodeHandoffPolicy` (`park`, `reassign-to-local`, `reassign-any-healthy`) so tasks resume from durable state on the picking node.
- Immediate global consistency for every data class remains a non-goal.
## 2. Terms