TextNLPClassifierApp/specs/006-article-consolidation-runtime/checklists/requirements.md

Specification Quality Checklist: Article Consolidation and Hygiene Runtime

Purpose: Validate specification completeness and quality before proceeding to planning
Created: 2026-08-23
Feature: spec.md

Content Quality

• No implementation details (languages, frameworks, APIs)
• Focused on user value and business needs
• Written for non-technical stakeholders
• All mandatory sections completed

Requirement Completeness

• No [NEEDS CLARIFICATION] markers remain
• Requirements are testable and unambiguous
• Success criteria are measurable
• Success criteria are technology-agnostic (no implementation details)
• All acceptance scenarios are defined
• Edge cases are identified
• Scope is clearly bounded
• Dependencies and assumptions identified

Feature Readiness

• All functional requirements have clear acceptance criteria
• User scenarios cover primary flows
• Feature meets measurable outcomes defined in Success Criteria
• No implementation details leak into specification

Verification Notes for the 4 Precision Adjustments

1. FR-057 Assertions do Promptfoo Completas (Doc 04 §22.2 e Doc 07 §11.3):
   • JSON Schema validation
   • Validadores Python customizados sem regex
   • IDs pertencentes ao contexto
   • Conjuntos e ordem esperada
   • URLs pertencentes à entrada
   • Precisão e recall
   • Enum e cardinalidade
   • Diffs com bibliotecas de sequência/Unicode sem regex
   • Comparação com a verdade de referência
   • Métricas de custo e latência
2. FR-073 Contrato das Tags na Golden Set:
   • Atualizado para accepted tags or a closed evaluation rubric.
3. US9 (Cenário 4) e FR-084 / Runbook Matriz de Responsabilidades Exata:
   • Orchestrator: provide article/ECP, control concurrency, and consume the manifest.
   • Operations: deploy, monitor, recover, and execute rollback.
   • Engineering: correct code, prompts, schemas, or integrations through the normal release process.
   • Curator/Eval: maintain the golden set and approve quality.
4. US2 Cenário 4 e FR-026 Desacoplamento entre Schema Inválido e Grounding Violation:
   • GROUNDING_VIOLATION restrito a IDs, URLs, imagens ou conteúdo sem origem nos candidatos de entrada (invalida toda a resposta e aciona fallback).
   • Schema inválido tratado como falha semântica acionando fallback; esgotadas as opções de fallback, aplica-se HYGIENE_FAILED.