Governance Review Surfaces (MORK Bench and Surface Studio) Implementation Status

Unit: governance-surfaces State: Skeleton UIs implemented, fixture-backed, pending backend integration Sketches:

Governing ADRs: ADR-A38, ADR-A42

What was built

Two fixture-backed UI shells that demonstrate the governance surface designs without backend integration:

Surface Contract Studio

MORK Review Workbench

Design Sketch Coverage

governance-and-versioning-migration.md specifies:

Design element Implemented Status
Thesis: MORK is substrate, not interface Yes Both UIs hide MORK graph, show domain claims
Four roles with separate perimeters Partially Studio shown for Surface author; Bench shown for Domain Steward; perimeter enforcement incomplete
Six review decisions (Confirm/Retarget/Reshape/Decline/Teach/Defer) Yes All six buttons present in Bench
Section as unit of judgement Yes Bench shows sections in queue sidebar
Token ribbon evidence display Partially Evidence displayed (Witness/Coverage/Alternative); token granularity not yet shown
MCN source affordance (View source) No Not yet implemented
Role-restricted content (no pack internals, teaching, syntax for Steward) Partially Fixture demonstrates restriction; not enforced in live integration

Gaps and Constraints

Evidence

Next Phase Work (Phase 2 and Phase 5 handoffs)

To move from skeleton to integrated surfaces:

  1. Backend wiring (Phase 2): Connect Studio to Surface revision API; connect Bench to review snapshot schema
  2. Permission model (Phase 2, Phase 5): Enforce role-based visibility for Steward/Engineer/Owner/Maintainer roles
  3. Evidence projection (Phase 5): Implement dynamic evidence projection per ADR-A42
  4. State management (Phase 2, Phase 5): Wire lifecycle state machine and decision persistence to ledger
  5. Token ribbon rendering (Phase 5+): Detailed MCN token-level evidence display for Teaching pack integration

Acceptance

The design sketch is well understood and the UI shells correctly demonstrate its intent. Skeleton implementation is complete. Full acceptance requires backend integration work in Phase 2 and Phase 5 validation gates.

Deferred (out of scope for skeleton phase)