lint

To fix broken cross-references and malformed YAML frontmatter in your markdown journal, run a workspace linting process that audits entries, detects metadata drift, and applies guarded edits limited to related records and frontmatter.

Journal memory drift is the gradual decay in a timeline knowledge base where newer entries contradict older conclusions, identity profiles become outdated, and cross-references go missing, degrading workspace navigability and consistency.

To reconcile outdated decisions and profile contradictions in your knowledge base, apply a four-phase maintenance process that audits timeline entries, marks superseded decisions without rewriting originals, and resolves profile contradictions using identity profiling rules.

Yes, you can automatically repair identity profiles and fill missing relationship links in your journal archive by running maintenance lint that resolves contradictions and enforces profile structure rules through identity profiling guidance.

The best way to perform whole-library maintenance on a messy timeline markdown archive is to run a four-phase audit that gathers signals with parallel analysis, applies confidence-based filtering for guarded edits, and outputs a maintenance summary.

You should not use automated consistency repair when you need to rewrite original journal content, as the process only marks older entries superseded by newer decisions and limits edits to related records and YAML frontmatter.