Add 'created' detection mode for rules system

Implements a new rule detection mode that only triggers when files are
newly created, not when existing files are modified. This enables rules
to enforce standards specifically for new code.

- Add CREATED detection mode to DetectionMode enum
- Add created_patterns field to Rule dataclass
- Update schema to validate 'created' field
- Implement evaluate_created() function
- Add get_created_files_* functions for each compare_to mode
- Update evaluate_rule() and evaluate_rules() to handle created mode
- Update documentation with examples and field reference
- Add comprehensive tests for created mode (10 new tests)

Author: claude

doc/rules_syntax.md

@@ -95,6 +95,21 @@ This rule runs `ruff format` on any changed Python files to ensure
 consistent code style across the codebase.
 ```
 
+### Created Mode (file creation trigger)
+
+`.deepwork/rules/new-module-docs.md`:
+```markdown
+---
+name: New Module Documentation
+created: src/**/*.py
+---
+A new Python module was created. Please ensure:
+
+- Add module docstring explaining the purpose
+- Update relevant documentation if adding a public API
+- Consider adding tests for the new module
+```
+
 ## Rule Structure
 
 Every rule has two orthogonal aspects:
@@ -108,6 +123,7 @@ How the rule decides when to fire:
 | **Trigger/Safety** | `trigger`, `safety` | Fire when trigger matches and safety doesn't |
 | **Set** | `set` | Fire when file correspondence is incomplete (bidirectional) |
 | **Pair** | `pair` | Fire when file correspondence is incomplete (directional) |
+| **Created** | `created` | Fire when newly created files match patterns |
 
 ### Action Type
 
@@ -198,6 +214,47 @@ If `api/users/create.py` changes:
 If `docs/api/users/create.md` changes alone:
 - No trigger (documentation can be updated independently)
 
+### Created Mode (File Creation Detection)
+
+Fires only when files are newly created (not modified). Useful for enforcing standards on new files.
+
+```yaml
+---
+name: New Component Documentation
+created:
+  - src/components/**/*.tsx
+  - src/components/**/*.ts
+---
+```
+
+**How it works:**
+
+1. A file is created that matches a `created` pattern
+2. Rule fires with instructions
+
+Key differences from Trigger/Safety mode:
+- Only fires for **new** files, not modifications to existing files
+- No safety patterns (use Trigger/Safety mode if you need safety)
+- Good for enforcing documentation, tests, or standards on new code
+
+**Examples:**
+
+```yaml
+# Single pattern
+created: src/api/**/*.py
+
+# Multiple patterns
+created:
+  - src/models/**/*.py
+  - src/services/**/*.py
+```
+
+If a new file `src/api/users.py` is created:
+- Rule fires with instructions for new API modules
+
+If an existing file `src/api/users.py` is modified:
+- Rule does NOT fire (file already existed)
+
 ## Action Types
 
 ### Prompt Action (Default)
@@ -373,6 +430,22 @@ pair:
 ---
 ```
 
+### created
+
+File patterns that trigger when files are newly created (created mode). Only fires for new files, not modifications. Can be string or array.
+
+```yaml
+---
+created: src/**/*.py
+---
+
+---
+created:
+  - src/**/*.py
+  - lib/**/*.py
+---
+```
+
 ### action (optional)
 
 Specifies a command to run instead of prompting.
@@ -503,6 +576,39 @@ This rule is suppressed if you've already modified pyproject.toml
 or CHANGELOG.md, as that indicates you're handling versioning.
 ```
 
+### Example 6: New File Standards (Created Mode)
+
+`.deepwork/rules/new-module-standards.md`:
+```markdown
+---
+name: New Module Standards
+created:
+  - src/**/*.py
+  - lib/**/*.py
+---
+A new Python module was created. Please ensure it follows our standards:
+
+1. **Module docstring**: Add a docstring at the top explaining the module's purpose
+2. **Type hints**: Use type hints for all function parameters and return values
+3. **Tests**: Create a corresponding test file in tests/
+4. **Imports**: Follow the import order (stdlib, third-party, local)
+
+This rule only fires for newly created files, not modifications.
+```
+
+### Example 7: New Component Checklist (Created Mode with Command)
+
+`.deepwork/rules/new-component-lint.md`:
+```markdown
+---
+name: New Component Lint
+created: src/components/**/*.tsx
+action:
+  command: eslint --fix {file}
+---
+Automatically lints newly created React components.
+```
+
 ## Promise Tags
 
 When a rule fires but should be dismissed, use promise tags in the conversation. The tag content should be human-readable, using the rule's `name` field:
@@ -525,7 +631,7 @@ Error: .deepwork/rules/my-rule.md - invalid YAML frontmatter
 
 **Missing required field:**
 ```
