docs: systematize feature requirements

dependency-tree.md

@@ -53,9 +53,11 @@ template/memory-bank/dna/principles.md
     ├── template/memory-bank/engineering/testing-policy.md
     ├── template/memory-bank/features/README.md
     ├── template/memory-bank/flows/README.md
+    ├── template/memory-bank/flows/behavior-specification.md
     ├── template/memory-bank/flows/bug-fix.md
     ├── template/memory-bank/flows/epic.md
     ├── template/memory-bank/flows/feature.md
+    ├── template/memory-bank/flows/feature-requirements.md
     ├── template/memory-bank/flows/incident.md
     ├── template/memory-bank/flows/refactoring.md
     ├── template/memory-bank/flows/research.md
@@ -92,7 +94,9 @@ template/memory-bank/dna/principles.md
 
 - Этот файл `dependency-tree.md` зависит от [`template/memory-bank/dna/governance.md`](template/memory-bank/dna/governance.md), но сознательно живет вне `template/memory-bank/`.
 - [`template/memory-bank/flows/routing.md`](template/memory-bank/flows/routing.md) зависит от governance и [`template/memory-bank/engineering/autonomy-boundaries.md`](template/memory-bank/engineering/autonomy-boundaries.md); branch flows используют его как upstream owner route selection.
-- [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md) зависит от governance, frontmatter и [`template/memory-bank/flows/routing.md`](template/memory-bank/flows/routing.md).
+- [`template/memory-bank/flows/behavior-specification.md`](template/memory-bank/flows/behavior-specification.md) зависит от governance и principles; он владеет BDD practice без создания отдельного delivery route.
+- [`template/memory-bank/flows/feature-requirements.md`](template/memory-bank/flows/feature-requirements.md) зависит от governance, frontmatter и [`template/memory-bank/engineering/validation-profiles.md`](template/memory-bank/engineering/validation-profiles.md); он владеет requirement taxonomy и двусторонней traceability policy.
+- [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md) зависит от governance, frontmatter, [`template/memory-bank/flows/routing.md`](template/memory-bank/flows/routing.md), [`template/memory-bank/flows/feature-requirements.md`](template/memory-bank/flows/feature-requirements.md), [`template/memory-bank/flows/behavior-specification.md`](template/memory-bank/flows/behavior-specification.md), validation profiles и autonomy boundaries.
 - [`template/memory-bank/flows/research.md`](template/memory-bank/flows/research.md) зависит от governance, frontmatter и [`template/memory-bank/flows/routing.md`](template/memory-bank/flows/routing.md); он определяет lifecycle research packages и их artifact ownership.
 - [`template/memory-bank/flows/epic.md`](template/memory-bank/flows/epic.md) зависит от governance/frontmatter, [`template/memory-bank/flows/routing.md`](template/memory-bank/flows/routing.md) и [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md); Epic Intake templates `package-README.md` и `brief.md` зависят от этого flow.
 - [`template/memory-bank/flows/small-change.md`](template/memory-bank/flows/small-change.md), [`template/memory-bank/flows/bug-fix.md`](template/memory-bank/flows/bug-fix.md) и [`template/memory-bank/flows/refactoring.md`](template/memory-bank/flows/refactoring.md) зависят от routing, governance и [`template/memory-bank/engineering/testing-policy.md`](template/memory-bank/engineering/testing-policy.md).
@@ -101,13 +105,14 @@ template/memory-bank/dna/principles.md
 
 ### Feature-related Docs
 
-- [`template/memory-bank/engineering/testing-policy.md`](template/memory-bank/engineering/testing-policy.md) зависит от [`template/memory-bank/dna/governance.md`](template/memory-bank/dna/governance.md) и [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md).
+- [`template/memory-bank/flows/feature-artifact-catalog.md`](template/memory-bank/flows/feature-artifact-catalog.md) зависит от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md) и [`template/memory-bank/flows/feature-requirements.md`](template/memory-bank/flows/feature-requirements.md).
+- [`template/memory-bank/engineering/testing-policy.md`](template/memory-bank/engineering/testing-policy.md) зависит от [`template/memory-bank/dna/governance.md`](template/memory-bank/dna/governance.md), [`template/memory-bank/flows/behavior-specification.md`](template/memory-bank/flows/behavior-specification.md), [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md), [`template/memory-bank/flows/feature-requirements.md`](template/memory-bank/flows/feature-requirements.md) и validation profiles.
 - [`template/memory-bank/features/README.md`](template/memory-bank/features/README.md) зависит от [`template/memory-bank/dna/governance.md`](template/memory-bank/dna/governance.md) и [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md).
 - [`template/memory-bank/flows/templates/feature/README.md`](template/memory-bank/flows/templates/feature/README.md) зависит от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md) и [`template/memory-bank/dna/frontmatter.md`](template/memory-bank/dna/frontmatter.md).
-- [`template/memory-bank/flows/templates/feature/brief.md`](template/memory-bank/flows/templates/feature/brief.md) зависит от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md), [`template/memory-bank/dna/frontmatter.md`](template/memory-bank/dna/frontmatter.md) и [`template/memory-bank/engineering/testing-policy.md`](template/memory-bank/engineering/testing-policy.md).
-- [`template/memory-bank/flows/templates/feature/design.md`](template/memory-bank/flows/templates/feature/design.md) зависит от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md) и [`template/memory-bank/dna/frontmatter.md`](template/memory-bank/dna/frontmatter.md).
-- [`template/memory-bank/flows/templates/feature/implementation-plan.md`](template/memory-bank/flows/templates/feature/implementation-plan.md) зависит от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md), [`template/memory-bank/dna/frontmatter.md`](template/memory-bank/dna/frontmatter.md) и [`template/memory-bank/engineering/testing-policy.md`](template/memory-bank/engineering/testing-policy.md).
-- Feature-support templates [`runtime-surfaces.md`](template/memory-bank/flows/templates/feature/support/runtime-surfaces.md), [`ui-reference.md`](template/memory-bank/flows/templates/feature/support/ui-reference.md) и [`use-cases.md`](template/memory-bank/flows/templates/feature/support/use-cases.md) зависят от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md) и [`template/memory-bank/dna/frontmatter.md`](template/memory-bank/dna/frontmatter.md).
+- [`template/memory-bank/flows/templates/feature/brief.md`](template/memory-bank/flows/templates/feature/brief.md) зависит от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md), [`template/memory-bank/flows/feature-requirements.md`](template/memory-bank/flows/feature-requirements.md), [`template/memory-bank/flows/behavior-specification.md`](template/memory-bank/flows/behavior-specification.md), [`template/memory-bank/dna/frontmatter.md`](template/memory-bank/dna/frontmatter.md) и [`template/memory-bank/engineering/testing-policy.md`](template/memory-bank/engineering/testing-policy.md).
+- [`template/memory-bank/flows/templates/feature/design.md`](template/memory-bank/flows/templates/feature/design.md) зависит от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md), [`template/memory-bank/flows/feature-requirements.md`](template/memory-bank/flows/feature-requirements.md), [`template/memory-bank/flows/feature-artifact-catalog.md`](template/memory-bank/flows/feature-artifact-catalog.md) и [`template/memory-bank/dna/frontmatter.md`](template/memory-bank/dna/frontmatter.md).
+- [`template/memory-bank/flows/templates/feature/implementation-plan.md`](template/memory-bank/flows/templates/feature/implementation-plan.md) зависит от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md), [`template/memory-bank/flows/feature-requirements.md`](template/memory-bank/flows/feature-requirements.md), [`template/memory-bank/dna/frontmatter.md`](template/memory-bank/dna/frontmatter.md) и [`template/memory-bank/engineering/testing-policy.md`](template/memory-bank/engineering/testing-policy.md).
+- Feature-support templates [`runtime-surfaces.md`](template/memory-bank/flows/templates/feature/support/runtime-surfaces.md), [`ui-reference.md`](template/memory-bank/flows/templates/feature/support/ui-reference.md) и [`use-cases.md`](template/memory-bank/flows/templates/feature/support/use-cases.md) зависят от [`template/memory-bank/flows/feature.md`](template/memory-bank/flows/feature.md), [`template/memory-bank/dna/frontmatter.md`](template/memory-bank/dna/frontmatter.md) и своих direct companions; `use-cases.md` также зависит от [`template/memory-bank/flows/behavior-specification.md`](template/memory-bank/flows/behavior-specification.md).
 
 ### Research-related Docs
 

template/memory-bank/engineering/testing-policy.md

@@ -7,6 +7,7 @@ derived_from:
   - ../dna/governance.md
   - ../flows/behavior-specification.md
   - ../flows/feature.md
+  - ../flows/feature-requirements.md
   - validation-profiles.md
 status: active
 canonical_for:
