> 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/company/about.md). # About **Optivalux builds Product Identity Infrastructure for original physical products.** ## Why this should exist Physical products last for years, sometimes generations. Their evidence usually does not: receipts are lost, certificates are paper, and ownership is remembered rather than recorded. We believe original products should keep a continuous, verifiable identity that travels with the item itself: its authenticity evidence, its certificate, its owners and its history. That identity should be: * **precise** about what it proves, and about what it does not; * **respectful** of the people who own the product, keeping their personal information off the public record; * **meaningful beyond any single application**: core ownership, certificate state and recorded provenance should not depend on one company, including Optivalux, remaining unchanged. Optivalux is designed toward that last goal, not a guarantee of it. The core record is kept on blockchain infrastructure and cannot be reassigned by Optivalux, while several services around it (verification for some authenticators, applications, product details) are still operated services. See [Trust Model](/trust/trust-model.md). ## What we are building * A **protocol** for product certificates, owner-authorized transfer, controlled recovery and Protection Mode. The Production V2 implementation is complete and accepted. * The **verification experience**, owner applications and brand tools that sit on top of it. * A **pilot** with design partners on real products. See [Current Stage](/getting-started/current-stage.md) for what is and is not live. ## Founder **Milan Kozlevčar**, Infrastructure & Incentive Architect. Milan designs the Optivalux protocol and product architecture: how product identity, certificates, ownership and recovery fit together, and how the system stays trustworthy over time. ## Contact See [Contact & Partnerships](/company/contact-and-partnerships.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/company/about.md?ask=&goal= ``` `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.