roadscript-site is the public website and demo surface for Roadscript.
Roadscript is an authenticity tooling project focused on media provenance, invisible watermarking workflows, and verification-oriented product experiences. This repository presents the public-facing website, sample-driven demo flow, and local mock backend contract used to communicate the product direction without exposing the private core engine implementation.
This repository is part of the Roadscript public/private repository ecosystem:
| Repository | Visibility | Purpose |
|---|---|---|
roadscript-docs |
Public | Public overview, architecture notes, repository boundaries, and development milestones. |
cyphra-cli |
Public | Public repository for Cyphra CLI, the developer-facing command-line and workflow layer. |
roadscript-site |
Public | Public website and sample-driven demo surface. |
roadscript-engine |
Private | Private C++ core package consumed by the application layer. |
The site is intentionally separated from the private engine. It demonstrates product flow and system behavior at the presentation layer while engine integration remains under active development.
- Static multi-page website
- Public product overview and roadmap pages
- Sample-driven verification workflow demo
- Frontend mock demo data for deployed static hosting
- Minimal FastAPI mock backend contract for local development and future integration
- No production engine execution in this repository
The current demo is intentionally sample-driven. It is designed to communicate Roadscript’s product direction and verification workflow without claiming production readiness.
- Static HTML, CSS, and vanilla JavaScript
- FastAPI for the local mock backend contract
- Cloudflare Pages hosting for the public website
There is no frontend build step in this repository. The public website is a lightweight static site.
index.html— homepage and product overviewdemo.html— interactive verification workflow demoroadmap.html— product and engineering roadmapwhitepaper.html— product thesis and technical direction summary
From the Website repository root:
python3 -m http.server 8080Then open:
http://127.0.0.1:8080/index.html
http://127.0.0.1:8080/demo.html
By default, the deployed site and local static preview use frontend mock demo data from:
scripts/demoMockData.js
That means demo.html works without the FastAPI backend.
Create and activate a virtual environment:
python3 -m venv .venv
source .venv/bin/activate
pip install -r backend/requirements.txtStart the mock backend:
uvicorn backend.main:app --reloadThe local API will be available at:
http://127.0.0.1:8000/api/health
http://127.0.0.1:8000/api/demo/embed
The frontend demo currently uses frontend mock data by default. The FastAPI backend remains available as a local development contract for future integration work. See backend/README.md for the response shape and local CORS notes.
# Preview the static site
python3 -m http.server 8080
# Run the mock backend
uvicorn backend.main:app --reload
# Validate backend modules
python3 -m compileall backend.
├── assets/
│ ├── brand/
│ │ ├── favicon.svg
│ │ └── wordmark.svg
│ └── demo/
│ └── README.md
├── scripts/
│ └── demoMockData.js
├── backend/
│ ├── __init__.py
│ ├── main.py
│ ├── models.py
│ ├── README.md
│ ├── requirements.txt
│ └── services/
│ ├── demo_service.py
│ └── mock_samples.py
├── demo.html
├── index.html
├── roadmap.html
├── whitepaper.html
├── robots.txt
├── sitemap.xml
└── README.md
The public-facing demo is currently driven by preset sample selections.
- Deployed pages read sample results from
scripts/demoMockData.js. - The FastAPI backend returns mock verification results using a typed response contract.
- Missing demo image assets are handled by the UI fallback state.
- Workflow states in
demo.htmlare simulated to preview the future verification experience. - No real engine execution, upload processing, or production verification job is performed by this repository.
Backend mode can be re-enabled later by changing USE_FRONTEND_MOCK_DATA in demo.html and pointing window.DEMO_API_BASE to the desired API host.
Planned directions include:
- Real custom upload workflow
- Backend integration with the private Roadscript engine package
- Account and credit system for productized runs
- Packaged CLI and desktop/app releases
- More complete public demo assets and product documentation
These items are under active development and should not be interpreted as production availability.
roadscript-docs— public overview, architecture notes, and repository boundaries.cyphra-cli— public repository for Cyphra CLI, the developer-facing command-line and workflow layer.roadscript-engine— private C++ core package used behind the application layer.
- Editor files, Python cache files, virtual environments, and system junk should remain untracked.
- Website build artifacts such as
node_modules/,dist/,build/, and.vite/should remain untracked. - No secrets, tokens, production credentials, or private keys belong in this repository.
- Sample/demo behavior should remain clearly separated from real engine execution code.
Roadscript is an active independent product-engineering project.
All rights reserved © 2026 Roadscript.