Back to Details

actualize

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Actualize Knowledge Base

更新知识库

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).
该命令是维护动态保证案例的核心部分。它使你的FPF知识库（
.fpf/
）与项目代码库的不断演进保持同步。
该命令针对近期的git变更执行三部分审计，以发现潜在的上下文偏移、过时证据和陈旧决策。这与FPF标准演进循环（B.4）的观察阶段一致，并有助于管理认知债务（B.3.4）。

Action (Run-Time)

操作（运行时）

Step 1: Check Git Changes

步骤1：检查Git变更

Run git commands to identify changes since last actualization:
bash
undefined
运行git命令以识别自上次更新以来的变更：
bash
undefined

Get current commit hash

Get current commit hash

git rev-parse HEAD
git rev-parse HEAD

Check for changes since last known baseline

Check for changes since last known baseline

(Read .fpf/.baseline file if it exists, otherwise use initial commit)

(Read .fpf/.baseline file if it exists, otherwise use initial commit)

git diff --name-only <baseline_commit> HEAD
git diff --name-only <baseline_commit> HEAD

List all changed files

List all changed files

git diff --stat <baseline_commit> HEAD
undefined
git diff --stat <baseline_commit> HEAD
undefined

Step 2: Analyze Report for Context Drift

步骤2：分析报告以发现上下文偏移

  1. Review changed files for core project configuration:
    • package.json
      , 
      go.mod
      , 
      Cargo.toml
      , 
      requirements.txt
    • Dockerfile
      , 
      docker-compose.yml
    • .env.example
      , config files
  2. If configuration files changed:
    • Re-read project structure (README, config files)
    • Compare detected context with 
      .fpf/context.md
    • Present diff to user
  3. Ask user if they want to update 
    context.md
  1. 检查变更文件中的核心项目配置：
    • package.json
      , 
      go.mod
      , 
      Cargo.toml
      , 
      requirements.txt
    • Dockerfile
      , 
      docker-compose.yml
    • .env.example
      , config files
  2. 如果配置文件发生变更：
    • 重新读取项目结构（README、配置文件）
    • 将检测到的上下文与
      .fpf/context.md
      进行对比
    • 向用户展示差异
  3. 询问用户是否要更新
    context.md

Step 3: Analyze Report for Evidence Staleness (Epistemic Debt)

步骤3：分析报告以发现证据过时（认知债务）

  1. Read all evidence files in 
    .fpf/evidence/
  2. Check 
    carrier_ref
    field in each evidence file
  3. Cross-reference with changed files from git diff
  4. If a referenced file changed:
    • Flag the evidence as STALE
    • Note which hypothesis is affected
  1. 读取
    .fpf/evidence/
    中的所有证据文件
  2. 检查每个证据文件中的
    carrier_ref
    字段
  3. 与git diff中的变更文件进行交叉引用
  4. 如果引用的文件发生变更：
    • 将该证据标记为过时
    • 记录受影响的假设

Step 4: Analyze Report for Decision Relevance

步骤4：分析报告以评估决策相关性

  1. Read all DRR files in 
    .fpf/decisions/
  2. Trace back to source evidence and hypothesis files
  3. If foundational files changed:
    • Flag the DRR as POTENTIALLY OUTDATED
  1. 读取
    .fpf/decisions/
    中的所有DRR文件
  2. 追溯到源证据和假设文件
  3. 如果基础文件发生变更：
    • 将DRR标记为可能过时

Step 5: Update Baseline

步骤5：更新基线

Create/update 
.fpf/.baseline
file:
undefined
创建/更新
.fpf/.baseline
文件：
undefined

FPF Actualization Baseline

FPF Actualization Baseline

Last actualized: 2025-01-15T16:00:00Z

Last actualized: 2025-01-15T16:00:00Z

commit: abc123def456
undefined
commit: abc123def456
undefined

Step 6: Present Findings

步骤6：展示结果

Output a structured report:
markdown
undefined
输出结构化报告：
markdown
undefined

Actualization Report

更新报告

Baseline: abc123 (2025-01-10) Current: def456 (2025-01-15) Files Changed: 42
基线: abc123 (2025-01-10) 当前版本: def456 (2025-01-15) 变更文件数量: 42

Context Drift

上下文偏移

The following configuration files have changed:
  • package.json (+5 dependencies)
  • Dockerfile (base image updated)
Action Required: Review and update 
.fpf/context.md
if constraints have changed.
以下配置文件已变更：
  • package.json (+5 dependencies)
  • Dockerfile (base image updated)
需执行操作：如果约束条件已变更，请检查并更新
.fpf/context.md
。

Stale Evidence (3 items)

过时证据（3项）

EvidenceHypothesisChanged File
ev-benchmark-apiapi-optimizationsrc/api/handler.ts
ev-test-authauth-modulesrc/auth/login.ts
ev-perf-dbdb-indexingmigrations/002.sql
Action Required: Re-validate to refresh evidence for affected hypotheses.
证据假设变更文件
ev-benchmark-apiapi-optimizationsrc/api/handler.ts
ev-test-authauth-modulesrc/auth/login.ts
ev-perf-dbdb-indexingmigrations/002.sql
需执行操作：重新验证以更新受影响假设的证据。

Decisions to Review (1 item)

需审查的决策（1项）

DRRAffected By
DRR-2025-01-10-api-designsrc/api/handler.ts changed
Action Required: Consider re-evaluating decision via 
/fpf:propose-hypotheses
.
DRR影响因素
DRR-2025-01-10-api-designsrc/api/handler.ts changed
需执行操作：考虑通过
/fpf:propose-hypotheses
重新评估决策。

Summary

摘要

  • Context drift detected: YES
  • Stale evidence: 3 items
  • Decisions to review: 1 item
Run 
/fpf:decay
for detailed freshness management.
undefined
  • 检测到上下文偏移：是
  • 过时证据：3项
  • 需审查的决策：1项
运行
/fpf:decay
进行详细的新鲜度管理。
undefined

File: .fpf/.baseline

文件：.fpf/.baseline

Track the last actualization point:
yaml
undefined
记录上次更新的节点：
yaml
undefined

FPF Actualization Baseline

FPF Actualization Baseline

last_actualized: 2025-01-15T16:00:00Z commit: abc123def456789 branch: main
undefined
last_actualized: 2025-01-15T16:00:00Z commit: abc123def456789 branch: main
undefined

When to Run

运行时机

  • Before starting new work: Ensure knowledge base is current
  • After major changes: Sync evidence with code changes
  • Weekly maintenance: Part of regular hygiene
  • Before decisions: Ensure evidence is still valid
  • 开始新工作前：确保知识库是最新的
  • 重大变更后：使证据与代码变更保持同步
  • 每周维护：常规运维的一部分
  • 决策前：确保证据仍然有效