> For the complete documentation index, see [llms.txt](https://polarischain-1.gitbook.io/polarischain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarischain-1.gitbook.io/polarischain/10.-real-world-asset-tokenization/10.5-legal-enforceability-and-off-chain-mapping.md).

# 10.5 - Legal Enforceability & Off-Chain Mapping

While tokenization occurs on-chain, legal ownership remains governed by off-chain agreements. Polarischain bridges this gap through **Compliance-Bound Asset Descriptors (CBADs)**:

* Legal wrappers, SPV structures, and custodial agreements are hashed and referenced in the asset registry.
* Court orders, regulatory directives, and agent actions are executed via native privileged transactions, creating an immutable, auditable enforcement trail.
* Regulator nodes can correlate on-chain state with off-chain legal documentation in real-time, enabling proactive supervision without compromising data minimization principles.

This architecture ensures that Polarischain does not merely replicate traditional finance on a ledger—it upgrades it with deterministic execution, cryptographic accountability, and institutional-grade compliance.


---

# 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://polarischain-1.gitbook.io/polarischain/10.-real-world-asset-tokenization/10.5-legal-enforceability-and-off-chain-mapping.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.