Establish the successor semantic baseline

[Allann]

Question

Which legacy Modeller and rules capabilities, gaps, and constraints must the successor preserve, replace, or retire?

[Allann]

Resolution

The successor baseline is established from the legacy implementation, specifications, tests, and rules prototype.

• Modeller's documented behaviour-first intent is ahead of its executable semantic model, which currently centers entities and endpoint-like command/query contracts.
• Several parsed concepts are not yet integrated into the resolved semantic graph; behaviours lack first-class participants, rules, guards, invariants, effects, transitions, workflows, and diagram projections.
• The legacy rules prototype contributes valuable decision tables, graph evaluation, expressions, hit policies, traces, explanations, and editing concepts.
• It must be adapted behind a Modeller-owned semantic model rather than transplanted.
• Known runtime concerns include object-typed facts/results, layout mixed with semantics, shared per-decision evaluation state, incomplete cancellation propagation, hard-coded validation, unstructured statuses, ambiguous expression ownership, and missing dedicated conformance coverage.

Constraints carried forward:

• Rules produce typed conclusions and explanations; behaviours own effects.
• Diagrams are projections over authoritative semantic meaning.
• External rule formats and runtimes are adapters.
• Implementation begins only after this map's architectural handoff.