reversa-principles

Maintain consistent project principles across templates by defining durable rules in a centralized principles.md file with before and after hooks. This prevents rework when core governance rules evolve, ensuring downstream templates require minimal manual adjustment.

Track versioned change history for project governance principles by recording creation dates and maintaining a detailed alteration log. The system preserves historical numbering and retired entries, ensuring full traceability of when and why each principle was modified.

Propagate impact updates safely by generating a dated impact report listing template adjustment suggestions, rather than automatically rewriting downstream files. This controlled propagation ensures changes are reviewed before being applied to dependent requirements documents.

Manage the lifecycle of project principles using a controlled process covering creation, addition, alteration, and retirement. This approach ensures outdated governance rules are formally retired and preserved historically, maintaining clear documentation automation throughout the project.

Requirements management documentation does not support automatic template rewriting. Instead, it generates a dated principles-impact report listing specific adjustment suggestions, ensuring that users review and manually apply governance changes to dependent templates.

Generate an impact report for project principles whenever durable governance rules are created, updated, or retired. This dated report identifies necessary adjustments for dependent templates, ensuring downstream requirements documents remain aligned with the latest core rules.