Skip to main content
Knowledge docs (VISION.md, THESIS.md, etc.) are living documents that should evolve with your project. jfl organize audits them for staleness.

​
The Problem

Knowledge docs drift. You write VISION.md on day 1, then 30 days of journals accumulate with decisions, pivots, and discoveries that the doc doesn’t reflect.

​
The Solution

jfl organize
Scans docs against journal evidence, computes drift scores, generates PENDING.md with proposed updates and open questions. See jfl organize for the full command reference. 
knowledge/
├── VISION.md            # What we're building (update quarterly)
├── THESIS.md            # Why we win (update with competitive changes)
├── NARRATIVE.md         # How we tell the story (update with product changes)
├── PHILOSOPHY.md        # Core principles (rarely changes)
├── BRAND_DECISIONS.md   # Visual identity, naming (update with rebrand)
└── archive/             # Old docs organized by era
    ├── specs/
    ├── research/
    └── strategy/

​
Lifecycle

Created (manual or jfl init)
  ↓ time passes, journals accumulate
Stale detected (jfl organize flags it)
  ↓
PENDING.md generated (proposed updates + questions)
  ↓
Human reviews + answers questions
  ↓
jfl organize --apply → changes applied, PENDING cleared
  ↓ if no journal activity for 60 days
Archive candidate → knowledge/archive/