Rules
Operational rules the ERP enforces. Rules pages codify what the DDL + domain knowledge say about valid state transitions and required inputs.
Canonical rules pages
- MEL Deferral Rules — the full MEL mechanics. Separate page because of its depth.
- Rules Reference — compact catalog of the other 14 rule sets. Sections below.
Rules catalog
The 14 sections inside Rules Reference:
- Discrepancy Types and Categories — MIREP, MLGEN, DPGEN, QC categories, ATA chapters
- Sign-Off Requirements — who can sign off what, skill authorities
- Work Unit Completion Rules — task state transitions + sign-off gates
- Certificate of Maintenance — when a COM / CRS is required
- Component Removal Reasons — scheduled / unscheduled / BER / MFR / NFF
- Shop WO Routing and Disposition — routing hops, dispositions, core
- Customer Warranty and Charging — billable vs non-billable
- Priority Classifications — AOG / urgent / routine scheduling
- Visit Package Planning Rules — C-check / D-check planning gates
- Three-Way Match on Shop WOs — routing vs parts vs sign-off reconciliation
- Defect Deferral Limits — time + usage limit enforcement
- Task Effectivity Model — model/serial/config applicability
- OU Scoping — how OUINSTANCE columns partition data
- Data Quality and Case Sensitivity — reg casing, orphan records, wildcards
How the rules are enforced
The ERP is the enforcer — most of these rules are implemented as triggers, validation logic, or workflow gates in the source system. The Brain's role here is to explain the rules so the LLM can answer questions like "why can't this discrepancy be closed?" or "what's blocking this AME release?" by reading the relevant rule section and comparing it to the row state.