> ## Documentation Index
> Fetch the complete documentation index at: https://tetrafi.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> The integration shape of Multilateral Netting - a second firm quote per settlement, a member surface for your own slice of the graph, and your own policy domain. Coming soon.

<Note>
  **Coming soon.** [Multilateral Netting](/netting) is in design, not yet live. This is the planned integration shape; paths, schemas, run timing, fee schedules, and membership criteria publish at launch.
</Note>

## What Changes in Your Integration

Nothing in the rails flow. Netting arrives as a **second firm quote**: settle instantly at today's price, or clear at a deadline you pick, at a tighter one. Both are firm; the choice is per settlement.

Two planned quote-request inputs: the settlement mode (instant or cleared) and the deadline tier (an hours-class tier or T+1 / T+2). Instant moves the order now, in full, as quoted. Cleared records the debt with one signature and pre-approves its collection; nothing leaves your wallet until the pull window opens.

## What a Member Reads and Writes

Inside a [sealed engine](/netting/privacy-and-control) you see your own obligations and net, never the graph.

| Surface                        | What it carries                                                                                                   |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
| **Obligations** (read)         | Each debt you signed - asset, amount, corridor, counterparty, deadline - as signed, set off, remaining            |
| **Net positions** (read)       | One signed figure per asset and corridor after each run                                                           |
| **Runs and statements** (read) | Run stage, timing, proof and commit references; a per-run statement of every touched obligation and its fee lines |
| **Notices** (read, plus push)  | The hold-don't-pay notice per run: keep enough balance for your net; silence accepts                              |
| **Objections** (write)         | A signed objection naming obligation ids, inside the notice window                                                |
| **Resolutions** (write)        | Your election when a counterpart is late on a paired leg                                                          |

## Funding the Net

One amount is due per asset and corridor at your deadline. Rank the sources once - wallet, a yield position, an exchange balance, a bank rail last - and one atomic pull takes the net from the first that can pay. Or settle a debt your own way and prove it: both signatures, a custody balance change, or a cryptographically proven receipt closes it.

## Your Own Policy Domain

There is one clearing network, and **modularity** means configuring your participation in it, not running the engine: your own **policy domain**, with your counterparty sets, deadline-tier menu, backstop configuration, funding mode, perimeter policy, and visibility slice. The clearing service is packaged to run on your institution's own infrastructure, or alongside a backend you already operate.

The engine is domain-blind: a book that settles gross today - loans on a lending market, receivables, trade finance, payment obligations - enters through an **intake lane** under the same [compliance policy](/core-concepts/compliance-policy). Lanes: [Where It Applies](/netting/where-it-applies). Fees: [Monetization](/core-concepts/monetization#fees-on-the-next-layers).

<CardGroup cols={2}>
  <Card title="How It Works" icon="gears" href="/netting/how-it-works">
    The clearing run step by step.
  </Card>

  <Card title="Register Interest" icon="sparkles" href="/support">
    Get on the early list.
  </Card>
</CardGroup>