MCAF: Non-Functional Requirements
Read root/local AGENTS.md, the affected flow, workload, and accepted quality expectations. Do not treat every quality attribute as mandatory for every task.
Workflow
- Select the attributes that materially affect the requested change.
- For each, record the metric/invariant, threshold, workload/environment, failure/degraded behavior, owner, and evidence needed for pass/fail.
- Link design-driving constraints to feature requirements, ADRs, tests, and operational evidence. Obtain approval before changing architecture or material contracts to meet them.
- Use product-specific targets; illustrative thresholds or technology examples are not requirements.
- Review the criteria for measurability and meaningful failure detection before executing the planned checks.
Deliver the relevant requirements and their verification mapping in the existing canonical feature/ADR docs.
References
Read only the active attribute's reference: