> For the complete documentation index, see [llms.txt](https://docs.metalex.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metalex.tech/how-cybercorps-works/explanation.md). # Overview Why the protocol is designed as it is, what it relies on in law, and how far MetaLeX's control over a deployed company reaches. These pages explain the design and its legal grounding for lawyers, investors and integrators deciding whether the model fits. They argue why a company's onchain records can be its legal record, why each security has two token forms, where compliance runs, and what MetaLeX can and cannot do once a company is deployed. To build on the protocol, start with the [guides](/building-on-the-protocol/how-to.md), which also list the contracts each product uses, and the [reference](/building-on-the-protocol/reference.md). * [Constitutive vs. pointer tokenization](/how-cybercorps-works/constitutive-vs-pointer.md) is the thesis: where a company's governing documents designate the onchain records as its securities ledger, changing onchain state is the legal change. * [Ledger Entry Tokens and scrip](/how-cybercorps-works/lets-and-scrip.md) shows how a Ledger Entry Token (LET) records a holding on the register while scrip, its fungible counterpart, trades without moving it. * [Legal mappings across jurisdictions](/how-cybercorps-works/legal-mappings.md) sets out the statutes and governing documents that anchor the register for Delaware corporations and LLCs, Cayman and BVI entities, English companies and funds. * [Compliance architecture](/how-cybercorps-works/compliance-architecture.md) covers condition contracts, credentials, and the choice of where in the scrip lifecycle the strictest gate sits. * [Composability and DeFi](/how-cybercorps-works/composability.md) weighs what scrip can do in AMMs and lending markets against what its restrictions cost. * [Upgrades and what MetaLeX controls](/how-cybercorps-works/upgrades-and-control.md) explains opt-in upgrades, fees and templates, and the owner role the deploying factory keeps. * [Regulatory context](/how-cybercorps-works/regulatory-context.md) maps the US exemptions and SEC staff statements the protocol is built around. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.metalex.tech/how-cybercorps-works/explanation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.