spec: add fraud detection engine specification (001)

4 user stories: alert investigation (P1), transaction ingestion
+ rule engine (P1), rule management (P2), dashboard (P3).
16 functional requirements, 7 success criteria, 5 entities.
Quality checklist: all 16 items passed.

specs/001-fraud-detection-engine/checklists/requirements.md

@@ -0,0 +1,36 @@
+# Specification Quality Checklist: Motor de Detecção de Fraudes Bancárias
+
+**Purpose**: Validate specification completeness and quality before proceeding to planning
+**Created**: 2026-05-11
+**Feature**: [spec.md](../spec.md)
+
+## Content Quality
+
+- [x] No implementation details (languages, frameworks, APIs)
+- [x] Focused on user value and business needs
+- [x] Written for non-technical stakeholders
+- [x] All mandatory sections completed
+
+## Requirement Completeness
+
+- [x] No [NEEDS CLARIFICATION] markers remain
+- [x] Requirements are testable and unambiguous
+- [x] Success criteria are measurable
+- [x] Success criteria are technology-agnostic (no implementation details)
+- [x] All acceptance scenarios are defined
+- [x] Edge cases are identified
+- [x] Scope is clearly bounded
+- [x] Dependencies and assumptions identified
+
+## Feature Readiness
+
+- [x] All functional requirements have clear acceptance criteria
+- [x] User scenarios cover primary flows
+- [x] Feature meets measurable outcomes defined in Success Criteria
+- [x] No implementation details leak into specification
+
+## Notes
+
+- All items pass. Spec is ready for `/speckit.clarify` or `/speckit.plan`.
+- No [NEEDS CLARIFICATION] markers were needed — all design decisions had reasonable defaults based on industry standards for fraud detection systems.
+- Key assumptions documented: tokenized transactions, OAuth2/OIDC auth delegation, rules-based v1 (no ML), LGPD compliance, web-based delivery.