Package: ASTRA_INTAKE_READY / Server & Control-Plane Canonical Handoff
Owner / Final Architectural Decision Authority: Alexander Romaskevich
Public signature: RomaskevicH
Architecture: Federated Multi-Orchestrator Architecture
Checkpoint: 2026-09-11

This file is the canonical handoff for Astra. Astra must consume this state before spending reasoning/tool budget on infrastructure reconstruction. Do not infer topology from legacy project names, temporary bridges, or auxiliary runtimes.

Node	Provider	Canonical role	Runtime capability	Leader eligible
VAL_TOWN_PRIMARY	Val Town	PRIMARY	FULL_CONTROL_PLANE	yes
SUPABASE_NODE_3	Supabase	HOT_STANDBY	CONTROL_PLANE_STANDBY	yes, failover only
NETLIFY_NODE_2	Netlify	SECOND_STANDBY	HEALTH_BRIDGE_ONLY	no

Canonical control-plane node count = 3. Auxiliary Render/Remote Desktop/runtime nodes are not part of this three-node control-plane count.

astra_server_bindings.json contains GENERAL_INFRASTRUCTURE_BINDINGS (for example the public imperialcore.netlify.app web runtime). The hanter_control_plane section contains the separate CANONICAL_THREE_NODE_CONTROL_PLANE resources (including the dedicated Netlify hanter-bridge-node-2 site). These are intentionally different resource scopes and must not be merged or treated as conflicting server identities.

• HANTER leader: VAL_TOWN_PRIMARY.
• Leader epoch: 6 at remediation verification.
• VAL_TOWN_PRIMARY: ACTIVE, HTTP 200, consecutive failures 0.
• SUPABASE_NODE_3: STANDBY, HTTP 200, consecutive failures 0.
• NETLIFY_NODE_2: STANDBY, HTTP 200, consecutive failures 0.
• Supabase project flqxwhibxnyujynmopmr: ACTIVE_HEALTHY at verification.
• Netlify production deploy for hanter-bridge-node-2: READY at verification.
• HANTER status API version after normalization: 1.1.1.

VAL_TOWN_PRIMARY runs on a 15-minute interval. The Supabase standby tick checks primary freshness using a 35-minute safety window. While the primary heartbeat is fresh, the leader lease belongs to VAL_TOWN_PRIMARY. SUPABASE_NODE_3 may acquire/renew leadership only when the primary is stale/unavailable. NETLIFY_NODE_2 is a health bridge and must not become leader.

The remediation migration is hanter_canonical_primary_failover_v8.

The following Val Town projects are retained only to avoid destructive cleanup and are explicitly non-canonical:

• oromaskevic23/hanter-bridge-node-1 — legacy health bridge only; NOT PRIMARY.
• oromaskevic23/hanter-bridge-node-2-temp — ARCHIVED / DO NOT USE.
• oromaskevic23/hanter-bridge-node-3-temp — ARCHIVED / DO NOT USE.

Do not route control-plane decisions through those objects.

REMOTE-DESKTOP-BRIDGE-001 is an auxiliary access/runtime channel, not one of the three canonical HANTER control-plane nodes. Its last verified live connector state during remediation was OFFLINE; registry state was normalized to OFFLINE_AUTH_REQUIRED so stale metadata does not imply availability.

Use hanter_status.ts in oromaskevic23/imperial-nca-runtime-recovery as the human/agent-facing canonical status projection. It exposes canonical self, leader identity, exactly three control-plane nodes, and an explicit boundary separating auxiliary runtime nodes.

Do not repeat infrastructure discovery if the last verified evidence remains current and no material state changed. Revalidate only after a runtime/code/credential/provider/deployment/security/financial state change, live error, failed action, timeout, rate limit, or a materially stale checkpoint required for live execution.

The prior false DEGRADED state was traced to registry policy v2.0.0 classifying registered specialized NCA-CYBER-* namespaces as invalid. Policy v2.1.0 now recognizes the registered runtime namespaces NCA-###, NCA-CYBER-###, and NCA-CYBER-HAK-### without renaming any agent or changing canonical governance membership.

Verified reconciliation after repair: 1777 total agent records = 1733 valid runtime NCA + 44 non-NCA records; invalid NCA format = 0; duplicate agent IDs = 0; duplicate numeric IDs = 0; missing numeric IDs = 0. ORION fleet cycle = PASS, verifier = PASS, watchdog = PASS, missing ORION bindings = 0, unread canonical briefs = 0 after feedback. ORION remains ADVISORY_ONLY.

ORION delivery was also normalized from per-agent insert batches to a set-based SQLite insert so the 1600+ agent advisory cycle completes within the runtime window without partial delivery.

Other Astra-readiness directions may remain PARTIAL/BLOCKED for reasons unrelated to three-node server topology. Do not reopen server topology remediation solely because another mission direction is incomplete.

Preserve AI Passport, Enterprise Skills, Guardian Core, Approval Gateway, Audit Ledger, Zero Trust, capability-based authorization, Public/Private Boundary, CRYPTO IMPERIAL Ecosystem Boundary, and the Federated Multi-Orchestrator Architecture. HANTER is AI Command Center / Deputy to the Architect within delegated bounded authority; it is not a global orchestrator. ORION is advisory-only. Final architectural authority remains with Alexander Romaskevich.

ARCHITECTED != IMPLEMENTED != RUNTIME_VERIFIED != PRODUCTION_VERIFIED.

A health check proves endpoint/runtime health only. It does not prove full production execution, external commercial success, payments, or unrestricted authority.

The Architect authorized Scrapling and ScrapeGraphAI as Astra-supporting public-web research capabilities under FREE_ONLY, Zero Trust and the existing Public/Private Boundary.

Canonical reference: ASTRA_WEB_SCRAPING_TOOLCHAIN.md. Live governed status: scraping_toolchain_status.ts.

Current truth state:

• Scrapling 0.4.15: governed IMPERIAL skill registered at skills/scrapling/SKILL.md.
• ScrapeGraphAI 2.2.4: governed skill baseline updated at skills/scrapegraphai/SKILL.md; telemetry disabled by default; paid managed API denied; AI graph execution requires a separately verified local/self-hosted LLM worker.
• VAL_TOWN_PRIMARY: live adapter/status HTTP 200 with security self-test PASS.
• SUPABASE_NODE_3: JWT-protected imperial-scraping-toolchain Edge Function deployed ACTIVE as a control-plane adapter.
• NETLIFY_NODE_2: toolchain versions/policy/status URL config-bound; node remains HEALTH_BRIDGE_ONLY, and no native Python package execution is claimed.
• Native Python worker deployment is not yet production-verified across the canonical control-plane nodes. A separate Render worker attempt was blocked by the free Hobby 25-service cap; no service was deleted.

Astra should reuse this binding rather than rediscovering the tools. Prefer official structured connectors/APIs when they provide equivalent evidence. Public-web extraction does not grant authority to bypass authentication, CAPTCHA, paywalls, site access controls, robots/Terms, network boundaries, or financial/security governance.