> 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/full-language-breakdown.md).

# Full language breakdown

> Generated 2026-08-02T12:03:42Z · **0** language modules · **0** outcomes · **0** invariants · **0** `fn` declarations

Moniversive Invariant Static (MIS) is the **deep-root replacement** for legacy **Solidity** (contracts) and **Python** (application logic) in the Clarity-Fintech authoring model. You write **`.mis`**; you check with **`bin/misc`**; host Python is bootstrap/verify only.

## Replaces Solidity and Python

| Was                                    | Now (MIS)                                                                                                                                                                                 |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Solidity `.sol` / Foundry / OZ         | **`.mis`** · `module` / `outcome` / `invariant` / `signal` (see [Extension map](/clarity-docs/clarity-moniversive-invariant-static-mis/migration-replaces-python-solidity/extensions.md)) |
| Python app code under `moniversive/`   | **`.mis`** in `moniversive/framework/` + **232** paths in `mis_py_to_mis_conversion_map.json`                                                                                             |
| `python3 clrtyc.py` / `solc` / `forge` | **`bin/misc`** only (`misc.mis` · `reject_foreign_kernel`)                                                                                                                                |
| Dynamic exceptions / hidden state      | Named **`invariant`** predicates + **`outcome`** intents                                                                                                                                  |

Execution model: **Code = intent · Execution = optimized outcomes · State = verified invariants**.

## Symbol kinds (language corpus)

| Kind        | Count | Role                                                           |
| ----------- | ----- | -------------------------------------------------------------- |
| `module`    | 0     | Namespace + EMBED block                                        |
| `outcome`   | 0     | Callable execution intent (Sol `function` / Py `def` analogue) |
| `invariant` | 0     | Static predicates (Sol `require` / assert analogue)            |
| `fn`        | 0     | Native `fn` when declared in kernel/architecture packs         |

Indexed GitBook catalog: [symbols-full.md](/clarity-docs/clarity-moniversive-invariant-static-mis/catalog-generated/symbols-full.md) · [per-file sources](/clarity-docs/clarity-moniversive-invariant-static-mis/catalog-generated/sources.md).

## All outcomes (alphabetical)

*No entries.*

## All invariants (alphabetical)

*No entries.*

## All `fn` (alphabetical)

| fn | File |
| -- | ---- |
| —  | —    |

## Per-module reference

## Authoring & AI prompts (input rules)

Cursor + GitBook authoring inputs should follow:

| #  | Rule (authoring / AI input)                                                                                                                                                          |
| -- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 1  | Resolve surfaces via `mis_code_index.json` / `clrty_getMisCodeIndex` before inventing modules                                                                                        |
| 2  | Author **`.mis` only** — not new Python packages or `.sol`                                                                                                                           |
| 3  | Sole compiler: **`bin/misc`** (foreign kernels → exit **3**)                                                                                                                         |
| 4  | Every module: **EMBED gates 3..=6** + **letter-hash**                                                                                                                                |
| 5  | Prefer **`invariant`** + **`outcome`** over exceptions and nested control flow                                                                                                       |
| 6  | Pick taxonomy **family → branch** from `mis_framework_taxonomy.json`                                                                                                                 |
| 7  | Bound recursion: `@mis_kernel(max_depth=…)` / `@mis.inductive` (see [prompt-mlx-routing](/clarity-docs/clarity-moniversive-invariant-static-mis/mis-taxonomy/prompt-mlx-routing.md)) |
| 8  | Use **`mis.select(mask, a, b)`** over deep if/else for LLM-stable codegen                                                                                                            |
| 9  | Index new `.mis` in `mis_code_index.json` (Cursor tip-of-spear)                                                                                                                      |
| 10 | This space is **language + code only** — no institutional, investor, chain, or wallet chapters                                                                                       |

Hand guide: [AI prompting](/clarity-docs/clarity-moniversive-invariant-static-mis/learn/ai-prompting.md) · [Prompt / MLX routing](/clarity-docs/clarity-moniversive-invariant-static-mis/mis-taxonomy/prompt-mlx-routing.md) · [Cheatsheets](/clarity-docs/clarity-moniversive-invariant-static-mis/learn/cheatsheets.md).

## Last 48 hours — Moniversive / MIS activity (git)

* *(no git commits in window)*

Recent **Moniversive Invariant Static** work (48h window, repo + docs):

* **Full language breakdown** — outcomes, invariants, per-module `bin/misc --check`
* **Solidity / Python → `.mis`** authoring policy and `mis_py_to_mis_conversion_map.json`
* Kernel: **`moniversive_invariant_static_ML`** · **`bin/misc --check`**
* Cursor **MIS filter** in `.cursor/rules/moniversive-clrty.mdc`

## Session user inputs (Cursor, sanitized)

Authoring requests that drove this corpus (API tokens and secrets redacted):

