Skip to content

docs(governance): per-EP migration-complete badge on the Migrate tab #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
viethqb merged 1 commit into from
Nov 13, 2026
Merged

docs(governance): per-EP migration-complete badge on the Migrate tab #78

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions platform/data-governance/engines-and-policy/migrate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,22 @@ The tab opens with *Profile \<profile\>: who owns each policy, whether it can mo

Every sentence explaining a verdict, a blocker, a disagreement or a refusal comes from the server verbatim, so the screen never tells you something different from what the server enforces.

## Migration status of the enforcement point

Above the list the tab shows a status badge for the enforcement point. It counts only operator policies, the hand-written ones; policies egret compiled are not part of it.

| Badge | Meaning |
|---|---|
| **Migration complete — every manual policy is in the model** | No operator policy remains un-migrated on this enforcement point. |
| **N to migrate** | N operator policies can be migrated but have not been yet. |
| **M blocked** | M operator policies cannot be migrated at all. Each is listed with its name and the reason. |

A blocked policy keeps the enforcement point **incomplete** until you remove it or rewrite it so that it can be migrated. Migrating the other policies does not complete the enforcement point while one is still blocked.

This completeness is the signal the per-enforcement-point switch to the model is planned to use.

<!-- TODO(SP3d): screenshot of the migration-complete badge once the demo stack is rebuilt -->

## Migrate policies

1. Tick the migratable policies you want. The line below the table reads *Selected: …* or *No policy selected.*
Expand Down
Loading