Compare

from 173cf8ad · seed platform scenario → to b38ea131 · seed platform scenario

Variant impact

Which platform requirements each side satisfies, where the two versions' subsystem choices differ, and what each side's cross-model edges resolve to.

References

role	from · with-microduck	to · main
beverage	coffee-machine`@1ec97db8`	coffee-machine`@1ec97db8`
floor-care	microduck`@d1819603`	floor-robot`@8e42ad84`changed
food	sandwich-toaster`@0399697d`	sandwich-toaster`@0399697d`
payment	purchasing-terminal`@87be9f07`	purchasing-terminal`@87be9f07`

Requirements

CS-1Service Timeboth
CS-2One Paymentboth
CS-3No Provision Before Paymentboth
CS-4Floor Kept Clearboth

Cross-model edges

Each declared cross-model edge, resolved at its pinned revision. A resolved edge names the element inside the referenced subsystem that implements or satisfies the platform element; an edge that does not resolve is reported by name, never dropped.

platform element	relation	from · with-microduck	to · main
CS-4 · Floor Kept Clear	satisfied by	Gripper Arm (microduck@`d1819603`)	Cup Collector (floor-robot@`8e42ad84`)changed

Requirements CS-1, CS-2, CS-3 and CS-4 are satisfied in both versions.

What this panel proves — and what it does not

Coverage is computed over each version's own graph; a cross-model edge is resolved at its pinned revision, so a requirement satisfied by a named element inside a referenced subsystem is proved, not merely asserted.

Computed

the platform model's own requirement coverage on each side, from the engine's requirement_coverage over that version's graph
the subsystem reference differences, shown role → project@revision and marked where they change
each cross-model edge, resolved at its pinned revision — the named element inside the referenced subsystem is shown with its name and project@revision

Not computed — asserted, not proved

the global graph property: that the union of the platform and all its subsystems, transitively, at their pinned revisions, forms one connected, coverage-complete, orphan-free graph — proving it would require importing every subsystem, which is the copy R1 forbids

Diff

Other

Removed

reference:microduck

Added

reference:floor-robot

Gate

Verdict: failed

Failures

roundtrip: 1 missing elements, 1 extra elements, 0 missing edges, 0 extra edges, 0 changed attributes
integration: 2 connected components

This comparison is not recorded. Run the gate for 173cf8ad → b38ea131 to persist an evidence record; the run will then appear in the gate list.