* **Sunday, Jul 26, 2026, 11:26 AM (UTC-6)** — Seperate any usage for the crypto, and keep ONLY .mis, the language itself, not anyting to do with CLRTY-1, crypto or the blockchain
* **Sunday, Jul 26, 2026, 11:30 AM (UTC-6)** — Fully breakdown the language all functions, pull all data from the last 48 hours on moniversive inariant static and breakdown the full language, all prompts that had been on input and other, also can mention that it replaces solidity, and python
* **Sunday, Jul 26, 2026, 11:39 AM (UTC-6)** — PUsh this live and fully edited within using the api key and account <https://app.gitbook.com/o/lU2onmCPX2rTApapPYHB/home>
* **Sunday, Jul 26, 2026, 11:44 AM (UTC-6)** — Gitbook -- Clarity Fintech API \[REDACTED] MCP ## Server URL Point your client at the GitBook MCP endpoint. You can authenticate with OAuth (a browser sign-in with nothing to configure) or with a personal access token. <https://mcp.gitbook.com/mcp> ## Connect your client Claude CodeCodex CursorVS CodeOther Add the server to `~/.cursor/mcp.json` (or a project's `.cursor/mcp.json`), then sign in when Cursor prompts you. { "mcpServers": { "gitbook": { "url": "<https://mcp.gitbook.com/mcp>" } } } ## Explore MCP ## Access tokens GitBook uses personal access tokens to authenticate requ
* **Sunday, Jul 26, 2026, 11:48 AM (UTC-6)** — PUSH INTO GIT \[REDACTED] Make your first request The example below shows how to make an API call that asks GitBook Assistant a question in a site within your organization. # The Ask endpoint requires an Organization ID and Site ID POST /v1/orgs/6MCNfiz1cpjlR5LX4kWw/sites/site\_xTRE6/ask HTTP/1.1 Host: api.gitbook.com # Generate a personal access token in Developer settings first. Authorization: Bearer YOUR\_ACCESS\_TOKEN Content-Type: application/json Accept: */* { "question": "How do I get started?", "scope": { "mode": "default" } } API requests are authenticated using the Bearer Aut
* **Sunday, Jul 26, 2026, 11:52 AM (UTC-6)** — Fully autocreate for Moniversive Invariant Static \[REDACTED] Make your first request The example below shows how to make an API call that asks GitBook Assistant a question in a site within your organization. # The Ask endpoint requires an Organization ID and Site ID POST /v1/orgs/6MCNfiz1cpjlR5LX4kWw/sites/site\_xTRE6/ask HTTP/1.1 Host: api.gitbook.com # Generate a personal access token in Developer settings first. Authorization: Bearer YOUR\_ACCESS\_TOKEN Content-Type: application/json Accept: */* { "question": "How do I get started?", "scope": { "mode": "default" } } API requests a
* **Sunday, Jul 26, 2026, 12:01 PM (UTC-6)** — Grab all of the data and prompt intpouts that were placed within the last 48 hours covering MIS and all else and ensure that they are broken down and the lanugage is built even further
* **Sunday, Jul 26, 2026, 12:19 PM (UTC-6)** — Also use Continue building and showing the language in full on the gitbook with commands, functions, defininations, all unique variables, all sets of 20, the ability to prompt engineer and combine with langchain Language repo <https://github.com/clarity-fintech/moniversive\\_invariant\\_static\\_ML> <https://github.com/clarity-fintech/moniversive\\_invariant\\_static\\_ML> 🔷 5. HARDWARE-ACCELERATED VECTOR MATH INVARIANTS (761–775)SIMDRegisterAlignment: Hardware requirement ensuring all vector registers ($ZMM0\dots ZMM31$) are zeroed between ticks.DeterministicDotProductIntrinsics: Direct assembly bindin
* **Sunday, Jul 26, 2026, 12:25 PM (UTC-6)** — Process make gitbook-moniversive-build make gitbook-publish
* **Sunday, Jul 26, 2026, 12:34 PM (UTC-6)** — Needs to include Core Protocol Specs: gitbook.moniversive.mis — Mathematical tensor definitions, Q64.64 fixed-point math rules, and invariant state frameworks.
* **Sunday, Jul 26, 2026, 12:54 PM (UTC-6)** — Continue to find all data throughout my entire database and USE the entire index and remove anythgin that is not educatoin and showcases the files .mis Then anothe page for.clrty
* **Sunday, Jul 26, 2026, 1:04 PM (UTC-6)** — Push only to this gitbook The FULL FOrmat live remove this page <https://app.gitbook.com/o/6MCNfiz1cpjlR5LX4kWw/sites/site\\_xTRE6/s/0HTVa6bLpMobpLPRo2d2/fei-cheng-xu-yuan-ru-men>

## Commands

```bash
bin/misc path.mis --check --compact-letters
make misc-build
make mis-ml-check
python3 scripts/mis-ml/verify_misc_kernel_only.py
make gitbook-moniversive-build
```

Kernel clone: [moniversive\_invariant\_static\_ML](https://github.com/clarity-fintech/moniversive_invariant_static_ML) · Language repos.


---

# 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/full-language-breakdown.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.
