Reconcile the project's FPF state with recent repository changes
This command is a core part of maintaining a living assurance case. It keeps your FPF knowledge base (.fpf/) in sync with the evolving reality of your project's codebase.
The command performs a three-part audit against recent git changes to surface potential context drift, stale evidence, and outdated decisions. This aligns with the Observe phase of the FPF Canonical Evolution Loop (B.4) and helps manage Epistemic Debt (B.3.4).
Run git commands to identify changes since last actualization:
# Get current commit hash
git rev-parse HEAD
# Check for changes since last known baseline
# (Read .fpf/.baseline file if it exists, otherwise use initial commit)
git diff --name-only <baseline_commit> HEAD
# List all changed files
git diff --stat <baseline_commit> HEAD
Review changed files for core project configuration:
package.json, go.mod, Cargo.toml, requirements.txtDockerfile, docker-compose.yml.env.example, config filesIf configuration files changed:
.fpf/context.mdAsk user if they want to update context.md
.fpf/evidence/carrier_ref field in each evidence file.fpf/decisions/Create/update .fpf/.baseline file:
# FPF Actualization Baseline
# Last actualized: 2025-01-15T16:00:00Z