> For the complete documentation index, see [llms.txt](https://clarity-7.gitbook.io/clarity-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clarity-7.gitbook.io/clarity-docs/clarity-moniversive-invariant-static-mis/language-and-coding-breakdown/invariants.md).

# Invariants

**Invariant-first execution:** instead of writing unbounded functions, you define truth conditions the system **never** violates.

```clrty
invariant fee_bps_cap: fee_bps <= 10000;
invariant split_balanced: treasury_bps + bank_bps == 10000;
invariant settlement_chain: chain_id == 1202;
```

### Guarantees

* Inclusion on CLRTY-1 fails if any invariant is false post-transition
* Static ML checks (`clrtyc --check`) reject modules with zero invariants when outcomes mutate state
* Product rails (Split Gateway 50/50) and L01 tax (400 bps) stay **separate** invariant families


---

# 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://clarity-7.gitbook.io/clarity-docs/clarity-moniversive-invariant-static-mis/language-and-coding-breakdown/invariants.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.