govoplan-risk-compliance/docs/INTERFACE_PATTERN_MIGRATION.md

Risk Compliance interface pattern migration

Risk Compliance uses the platform source-evidence, governed-operation, review-queue, and revisioned-record patterns. It owns sanctions screening and assurance evidence; Connectors owns optional external source acquisition.

Surfaces

• risk_compliance.workspace is the stable route surface and risk_compliance.navigation is its navigation entry.
• risk_compliance.sanctions.sources lists immutable source snapshots. risk_compliance.action.import-snapshot confirms copying acquired connector evidence into the normalized sanctions store.
• risk_compliance.sanctions.screening collects the minimum subject data needed for a version-pinned run. risk_compliance.action.run-screening creates durable screening evidence.
• risk_compliance.sanctions.review is a list-detail review queue. risk_compliance.review.disposition appends a legal disposition or time-bounded reusable exception.
• risk_compliance.assurance.graph exposes current effective assurance revisions and their bounded relationships. risk_compliance.assurance.editor appends object revisions and risk_compliance.action.connect-assurance appends typed relationships.

Backend and WebUI manifests publish the same surface identifiers and parent hierarchy so Views can reduce the workspace without private module knowledge.

Consequences and recovery

Snapshot import is confirmed because it creates immutable normalized evidence. Importing the same content reuses the existing snapshot. A screening run pins that snapshot version and clears the transient subject draft after the backend has accepted the run.

Review dispositions are append-only. Reusable exceptions require an explicit expiry. Assurance edits preserve earlier effective-dated revisions, while system-managed sanctions projections remain read-only. A failed request leaves the draft available; navigating away from a changed screening, disposition, assurance object, or relationship invokes the shared unsaved-change guard.

Unavailable actions remain visible with selection, permission, busy-state, missing-snapshot, system-managed-record, or optional-provider reasons. Contextual help resolves through govoplan-docs when enabled and through the hosted fallback otherwise.

Optional boundaries

Connectors may announce sanctions-source snapshots through its public capability. Risk Compliance does not import connector internals or credentials. Audit, Policy, Records, Files, Tasks, Notifications, Views, and Workflow integrations remain optional and communicate through declared capabilities, interfaces, and stable references.