> For the complete documentation index, see [llms.txt](https://gabriel-j-shapiro.gitbook.io/metalex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gabriel-j-shapiro.gitbook.io/metalex-docs/protocol-explanation/explanation.md).

# Overview

Explanation is understanding-oriented. The other three quadrants tell you *what* and *how*; explanation tells you *why*. Read these when you want to know the design rationale, the legal grounding, and the trade-offs the protocol makes.

## Contents

* [Constitutive vs. pointer tokenization](/metalex-docs/protocol-explanation/constitutive-vs-pointer.md) — the thesis on which the protocol rests.
* [The dual-token model](/metalex-docs/protocol-explanation/dual-token-model.md) — why cyberCERT (ERC-721) and cyberSCRIP (ERC-20) coexist, and how they relate.
* [Legal mappings across jurisdictions](/metalex-docs/protocol-explanation/legal-mappings.md) — how Delaware, LLC, Cayman, BVI, and English law map onto the same primitives.
* [Co-approval upgradeability](/metalex-docs/protocol-explanation/co-approval-upgradeability.md) — why neither MetaLeX nor any single issuer can unilaterally upgrade.
* [Composability and DeFi](/metalex-docs/protocol-explanation/composability.md) — what scripification enables and where its boundaries are.
* [Compliance architecture](/metalex-docs/protocol-explanation/compliance-architecture.md) — conditions, credentials, zkPassport, Reg D vs. Reg S, and the de-scripification boundary.
* [The role of MetaLeX](/metalex-docs/protocol-explanation/role-of-metalex.md) — protocol developer and steward, not securities intermediary.
* [Regulatory context](/metalex-docs/protocol-explanation/regulatory-context.md) — SEC statements, statutory grounding, UI-provider safe harbour.
* [The cyberCORPs application stack](/metalex-docs/protocol-explanation/application-stack.md) — cyberRAISE, cyberTRADE, ACE, LiquiLeX, cyberSign, Mainframe, and how the illustrative apps in `metalex-webapp` realise them.


---

# 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://gabriel-j-shapiro.gitbook.io/metalex-docs/protocol-explanation/explanation.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.