-Error: .deepwork/rules/my-rule.md - must have 'trigger', 'set', or 'pair'
+Error: .deepwork/rules/my-rule.md - must have 'trigger', 'set', 'pair', or 'created'
 ```
 
 **Invalid pattern:**

doc/rules_system_design.md

@@ -22,6 +22,7 @@ Every rule has two orthogonal aspects:
 | **Trigger/Safety** | `trigger`, `safety` | Fire when trigger matches and safety doesn't |
 | **Set** | `set` | Fire when file correspondence is incomplete (bidirectional) |
 | **Pair** | `pair` | Fire when file correspondence is incomplete (directional) |
+| **Created** | `created` | Fire when newly created files match patterns |
 
 **Action Type** - What happens when the rule fires:
 
@@ -47,6 +48,12 @@ Every rule has two orthogonal aspects:
 - Changes to expected files alone do not trigger the rule
 - Example: API code requires documentation updates
 
+**Created Mode (File Creation Detection)**
+- Define patterns for newly created files
+- Only fires when files are created, not when existing files are modified
+- Useful for enforcing standards on new code (documentation, tests, etc.)
+- Example: New modules require documentation and tests
+
 ### Pattern Variables
 
 Patterns use `{name}` syntax for capturing variable path segments:
@@ -288,6 +295,21 @@ the pair rule does NOT trigger (directional).
 7. Evaluator: If changes keep occurring, mark .failed, alert user
 ```
 
+### Created Rule
+
+```
+1. Detector: New file created, matches "src/**/*.py" created pattern
+2. Detector: Verify file is newly created (not just modified)
+3. Detector: Create .queued entry for new file rule
+4. Evaluator: Return instructions for new file standards
+5. Agent: Addresses rule, includes <promise> tag
+6. Evaluator: On next check, mark .passed (promise found)
+```
+
+Note: Created mode uses separate file detection to distinguish newly
+created files from modified files. Untracked files and files added
+since the baseline are considered "created".
+
 ## Agent Output Management
 
 ### Problem

src/deepwork/core/rules_parser.py

@@ -29,6 +29,7 @@ class DetectionMode(Enum):
     TRIGGER_SAFETY = "trigger_safety"  # Fire when trigger matches, safety doesn't
     SET = "set"  # Bidirectional file correspondence
     PAIR = "pair"  # Directional file correspondence
+    CREATED = "created"  # Fire when created files match patterns
 
 
 class ActionType(Enum):
@@ -73,6 +74,7 @@ class Rule:
     safety: list[str] = field(default_factory=list)  # For TRIGGER_SAFETY mode
     set_patterns: list[str] = field(default_factory=list)  # For SET mode
     pair_config: PairConfig | None = None  # For PAIR mode
+    created_patterns: list[str] = field(default_factory=list)  # For CREATED mode
 
     # Action type
     action_type: ActionType = ActionType.PROMPT
