> For the complete documentation index, see [llms.txt](https://docs.optivalux.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optivalux.com/getting-started/current-stage.md).

# Current Stage

*Last reviewed: September 2026.*

Optivalux is preparing its first physical pilot. This page states precisely what exists today and what does not.

## Status

| Area                                  | Status             | What it means                                                                                                                  |
| ------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
| Core certificate architecture         | **Complete**       | Designed and specified: product identity, certificate standing and provenance model.                                           |
| Owner sovereignty                     | **Complete**       | Designed and specified: owner-authorized transfer; later software cannot silently reassign ownership.                          |
| Failure & recovery architecture       | **Complete**       | Designed and specified: controlled recovery and Protection Mode.                                                               |
| Production V2 protocol implementation | **Complete**       | The production protocol has been implemented and accepted.                                                                     |
| Public-network validation             | **In development** | Compatibility, deployment evidence and operational behaviour are being validated before public testnet deployment.             |
| Application experience                | **Preparing**      | Owner and brand applications are not yet connected to the protocol. A simulated product preview is available on optivalux.com. |
| Physical pilot                        | **Preparing**      | Pilot preparation follows public-network validation and application integration.                                               |

## Three kinds of "complete"

"Complete" means different things for different rows, and they should not be confused:

* **Architecture items** are designed, specified and documented.
* **The Production V2 protocol** is implemented, tested and accepted. It has been exercised on local development networks only.
* **Nothing is deployed on a public network**, test or production. A complete protocol implementation is not a public deployment.

## What is not yet live

* **No public-chain deployment.** The protocol has not been deployed to any public test network or production network.
* **No production mainnet deployment.** A production deployment additionally requires an external security audit and explicit written authorization.
* **No connected applications.** Owner and brand applications are not yet connected to the protocol.
* **The product preview on optivalux.com is simulated.** It uses fictional products and mock data. No real authentication or network activity takes place.
* **No physical products** are registered yet.

## What comes next

1. **Public-network validation**: confirming that the protocol's deployment and operating assumptions hold on a candidate public network. See [Network & Finality](/technical/network-and-finality.md).
2. **Application integration**: connecting owner and brand applications to the protocol.
3. **Physical pilot**: registering real products with design partners. See [Pilot Program](/for-brands/pilot-program.md).

No dates are committed for these steps. This page will be updated when a status changes.

## Reading the rest of these docs

Pages describe the **designed and implemented behaviour** of Optivalux in the present tense for readability. Unless a page says otherwise, that behaviour is not yet available on a public network or in a connected application.


---

# 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://docs.optivalux.com/getting-started/current-stage.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.