# 3.3 What PTERI Is NOT

Clarity matters as much as capability.

PTERI explicitly does **not** use:

* Tokens
* OmniLite
* NFTs
* RWAs
* IPFS
* Smart contracts

This is not a limitation.

It is a **design decision**.

***

#### Why these are excluded

These systems introduce:

* Additional trust assumptions
* Larger attack surfaces
* Operational complexity
* Incentive misalignment

None of them are required for:

* Identity
* Authority
* Intent
* Verification
* Settlement

> If a component does not strengthen cryptographic trust, it is removed.

***

#### What this enables instead

By excluding these elements, PTERI achieves:

* Predictable security properties
* Easier audits
* Lower operational risk
* Better UX
* Faster iteration

This makes PTERI suitable for:

* Infrastructure
* Enterprises
* Developers
* AI systems

***

<figure><img src="/files/LVEwVK9jAs7hf45rZC45" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.kakrlabs.com/3.-pteri-model-and-universal-trust-layer/3.3-what-pteri-is-not.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.