---
name: verify-sovereign-runtime
description: Verify Sovereign Commander, Stephanos AI and the goal-building conveyor from live, exact-head Battle Bridge receipts; distinguish MCP capability activation, controller health and material building without using remote-control vendor meters.
---

# Verify Sovereign runtime and climb the stack without claiming false greens

Use alongside `use-sovereign-commander`; do not invent an alternative machine endpoint, controller, scheduler, reviewer, publisher or source-lease plane. This skill is a verification procedure, not a tool grant.

## One evidence chain, minimal GitHub reads

1. Read the current `main` SHA from the actual `Cheekyfellastef/stephan-os` repository. Never recycle a prior turn's SHA without rechecking.
2. Prefer the small `#1575` authoritative receipt index to discover the latest terminal request IDs. Read only the specific matching `#2808` receipt comments required for the current question. Avoid repeated full issue-comment scans, duplicate action submissions and GitHub API hammering.
3. Use the connected authenticated local/private Sovereign MCP when actually exposed in this client, or the existing canonical owner-approved #2808 fast/scheduled mailbox fallback where the user's action-category authorization exists. A skill install alone does not connect local stdio to ChatGPT web/mobile. Never use arbitrary commands, paths, URLs, external script execution or shell via public GitHub comments.
4. Bind an allowed mailbox request to the fresh exact `main` head, a unique stable `requestId`, existing schema, short expiration and real operator approval. Check the canonical allowlist in source before dispatch. Reuse its request ID for retries; an ACCEPTED checkpoint or healthy relay is not terminal execution. Do not create a second request for a potentially running mutation.
5. Verify a terminal DONE/BLOCKED/REJECTED result, exact request ID, process head, typed blocker and supported proof hash. `visibility-snapshot` proves an observation, **not** physical worker pickup. If the terminal receipt is missing or its head differs, mark the observation unproven.

## Private MCP v5 proof is not source presence

The source implementation for private `get_file_info` and `read_multiple_files`, and the generation-activation repair in PRs #3080, #3082 and #3089, do **not** prove the running service exposes them. An authorised `private-mcp-parity-proof` is a registered, one-shot, read-only #2808 action which checks authenticated local tool listing and invokes fixed, bounded calls; report the typed terminal acceptance and capability booleans or a precise blocker. Do not disclose local paths, filenames, contents, raw MCP payloads, tokens or secret-related metadata through public GitHub. Do not substitute `/health` for authenticated tools-list plus successful tool calls. Never terminate or restart a process merely to improve a reported version; guarded lifecycle is separately owned and reviewed.

## Stephanos AI elevation needs actual tool use

The existing `/sovereign` chat route currently has a narrowly bounded read-only health-tool acceptance; even passing `prove-stephanos-ai-commander` does not grant arbitrary PC control, source mutation, merge or a completed self-repair. Require a registered, approved tool action, its terminal receipt, and independently verified before/after state for every further capability. Keep reasoning/planning separate from execution authority.

## Goal-to-build and game protection

A source edit, dispatched request, healthy daemon, valid logical-controller fabric or GitHub PR is not a completed goal. Report SELECT -> CLAIM -> authentic OS process pickup -> material diff/tests -> qualified independent review -> protected owner-authorised merge -> live exact-main verification -> two unattended refills separately. The disputed original #2962 r7 source lease and gates under #2961 remain held until their existing signer/owner admits them; never release, spoof, quarantine-as-success or bypass this custody. Independent Seed Canopy proposal authoring, where qualified, must not steal the incumbent writer's task or claim a canonical goal built.

When gaming is protected, do not start local heavyweight models, builders or repair bootstraps. If governor state is missing/invalid, treat new local heavy work as held rather than assuming gaming inactive. Cloud-hosted independent work can continue within its own quotas. Avoid repeated GitHub polling and preserve the existing dirty checkout; no reset/force-push.

## Minimal report

Use evidence-backed traffic lights: 🟢 verified live, 🟠 source merged/proposed but runtime not proven, 🔴 explicit live blocker, ⚪ not checked. Include exact observation time, main head, terminal request ID, PR numbers with titles, capability tested, proof link, original lease status, whether any material code/build/merge occurred, and the precise next safe gate. Never imply this skill alone added tools or autonomy to Battle Bridge.