docs(bmns): reopen mission-critical application migrations #10

Merged
mxm merged 3 commits from bmns-028-mission-critical-scope into main 2026-08-10 07:03:46 +00:00
Owner

Summary

  • reopen BMNS-028 after correcting the mission-critical application scope
  • add serial BMNS-028E through BMNS-028K task cards for the seven remaining application CTs
  • keep BMNS-029 and BMNS-030 blocked until every child receives an explicit disposition

Changes

  • add the approved BMNS-028 scope design
  • add the documentation-only execution plan
  • replace the incorrect BMNS-028 closure and record per-service recovery, validation, rollback, and authorization contracts
  • keep both NAS systems outside BMNS-028 and avoid preassigning Orion or Taurus

No Forgejo issue; this records the operator's correction of the BMNS-028 scope.

Test Plan

  • nix flake check -L
  • git diff --check origin/main...HEAD
  • verified the PR contains only the scope design, implementation plan, and execution-board correction
## Summary - reopen BMNS-028 after correcting the mission-critical application scope - add serial BMNS-028E through BMNS-028K task cards for the seven remaining application CTs - keep BMNS-029 and BMNS-030 blocked until every child receives an explicit disposition ## Changes - add the approved BMNS-028 scope design - add the documentation-only execution plan - replace the incorrect BMNS-028 closure and record per-service recovery, validation, rollback, and authorization contracts - keep both NAS systems outside BMNS-028 and avoid preassigning Orion or Taurus ## Related Issue No Forgejo issue; this records the operator's correction of the BMNS-028 scope. ## Test Plan - [x] `nix flake check -L` - [x] `git diff --check origin/main...HEAD` - [x] verified the PR contains only the scope design, implementation plan, and execution-board correction
mxm merged commit b0ebe94ef0 into main 2026-08-10 07:03:46 +00:00
mxm deleted branch bmns-028-mission-critical-scope 2026-08-10 07:03:46 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mxm/homelab!10
No description provided.