> 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/for-brands/lifecycle-value.md). # Lifecycle Value A product's life does not end at the first sale. This page walks through each stage and describes what a continuous product identity adds for the brand, the owner and anyone else involved. The value described here is qualitative. Optivalux does not publish projected financial returns; measuring real-world impact is one of the purposes of the [pilot](/for-brands/pilot-program.md). ## Manufacture and registration **What happens.** The brand, or its manufacturer, places a secure authenticator in the product and registers it. Registration requires fresh evidence from the authenticator and happens within a batch whose size limit the brand sets. **What it adds.** * Each item has its own identity from the start, not only a SKU. * Registration cannot exceed the batch limit, and an authenticator cannot be registered twice. * The brand has a record of how many products it has registered, per batch. ## First sale **What happens.** The brand makes the product available to be claimed. After purchase, the buyer claims it with the brand's authorization. **What it adds.** * A direct, product-level link between the brand and the item at the moment it reaches its first owner. * Claims require brand authorization, so products cannot be claimed before they are sold. ## Ownership **What happens.** The owner holds the product's certificate and history in their account, and can verify the product at any time. **What it adds.** * Owners can see precisely what was verified and when, and the certificate standing. * The product's history no longer depends on the owner keeping a receipt. ## Gifting **What happens.** The owner transfers the product to the recipient, who accepts and verifies it in hand. **What it adds.** * The history travels with the gift rather than staying with the giver's receipt. * The recipient becomes a recorded owner with the same ability to verify and later transfer. ## Resale **What happens.** A seller transfers the product to a buyer. Before the sale, the buyer (or a platform) can check the product and its certificate standing. **What it adds.** * Buyers can rely on product-level evidence instead of photos and the seller's word. * A seller who does not own the product's certificate cannot complete the transfer, even if they hold the item. * The brand's product continues to carry its identity in the secondary market. ## Service and repair **What happens.** The product is brought to a service centre. **What it adds.** * The service centre can verify the product it is working on against its registered identity. * If the authenticator is damaged, brand-assisted recovery can bind a new one without changing ownership. * *Future direction:* linking service and warranty history to the specific product. This is not an implemented capability today. ## Recovery **What happens.** An authenticator is lost or damaged, or a service the product depends on fails. **What it adds.** * The product keeps its identity and owner through controlled recovery. * Recovery and Protection Mode provide bounded continuity paths when normal infrastructure is unavailable, while preserving ownership. See [Recovery & Protection](/product/recovery-and-protection.md). ## Long-term provenance **What happens.** Over years, the product passes through several owners and service visits. **What it adds.** * An append-only record of registration, ownership changes, standing changes and recovery that outlasts any single receipt, listing or application. * A foundation for the brand's long-term relationship with its products in circulation. --- # 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/for-brands/lifecycle-value.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.