---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/narrative-graph-content-model/
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/)

Narrative Graph guide — October 30, 2026

# Designing a Narrative Graph: A Practical Relationship Worksheet

A business is more than a collection of facts. The relationships between those facts explain what the business does, who it serves and why its claims matter.

By Optiview · Sources checked October 30, 2026

[Download this article (.md)](https://optiview.ai/resources/narrative-graph-content-model.md)

Most websites contain the ingredients of a business narrative: company descriptions, products, proof points, policies and calls to action. The problem is that these ingredients often live on separate pages, without an explicit explanation of how they relate.

A Narrative Graph organizes those relationships. Optiview's [How It Works](https://optiview.ai/how-it-works/) page describes six areas: Identity, Story, Offerings, Trust, Knowledge and Actions. The following worksheet is a proposed editorial method for developing content across those areas, not a description of an automated graph-building or validation feature.

Start with one customer question. The objective is not to fill six boxes with marketing language. It is to assemble a connected explanation that can be supported by approved business information.

## 1\. Build the six-element worksheet

| Element | Question to answer | Required work product |
| --- | --- | --- |
| Identity | Who are we and whom do we serve? | Canonical identity statement |
| Story | Why does this business exist? | Purpose and positioning statement |
| Offerings | What problems do we solve? | Offering-to-need mapping |
| Trust | What supports our claims? | Evidence and qualification references |
| Knowledge | What should customers understand? | Approved answers and explanations |
| Actions | What can someone do next? | Verified destinations and prerequisites |

Each entry should identify an authoritative source and responsible owner. Leave unsupported information unresolved rather than generating plausible-sounding descriptions.

## 2\. Connect the elements with explicit relationships

The value of the worksheet comes from the connections. A product belongs to a business, addresses a customer need, may require eligibility conditions, and can be supported by particular evidence. Those relationships help explain why a fact matters.

| Relationship | Editorial question |
| --- | --- |
| Identity → Offerings | Which business actually provides this offering? |
| Offerings → Knowledge | Which questions explain its use and limitations? |
| Offerings → Trust | Which approved evidence supports important claims? |
| Knowledge → Actions | What should a qualified customer do next? |
| Story → Offerings | How does the offering support the stated purpose? |

The [W3C PROV overview](https://www.w3.org/TR/prov-overview/) describes a general model for representing the entities, activities and people involved in creating information. It offers useful provenance concepts, but this worksheet does not claim to implement the PROV standard.

## 3\. Walk through a hypothetical example

Consider a fictional company, Northstar Scheduling, that provides appointment software for small service businesses. Its identity identifies the company and audience. Its offerings describe scheduling and reminders. Its knowledge explains which calendar connections are supported. Its trust section links to verified technical documentation. Its actions direct eligible customers to a demonstration.

Now consider the question, 'Can Northstar Scheduling connect to my calendar?' A useful narrative points toward the precise supported integrations and any restrictions. The company's general statement that it simplifies appointments is not sufficient evidence of compatibility.

The example is illustrative, not a real company, customer case or tested AI response.

## 4\. Review the graph as a connected explanation

1.  Choose five important customer questions.
2.  Map the facts and relationships needed to answer each.
3.  Identify missing evidence or unresolved qualifications.
4.  Have responsible owners confirm the information.
5.  Review whether the elements communicate a coherent, noncontradictory explanation.
6.  Choose which approved information belongs site-wide and which belongs on individual pages.

Optiview's [setup guide](https://optiview.ai/docs/setup/) documents saving Narrative Graph drafts, selecting site-wide or exact-page scope, and explicitly publishing reviewed changes. The relationship worksheet is an optional preparation method that can support that process.

## 5\. Define what a finished worksheet contains

The finished work product should contain six reviewed content groups, named relationships, authoritative source links, unresolved questions and an approval owner. It should make the business easier to explain without pretending that the publisher controls what a third-party AI system eventually says.

## Additional source context

A useful Narrative Graph connects who a business is, what it offers, why its claims are credible and what a customer can do next. Every relationship should be explainable and supported.

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
- [Building a Provenance Ledger for Brand Claims Published to AI](https://optiview.ai/resources/brand-claims-provenance-ledger/) — 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.