> 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/why-optivalux-exists.md).

# Why Optivalux Exists

## A product's identity ends at the point of sale

Inside a brand's own channels, an original product is easy to vouch for. The brand knows where it was made, which batch it belongs to and who sold it.

Once the product leaves those channels, that knowledge fragments. What remains is a collection of disconnected pieces of evidence, none of which is attached to the product itself:

| Moment               | Where the evidence usually sits                                            |
| -------------------- | -------------------------------------------------------------------------- |
| **Purchase**         | A receipt, or a retailer's system the owner cannot see                     |
| **Ownership**        | Nowhere. Nothing connects the owner to the specific item                   |
| **Gifting**          | The receipt stays with the giver; the history rarely travels with the gift |
| **Resale**           | Photos, a listing description and the seller's word                        |
| **Service & repair** | The workshop's own records, invisible to the next workshop                 |
| **Provenance**       | Memory, until it is forgotten                                              |

Paper certificates can be lost or copied. Marketplace listings disappear when the sale closes. Receipts prove a purchase happened, not which physical item was bought or who holds it now.

## Why product-level continuity matters

The gaps appear at exactly the moments when trust is most needed:

* **Resale.** A buyer is asked to trust a stranger's photos and word about an item that may be worth a great deal. The seller has no simple way to demonstrate what they are selling.
* **Gifting.** A product received as a gift arrives without its paperwork. The new owner has little to show for it.
* **Service.** A service centre cannot see what was done before, or easily confirm that the item in front of it is the one the brand made.
* **Loss and theft.** Holding an item has become the main evidence of owning it, which rewards whoever holds it, including someone who should not.

Each of these is a gap between the product and its evidence. Evidence stored somewhere else (a receipt, a database, a listing) can always be separated from the product.

## Why the product itself needs a continuing identity

Optivalux closes that gap by giving **the product itself** a continuous identity:

* The product carries a **registered authenticator**, so evidence can be checked against the item in hand rather than against a document.
* The brand issues a **product certificate** for that one item, with a standing everyone can see.
* **Ownership** is recorded and changes only when the current owner authorizes it, the recipient accepts it, and the product is verified in the recipient's possession. Holding the item alone is never enough.
* **Provenance** accumulates on the same record, owner after owner.

Physical products last for years, sometimes generations. Their identity and evidence should last as long.

Next: [How It Works](/getting-started/how-it-works.md).


---

# 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/why-optivalux-exists.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.