---
name: saturated-mailbox-sovereign-recovery
description: Restore Stephanos Control Tower and guarded canonical mailbox cutover without Codex, Work or Remote Desktop Commander meter dependence; avoid saturated GitHub issue transport and preserve original native custody.
---

# Saturated mailbox: sovereign Control Tower and original-owner cutover

For conversational Control Tower, self-repair or no-meter requests, first read
[Sovereign conversational control](../use-sovereign-commander/references/conversational-control-v1.md).
Use its fixed observation/build routing only after current-source and native
adoption checks; preserve every existing private capability and authority gate.

This skill is a bounded workflow for the existing #2315, #2961, #1557 and #2968 owners. It provides **guidance, not a callable tool, runtime installation, source-writer grant, approval, queue, reviewer, or new command transport**. Installing this skill does not establish cloud ChatGPT-to-Battle Bridge access or change an installed service.

## Discover the real route, never invent one

1. Read protected `main` and the exact blob of `shared/agents/canonicalMailboxAuthorityV1.mjs`; obtain the canonical issue number from this fresh source, not from this skill. Inspect actual successor marker and current issue comment capacity. If the selected canonical issue has reached its hard limit or returns a denial, **do not keep attempting new command comments**, edit/delete history, replay prior commands, or use the inactive successor as a substitute. Never route to a retired issue.
2. Check for genuinely exposed private local Sovereign Commander MCP tools and their authenticated runtime identity. The existing personal plugin's local stdio configuration does not prove tool exposure in an iPad/cloud chat. Use only listed and qualified fixed actions, not arbitrary shell. Local OpenClaw/Ollama/Forge can act only through their existing authenticated host/controller/lease mechanisms.
3. If private MCP is not callable, inspect the existing source-controlled, operator-authenticated GitHub Actions Control Tower workflow `.github/workflows/stephanos-control-tower-build.yml` at fresh protected main. Use only its currently defined fixed operations and verified native consumer. Where present and adopted, `OBSERVE_CONTROL_SYSTEM` reads bounded native status; `BUILD_NEXT_ELIGIBLE_GOAL` keeps the original guarded goal-building path. A GitHub connector's ability to read PRs, comment or rerun jobs is not `workflow_dispatch`. Do not simulate an owner event, open fake issues/PRs or rerun a first-attempt-only workflow. An authorised owner UI dispatch still needs exact trusted run/artifact, authenticated relay uptake, original durable ledger evidence and the existing native owner's admission.
4. A successful Actions request or healthy relay is **not a source build**. Require canonical SELECT→CLAIM→actual operating-system pickup→material edit→tests→qualified independent review→approved protected integration→live served runtime proof. If existing native maintenance custody is held, preserve it and report the typed refusal; do not submit repeated new wake requests while an outcome is uncertain.

## Finish the two distinct workstreams without deadlock

**Control Tower build path**: Reuse #1557/#2961 original owner and merged source. Correct the existing #3303 native transport-cancellation claim-retention issues within its original writer reservation, obtain genuinely qualified exact-head Windows-authority specialist coverage, guarded protected integration and separately approved physical host adoption. Prove one actual original-worker build under truthful source, gaming and process custody. Continue safely disjoint tasks through qualified existing providers while this owner is held. Never count observation or external handoff as material pickup.

**Mailbox rotation path**: The existing #3302 source is a **design** for a purpose-scoped private rotation control carrier when a predecessor issue is saturated. It is not a commissioned native signer or installer. Original #2315 owner must independently implement, review and enroll the fixed purpose-only FREEZE/DRAIN/STATUS authority, keeping the original command executor, ledger, fence, signed evidence and review/protected gates. Control Tower BUILD_NEXT_ELIGIBLE_GOAL must never be promoted into mailbox-rotation authority. Preserve original activation PR #3268 and its branch. An authentic FROZEN fence, empty native/outbox/Actions work and current-head qualification must precede an exact-operator-approved protected merge. Then require guarded main adoption, producer and consumer epoch acknowledgements, two distinct owner-authored successor read-only ACCEPTED→DONE loops, and final VERIFY. Source presence and a read-only pre-drain assessment are not live cutover proof.

## Meter and sovereignty truth

Prefer local Sovereign Commander, OpenClaw/Ollama, native Forge, local tests and appropriately qualified Sovereign Reviewer over metered Codex/Work/Remote Desktop Commander whenever a lawful, actual scope-matching capability exists. Do not ask Codex to perform recurring review by default when its meter is empty. Hosted GitHub API, Actions and branch protection are still external/quota-bearing and do not become local sovereignty by renaming them. Security-sensitive Windows custody requires a genuinely qualified independent specialist; an unqualified local model or documentation claim cannot waive it.

## Report exactly what changed

Keep one original owner per lease/branch and one requestId through uncertain transport. State the exact checked source head, status of original PRs, real callable route, current custody predicate and whether a source commit, accepted request, physical pickup, reviewed merge, installed adoption or verified cutover actually occurred. If blocked, identify one smallest owner-owned capability gap and keep unrelated legitimate work alive. No false green and no repeated diagnostics as a substitute for work.