BLACK HOUSE // GOVERNED MISSION ROUTER // XUNIA

XUNIAverse production pipeline

The public architecture view now mirrors the repository’s governed mission path: identity and scope checks, ontology grounding, planning, Zyra authorization, bounded dispatch, verification, evidence capture, and audit. This agent pipeline documents the control flow; it is not a remote-control surface and does not claim background execution from the browser.

ROUTER CONTRACT VERIFIED FAIL-CLOSED EVIDENCE-FIRST HUMAN-GOVERNED WRITES

Canonical mission flow

The ten documented routing stages are shown in execution order. Component labels describe the primary responsibility, not an exclusive implementation boundary.

RVIA

Mission intake

Accept the governed mission envelope and establish the routing contract for the requested work.

IDENTITY

Scope + principal

Resolve who or what is acting, the allowed scope, and the authority attached to the mission.

SHADOW GLASS

Preflight

Inspect mission context and constraints before planning or external action is allowed to proceed.

ONTOLOGY CONTEXT

NXYZ + knowledge graph

Ground objects, links, repositories, services, evidence, policies, and prior state in the shared ontology.

PLANNER

Reasoning layer

Turn the grounded mission into an explicit plan with required capabilities, bounded tools, and verification criteria.

ZYRA AUTHORIZATION

Policy gate

Authorize, deny, or require approval based on policy, mutation risk, scope, and the requested tool boundary.

DISPATCH

XUNIA orchestration

Route approved work to the registered builder, agent, cloud, registry, or integration target needed for the mission.

GLASS ONION

Verification

Compare claimed outcomes with observable results, tests, postconditions, and returned tool evidence.

EVIDENCE

Proof capture

Persist result evidence, provenance, attempts, outputs, and verification state instead of relying on completion claims.

AUDIT

History + feedback

Record the durable mission timeline and feed verified state back into later routing and ontology context.

REGISTERED DISPATCH TARGETS selected by mission requirements; not all run on every mission

XUNIA GPT-DOUG MAX VIRGINIA WAKEUP3LM ZYRA NXYZ ZYRA CLOUD AIP REGISTRY PALANTIR

DENY / HOLD PATH

If Zyra authorization fails or required approval is missing, dispatch does not proceed. The denial/hold state and reason become part of the mission record.

VERIFY → REPAIR → RETEST LOOP

A failed verification result can return the bounded mission to planning or execution for repair. Success is based on observed proof, not an agent saying “done.”

CONTROL PLANE

The Black House defines the canonical mission, routing, ontology, agent/service registry, evidence, and audit contracts.

EXECUTION BOUNDARY

XUNIA coordinates approved work. External writes and higher-impact mutations remain subject to authorization and postcondition checks.

PUBLIC PAGE

pipeline.html is documentation. Animated or visual flow never implies that this browser page is itself running private agents.

Repository source of truth: mission router manifest, mission envelope schema, and ontology schema.