fact-writer

Maintaining contradiction-free project facts requires enforcing strict ingestion and update rules that detect conflicting facts and replace them rather than appending duplicates. This ensures your canonical fact files remain verifiable and free of silent overwrites.

Lexical sorting and state compression enforce strict alphabetical or natural ordering within fact files to preserve a deterministic, high-density state representation. This structured formatting approach keeps project facts organized and easily verifiable across updates.

Handling contradictions in architecture decision records requires explicit conflict handling via replacement instead of silent overwrites. You must perform full prior state verification before applying updates, ensuring conflicting facts are transparently replaced.

Formatting canonical fact files for documentation governance requires structured dense formatting with deterministic alphabetical insertion. This approach preserves state compression and ensures facts remain objective, repo-grounded truths rather than subjective prose.

Project facts files accumulate duplicate or conflicting entries when updates are appended without full prior state verification. Strict ingestion rules that enforce contradiction checking and explicit replacement of conflicting facts prevent this documentation drift.

State compression techniques suit managing FACTS.md files in large repositories by enforcing strict alphabetical ordering and structured density. This approach keeps history in Git diffs rather than embedding obsolete states inside the fact store itself.