# 10.1 Stateless by Design

*Running PTERI in production*

> This section explains how PTERI operates at scale, how it behaves under load, and what guarantees it provides in real-world production environments.

PTERI is designed as **infrastructure**, not an application.\
Operational simplicity and predictability are first-class goals.

***

PTERI verification services are **stateless** wherever possible.

This means:

* No session affinity
* No per-user server memory
* No hidden state between requests

Each request contains everything needed for verification:

* The message or intent
* The signature
* The context (challenge, address, scope)

As a result:

* Requests can be handled by any instance
* Horizontal scaling is trivial
* Failover does not affect correctness

> If a verifier goes down, another can immediately replace it.

***


---

# 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/10.-operations-and-scaling/10.1-stateless-by-design.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.