Dashboard

The Dashboard is the system-level view of Penrose. It summarizes engine freshness, active-epoch verdicts, candidate readiness, run activity, data blockers, and the P1–P9 evidence flow.

What to look at first

1. Engine status — confirm the dashboard process is running the current repository commit.
2. Active epoch — know which corpus generation the counts describe.
3. Authoritative verdict state — use active-epoch counts, not all-time physical ledger rows.
4. Candidate readiness — see whether eligible observations have formed supported abstractions.
5. Action items — distinguish missing data, missing modules, review states, and engine errors.

Count semantics

The overview may display multiple scopes:

• active-epoch decisions;
• Legacy Epoch 0 or prior-epoch decisions;
• physical decision-history rows;
• eligible corpus evidence;
• carried-forward data requests.

These values should be labeled and must not be added together. A fresh epoch can legitimately show zero corpus observations while retaining hundreds of historical decisions.

Pennie

Pennie helps turn a rough research idea into one falsifiable claim. Conversation state lives in the browser. Only a user-confirmed hypothesis may be written to inbox/, and that file still travels through the normal pipeline. Pennie cannot write verdicts, approve P9, read confirmation data, or modify the corpus.

Read-only contract

The Dashboard is an observability surface. It does not place orders, alter verdicts, promote knowledge, burn a holdout, or unfreeze generation.

Healthy empty state

After a fresh corpus epoch, a healthy dashboard can show:

• zero eligible observations;
• zero principles and candidates;
• legacy decisions retained separately;
• carried-forward data requests;
• idle pipeline status.

Empty is not broken. Unlabeled mixing of legacy and active state is broken.