[LESSON] 03.1 What A Detection Requirement Is #28

Lesson

Module: 03 Detection Requirements

Lesson: 1. What A Detection Requirement Is

Target file: core/03-detection-requirements/01-what-a-detection-requirement-is.md

Research issue: #12

Scope

Copied from the module README, which is the source of truth. If the scope needs to change while writing, change the README in the same pull request and say why.

Learning Objectives

• Explain why requirements come before design, and why a blocked requirement is a valid outcome.
• Scope a vague detection request into a defined problem.
• Write a requirement that states the behavior, data, conditions, context, and success criteria.

Key Topics

• Starting from the problem, not a query
• Scoping questions (who, which systems, what data, what priority, what response)
• Visibility problems vs. detection problems
• Minimum contents of a requirement
• Verify, don't assume
• Requirements vs. hypotheses and designs

Out of Scope

• Sources of detection ideas (Lesson 2)
• Feasibility in depth (Lesson 5)
• Hypotheses and design (Module 04)

Goal of This Issue

Write the lesson. The lesson is complete when a pull request is merged that:

• adds the target file, based on templates/lesson-template.md and written to the Style Guide
• meets each learning objective above and stays out of the out-of-scope topics, pointing to the lesson or module that covers them instead
• passes the checklist for authors
• links the lesson from the module README's lesson list
• updates the module's ai_assistance field and README AI Assistance section to cover this lesson

The module's status stays draft. Technical review happens at the module level once its lessons are written (Review Process).

How to Participate

• Claim: comment on this issue to take it. A maintainer will assign you and add you to the Contributors section below. One writer leads each lesson; others are welcome to contribute.
• Collaborate: open a draft pull request early and link this issue. To let co-contributors push to your branch, add them as collaborators on your fork (fork Settings → Collaborators). Every commit must be signed off (DCO).
• Boundaries: if the lesson starts covering material owned by another lesson or module, raise it here or in the pull request rather than expanding the scope.
• Inactivity: claims with no activity for 4 weeks may be released after a reminder.

Contributors

Writer:

Contributors:

Additional Context

None yet.