diff --git a/docs/cross-device-sofi-test.md b/docs/cross-device-sofi-test.md index 4d9d257e..2ffb8823 100644 --- a/docs/cross-device-sofi-test.md +++ b/docs/cross-device-sofi-test.md @@ -1,5 +1,31 @@ # Cross-Device SoFi Trade Test (Phase 8) +> ## STATUS 2026-09-09 — this test's settle assertion cannot pass on main +> +> The trader's routed settlement (`dlv.unlockRouted`) is deliberately **fail-closed** on `main` and +> refuses before binding anything: +> +> > `dlv.unlockRouted: market settlement is deployment-blocked until 5c-2 Step 2 — a canonical` +> > `market bundle needs the bundled trader successor evidence, which this device cannot produce` +> > `before it advances; vault parent (generation ) was NOT bound and nothing moved` +> +> This is a **deployment block, not a bug and not a misconfiguration**. No setting lifts it. The +> refusal fires *after* every eligibility gate passes, and nothing is stored, fenced, bound, signed +> or advanced when it does: the trader's balances do not move and the vault generation stays free. +> +> The reason is an ordering one. A canonical market bundle must carry the trader's prepared +> successor and its `0x0031` successor evidence, and today the trader binds BEFORE it advances, so +> there is no signed successor to name and nothing may be fabricated in its place. 5c-2 Step 2 is +> the only thing that lifts it. +> +> **What still works:** vault creation and funding, routing advertisement, discovery, quoting, and +> the **owner close path**, which is live and unaffected. +> +> The capability table below records what this test proved when it was written. Its +> `dlv.unlockRouted` rows are the ones the refusal now blocks; the discovery, advertisement and +> cross-device composition rows are unaffected. + + Automated end-to-end test that proves SoFi spec §4.1's _"once a valid σ exists on storage, the unlock is computable by anyone"_ property on real hardware. Wallet A on one device creates AMM vaults and diff --git a/docs/sofi-lp-walkthrough.md b/docs/sofi-lp-walkthrough.md index 92c4e45e..198bc2bd 100644 --- a/docs/sofi-lp-walkthrough.md +++ b/docs/sofi-lp-walkthrough.md @@ -1,5 +1,30 @@ # SoFi LP Walkthrough — Alice's Journey +> ## STATUS 2026-09-09 — the trade step is fail-closed today +> +> The trader's routed settlement (`dlv.unlockRouted`) is deliberately **fail-closed** on `main` and +> refuses before binding anything: +> +> > `dlv.unlockRouted: market settlement is deployment-blocked until 5c-2 Step 2 — a canonical` +> > `market bundle needs the bundled trader successor evidence, which this device cannot produce` +> > `before it advances; vault parent (generation ) was NOT bound and nothing moved` +> +> This is a **deployment block, not a bug and not a misconfiguration**. No setting lifts it. The +> refusal fires *after* every eligibility gate passes, and nothing is stored, fenced, bound, signed +> or advanced when it does: the trader's balances do not move and the vault generation stays free. +> +> The reason is an ordering one. A canonical market bundle must carry the trader's prepared +> successor and its `0x0031` successor evidence, and today the trader binds BEFORE it advances, so +> there is no signed successor to name and nothing may be fabricated in its place. 5c-2 Step 2 is +> the only thing that lifts it. +> +> **What still works:** vault creation and funding, routing advertisement, discovery, quoting, and +> the **owner close path**, which is live and unaffected. +> +> This document is about concepts, and the concepts are unchanged. Only the click-path note +> that says the unlock proceeds is currently untrue on `main`. + + A side-by-side narrative for liquidity providers transitioning from pool-AMM mental models (Uniswap, Curve, Balancer) to DSM's sovereign- vault model. Companion to the two-device playbook; this one is about diff --git a/docs/sofi-two-device-playbook.md b/docs/sofi-two-device-playbook.md index 928e3bce..a2d1ad29 100644 --- a/docs/sofi-two-device-playbook.md +++ b/docs/sofi-two-device-playbook.md @@ -1,5 +1,30 @@ # SoFi Two-Device Playbook +> ## STATUS 2026-09-09 — the settle step does not currently succeed +> +> The trader's routed settlement (`dlv.unlockRouted`) is deliberately **fail-closed** on `main` and +> refuses before binding anything: +> +> > `dlv.unlockRouted: market settlement is deployment-blocked until 5c-2 Step 2 — a canonical` +> > `market bundle needs the bundled trader successor evidence, which this device cannot produce` +> > `before it advances; vault parent (generation ) was NOT bound and nothing moved` +> +> This is a **deployment block, not a bug and not a misconfiguration**. No setting lifts it. The +> refusal fires *after* every eligibility gate passes, and nothing is stored, fenced, bound, signed +> or advanced when it does: the trader's balances do not move and the vault generation stays free. +> +> The reason is an ordering one. A canonical market bundle must carry the trader's prepared +> successor and its `0x0031` successor evidence, and today the trader binds BEFORE it advances, so +> there is no signed successor to name and nothing may be fabricated in its place. 5c-2 Step 2 is +> the only thing that lifts it. +> +> **What still works:** vault creation and funding, routing advertisement, discovery, quoting, and +> the **owner close path**, which is live and unaffected. +> +> The body below is **not rewritten**. It is the runbook as validated, and every step before +> the settle is still exactly right. Expect the refusal above where it says the trade settles. + + End-to-end runbook for exercising the SoFi pipeline on two real phones over a real storage node. After this, the claim "SoFi works on my phone" is defensible from a clean device.