reversa-principles

Project principles are standardized by storing them in a .reversa/principles.md file and generating a dated impact report for dependent templates. This ensures requirements remain consistent across the rebuild workflow without automatic rewrites.

Retiring project principles involves recording a timestamp in the versioned history without reusing the original Roman numeral. The system preserves the numbered sequence and generates a dated impact report for affected templates.

Impact analysis for updated requirements templates works by generating a template-by-template report without automatically rewriting the files. This safe propagation requires human approval before any changes are applied to the dependent templates.

No, you do not need to manually rewrite templates when adjusting rebuild workflow principles. The system generates a dated principles-impact report that highlights necessary changes, leaving the actual template modifications for human approval.

No, you cannot assign custom identifiers; the system automatically assigns sequential Roman numerals to new project principles. This enforces a standardized numbering convention that persists even when principles are retired.

When a project principle is retired during the rebuild process, its Roman numeral is preserved in the versioned history and not reused for new entries. Subsequent principles receive the next available number to maintain an accurate audit trail.