PENROSE
Penrose/Documentation
Back to site

Operate the dashboard

Lifecycle commands

make dash          # start in the foreground
make dash-status   # report process, port, engine commit, and freshness
make dash-restart  # stop a verified Penrose dashboard, then restart it
make dash-stop     # stop only the verified process for this checkout

Open http://127.0.0.1:8077/ unless PENROSE_PORT specifies another port.

Process identity

Dashboard control must verify the PID, checkout root, and port before signaling a process. It must never kill an unrecognized listener merely because it occupies the default port.

Freshness

The dashboard server embeds the engine commit it started with. Restart after code changes when it reports stale code.

Missing derived files

A fresh epoch may legitimately have no prior live or corpus projection. The server must synthesize a real empty state, never expose sample placeholder claims as live data, and clearly distinguish active, legacy, and all-history decision scopes.

Write surface

The dashboard is read-only except for narrowly validated inbox and support submissions. It cannot write decisions, approved knowledge, confirmation state, or holdout files.

Penrose is a falsification referee for quantitative trading claims. A verdict is evidence about survival under the referee, never a trading instruction.