> For the complete documentation index, see [llms.txt](https://triple-plus-global.gitbook.io/tpt-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://triple-plus-global.gitbook.io/tpt-whitepaper/trust-and-security/legal-structure.md).

# Legal Structure

## Asset Custody

### Digital Assets

| Asset Type      | Custody Method               |
| --------------- | ---------------------------- |
| **TPT Tokens**  | User wallets (non-custodial) |
| **Stablecoins** | Smart contract escrow        |
| **Asset NFTs**  | Smart contract registry      |

The protocol does not take custody of user funds. All assets remain in smart contracts with predefined rules.

### Off-Chain Documentation

| Document Type         | Custody                     |
| --------------------- | --------------------------- |
| **Original Invoices** | Licensed document custodian |
| **Proof of Delivery** | Platform secure storage     |
| **KYC/KYB Records**   | Compliant identity provider |

## Investor Protections

### Structural Protections

| Protection                     | Description                                   |
| ------------------------------ | --------------------------------------------- |
| **Bankruptcy Remote**          | Asset pools isolated from platform operations |
| **First-Priority Interest**    | Investors have senior claim on receivables    |
| **Legal Assignment**           | Clear title transfer to investors             |
| **Smart Contract Enforcement** | Automatic execution of terms                  |

### Documentation

Each investment includes:

* Assignment agreement (receivable → investor)
* Debtor acknowledgment (where applicable)
* Clear waterfall for payments
* Default and recovery procedures

## Legal Recourse

### Against Defaulting Debtors

{% stepper %}
{% step %}

### Grace Period

Allow for late payment.
{% endstep %}

{% step %}

### Formal Demand

Legal notice to debtor.
{% endstep %}

{% step %}

### Collection Agency

Third-party collectors engaged.
{% endstep %}

{% step %}

### Legal Action

Court proceedings if necessary.
{% endstep %}

{% step %}

### Judgment Enforcement

Asset seizure, wage garnishment.
{% endstep %}
{% endstepper %}

### Against Fraudulent Sellers

{% stepper %}
{% step %}

### Stake Slashing

Seller's collateral forfeited.
{% endstep %}

{% step %}

### Platform Ban

Permanent exclusion.
{% endstep %}

{% step %}

### Legal Reporting

Authorities notified.
{% endstep %}

{% step %}

### Civil Action

Damages pursued.
{% endstep %}
{% endstepper %}

## Jurisdictional Considerations

### User Considerations

| User Type     | Requirements                            |
| ------------- | --------------------------------------- |
| **Investors** | KYC verification, jurisdiction check    |
| **Sellers**   | KYB verification, business registration |
| **Traders**   | Basic verification                      |

### Restricted Jurisdictions

The platform may not be available in certain jurisdictions due to regulatory requirements. Users are responsible for compliance with local laws.

{% hint style="warning" %}
Specific legal structure details will be published in a separate legal disclosure document.
{% endhint %}

## Compliance Framework

### AML/KYC

| Requirement                | Implementation           |
| -------------------------- | ------------------------ |
| **Identity Verification**  | Third-party KYC provider |
| **Business Verification**  | KYB for all sellers      |
| **Transaction Monitoring** | Automated screening      |
| **Suspicious Activity**    | SAR filing procedures    |

### Regulatory Engagement

The team maintains:

* Ongoing dialogue with regulators
* Legal counsel in key jurisdictions
* Adaptable compliance framework
* Transparent communication with users


---

# 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://triple-plus-global.gitbook.io/tpt-whitepaper/trust-and-security/legal-structure.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.