> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blips.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Demo Overview

> How the BLIPS demo should be exposed as a website-owned surface without being merged into the docs runtime.

# Demo Overview

The BLIPS demo should be published as its own runtime surface:

* public target: `demo.blips.network`
* role: guided product and MVP walkthrough
* ownership: linked from the website and developer docs, but not embedded into Mintlify

## Why the demo stays separate

The demo is not just documentation. It carries runtime state, scenario progression, and product walkthrough logic that should not be mixed into the API Reference layer.

That separation keeps:

* Mintlify focused on docs and Playground
* the demo free to evolve as a guided console experience
* the main marketing site clean and lightweight

## Current runtime reality

The active demo currently lives in the BLIPS MVP/runtime project, not in this Next.js website repo.

That means the website repo should own:

* the entry links
* the public-facing domain plan
* the docs handoff

And the runtime project should own:

* the demo application
* scenario logic
* request proxying and state handling