Validation Registry

1. Validation Framework

1.1 Validation Levels

1.2 Validation Bundle Structure

Each component's validation is packaged as a bundle:

---

2. Current Validation Status

2.1 Core Engine Bundles

2.2 Pipeline Bundles

2.3 Node Executor Bundles

2.4 Runtime Bundles

2.5 API and Admin Bundles

---

3. Conformance Test Categories (CT-)

Referenced from Deployment Matrix Section 5. Each target stack must pass applicable CT categories.

---

4. Validation Process

4.1 New Component Validation Workflow

1. Implement -- Write code, register in Component Status as "Implemented"
2. Write tests -- Create test file in tests/, target VL-2 minimum
3. Run suite -- Execute pytest with coverage measurement
4. Record bundle -- Add entry to Section 2 of this registry
5. Conformance -- If applicable, run CT-* tests for the target contract
6. Certify -- Update Component Status to "Production" if VL-3+ achieved

4.2 Validation on Change

When a component is modified:

1. Run existing validation bundle
2. If any test fails: component reverts to "Implemented" status
3. Fix and re-validate before re-certifying as "Production"
4. Update validated_date in this registry

4.3 Cooperator Validation Requirements

Each work package delivered by a cooperator must include:

---

5. Aggregate Metrics

---

6. Version History

Referencing This Registry

The NSD deployment section references validation registry version via: "validation_registry_version": "VR-1.0". Component Status Matrix references bundle IDs for certification evidence.