Business Data Type Registry

1. Why Business Data Types

Primitive types (str, int, float) tell the machine what bytes to allocate. Business Data Types tell the system what the value means and how it behaves:

---

2. BDT Structure

Every BDT carries:

---

3. Lifecycle Classes

3.1 Lifecycle Enforcement Rules

---

4. Complete Type Registry

4.1 Monetary Types

4.2 Score and Metric Types

4.3 Enumeration Types

4.4 Count Types

4.5 Identifier Types

4.6 Engineering Types

4.7 Temporal Types

---

5. BDT in Practice

5.1 Field Declaration Example

{
  "field_type_map": {
    "worker.date_of_birth": "DateOnly",
    "worker.last_medical_check": "ISO_DateTime",
    "worker.salary": "USD_Amount",
    "worker.compliance_score": "Score_0_100",
    "worker.visa_type": "CoolingTechnology"
  }
}

The validator enforces:

• date_of_birth cannot be updated (IMMUTABLE_IDENTITY)
• last_medical_check is freely updated (OPERATIONAL_EVENT)
• salary must be >= 0 and <= 1,000,000,000 (USD_Amount constraints)
• compliance_score must be 0-100 (Score_0_100 constraints)

5.2 Entity Class Field Mapping

Every entity class field MUST map to a registered BDT. No field may use a raw primitive type without BDT assignment. The DataValidator rejects fields without BDT mapping.

---

6. Adding New BDTs

New BDTs are added to wormwood/core/business_data_types.py following this process:

1. Define the BusinessDataType constant with all fields
2. Add to TYPE_REGISTRY dict
3. Add entry to this document (Section 4)
4. Map fields using the new BDT in data_lifecycle_policy.json
5. Run test_business_data_types_and_validator.py
6. Update BDT-1.0 version if adding a new category

---

7. Version History