Write the Task 1 metamodelling report #88

Parent

#78

What to build

The course's first graded report, due 2026-09-25. It describes the two metamodels (source: Project Intent with the Platform document; target: the Resolved Deployment with its typed resources), the concrete syntax and its OCL-validating editor, and the constraints, and cites the parity-checked artefacts as evidence. It also states that the TypeScript production implementation is a second, hand-written declaration, compared with this one on validation, dependency resolution, errors and generated resources.

• Class diagrams are drawn from the .ecore files, not maintained separately.
• Each constraint shown is quoted with its code and the refusal fixture that proves it fires.
• The report's claims about scope match emf/docs/architecture.md and the parity contract.

Acceptance criteria

• The report is submitted by 2026-09-25, and its mirror in the repository matches what was submitted.
• Every artefact the report cites exists on main and is green in the emf job.

Blocked by

• Widen the Java Project Intent to every accepted example, and export its descriptor #84
• Refuse documents with OCL, addressed by JSON Pointer #85
• Model Platform Intent in Ecore, parse it, and check its cross-document references #86
• Model the Resolved Deployment target metamodel in Ecore #87