All three artifacts

No /health use case

Aggregated use cases

Two actors identified

PlantUML format

UC IDs in diagram

Spec files match diagram

Business-level steps

Alternative flows present

Entity model ER diagram

AI Unified Process data types

Five-column attribute tables

No endpoint-named use cases

Business rules numbered

Email validation rule

Decimal type for price

Decimal precision 10,2

Enrollment status uses Values rule

Multi-column constraint line

5-column attribute tables

No empty Validation Rules

Allowed data types only

No attributes in Mermaid diagram

No prose descriptions

Uppercase entity headings

Output path

Mermaid block present

No attributes in diagram

Correct relationship syntax

Entity ### headings uppercase

One-sentence description per entity

5-column attribute table

AI Unified Process data types only

Valid validation rules

No empty validation rules

Multi-column constraint note

No prose or Relationships table

@startuml / @enduml

Left to right direction

Actor declaration syntax

Rectangle system block

UC-{3-digit} IDs

Usecase two-line format

Arrow syntax

All actors connected

FR coverage (no NFR/constraint use cases)

No implementation details in names

Correct output path

FR user story format

NFRs are measurable

Separate tables per type

FR ID prefix

NFR ID prefix

Constraint ID prefix

No duplicate IDs

Status column filled

NFR category column

Singular requirements

Ambiguous NFR rewritten

Conflict flagged in notes

Conflict resolution documented

Missing roles noted

User story format

All NFRs measurable

Separate requirement tables

Correct ID prefixes

No duplicate IDs

Status column filled

Assumed threshold documented

Notes file structure

PLAN.md exists

Blazor entry points listed

Feature clustering documented

No C# or SQL types in entity model

AIUP types used

UC IDs grouped by actor

Endpoints aggregated into use cases

PLAN.md exists

Controller file list

Feature clustering documented

Excluded tables listed

No SQL types in entity model

AI Unified Process types used

spring_session absent

audit_log absent

UC IDs grouped by actor

Partial implementation noted

Endpoints aggregated into use cases

Entity model from migrations

Output path and naming

Overview section

Roles section

Preconditions name their data source

Flow table with five columns

Both use cases linked

Journey order carries state

Literal test data

Verification steps present

Validation section

No per-use-case detail re-tested

No implementation detail

Priority in Overview

Postconditions cleanup inventory

UC-001 preserved

UC-002 preserved

UC-003 preserved

No ID gaps or duplicates

FR-004 use case added

FR-005 use case added

Auditor actor declared

Auditor actor connected

Valid PlantUML structure

No implementation details in names

All actors connected

File location & name

Overview: UC-XXX ID

Overview: primary actor

Overview: goal stated

Overview: valid Status

Numbered steps, no gaps

Main scenario ends with goal

At least two alternative flows

Trigger references a step number

Alternative flow endings

Success postcondition

Failure postcondition

Business rules with BR-XXX IDs

Business-level step language

UC-001 file name

UC-002 file name

One use case per file

No SMTP/email-protocol steps

No password-hashing steps

No JWT/token-issuance steps

No SQL/database steps

Alt flow trigger references step number

Alt flow ending

At least one alt flow per use case

Business rule IDs unique globally

Business rules present

Main scenario numbered steps