methodology-spec-evolution

Methodology specification evolution propagates changes across related organon files like ETHOS.md and PHILOSOPHY.md, coordinating version bumps and terminology to prevent cross-file drift.

The best way to propagate terminology changes across book-llms files is by loading core documents like overview.md and CLAUDE.md to enforce invariants and apply updates via frontmatter and templates.

Methodology specification drift occurs when modifying files in book-llms/ without coordinating version bumps, terminology propagation, and backward-compatibility checks across related organon files.

Enforce backward compatibility when modifying methodology specs by applying governance guardrails that verify invariants and check compatibility across ETHOS.md, PHILOSOPHY.md, overview.md, and CLAUDE.md before finalizing changes.

Yes, you can use frontmatter and templates to govern specification version bumps by propagating methodology changes across related organon files and enforcing invariants loaded from core documents.

You need cross-file methodology specification governance when modifying any file in book-llms/ to ensure high-risk specification changes maintain consistency, propagate terminology, and enforce compatibility across the documentation suite.