Quality assurance

CIEL Lab uses two complementary forms of validation:

• focused QA tools answer one operational question and support immediate repair;
• Bulk Validation applies a deterministic rule catalog to a source/version and stores a complete report.

In-form validation should catch obvious errors while an editor is working. A bulk report is the reproducible pre-release check and the best way to coordinate a larger cleanup.

Choose the right tool

Question	Tool
Which concept classes lack a required target mapping?	Required Class Mappings
Which existing mappings now point to retired codes?	Retired Codes
Which names have a display or casing finding?	Display Issues
Does HEAD pass the complete release rule set?	Bulk Validation
How do I preserve a review while HEAD continues to change?	Save report findings as a worklist

Safe review pattern

1. Select the intended OCL source and version.
2. Confirm the data timestamp.
3. Run the narrowest useful check.
4. Filter to a manageable group.
5. Save a worklist before a long review.
6. Inspect each suggested code in its authoritative terminology.
7. Apply approved changes.
8. rerun the relevant validation and confirm the result.

Reports and worklists

A report is the output of a validation run at a point in time. A worklist is a durable set of items selected for human review. Reports can become stale as HEAD changes; worklists are the checkpoint that lets a reviewer resume without depending on the original query returning the same rows.

Release gate

The Release workflow expects a recent successful HEAD bulk validation. The observed implementation requires a zero-error HEAD report within the previous 24 hours. Warnings still require judgment, but an error is a hard signal that the source is not release-ready.

The deterministic rules and UI behavior were developed under OpenConceptLab/ocl_issues#2401.