Business Rule Strategy

This document provides a high-level overview of Business Rule documentation for WepNG. For detailed templates and extraction workflow, refer to the Specification Extraction Skill.

[!TIP] Detailed Instructions: See Specification Extraction Skill and BR Development Workflow.

1. Philosophy

A Business Rule (BR) is a constraint or logic statement that exists independently of the software. To avoid "Hidden Logic", we extract these rules from code and document them explicitly.

2. Naming Convention

BR-[MODULE]-[XXX]

Module	Area
`OMGT`	Order Management
`FEE`	Fee/Pricing
`FIN`	Finance
`CRM`	Customer Relationship
`BO`	Back Office
`WA`	Web Access
`MNT`	Maintenance/Config

ID: 3-digit, start at 010 (leave gaps for future insertions).

3. Where BRs Live

Type	Location
Draft candidates	`specs/draft/[module]/br_candidates_[module].md`
Validated rules	`specs/current/business_rules_index.md`
In Gherkin	Tagged as `@BR-OMGT-XXX`
In Use Cases	Section 7: Business Rules

4. Status Workflow

5. In Code

Reference BRs in code comments:

// BR-OMGT-001: Ensure at least one recipient
if (to == null || !to.Any()) { ... }

6. Template

See: .agent/skills/specification_extraction/templates/br_candidates_template.md

1. Philosophy​

2. Naming Convention​

3. Where BRs Live​

4. Status Workflow​

5. In Code​

6. Template​

Related Resources​