<!--
Body template for principles.md
Loaded by /reversa-principles.

FILLING RULES:
- Principles numbered in Roman numerals (I, II, III, ...). Numbering is stable and never recycled.
- Retired principles are NOT deleted; they are marked as "retired on YYYY-MM-DD" and moved to the end.
- Each principle has a short title, a full description, and ONE concrete application example.
- The "Impact" section lists which templates depend on that principle.
- Principles are rare — typically less than once a month.
-->

# Project Principles

> Project: `<project name>`
> Date of last change: `YYYY-MM-DD`
> Maintained by: `/reversa-principles`

## Active principles

### I. <Short title>

**Description.** <Paragraph of one to three sentences describing the principle in plain language.>

**Application example.** <Concrete scenario where the principle applies and how it influences the decision.>

**Impact on templates.**
- `requirements-template.md`: <how this principle shapes the content of requirements>
- `roadmap-template.md`: <how this principle shapes technical decisions>
- `actions-template.md`: <when applicable>

**Created on.** `YYYY-MM-DD`
**Last reviewed.** `YYYY-MM-DD`

---

### II. <Short title>

**Description.** <...>

**Application example.** <...>

**Impact on templates.**
- `requirements-template.md`: <...>
- `roadmap-template.md`: <...>

**Created on.** `YYYY-MM-DD`
**Last reviewed.** `YYYY-MM-DD`

---

## Retired principles

<!--
Principles that are no longer valid stay here, with their retirement date.
Do not delete them — the history helps understand past decisions.
-->

### <ROMAN NUMERAL>. <Original title>

**Original description.** <text>

**Retired on.** `YYYY-MM-DD`
**Reason.** <why it is no longer valid>

---

## Change history

| Date | Operation | Principle | Summary |
|------|-----------|-----------|---------|
| YYYY-MM-DD | create | I | Initial version |
| YYYY-MM-DD | add | II | <summary> |
| YYYY-MM-DD | update | I | <summary of change> |
| YYYY-MM-DD | retire | III | <short reason> |
