Master smith at the dashboard control room, wall of glowing amber screens showing live gauges, charts, and status lights
Chapter 7 · LiveGuard Tabs

Dashboard — LiveGuard Tabs

Five amber-accented tabs for post-deploy defense: Health, Incidents, Triage, Security, and Env. Part of Chapter 7: The Dashboard.

Part of Chapter 7, This page covers the LiveGuard top-level group. See The Dashboard for the Forge group tabs, Dashboard — Settings Group, and Dashboard — Forge-Master Studio.

LiveGuard Section

Five amber-accented tabs separated by a visual divider from the FORGE section. LiveGuard tools (forge_drift_report, forge_regression_guard, forge_incident_capture, forge_secret_scan, forge_env_diff, forge_liveguard_run, etc.) broadcast liveguard + liveguard-tool-completed events that populate these tabs in real time.

For a full LiveGuard deep-dive, what it guards against, how drift detection works, and how incidents flow to resolution, see Chapter 16: What Is LiveGuard? and Chapter 17: LiveGuard Tools Reference.

Health Tab LiveGuard

Composite project health fingerprint produced by forge_health_trend and forge_liveguard_run:

  • Overall score (0–100) with trend direction (improving / stable / degrading)
  • Component metrics, drift average, incident rate, test pass rate, model success rate, cost per slice
  • Gate summary, drift / sweep / secret-scan / regression-guard / dep-watch / alert-triage pass/fail counts from the last forge_liveguard_run
  • Health DNA, persisted to .forge/health-dna.json for cross-session decay detection

Incidents Tab LiveGuard

Open and recently resolved incidents captured by forge_incident_capture and auto-chained from drift:

  • Incident list, ID, severity, description, affected files, first seen, MTTR when resolved
  • Recurring pattern flag, incidents on the same files ≥3 times in 30 days are auto-escalated to high
  • Auto-resolve, incidents close automatically when forge_regression_guard passes on overlapping scope
  • Fix proposals, forge_fix_proposal plans linked to the originating incident are surfaced inline

Triage Tab LiveGuard

Prioritized alert stream from forge_alert_triage:

  • Severity-ordered alerts, critical / high / medium / low with source tool and timestamp
  • Source breakdown, drift violations, secret-scan findings, env-diff gaps, dep-watch vulnerabilities
  • Framework-code filtering, pforge-mcp/, pforge.*, setup.* paths are excluded from app-code scoring

Security Tab LiveGuard

Secret hygiene and dependency vulnerability posture:

  • Secret scan results, entropy + key-name findings from forge_secret_scan, masked as <REDACTED>, confidence high / medium / low
  • Vulnerable dependencies, forge_dep_watch output for npm (npm audit) and .NET (dotnet list package --vulnerable)
  • PreDeploy gate status, blocks deploys on high-severity secret findings when hooks.preDeploy is enabled

Env Tab LiveGuard

Environment-variable drift between local .env, example templates, and deploy targets via forge_env_diff:

  • Missing keys, present in .env.example / deploy config but absent from local .env
  • Extra keys, local-only values that are not in the shared template
  • Cache freshness, stale-cache warning when the scan has not run since the last deploy
  • Deploy journal link, correlates env gaps with the most recent forge_deploy_journal entry