IMPERIAL Core — Provider Recovery Status — 2026-08-29

Verified current state

Provider #1 — Val Town

  • Original oromaskevic23/imperial-nca-31day-runtime: not present in authenticated project listing.
  • Recovery runtime: oromaskevic23/imperial-nca-runtime-recovery — ACTIVE_CONSERVATIVE_BASELINE.
  • Public skill status endpoint: HTTP 200.
  • SQLite: 100 agents; 100 RUNNING_RECOVERY; 100 network_ok.
  • Active skill bindings: 1700 across 100 agents.
  • ORION policy: ORION_ALWAYS_ON=1, mode FEDERATED_ACK_OUTCOME_LEARNING, authority ADVISORY_ONLY.
  • ORION latest manual cycle: PASS at 2026-08-29T02:09:15.211Z.
  • ORION feedback: PASS at 2026-08-29T02:09:24.995Z.
  • ORION watchdog: PASS at 2026-08-29T02:09:42.517Z; missingOrion=0; after recovery stale agents=0, unread=0.
  • Free-tier Val Town interval minimum: 15 minutes. Current runner/fleet-cycle/feedback/watchdog intervals are active at that minimum.
  • Truth boundary: recovery runtime active != original runtime restored != production.

Provider #2 — Netlify

  • Project hanter-bridge-node-2 exists, site id 7a998b62-9d9f-4114-b3c8-e1001ef56d77.
  • Visitor SSO requirement was disabled; password requirement is false.
  • Public /health remains HTTP 404 Site not found after two deployment-proxy attempts timed out.
  • A minimal health-only keyless payload was prepared locally, but upload/deploy completion was not verified.
  • Status: BLOCKED / NOT PASS.

Provider #3 — Supabase

  • Project flqxwhibxnyujynmopmr: ACTIVE_HEALTHY.
  • Edge Function hanter-bridge-node-3: ACTIVE.
  • Public function endpoint: HTTP 200.
  • Response declares provider supabase, mode keyless-transport, side effects denied, authority none, runtime claim health-only.
  • Status: VERIFIED LIVE (health-only node).

Provider diversity

PROVIDER_DIVERSITY_3_OF_3 = NOT PASS

Reason: Netlify Provider #2 still returns 404; original Val Town runtime has not been restored, although the recovery runtime is actively running the 100-NCA recovery baseline and ORION.

Continuity truth boundary

This file is persisted server-side in the imperial-obsidian export project and is Obsidian-ready Markdown. Direct write/sync into a local Obsidian Vault is NOT currently connected and must not be claimed as connected without evidence.