@@ -89,6 +90,8 @@ Canonical lifecycle gates живут в [../flows/feature.md](../flows/feature.m
 
 ## Что Считается Sufficient Coverage
 
+For each applicable `REQ-*`, preserve the `brief.md` verification method and evidence contract. Quality requirements include an observable threshold and a repeatable measurement/check. The plan maps each changed implementation, test, and config path plus symbol/section back to a `REQ-*` or explicit supporting rationale; review checks that mapping in both directions.
+
 - Покрыт основной changed behavior и ближайший regression path.
 - Покрыты новые или измененные contracts, события, schema или integration boundaries.
 - Покрыты критичные failure modes из `FM-*` в required `design.md`, bug history или acceptance risks.

template/memory-bank/flows/README.md

@@ -16,6 +16,7 @@ derived_from:
   - behavior-specification.md
   - use-case.md
   - feature.md
+  - feature-requirements.md
   - feature-artifact-catalog.md
   - templates/README.md
 status: active
@@ -36,6 +37,7 @@ audience: humans_and_agents
 - [Epic Flow](epic.md) — Epic Intake/Proposal, lifecycle крупных инициатив, roadmap, decision log, risks и handoff в feature packages.
 - [Behavior Specification Practice](behavior-specification.md) — BDD-цикл Discovery → Formulation → Automation, качество concrete examples и traceability `UC/REQ → SC/NEG → CHK → test evidence`; это практика внутри выбранного flow, а не отдельный route.
 - [Use Case Flow](use-case.md) — критерии, lifecycle и ownership для project-level `UC-*`, включая operational / agentic сценарии.
-- [Feature Flow](feature.md) — lifecycle `brief.md -> optional design.md -> implementation-plan.md`, gates и стабильные ID (`REQ-*`, `SOL-*`, `STEP-*`).
+- [Feature Flow](feature.md) — lifecycle `brief.md -> optional design.md -> implementation-plan.md` и transition gates.
+- [Feature Requirements, Identifiers And Traceability](feature-requirements.md) — requirement classes, stable IDs, applicability и двусторонняя трассировка до delivered surfaces и evidence.
 - [Feature Artifact Catalog](feature-artifact-catalog.md) — optional problem/solution/execution artifacts, selection triggers, ownership, default forms и template availability.
 - [Templates Index](templates/README.md) — эталонные шаблоны governed-документов, включая PRD, use case, epic, feature и ADR.

template/memory-bank/flows/feature-artifact-catalog.md

@@ -6,6 +6,7 @@ purpose: Каталог optional артефактов для постановк
 derived_from:
   - ../dna/governance.md
   - feature.md
+  - feature-requirements.md
 status: active
 audience: humans_and_agents
 ---
@@ -40,7 +41,7 @@ Formulation и Automation используют существующие owners 
 | Project-level `UC-*` | Какой устойчивый пользовательский / операторский сценарий поддерживает система? | Scenario повторяется во времени или используется несколькими features | `memory-bank/use-cases/UC-XXX.md` | Canonical reusable scenario | [Use Case](templates/use-case/UC-XXX.md) |
 | Epic package | Как координируются roadmap, risks и несколько delivery units? | Работа крупнее одной vertical feature | `memory-bank/epics/EP-XXX/` | Initiative coordination, не feature execution | [Epic](templates/epic/README.md) |
 | `README.md` | Какие artifacts реально входят в feature package и в каком порядке их читать? | Любой feature package | `features/FT-XXX/README.md` | Routing only | [Feature README](templates/feature/README.md) |
-| `brief.md` | Какую проблему решаем, что входит в scope и как принимаем результат? | Любой feature package | `features/FT-XXX/brief.md` | Canonical problem, requirements, acceptance and evidence contract | [Brief](templates/feature/brief.md) |
+| `brief.md` | Какую проблему решаем, какие requirement classes применимы, что входит в scope и как принимаем результат? | Любой feature package | `features/FT-XXX/brief.md` | Canonical problem, classified requirements, acceptance, evidence and traceability contract | [Brief](templates/feature/brief.md) |
 | Feature-local use cases / behavior example map | Какие happy, edge и error journeys и их `Given / When / Then` projections удобнее review отдельно? | Много scenarios/roles или нужен `FUC → SC/NEG → REQ → CHK` mapping | `use-cases/README.md` | Derived scenario/example projection; canonical acceptance остается в `brief.md`, новый verdict здесь запрещён | [Feature Use Cases](templates/feature/support/use-cases.md) |
 | Runtime surface inventory | Где behavior существует сейчас и какой context доступен? | Несколько entrypoints, mappings, fallbacks или context variants | `runtime-surfaces.md` | Current-state reference | [Runtime Surfaces](templates/feature/support/runtime-surfaces.md) |
 | UI flow / mockups | Что видит пользователь и какие interface states проходит? | Меняется UI, navigation, editor/preview или interaction model | `ui-reference/README.md`, `ui-reference/mockups/*`; ссылка на `engineering/ui-design-guide/README.md` или нужный surface document | Interface reference; requirements и selected solution остаются у canonical owners; shared UI catalog не копируется в feature | [UI Reference](templates/feature/support/ui-reference.md) |
@@ -78,7 +79,7 @@ Formulation и Automation используют существующие owners 
 | Error taxonomy | Какие errors/states существуют и как consumer их интерпретирует? | API/integration или много failure outcomes | Table in contract or `design.md` | `CTR-*` wire semantics and `FM-*` solution behavior | Interaction Contract pattern |
 | Failure-mode analysis | Что может сломаться и как решение ограничивает impact? | Distributed, financial, security-critical или degradation-sensitive flow | `FM-*` in `design.md`; table when richer analysis needed | Canonical solution failure semantics | Design section |
 | Idempotency / concurrency model | Как обрабатываются duplicates, races, locks и ordering? | Callbacks, jobs, financial operations или parallel writers | Contract/design tables and sequence branches | `CTR-*`, `INV-*`, `FM-*`, `SD-*` | Interaction/Sequence patterns |
-| Quality attributes / NFR | Какие latency, capacity, availability, consistency или recovery properties нужны? | Эти properties меняют класс допустимых решений | Constraints in `brief.md`; solution response in `design.md` | Requirement vs solution ownership сохраняется раздельно | pattern only |
+| Quality attributes / NFR | Какие measurable latency, capacity, availability, consistency или recovery properties нужны? | Applicability decision identifies a quality trigger or material risk | `REQ-*` class `performance` or `quality attribute` in `brief.md`; solution response in `design.md` | `MET-*` and `CON-*` do not replace a requirement | Brief/Design pattern |
 | Security / threat analysis | Какие trust boundaries, threats и controls существуют? | Auth, permissions, secrets, personal/financial data или external integration | Compact section/table in `design.md`; при росте `security-analysis.md` | Feature controls; reusable security policy требует ADR/project owner | pattern only |
 | Migration design | Как перейти из current state в target state без потери compatibility? | Data/schema/config migration, dual read/write или staged cutover | `migration-design.md` или compact `RB-*` section | Delegated migration facts indexed from `design.md` | pattern only |
 | Compatibility matrix | Какие producer/consumer/schema versions совместимы? | Rolling deploy или independently released components | Table in contract/migration design | Delegated compatibility contract | Interaction/Migration pattern |
@@ -91,6 +92,7 @@ Formulation и Automation используют существующие owners 
 | Artifact | Question answered | Trigger | Default form / suggested path | Ownership | Template |
 | --- | --- | --- | --- | --- | --- |
 | `implementation-plan.md` | В каком порядке реализовать accepted problem/solution contract? | Feature действительно переходит к execution | `features/FT-XXX/implementation-plan.md` | Workstreams, steps, commands, checkpoints and stop conditions | [Implementation Plan](templates/feature/implementation-plan.md) |
+| Traceability matrix | Как requirement reaches exact code/config target, test, evidence and CI review — and back? | Every feature; expand for multiple requirements/surfaces | `brief.md` + execution mapping in plan | Brief owns requirement chain; plan owns exact realization and reverse coverage | Brief/Plan sections |
 | Test matrix / strategy | Какие requirements, contracts и failures чем проверяются? | Change surface требует нескольких suites/types или manual gap | Canonical checks in `brief.md`; execution strategy in plan | Acceptance remains in `brief.md`; execution coverage in plan | Brief/Plan sections |
 | Evidence artifact | Чем доказан конкретный check? | Evidence удобнее хранить отдельно от CI link/path/screenshot | Linkable carrier, optionally `evidence.md` | Results only; не меняет expected behavior | pattern only |
 | Review report | Какие findings найдены и как закрыты? | Formal review/reconciliation materially useful | `<kind>-review-report.md` or external review link | Findings/status only; canonical owners update first | pattern only |