> 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.md). # How cyberCORPs works - [Overview](https://docs.metalex.tech/how-cybercorps-works/explanation.md): 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. - [Constitutive vs. pointer tokenization](https://docs.metalex.tech/how-cybercorps-works/constitutive-vs-pointer.md): Why a cyberCORP's onchain records can be its legal securities ledger, and what the company's governing documents must say for that to be true. - [Ledger Entry Tokens and scrip](https://docs.metalex.tech/how-cybercorps-works/lets-and-scrip.md): How a Ledger Entry Token records a holding on the register, how scrip trades apart from it, and where the two meet. - [Legal mappings across jurisdictions](https://docs.metalex.tech/how-cybercorps-works/legal-mappings.md): Which statutes and governing documents anchor the onchain register for Delaware corporations and LLCs, Cayman and BVI entities, English companies and funds. - [Compliance architecture](https://docs.metalex.tech/how-cybercorps-works/compliance-architecture.md): Where compliance runs: condition contracts on every legally significant transition, the credentials they read, and the point where scrip becomes a Ledger Entry Token again. - [Upgrades and what MetaLeX controls](https://docs.metalex.tech/how-cybercorps-works/upgrades-and-control.md): What MetaLeX can and cannot do to a cyberCORP: published implementations, opt-in upgrades, fees, templates, shared contracts, and the owner role the deploying factory keeps. - [Composability and DeFi](https://docs.metalex.tech/how-cybercorps-works/composability.md): What scrip can do in AMMs, lending markets and vesting contracts, and what its transfer restrictions and compliance powers cost in integrations. - [Regulatory context](https://docs.metalex.tech/how-cybercorps-works/regulatory-context.md): The US exemptions and SEC staff statements the protocol is built around, and what lies outside it. Not legal advice. --- # 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.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.