> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/public-demo/docs_public-demo/readme_docs_public-demo.md).

# Public Demo Documentation

This folder documents `public-demo/` as its own standalone static project.

The public demo is not a build of `apps/web`. It is a copyable static artifact: one HTML app, local demo art, PWA metadata, a service worker, and project docs. Its official public host is Cloudflare Pages. It can also be served by any static host without installing npm dependencies or running a server.

## Start Here

| Document                                                                                | Purpose                                                                                  |
| --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| [Project overview](/faction-os-docs/public-demo/docs_public-demo/project-overview.md)   | What the standalone demo is for, what it is not for, and how to use it.                  |
| [Architecture](/faction-os-docs/public-demo/docs_public-demo/architecture.md)           | File map, runtime model, synthetic event loop, assets, and browser dependencies.         |
| [Static artifact](/faction-os-docs/public-demo/docs_public-demo/static-artifact.md)     | Artifact boundary, first-load behavior, service worker rules, and deployable shape.      |
| [Local development](/faction-os-docs/public-demo/docs_public-demo/local-development.md) | How to serve, edit, and test the demo without a build tool.                              |
| [Deployment](/faction-os-docs/public-demo/docs_public-demo/deployment.md)               | Official Cloudflare Pages project, Wrangler deploy flow, and fallback static-host notes. |
| [Validation](/faction-os-docs/public-demo/docs_public-demo/validation.md)               | Manual and browser-smoke checks before publishing.                                       |
| [Maintenance](/faction-os-docs/public-demo/docs_public-demo/maintenance.md)             | Sync rules for mirrored app behavior, assets, helper logic, and cache changes.           |
| [Troubleshooting](/faction-os-docs/public-demo/docs_public-demo/troubleshooting.md)     | Known failure modes and how to diagnose them.                                            |

## Current Project Shape

```
public-demo/
|-- index.html
|-- sw.js
|-- manifest.webmanifest
|-- icon-192.png
|-- icon-512.png
|-- icon-maskable-512.png
|-- assets/
|   |-- battlefield/
|   |-- music/
|   |-- portraits/
|   |-- speech/
|   \-- showcase/
|-- docs_public-demo/
\-- README_public-demo.md
```

## Quick Serve

From the repository root:

```bash
python3 -m http.server 8101 --directory public-demo
```

Then open:

```
http://127.0.0.1:8101/
```

For path-prefix compatibility testing, serve a copied artifact under a repo path such as `/factionos/`; see [Local development](/faction-os-docs/public-demo/docs_public-demo/local-development.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://faction-os.gitbook.io/faction-os-docs/public-demo/docs_public-demo/readme_docs_public-demo.md?ask=<question>&goal=<endgoal>
```

`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.