ADR-0007 · Prove Redline standalone, dashboard and API on one origin

Status: Accepted, 2026-10-10.

Context

YYZ’s pages now come from kb-packages without build-time history or block ids, so adopting Redline there first would test the kb-package pipeline, not Redline. The Markdown Renderer proved itself on its own dashboard at lcy.fio.sh before YYZ adoption counted.

Decision

Stage 1 is a dashboard in this repository that renders its own kb/ with the review components, served by the service container beside /v1 on one origin. Components accept a relative serviceUrl (/) resolved in the browser, so one built dashboard runs on any host. YYZ adoption is Stage 2.

Why

One origin removes CORS and cross-site cookies from the standalone path, and the content lives in this repository’s git, so every capability can be proven against real GitLab without other variables.

Consequences

The usage measurement moves to Stage 2: a standalone dashboard has too few readers. Redline’s own documentation is reviewed with Redline.

Evidence

efc77ff, e898411; test/dashboard.test.js, kb/plans/redline-experiment/design/standalone.md.

Revisit when

Stage 2 is planned (TD-002 to TD-004), or the dashboard needs content from other repositories.