Regression Check Record¶
Example purpose¶
This artifact records regression checks after ES-108 integration.
Regression checks confirm that integration did not break the core baseline behavior needed for LMU internal engineering review.
Project¶
LMU Campus Operations and Incident Coordination Platform
Document control¶
| Field | Value |
|---|---|
| Artifact owner | COICP Product Engineer |
| Primary reviewers | Architecture Review Board chair, IT security reviewer, AI reviewer, Compliance reviewer, Campus Safety liaison |
| Status | Accepted with regression gaps |
| Last updated | 2026-07-06 |
| Related Engineering Stage | ES-109 — Testing and Verification |
| Project workspace target | docs/project-workspace/testing/regression_check_record.md |
Testing context¶
| Field | Value |
|---|---|
| Integrated baseline under test | LMU-COICP-INT-001 |
| Candidate produced by testing | LMU-COICP-RC-001 |
| Target release posture | Internal engineering review only |
| Planned review environment | LMU-COICP Internal Engineering Review Environment |
| Planned dataset | Spring Semester Synthetic Incident Dataset |
| Planned synthetic records | 421 |
| Planned reviewer accounts | 24 |
| Planned review window | March 18–22, 2026 |
| AI Incident Summary | Deferred / disabled |
| Operational pilot | Not approved |
Regression scope¶
Regression checks focus on core workflow and guardrails after ES-108 integration.
The goal is to determine whether the integrated baseline can be considered by ES-110 as LMU internal engineering review only, not whether it is pilot-ready.
Regression checks¶
| Check | Related Requirement / Guardrail | Result | Evidence | Notes |
|---|---|---|---|---|
| Create incident still works | FR-001 | Pass | TC-001 | Baseline stable. |
| Creation evidence event still created | FR-005, G-001 | Pass | TC-001 | Normal path stable. |
| Missing required field rejected | FR-001 | Pass | TC-002 | Validation stable. |
| Out-of-scope category blocked | C-005, G-004 | Pass | TC-003 | Scope boundary stable. |
| Unauthorized create denied | FR-006, G-003 | Pass with limited role set | TC-004 | More roles needed. |
| Core workflow works without AI | AI boundary | Pass | TC-009 | AI not required. |
| Retention not hard-coded | G-005 | Pass | TC-010 | Retention still open. |
Regression failures¶
| Failure | Related Defect | Notes |
|---|---|---|
| Invalid status transition behavior is inconsistent. | DEF-001 | Must be fixed and retested before pilot. |
Regression gaps¶
- Full role matrix coverage.
- Evidence write failure simulation.
- Broader update workflow regression.
- Emergency-boundary specific regression.
- Handoff evidence regression.
- Review/export regression is not applicable because review/export remains deferred.
Regression conclusion¶
Core create workflow regression is stable.
Regression evidence is sufficient for ES-110 release-readiness evaluation as an internal-review candidate. It is not sufficient for operational pilot.