@@ -112,10 +114,13 @@ def from_frontmatter(
         has_trigger = "trigger" in frontmatter
         has_set = "set" in frontmatter
         has_pair = "pair" in frontmatter
+        has_created = "created" in frontmatter
 
-        mode_count = sum([has_trigger, has_set, has_pair])
+        mode_count = sum([has_trigger, has_set, has_pair, has_created])
         if mode_count == 0:
-            raise RulesParseError(f"Rule '{name}' must have 'trigger', 'set', or 'pair'")
+            raise RulesParseError(
+                f"Rule '{name}' must have 'trigger', 'set', 'pair', or 'created'"
+            )
         if mode_count > 1:
             raise RulesParseError(f"Rule '{name}' has multiple detection modes - use only one")
 
@@ -125,6 +130,7 @@ def from_frontmatter(
         safety: list[str] = []
         set_patterns: list[str] = []
         pair_config: PairConfig | None = None
+        created_patterns: list[str] = []
 
         if has_trigger:
             detection_mode = DetectionMode.TRIGGER_SAFETY
@@ -149,6 +155,11 @@ def from_frontmatter(
                 expects=expects_list,
             )
 
+        elif has_created:
+            detection_mode = DetectionMode.CREATED
+            created = frontmatter["created"]
+            created_patterns = [created] if isinstance(created, str) else list(created)
+
         # Determine action type
         action_type: ActionType
         command_action: CommandAction | None = None
@@ -177,6 +188,7 @@ def from_frontmatter(
             safety=safety,
             set_patterns=set_patterns,
             pair_config=pair_config,
+            created_patterns=created_patterns,
             action_type=action_type,
             instructions=markdown_body.strip(),
             command_action=command_action,
@@ -418,6 +430,22 @@ def evaluate_pair_correspondence(
     return should_fire, trigger_files, missing_files
 
 
+def evaluate_created(
+    rule: Rule,
+    created_files: list[str],
+) -> bool:
+    """
+    Evaluate a created mode rule.
+
+    Returns True if rule should fire:
+    - At least one created file matches a created pattern
+    """
+    for file_path in created_files:
+        if matches_any_pattern(file_path, rule.created_patterns):
+            return True
+    return False
+
+
 @dataclass
 class RuleEvaluationResult:
     """Result of evaluating a single rule."""
@@ -428,13 +456,18 @@ class RuleEvaluationResult:
     missing_files: list[str] = field(default_factory=list)  # For set/pair modes
 
 
-def evaluate_rule(rule: Rule, changed_files: list[str]) -> RuleEvaluationResult:
+def evaluate_rule(
+    rule: Rule,
+    changed_files: list[str],
+    created_files: list[str] | None = None,
+) -> RuleEvaluationResult:
     """
     Evaluate whether a rule should fire based on changed files.
 
     Args:
         rule: Rule to evaluate
         changed_files: List of changed file paths (relative)
+        created_files: List of newly created file paths (relative), for CREATED mode
 
     Returns:
         RuleEvaluationResult with evaluation details
@@ -472,13 +505,28 @@ def evaluate_rule(rule: Rule, changed_files: list[str]) -> RuleEvaluationResult:
             missing_files=missing_files,
         )
 
+    elif rule.detection_mode == DetectionMode.CREATED:
+        files_to_check = created_files if created_files is not None else []
+        should_fire = evaluate_created(rule, files_to_check)
+        trigger_files = (
+            [f for f in files_to_check if matches_any_pattern(f, rule.created_patterns)]
+            if should_fire
+            else []
+        )
+        return RuleEvaluationResult(
+            rule=rule,
+            should_fire=should_fire,
+            trigger_files=trigger_files,
+        )
+
     return RuleEvaluationResult(rule=rule, should_fire=False)
 
 
 def evaluate_rules(
     rules: list[Rule],
     changed_files: list[str],
     promised_rules: set[str] | None = None,
+    created_files: list[str] | None = None,
 ) -> list[RuleEvaluationResult]:
     """
     Evaluate which rules should fire.
@@ -488,6 +536,7 @@ def evaluate_rules(
         changed_files: List of changed file paths (relative)
         promised_rules: Set of rule names that have been marked as addressed
                           via <promise> tags (case-insensitive)
+        created_files: List of newly created file paths (relative), for CREATED mode
 
     Returns:
         List of RuleEvaluationResult for rules that should fire
@@ -504,7 +553,7 @@ def evaluate_rules(
         if rule.name.lower() in promised_lower:
             continue
 
-        result = evaluate_rule(rule, changed_files)
+        result = evaluate_rule(rule, changed_files, created_files)
         if result.should_fire:
             results.append(result)