> 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/product/provenance.md). # Provenance **A history that stays with the product.** Provenance is the recorded history of a product: what has happened to it since the brand registered it. Because it is attached to the product's identity rather than to a receipt or an account, it continues through every owner. ## What is recorded The **core recorded provenance** consists of the lifecycle events of the product's certificate: | Event | What it records | | --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | **Registration** | The brand registered the product, with its authenticator, in a registered product batch, and later made it available to be claimed. | | **Claim** | The first owner claimed the product. | | **Transfer** | Ownership moved to a new owner. | | **Standing changes** | Suspension (with a reason), reinstatement, and voiding (with a reason). | | **Owner report of loss or theft** | The owner reported the product lost or stolen, or withdrew that report. | | **Authenticator replacement** | An authenticator was replaced, through recovery or before first ownership; the old one was retired. | | **Protection Mode** | The certificate was moved to, or out of, its protected state. | Each event is dated. The core record is **append-only**: events are added, never edited or erased. This includes voided certificates, whose history remains visible. The *current* state (for example, whether a certificate is suspended right now) can change through the defined processes above. The *history* of those changes cannot. ## Core provenance vs richer product data Two kinds of information appear on a product's record, and they are kept differently: | | Core recorded provenance | Richer product and service data | | -------------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | **Examples** | Registration, claim, transfers, standing changes, recovery | Product descriptions and images, materials, service and repair notes, individual verification checks | | **Where it is kept** | The core record, on blockchain infrastructure | Operated services (Optivalux or brand systems) | | **Properties** | Append-only; does not rely solely on an Optivalux database | Can be updated, corrected or extended; depends on the operating service | Product and batch details are kept off the core record; the core record holds only a fingerprint of them, so later changes to those details can be detected. Individual verification checks (taps) are generally **not** part of the core record. A verification reports a result; it does not change the certificate. When a claim, transfer or recovery is recorded, relevant verification outcomes or references may be recorded as part of that event, while raw authentication material and richer service data remain off-chain. ## Privacy Provenance tells the story of the **product**, not of the people who owned it. * **No personal data** (names, email addresses, phone numbers, postal addresses, receipts, images of people) is written to the core record. * **Public verification does not display the owner's identity or account.** Owners see that a product had previous owners and when ownership changed, without personal details. * Purchase and activation details used to authorize a claim are checked by the brand's claim service and are not written to the record. How owner account identifiers are protected on a public network is an open design and legal-review item that must be resolved before a pilot with real consumers. Optivalux does not claim that public account identifiers are, by themselves, compliant with data-protection law. ## What provenance does not claim Provenance records what happened to a registered product within Optivalux. It does not record what happened outside it, and it is not a legal chain of title. See [Claims & Limitations](/trust/claims-and-limitations.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/product/provenance.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.