Skip to content
Forgeplan

forgeplan fpf dashboard

forgeplan fpf dashboard renders a single-screen overview of how the project looks through the First Principles Framework lens: which bounded contexts are healthy, which carry reasoning debt, and what the rule engine recommends next (explore more options, investigate existing evidence, or exploit a proven path).

It’s the FPF counterpart to forgeplan health — health reports artifact-level facts (orphans, stale, blind spots); fpf dashboard interprets them through trust calculus and the explore/exploit model.

When to use

Section titled “When to use”
  • On session start, alongside forgeplan health — understand where reasoning effort should go today.
  • At sprint planning — pick the next bounded context to advance based on R_eff and explore/exploit signals.
  • Before a major decision — see whether you’re prematurely exploiting a low-trust path.
  • After a batch of activations — confirm scores moved in the expected direction.

When NOT to use

Section titled “When NOT to use”

Usage

Section titled “Usage”
forgeplan fpf dashboard [OPTIONS]

Options

Section titled “Options”
  -h, --help     Print help
  -V, --version  Print version

Examples

Section titled “Examples”
Terminal window
# Full dashboard
forgeplan fpf dashboard


# Typical session-start combo
forgeplan health
forgeplan fpf dashboard
forgeplan blocked

What you see

Section titled “What you see”

The dashboard groups output into three blocks:

  1. Bounded contexts — each context (e.g. search, scoring, fpf-kb) with aggregate R_eff, artifact count, and blind-spot flags.
  2. Quality scores — explore_reff / investigate_reff / exploit_reff per context, showing where trust is strongest.
  3. Recommended actions — one of EXPLORE (not enough hypotheses), INVESTIGATE (hypotheses exist but evidence is weak), or EXPLOIT (evidence is strong, ship it).

The action recommendation comes from the same rule engine surfaced by forgeplan fpf rules.

How it fits

Section titled “How it fits”

fpf dashboard is the visual synthesis of PRD-041 (FPF rule engine) and PRD-043 (methodology integrity). It reads:

  • Artifact metadata (kind, status, R_eff) from LanceDB
  • Active rules from the FPF KB
  • Evidence links and congruence levels

…and projects them onto the explore→investigate→exploit axis defined in FPF section B (trust calculus).

See also

Section titled “See also”