> For the complete documentation index, see [llms.txt](https://docs.syndromics.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.syndromics.xyz/transparency/commitments.md).

# Commitments

Transparency is the product's second promise after solvency. A lending market is only as trustworthy as what outsiders can verify about it, so these commitments are built into the contracts and the open-source services rather than left to policy.

## The eight commitments

| # | Commitment                           | How it is delivered                                                                                                                                             |
| - | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | **Every state change is an event**   | Offer fill, repayment, refinance, auction start and settle, parameter change: each emits an event, and the explorer links each one to Blockscout.               |
| 2 | **Public loan registry**             | Live loan book with collateral, LTV, rate, term, syndicate size, health and origination oracle price.                                                           |
| 3 | **Public risk page**                 | Protocol-wide LTV distribution, concentration by token and by issuer, bad debt ledger (expected zero), liquidation history with realised prices against oracle. |
| 4 | **Oracle and reserve transparency**  | Current Chainlink price, session status, staleness, multiplier and pause flag per token; issuer proof of reserve where a feed exists.                           |
| 5 | **Parameter governance log**         | Every timelock proposal and execution listed with its rationale before it takes effect.                                                                         |
| 6 | **Open source**                      | Contracts, relayer, indexer and keeper bots under a permissive licence; reproducible builds; verified bytecode on Blockscout.                                   |
| 7 | **No hidden order flow**             | The off-chain book is exportable in full. Anyone can run a relayer and will see the same offers, because offers are just signed messages.                       |
| 8 | **Nothing custodied before a match** | Funds move only at settlement through Permit2 or a prior approval. Repayment and post-repayment withdrawal are never pausable.                                  |

## What "verifiable" means here

Every number on the explorer and the risk page can be recomputed by anyone from two public sources: chain events and signed offers. There is no privileged database. If Syndromics Labs disappeared, a third party could run the open-source indexer against the chain and reproduce the same pages.

## What is deliberately not public

* Personal data behind attestations. It stays with the KYC provider and never touches the chain.
* The mapping between a wallet and a real identity. Addresses are shown as addresses.

Everything else about a loan is public, which is the point.

## Reporting

Alongside the live pages, the protocol will publish a periodic risk report summarising outstanding exposure, liquidations, auction performance against oracle, parameter changes and any incidents, with links to the on-chain evidence for each item.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.syndromics.xyz/transparency/commitments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.