XUNIAverse domain ontology, defensive identity layer, CRM, compliance, licensing, market discovery, and governed execution fabric
XuniaDAO is the root and front door of the XUNIAverse domain. The Black House is the canonical global control-plane root.
THE BLACK HOUSE → GPT-DOUG-LLM MAX → XUNIA → GCPXUNIA → VIRGINIA → VA3LM → ZYRA → EVIDENCE
BLACK HOUSE KERNEL 3.0.0 · GLASS ONION 2.6 · XUNIAVERSE DOMAIN ROOT · AGENT IDENTITY · GCPXUNIA DEFENSE · VA3LM :8088 · PROVENANCE REQUIRED
XUNIA is bound to the canonical Black House Kernel 3.0.0. The global control-plane authority lives at sonoxo/gpt-doug-llm/the-black-house. XUNIA remains authoritative for its own XUNIAverse domain graph; it does not supersede the Black House control plane.
THE BLACK HOUSE global control plane
└─ GPT-DOUG-LLM MAX planner / orchestration
└─ XUNIA / XuniaDAO XUNIAverse domain root
├─ GLASS ONION observable governance + provenance
├─ GCPXUNIA / VIRGINIA identity + policy boundary
├─ VA3LM :8088 bounded coding runtime
└─ ZYRA / Zyra Cloud approval + execution + audit
Machine contracts: .black-house/kernel.json · .black-house/runtime.json · src/lib/black-house-kernel.ts
Canonical Black House vocabulary is fail-closed: typed objects, registered relationships, evidence provenance, and explicit approval for consequential mutations are enforced as kernel invariants.
Command: /glass xuniaverse
sonoxo/xuniadao is the canonical registry and ontology root inside the XUNIAverse domain for the Sonoxo repositories indexed in its machine graph. The Black House remains the ecosystem-wide control-plane authority.
XUNIA / XuniaDAO
├─ Core runtimes and products
├─ XUNIA extensions
├─ Defensive systems
├─ Product applications
└─ Reference/upstream repositories
Every indexed repository keeps its own license, history, ownership, and upstream attribution. XUNIAverse membership does not rewrite an upstream project's ownership or imply vendor affiliation.
Registry: ecosystem/xuniaverse.json
| Layer | Mission | Source |
|---|---|---|
| THE BLACK HOUSE | global control plane, canonical kernel, mission protocol, cross-repo identity and ontology authority | sonoxo/gpt-doug-llm/the-black-house |
| XUNIA / XuniaDAO | XUNIAverse domain root, registry, ontology, governance, CRM, compliance, licensing | sonoxo/xuniadao |
| GCPXUNIA | agent identity, auth brokering, cloud-defense policy model | docs/GCPXUNIA_DEFENSE.md |
| VIRGINIA | policy boundary between identity/auth and agent execution | ecosystem/gcpxunia-defense.json |
| VA3LM | coding/reasoning runtime and defensive command center | gpt-doug-llm/va3lm · 127.0.0.1:8088 |
| ZYRA | workflows, routing, approvals, bounded execution | sonoxo/zyra |
| SONOXO / GPT-DOUG-LLM | model brain, orchestration and Black House kernel host | sonoxo/gpt-doug-llm |
| AlmightySonoxo | creative/media layer | sonoxo/AlmightySonoxo |
| GPT-UAP-XO | bounded local agent runtime | sonoxo/gpt-uap-xo |
flowchart TD
B[THE BLACK HOUSE\nKernel 3.0.0 / Global Control Plane]
X[XUNIA / XuniaDAO\nXUNIAverse Domain Root]
I[Agent Identity\nSPIFFE + Attestation]
G[GCPXUNIA\nAuth Broker]
V[VIRGINIA\nPolicy Boundary]
A[VA3LM :8088\nReason + Plan]
R[Runtime Guardrails]
Z[ZYRA / Zyra Cloud\nAction Gate]
E[Audit Evidence]
P[Technology Peer Graph]
C[CRM + Compliance]
B --> X
X --> I --> G --> V --> A --> R --> Z --> E
X --> P
X --> C
C --> Z
Command: /glass defense
Identity route: /glass identity
BLACK_HOUSE_MISSION
→ XUNIA_SCOPE
→ AGENT_IDENTITY_VERIFY
→ GCPXUNIA_AUTH_BROKER
→ VIRGINIA_POLICY_BOUNDARY
→ VA3LM_REASON_AND_PLAN
→ RUNTIME_GUARDRAIL
→ ZYRA_ACTION_GATE
→ AUDIT_EVIDENCE
The defensive model treats governed agents as first-class principals. It prefers SPIFFE-style agent identities, short-lived credentials, DPoP/mTLS token binding, least-privilege scopes, centralized auth brokering, separate user-delegated authority, explicit review for broad grants, runtime guardrails, and evidence logging. Shared or long-lived agent credentials are blocked by policy.
Docs: docs/GCPXUNIA_DEFENSE.md · Contract: ecosystem/gcpxunia-defense.json
Command: /glass peers
XUNIA maintains an evidence-backed graph of credible technical peer/reference domains. Current references include Google Cloud Security Community, Google Security Operations, Google Threat Intelligence, Security Command Center, Security Validation, Cloud Security Foundation, and Palantir Ontology.
TECH_PEER → SECURITY_DOMAIN → SOURCE → CREDENTIAL_EVIDENCE → ASSESSMENT
Peer-review/reviewer credentials are represented as evidence objects. Public credential or affiliation claims require evidence; community participation is not automatically promoted to vendor endorsement.
Docs: docs/TECH_PEERS.md · Contract: ecosystem/tech-peers.json
Command: /glass ontology governance
Architecture:
BLACK HOUSE CANONICAL OBJECT/LINK TYPES
↓
XUNIA DOMAIN OBJECT → PROPERTY → LINK → ACTION → EVIDENCE → DECISION
The XUNIA domain ontology spans repositories, licenses, tokens, exchanges, compliance requirements, agent identities, auth providers, access policies, runtimes, guardrails, security events, technology peers, security domains, XUNIAverse nodes, evidence, assessments, and attestations. src/lib/black-house-kernel.ts translates domain types into the canonical Black House vocabulary.
Contract: ecosystem/governance-ontology.json
Command: /glass crm
ACCOUNT → CONTACT → LEAD → OPPORTUNITY → ACTIVITY → TASK → DEAL → CUSTOMER
Pipeline:
CRM_INGEST → AIT_NORMALIZE → CRM_RELATIONSHIP_GRAPH → VA3LM_ANALYZE → ZYRA_WORKFLOW → UAP_AGENT_TASKS
Docs: docs/CRM.md · Contract: ecosystem/crm.json
Command: /glass crm port
Supports bulk read, bulk write, export, import, and migration for CSV, JSON, NDJSON, and ZIP_BUNDLE, with schema mapping, dedupe, consent/provenance gates, dry-run, human approval, idempotent upsert, batching, audit, redaction, and rollback manifests.
Docs: docs/CRM_PORT.md · Contract: ecosystem/crm-port.json
Command: /glass certify crm
The repository implements the GDPR/HIPAA software and policy control model and keeps regulator/government certification claims false unless external operational evidence exists.
Docs: docs/GDPR_HIPAA.md · Contract: ecosystem/gdpr-hipaa.json
Command: /glass evidence
The evidence registry tracks real operational artifacts separately from source code and CI. Assessment states are COMPLETE, PARTIAL, or MISSING; code readiness is never automatically promoted to production compliance.
Docs: docs/COMPLIANCE_EVIDENCE.md · Contract: ecosystem/compliance-evidence.json
Command: /glass licenses
| Repository | License |
|---|---|
sonoxo/xuniadao |
Apache-2.0 |
sonoxo/zyra |
repository license controls apply; verify current LICENSE before reuse |
sonoxo/gpt-doug-llm |
MIT |
sonoxo/AlmightySonoxo |
MIT |
sonoxo/gpt-uap-xo |
Apache-2.0 |
Docs: docs/LICENSES.md · Contract: ecosystem/licenses.json
Command: /glass exchanges
GLASS ONION provides read-only adapters for Coinbase Exchange and Kraken public market-data APIs. It does not place orders, move funds, store exchange credentials, or self-declare exchange listings.
Docs: docs/EXCHANGES.md · Contract: ecosystem/exchange-market.json
Command: /glass xrpl
XUNIA registers sonoxo/xrpl-dev-portalXUNIA as a federated, read-only documentation extension while preserving XRPLF/xrpl-dev-portal as the authoritative upstream. This integration provides provenance and source resolution; it does not imply XRPLF endorsement and does not sign transactions, store wallet seeds, or move funds.
Docs: docs/XRPL_INTEGRATION.md · Contract: ecosystem/xrpl-documentation.json
Command: /glass xrpl pathways
XUNIA connects standards (XRPL-StandardsXUNIA-), the TypeScript client (xrpl.jsXUNIA), and the ledger node (rippledXUNIA) through a governed token-and-wallet ontology. Public validated-ledger reads are allowed. Transaction construction is unsigned; signing and submission require human approval and a user-controlled external wallet. Seeds and private keys are blocked from repository and audit storage.
Docs: docs/XRPL_TOKEN_WALLET_PATHWAYS.md · Contract: ecosystem/xrpl-token-wallet.json
Command: /glass collective defense
XUNIA maps public collective cyber-defense references into an evidence-backed peer ontology and control baseline. Alignment states are TARGET, IMPLEMENTED, EVIDENCED, and EXTERNALLY_ATTESTED; no organization, partnership, endorsement, certification, or proprietary-standard claim is inferred.
Docs: docs/COLLECTIVE_CYBER_DEFENSE.md · Contract: ecosystem/collective-cyber-defense.json
Command: /glass ait
Typed agents, systems, capabilities, sources, evidence, observations, hypotheses, decisions, workflows, actions, and controls with provenance-bearing relationships.
Contract: ecosystem/ait-ontology.json
Command: /glass uap
BLACK_HOUSE_MISSION → XUNIA_SCOPE → GPT_UAP_XO_PLAN → GPT_UAP_XO_BOUNDED_WORKERS → PROVENANCE_CHECK → ZYRA_ACTION_GATE
| Command | Purpose |
|---|---|
/glass |
GLASS ONION router |
/glass xuniaverse |
XUNIAverse domain registry |
/glass identity |
agent identity and auth-broker security |
/glass defense |
GCPXUNIA/VIRGINIA/VA3LM defensive pipeline |
/glass peers |
technology peer/source ontology |
/glass ontology governance |
XUNIA domain governance ontology bound to Black House kernel |
/glass ait |
AIT ontology/intelligence |
/glass crm |
CRM relationship/pipeline layer |
/glass crm port |
bulk CRM read/write/migration |
/glass certify crm |
CRM controls and internal attestation |
/glass evidence |
GDPR/HIPAA production evidence tracking |
/glass licenses |
verified repository license registry |
/glass exchanges |
live read-only exchange listing/ticker discovery |
/glass xrpl |
governed XRPL documentation and upstream source resolution |
/glass xrpl pathways |
token, wallet, client, node, approval and audit ontology |
/glass collective defense |
collective cyber-defense alignment and evidence gaps |
/glass uap |
GPT-UAP-XO bounded-agent route |
/VA3LM-SAGI |
VA3LM guardrail intelligence surface |
Black House is global control-plane root YES
XuniaDAO is XUNIAverse domain root YES
Kernel version must match canonical v3 YES
Agent identity before brokered auth YES
Short-lived agent credentials YES
Shared/long-lived agent credentials NO
Broad agent grants without review NO
Provenance required YES
Human review for consequential mutation YES
External exchange listing self-declaration NO
Exchange order placement NO
Code => production compliance inference NO
Automatic fund movement NO
Automatic governance voting NO
Arbitrary remote shell NO
yarn install --frozen-lockfile
yarn build:main
yarn test:unit
node --test apps/resilience-atlas/tests/*.test.mjsGitHub Actions lock the XUNIAverse domain registry, Black House kernel binding, GCPXUNIA defense model, agent identity rules, technology peer ontology, ecosystem governance, CRM, compliance, licensing, exchange discovery, and evidence contracts.
The agent-identity/auth model is derived from public cloud and security guidance. Palantir-style ontology alignment means object/property/link/action/function/governance modeling based on public documentation. These references do not claim vendor sponsorship, endorsement, partnership, or a live external deployment.
The Flow native token-registry code/data originated from the FlowFans community project. XUNIA preserves that provenance and attribution.