# EM-PRD-03 provider comparison

Claude and Grok agree to complete and reclassify reserved WM-REC-006 as a Requirement aggregate and allocate no new model or runtime identifier. Requirement owns stable family identity, immutable revisions and their satisfaction clauses. Need, feature/design, task, test/result, evidence, waiver, decision, evaluation and enforcement remain externally mastered.

Both keep reusable Rule separate. WM-KNW-013 owns formal predicate identity, revisions, operands, units, tolerance and evaluation contract. A contained Acceptance Criterion belongs to one exact Requirement revision and either pins exact Rule revisions or records a one-off informal condition. Reusable and local tolerance changes follow separate revision paths.

Grok proposed a population-level Requirement Baseline collection artifact inside the model boundary. The frozen audit found that authority, effectivity, digest and successor lineage make that object an independent aggregate without an owning Requirement instance. The reconciled result therefore removes an authoritative Baseline from WM-REC-006. Requirement Baseline is now an identifier-unassigned candidate for separate reservation review. WM-REC-006 offers only a derived, non-authoritative revision-set comparison over caller-supplied exact revision, criterion and Rule pins.

Grok narrowed Trace Link to a contained outbound association whose owned source is one Requirement revision. The audit added a single-owner rule for Requirement-to-Requirement links: the target exposes only a derived inbound projection. Link presence never proves satisfaction and revised endpoints make old links suspect.

The frozen audit also moved inter-Requirement conflicts to an external issue/case/decision master, prohibited local overrides on Rule-pinned criteria, prevented revision-set views from freezing verdicts, and required partial-redacted coverage labelling.

Task Done remains inadmissible proof. Satisfaction requires a qualified external test result and evidence pinned to the same Requirement revision; failures remain visible and waivers never become silent passes.

The final candidate records 35 constraints, five external relations and 33 fixtures. Publication remains held by the missing WM-REC-006 specification, Requirement Baseline allocation review, relation-ledger cleanup, held dependencies, external master joins, trace vocabulary, field-level mastership and disclosure rules.