Surface-MORK Unified Projection Program — Plan

Unit: surface-mork-unified-projection
Type: Program/Epic
Status: Phases 0–8 complete; Phases 9–10 planned
Last updated: 2026-09-22
Owner: Surface and MORK maintainers


Executive Summary

This plan adopts a single top-level authoring approach for projection in LATTICE:

This avoids a third mapping language while preserving MORK’s machine contract for governance, provenance, and review.

Status: Phases 0–8 are complete and verified ✅ (see surface-mork-unified-projection.md). Phases 9–10 are planned, not started.


Architecture

Core Pipeline

Domain and substrate declarations
        ↓
Surface contracts (Promotion, Index, Projection)
        ↓
Surface validator and normaliser
        ↓
Surface-to-MORK lowering
        ↓
Validated MORK graph
        ↓
Target compilers
  - MORK to SPARQL
  - MORK to SHACL
  - MORK to SWRL
  - MORK to RML
  - MORK to native IR
        ↓
Generated artefacts (with provenance, governance, version records)

Responsibility Split


Phases (1-10 Roadmap)

Phase 0 — Architecture lock and ADR updates

Status: ✅ Complete
Scope:

Phase 1 — Surface Projection specification

Status: ✅ Complete
Scope:

Phase 2 — Surface compiler refactor and entailment policy

Status: ✅ Complete
Scope:

Phase 3 — Surface-to-MORK lowering engine

Status: ✅ Complete
Scope:

Phase 4 — MORK governance and versioning enhancements

Status: ✅ Complete
Scope:

Phase 5 — Compiler family implementation

Status: ✅ Complete
Scope:

Phase 6 — Eligibility tranche

Status: ✅ Complete (IntervalContainment strategy only)
Scope:

Not yet built:

Phase 7 — Provenance and invalidation hardening

Status: ✅ Complete (depth-1 scope)
Scope:

Deferred:

Phase 8 — Conformance and parity framework

Status: ✅ Complete (current Surface/Eligibility scope)
Scope:

Verification checklist: 7/8 items complete; SWRL reasoner integration (item 7) pending.


Phase 9 — Migration and rollout

Status: 🚧 Not started
Scope (planned):

Estimated: 2–3 weeks


Phase 10 — Scale and optimization

Status: 🚧 Not started
Scope (planned):

Estimated: Duration TBD (performance-dependent)


Acceptance Criteria

Authoring experience (✅ Met)

  1. ✅ Domain authors produce valid projection intent without raw MORK internals
  2. ✅ Same projection contract generates at least two backend families (SPARQL, SHACL confirmed; SWRL generated)
  3. ✅ Authoring docs sufficient for first successful compile in one session

Correctness (✅ Met)

  1. ✅ Deterministic regeneration for identical inputs (verified by test suite)
  2. ✅ Parity between source and generated artefacts (tools/surface/parity.py)
  3. ✅ Traceable provenance from output to source (full chain implemented)

Governance (✅ Met for current scope)

  1. ✅ Production compile mode rejects unapproved mappings (Phase 4 implementation)
  2. ✅ Mapping version and effective date policies enforced (Phase 4 SHACL shapes)
  3. ✅ Review state and provenance queryable (Foundation alignment complete)

Eligibility readiness (✅ Met for IntervalContainment)

  1. ✅ Interval containment works end-to-end
  2. ✅ Undetermined outcomes explicit with diagnostics
  3. ✅ SPARQL and native backends agree (15/15 tests + worked example verification)

Repository Structure

Surface layer

MORK layer

Eligibility integration

Architecture and governance


Risk Register and Mitigations

Risk Mitigation
Surface scope expansion causes conceptual drift Strict subsystem boundaries (Promotion/Index/Projection), separate shapes, separate compiler modules
MORK governance changes break compatibility Compatibility mode profiles, migration scripts, staged validation levels
Backend semantics divergence Shared executable IR + parity tests (all 15 MORK tests pass)
LLM completion introduces unstable mappings Deterministic mode default, governance gate for LLM nodes
Performance cost at scale Phase 10 optimization plan with caching and incremental regeneration

Governance Model — Three Operational Modes

Draft mode

Review mode

Production mode

A release cannot pass production gate without all four checks.


Completed Deliverables Checklist


Next Steps (Planned)

  1. Phase 8 final sign-off: Resolve SWRL reasoner verification blocker (item 7 of checklist)
  2. Phase 9 decomposition: Break migration/rollout into slices; author migration guides
  3. Phase 10 planning: Characterize performance profile; identify caching opportunities
  4. Phase 9.1 Pilot: Migrate one real domain to Surface-MORK; validate compatibility

Documentation and References


Maintenance

This plan is updated when:

Last updated: 2026-09-22
Next review: Phase 8 SWRL verification complete or Phase 9 ratification