#G.12:2 — Problem frame

Preface node heading:g-12-2-problem-frame:84212

#What this page is

This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

#Methodology

Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

#Content

Dashboards routinely drift or become illegal when they:

• mix scales (ordinal treated as interval; “average maturity level”),
• hide normalization and re‑parameterization (“normalized score” with no CN‑Spec pins),
• silently cross Contexts or planes (implicit reuse without explicit Bridge/Plane routing),
• fail to pin editions of computation methods, descriptor spaces, or distances,
• turn selected sets or archives into a single scalar “winner” by dashboard fiat,
• cannot refresh selectively (no actionable telemetry pins; only narrative “this changed”).

We need a dashboard kit that makes the method of obtaining dashboard values explicit and auditable, while keeping universal invariants governed in G.Core.

---

Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)