Repository navigation
Evaluate composition invariants over the composed union in Java #89
Description
Parent
What to build
The Java side of #46. Composition unions Intent Fragments as chapter 40 specifies: order-independent, every collision an error, nothing merged. The identity and reference invariants are Complete OCL whose context is the composed union. Each negative fixture directory's diagnostics oracle is compared for every order of its fragments.
Acceptance criteria
- Every negative fixture directory yields its committed diagnostics set, for every fragment order.
- The composed union is identical under every fragment order.
Activity
ExtraToast commentedon Oct 6, 2026
#278 lands the production implementation's half of the identity and reference invariants: the registry in
src/check/union.tsand one negative fixture per code underspec/v1/examples/negative/, each with its oracle beside it as<fixture>.diagnostics.json. REQ-054 is pending inemf/docs/witnesses.mdon this issue. Meeting it here means Complete OCL over the union, answering those same fixtures, andParityTestreadingnegative/as it readsrefusals/today.Pipeline.checkalready reads a fixture by itskind: Project.