# Quickstart: FDC3 Post-Trade Cash-Leg Settlement (TraderX ↔ BankerX)

> For the complete documentation index, see [llms.txt](https://deploy-preview-470--lucky-concha-f3599f.netlify.app/llms.txt).

## 1) Generate Baseline C3 Runtime

```bash
bash pipeline/generate-state.sh 012-platform-convergence-c3./scripts/start-state-012-platform-convergence-c3-generated.sh --provider kind./scripts/start-state-012-platform-convergence-c3-generated.sh --provider kind --skip-build
```

## 2) Start the State-016 Runtime (Settlement Adapter)

The default runtime for this state is the **offline acceptance flow** (FR-01608, Tier 2a — no cluster, no external services):

```bash
./scripts/start-state-016-post-trade-settlement-bankerx-generated.sh --static# serve + open automatically:./scripts/start-state-016-post-trade-settlement-bankerx-generated.sh --serve
```

Full walkthrough with gates: [acceptance/README.md](https://deploy-preview-470--lucky-concha-f3599f.netlify.app/specs/post-trade-settlement-bankerx/acceptance.md) · reviewer script: [acceptance-demo.md](https://deploy-preview-470--lucky-concha-f3599f.netlify.app/specs/post-trade-settlement-bankerx/acceptance-demo.md).

Cluster variant (014 generated baseline + Sail sidecar, mock-receiver record merged into the Sail app directory):

```bash
./scripts/start-state-016-post-trade-settlement-bankerx-generated.sh --provider kind./scripts/start-state-016-post-trade-settlement-bankerx-generated.sh --provider kind --skip-build
```

Expected UI endpoints:

*   Static acceptance: `http://localhost:8090` (blotter at `/generation/traderx-blotter-web/index.html`; mock receiver at `/generation/mock-receiver/index.html`)
*   Cluster variant: TraderX `http://localhost:8080` (Trade Blotter at `/trade`), Sail `http://localhost:8090`

Settlement note for this state:

*   Each confirmed blotter row carries a `SETTLE (BANKERX)` action.
*   With an FDC3 Desktop Agent present, the action raises `StartPayment` with a complete `fdc3.payment` context (UETR-keyed, per FINOS PR #2204).
*   Without a Desktop Agent, TraderX shows a non-blocking toast and links to `https://terminal.synapticchain.xyz` for direct web dispatch (FR-01605).

## 2c) Settlement registry dependency (documented + pinned)

The blotter reconciles completed settlements by polling `/position-service/trades/settlements/` (Angular: `position.service.ts` → `environment.positionsUrl`). That endpoint is **not** implemented by the base TraderX position-service: it is served by the settlement registry adapter (`synaptic-traderx-adapter`, file-backed `settlements.json`; demo estate: port 8415, routes `GET/POST /trade-service/trade/trades/settlements/`, egress `Pndg → Acsc/Rjct` one-way). The 016 start script checks the adapter at `SETTLEMENT_REGISTRY_URL` (default `http://localhost:8415/trade-service/trade/trades/settlements/`, override with the env var) and warns loudly when it is absent.

Without the route the runtime degrades, honestly: the reconciliation poll 404s, the blotter warns every 60 s (`reconcileFromRegistry`), and settled rows are driven by the FDC3 `synaptic.settlementStatus` broadcast instead. Base TraderX behavior is unchanged; no startup failure, no data corruption.

To pin the dependency in a cluster variant, route the settlement prefix to the adapter (demo estate pattern): the position-service nginx prefix `/position-service/trades/settlements/` proxies to the adapter, everything else keeps the position-service upstream.

## 3) Operator Demo Script

1.  Open the Trade Blotter and confirm a trade row (buyer/seller/currency pair populated).
2.  Click `SETTLE (BANKERX)`.
3.  With a Desktop Agent: confirm the `StartPayment` resolution is logged with the target application and status (FR-01604), and the BankerX terminal receives the payment context with the UUIDv4 `uetr`.
4.  Observe the settlement pipeline on the BankerX terminal: ISO 20022 pacs.008 generated, compliance pre-flight, atomic settlement on the declared rail, pacs.002 (`Acsc`) emitted.
5.  In TraderX, confirm the blotter row flips to `SETTLED` when the matching-UETR `Acsc` confirmation arrives (FR-01606).
6.  Kill the Desktop Agent and repeat step 2 to verify the graceful fallback toast and direct-dispatch link (FR-01605).

## 4) Stop Runtime

```bash
./scripts/stop-state-016-post-trade-settlement-bankerx-generated.sh --provider kind
```

## 5) Verification

*   Mocked DesktopAgent integration tests cover the `raiseIntent` → settlement-confirmation round-trip.
*   Degraded-mode tests prove the baseline blotter behavior is unchanged when FDC3 is absent.
*   Evidence classification (spec §0b): only the Solana-memo path verifies a settlement from the rail's own ledger (`txSignature` shown on the receipt); mock-receiver `Acsc`s are labeled `counterparty Acsc — no tx evidence (mock/demo boundary)` on the receipt modal, in the blotter log, and on the receiver page itself. The settlement registry adapter is demo-estate infrastructure (unauthenticated, file-backed) — the trust boundary is documented, not faked.