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

FILLING RULES:
- Write as a DELTA over the legacy; never re-describe the entire architecture.
- Cite components from _reversa_sdd/ by their literal name.
- Mark each decision with 🟢 / 🟡 / 🔴 according to the confidence of the source that backs it.
- Decisions dependent on unresolved [DOUBT] accepted as a premise are entered as 🟡 and appear in "Assumptions".
- Deep data model details go to data-delta.md, not here.
- Deep external contract details go to interfaces/<name>.md, not here.
-->

# Roadmap: <FEATURE NAME>

> Identifier: `<NNN>-<short-name>`
> Date: `YYYY-MM-DD`
> Requirements: `<feature-dir>/requirements.md`
> Confidence: 🟢 CONFIRMED, 🟡 INFERRED, 🔴 GAP

## 1. Approach summary

<!-- Up to ten lines. In prose, explain the chosen technical path. -->

## 2. Applied principles

<!--
List the principles from `.reversa/principles.md` that this feature respects or conflicts with.
For conflicts, describe the conflict without proposing a change to the principle (that is /reversa-principles work).
-->

| Principle | How the feature relates | Status |
|-----------|------------------------|--------|
| I. <title> | <observation> | respects / conflicts |

## 3. Technical decisions

| ID | Decision | Rationale | Discarded alternatives | Confidence |
|----|----------|-----------|------------------------|------------|
| D-01 | <decision> | <objective reason> | <a, b, c> | 🟢 |
| D-02 | <decision> | <objective reason> | <a, b> | 🟡 |

## 4. Assumptions

<!--
Assumptions adopted from unresolved [DOUBT] items.
Each assumption must become a resolvable item in /reversa-clarify in the future.
-->

| Assumption | Origin (`requirements.md` section) | Risk if wrong |
|------------|-------------------------------------|---------------|
| <text> | <section> | <impact> |

## 5. Architectural delta

<!--
List only the components from `_reversa_sdd/architecture.md` that change.
For each one, describe the type of change in one line.
-->

| Component | Source file in legacy | Type of change | Summary |
|-----------|----------------------|----------------|---------|
| <name> | `_reversa_sdd/architecture.md#<id>` | rule-changed / new-component / removed-component / new-contract / changed-contract / removed-contract | <one line> |

## 6. Data model delta

<!-- Summary. The detail (fields, migrations, indexes) lives in data-delta.md. -->

- Summary of changes: <short prose>
- Full detail in: `<feature-dir>/data-delta.md`

## 7. External contracts delta

<!-- Summary. Each affected contract has its own file in interfaces/. -->

| Contract | Type | Detail file |
|----------|------|-------------|
| <name> | HTTP / queue / gRPC / GraphQL / file | `<feature-dir>/interfaces/<name>.md` |

## 8. Migration plan

<!-- When applicable. If the change requires no migration, record "n/a" and move on. -->

1. <step>
2. <step>
3. <step>

## 9. Risks and mitigations

| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
| <risk> | high / medium / low | high / medium / low | <action> |

## 10. Done criterion

<!-- What must be true for the feature to be considered complete. -->

- [ ] All actions in `actions.md` marked `[X]`
- [ ] `cross-check.md` (if run) with no CRITICAL or HIGH
- [ ] `regression-watch.md` generated
- [ ] Reverse re-extraction run with no red regression (recommended, not mandatory)

## 11. Change history

| Date | Change | Author |
|------|--------|--------|
| YYYY-MM-DD | Initial version generated by `/reversa-plan` | reversa |
