status

Status Check

Display the current state of the FPF knowledge base.

Action (Run-Time)

1. Check Directory Structure: Verify .fpf/ exists and contains required subdirectories.
2. Count Hypotheses: List files in each knowledge layer:
   • .fpf/knowledge/L0/ (Proposed)
   • .fpf/knowledge/L1/ (Verified)
   • .fpf/knowledge/L2/ (Validated)
   • .fpf/knowledge/invalid/ (Rejected)
3. Check Evidence Freshness: Scan .fpf/evidence/ for expired evidence.
4. Count Decisions: List files in .fpf/decisions/.
5. Report to user.

Status Report Format

## FPF Status
 
### Directory Structure
- [x] .fpf/ exists

Phase Detection Logic

Determine current phase by examining the knowledge base state:

Evidence Freshness Check

For each evidence file in .fpf/evidence/:

1. Read the valid_until field from frontmatter
2. Compare with current date
3. Classify:
   • Fresh: valid_until > today + 30 days
   • Stale: valid_until > today but < today + 30 days
   • Expired: valid_until < today

If any evidence is stale or expired, warn the user and suggest /fpf:decay.

Example Output