--- optiview_delivery: edge_optimized content_type: semantic_markdown source_url: https://optiview.ai/resources/brand-claims-provenance-ledger/ brand_content: included publication_version: "9.0" published_at: 2026-10-16T20:36:07Z composition_version: composition-v2.1.0 presentation_version: presentation-v1.2.3 brand_content_source: narrative_graph delivery_publication: graph:33 narrative_versions: - 33 narrative_version: 33 --- [Resources](https://optiview.ai/resources/) [Brand context and governance](https://optiview.ai/resources/topics/brand-context/) Content governance — October 30, 2026 # Building a Provenance Ledger for Brand Claims Published to AI Before publishing a claim for AI systems to encounter, a business should know who approved it, what evidence supports it and when it needs another review. By Optiview · Sources checked October 30, 2026 [Download this article (.md)](https://optiview.ai/resources/brand-claims-provenance-ledger.md) A website might describe a product as compatible, a service as available nationwide or a business as certified. These are not merely writing choices. They are assertions that may influence customer decisions. A provenance ledger makes those assertions traceable. It creates a durable relationship between the published wording, its supporting information and the people responsible for confirming it. The [W3C PROV family](https://www.w3.org/TR/prov-overview/) provides established concepts for representing the origins and activities associated with information. The lightweight ledger below borrows the principle of traceability. It is an editorial worksheet, not a claim of formal PROV implementation, certification or a built-in Optiview feature. ## 1\. Create one record per material claim | Field | Purpose | | --- | --- | | Claim ID | Stable identifier for this assertion | | Exact wording | The specific statement proposed for publication | | Evidence | Authoritative document or source location | | Evidence owner | Person or team responsible for source accuracy | | Qualification | Conditions that materially limit the claim | | Scope | Pages, offerings or audiences where it applies | | Reviewer | Person authorized to approve the wording | | Status | Draft, verified, held, approved or retired | | Review trigger | Event requiring another assessment | Separate the evidence owner from the editorial reviewer where possible. A reviewer may approve clear wording without being the original authority for the product specification. ## 2\. Record a hypothetical product claim Suppose fictional company MeridianDesk proposes the statement, 'Our scheduling platform supports calendar synchronization.' Its product owner confirms that synchronization is supported only for two named calendar services. | Ledger field | Illustrative entry | | --- | --- | | Claim ID | MD-CALENDAR-01 | | Proposed wording | Supports synchronization with the two documented calendar services | | Evidence | Approved integration specification, revision 4 | | Owner | Product team | | Qualification | Supported plans and account requirements | | Status | Pending evidence and editorial review | | Trigger | Integration support or plan eligibility changes | This is a fictional example, not an Optiview customer record. The ledger forces the team to preserve the qualification instead of turning a limited compatibility statement into an unrestricted promise. ## 3\. Evaluate the supporting evidence 1. Locate the original evidence rather than relying on a previously generated summary. 2. Confirm that the source supports the exact wording and its qualifications. 3. Record the source revision, effective date and last verification. 4. Check whether the evidence applies to the intended audience and product version. 5. Flag contradictions or missing authorization for resolution. 6. Retain the reviewed claim and evidence reference as a linked record. The [PROV-O recommendation](https://www.w3.org/TR/prov-o/) defines vocabulary for representing provenance relationships. Organizations adopting that formal model should follow its actual specification. A spreadsheet inspired by provenance concepts should not be described as PROV-compliant. ## 4\. Connect approval to the published revision An approval should identify the specific wording reviewed. If someone later removes a limitation, changes a number or extends the claim to another product, the prior approval should not silently apply. * Verified: The evidence supports the precise statement. * Qualified: The statement may be used with specified limitations. * Held: Information or approval is insufficient. * Retired: The claim is no longer appropriate for publication. * Published: The approved revision has been confirmed in the intended destination. Optiview [documents draft and publication separation](https://optiview.ai/docs/setup/) for Narrative Graph content. Maintaining a separate claim-level provenance ledger is an additional recommended business process, not an assertion that the product automatically manages these fields. ## 5\. Make provenance useful after publication Use the ledger when a product changes, a policy expires or a reviewer disputes a statement. Search by source or claim ID to identify affected public content, then request a new review before updating material claims. The work product is complete when every prioritized assertion has a documented status, responsible owner and traceable evidence path. The ledger's purpose is operational accountability, not a claim that AI systems independently verify its contents. ## Additional source context Every material brand claim should have an identifiable source, scope, owner and review decision. Claims without adequate support should be held or rewritten before publication. Make your brand easier for AI to understand. ### Explore [Website publishing](https://optiview.ai/products/publish/) · [Developer tools](https://optiview.ai/products/#developers) · [Pricing](https://optiview.ai/pricing/) ### Learn [Guides](https://optiview.ai/resources/) · [Developer docs](https://optiview.ai/developers/) · [Research](https://optiview.ai/proof/) · [FAQ](https://optiview.ai/faq/) ### Company [About Optiview](https://optiview.ai/about/) · [Agencies](https://optiview.ai/partners/) · [Contact](https://optiview.ai/#contact) · [Privacy](https://optiview.ai/privacy/) · [Billing terms](https://optiview.ai/billing-policy/) ## Additional page links - [Why Markdown Conversion Is Different From Publishing Approved Brand Context](https://optiview.ai/resources/markdown-conversion-vs-approved-brand-content/) — Continue reading - [Designing a Narrative Graph: A Practical Relationship Worksheet](https://optiview.ai/resources/narrative-graph-content-model/) — Continue reading - [What Should Happen When Your Website Contradicts Itself?](https://optiview.ai/resources/resolve-conflicting-brand-facts/) — Continue reading - [Preview a page](https://optiview.ai/demo/) — Continue reading - [Read the setup guide](https://optiview.ai/docs/setup/) — Continue reading --- # Published brand narrative # Site-wide brand information ## Who we are ### Optiview — Parse, Retrieve and Publish for AI Optiview helps businesses and developers make website information easier for AI to use. Parse converts supplied HTML into clean Markdown and source metadata. Retrieve fetches an eligible public HTTPS webpage and prepares its content. Publish helps a verified business prepare its own website content and make approved Narrative Graph context available through a supported connection. Parse and Retrieve use application keys and a prepaid developer wallet. Publish has separate website setup, ownership checks and a subscription. Optiview does not control whether an outside AI service discovers, uses or cites the resulting content. Applies to: Optiview ## Why we matter ### A clearer source, from website content to business context Webpages mix useful information with navigation, layout and application code. Businesses may also have important qualifications, answers and context that are not clearly published. Optiview gives developers a way to prepare source content for their applications, and gives businesses a way to publish the context their teams approve. Your application chooses how to use Parse and Retrieve results. Your business controls what it publishes through Publish. Clearer publishing makes information available; it does not determine an AI system’s answer. Each outside service chooses its own retrieval, recommendations and citations. ## What we offer ### Three products, with separate jobs and clear pricing - **Optiview Parse:** Supply complete HTML and a source URL. Receive clean Markdown, source and output hashes, parser details and processing warnings. Parse does not fetch the URL or execute JavaScript. A successful page uses 1 credit. - **Optiview Retrieve:** Supply one eligible public HTTPS URL. Optiview checks supported access and publisher policies, fetches anonymous static HTML and parses it. It does not search the web, execute JavaScript, bypass a login or access private networks. A successful page uses 5 credits total, including parsing. - **Developer credits:** USD $20 buys 20,000 credits shared by Parse and Retrieve. There is no developer subscription, automatic recharge or scheduled credit expiration. Failed jobs consume no credits. Applicable taxes and the total appear at checkout. Source size, quotas and retention limits apply. - **Optiview Publish:** USD $99 per website per month plus applicable tax. Connect a verified website, review the prepared source and optionally maintain approved Narrative Graph context in Identity, Story, Offerings, Trust, Knowledge and Actions. Choose site-wide or exact-page scope. Saving drafts does not publish them. Eligible AI tools can receive prepared Markdown or HTML through supported delivery, while ordinary visitors keep the normal website. Developer credits do not purchase Publish subscriptions. Parse and Retrieve do not add a customer’s private Narrative Graph to arbitrary third-party pages. See https://optiview.ai/pricing/ and https://optiview.ai/developers/ for the current offer and limits. ## Why trust us ### Inspect the output and understand what the evidence establishes Developers can inspect the prepared Markdown, job status, source metadata, processing warnings and credit ledger. Retrieve records the public source response it observed; Parse identifies supplied HTML rather than claiming to verify the current origin. Publish administrators can review parser output, the combined published-output preview, source checks and publication history. A preview is separate from a recorded live delivery. Saved edits remain separate from the active publication until explicitly published. Our experiment pages contain selected first-party AI conversations and source comparisons. Delivery records establish what was served, not downstream ingestion, recommendations, citations or revenue. Observed language matches do not establish causation or a consistent visibility improvement. Explore the evidence and limitations at https://optiview.ai/proof/. ## Helpful knowledge ### Common questions about the three products **Which product should I use?** Use Parse when you already have HTML. Use Retrieve when you need Optiview to fetch one eligible public page first. Use Publish when your business wants to prepare its verified website and publish approved context. **Do Parse and Retrieve require website ownership or DNS changes?** No website connection is needed for these developer products. You remain responsible for source rights and permitted downstream use. Public availability does not grant a reuse license. **How do developer accounts and keys work?** Create a developer workspace and save the personal sign-in key and offline recovery code. Create scoped service keys for server-side applications. Email is an unverified contact identifier, not account-ownership proof or an email-only recovery method. Keep all credentials private. **Can my agent use Optiview?** The authenticated developer API returns prepared content for your application or model. A downloadable JavaScript client and local MCP adapter are available. Your host must authorize sources and any credit expenditure. Compatibility does not establish adoption or a partnership with an AI provider. **Does the API include my private Narrative Graph?** Parse and Retrieve are source-only. Verified website publishing and approved publisher context belong to the separate Publish workflow. **Does Publish replace our website or CMS?** No. Your website stays in its existing system. Your web team establishes and tests a supported connection. Your team reviews and explicitly publishes any Narrative Graph additions. Ordinary visitors retain the normal website experience. **Does every AI tool get the prepared version?** No. Delivery depends on the website connection, source eligibility and the request. Some tools explicitly request Markdown; supported AI requests may also receive prepared Markdown or HTML through eligible delivery paths. Traditional search crawlers retain the original website response. A claimed tool name does not prove the requester’s identity. **Does the demo publish or save to our workspace?** No. The public demo is a separate preview. Its AI-generated examples require review and do not transfer automatically into an approved publication. **Will Optiview guarantee citations or recommendations?** No. Optiview prepares and publishes sources. Outside AI services choose what to retrieve, use and cite. ## What to do next ### Choose your starting point - [Compare Parse, Retrieve and Publish](https://optiview.ai/products/) to choose the right workflow. - [Create a developer workspace](https://app.optiview.ai/developers) for self-service Parse and Retrieve, then add credits and create an application key. - [Read the API quickstart and agent-tool setup](https://optiview.ai/developers/) for request examples, supported sources, errors, quotas and downloads. - [Review pricing and terms](https://optiview.ai/pricing/) for prepaid credits and the separate Publish plan. - [Preview your website](https://optiview.ai/demo/) to inspect prepared content and explore unapproved narrative examples without connecting or publishing. - [Plan Publish setup](https://optiview.ai/onboarding/) with your web team. Publishing requires ownership checks, review and a supported connection; contact [hello@optiview.ai](mailto:hello@optiview.ai) for assisted setup. Already using Publish? Review your Narrative Graph, publish approved changes explicitly, inspect the combined source in Markdown and check recorded delivery in Activity. Keep your existing visibility tools to study downstream AI answers.