# ML-NIGHTWORX — Hermes Dashboard Estate
> © 2026 ML-NIGHTWORX (ML-NTWX) · Commander: Mark Lewinsohn · ml-nightworx.io
> Internal working documents. Statuses machine-verified 2026-08-22 (HTTP codes from M5 Mac).

## What this estate is
A four-view command surface over the ML-NIGHTWORX product ecosystem, merged from two
independent AI-harness audits: a Hermes conversation-corpus audit (16,719 messages,
206 sessions, 2026-07-22→08-22) and a Cursor Cloud Agent audit (37 runs, 40 projects,
14 MCP servers). Every project is source-tagged H (Hermes-seen) or C (Cursor-seen).

## Pages
- [NTWX-HQ.html](NTWX-HQ.html) — Unified 6-tab command console (iframe shell): Org, Audit Master, Cross-Reference, Polyglot, Sync Map, Explorer. Deep links: #audit, #xref2, #polyglot/mesh etc.
- [NTWX-ORG-DASHBOARD.html](NTWX-ORG-DASHBOARD.html) — Agent organisation: ATLAS chief-of-staff, 4 vertical chiefs (MERIDIAN/Commerce, VECTOR/Trading, SPECTRE/Intel, CIPHER/Platform), 7 Archers, launch prompts.
- [NTWX-AUDIT-DASHBOARD.html](NTWX-AUDIT-DASHBOARD.html) — 62 findings traffic-light dashboard, filterable by vertical/project/severity + free text; priority roadmap.
- [NTWX-AUDIT-CROSSREF-v2.html](NTWX-AUDIT-CROSSREF-v2.html) — Vertical × project cross-reference, 48 project cards with drill-down filters.
- [hermes-master-dashboard.html](hermes-master-dashboard.html) — ALL projects with status badges (LIVE/DEV/PAUSED/PLANNED/ARCH), 120 scored next-steps across 40 cards, MCP registry, governance findings.
- [hermes-sync-map-v2.html](hermes-sync-map-v2.html) — Business architecture: 4 pillars (Intel, Glass Fleet, Trading Engine, Commerce), 3 channels (CH1 intel pipeline, CH2 trading telemetry, CH3 money rails), isolated lanes (Sovereign Messenger air-gap, experiments).
- [hermes-explorer.html](hermes-explorer.html) — Filterable value-chain explorer: every product as a node with upstream/downstream edges; filter by pillar, status, source; search by name/URL.
- [hermes-polyglot.html](hermes-polyglot.html) — AI interconnect mesh: 6 models, 3 harnesses, 15 MCP servers; usage ledger (GLM-5.2 5,142 calls main; free-tier risk lanes flagged); 10 named call routes R1–R10.

## Key facts an agent should know
- Live flagship surfaces: reflector.ml-nightworx.io · nighthawk.ml-nightworx.io (+ -api) · aaas.ml-nightworx.io (catalogue + llms.txt) · payflow.ml-nightworx.io · dome.ml-nightworx.io
- Known-dead advertised hosts (do NOT cite as live): studio.ml-nightworx.io (NXDOMAIN) · moat.* (522) · oasisproperty.* (404) · legal777.* (NXDOMAIN) · runtime-api/runtime-mcp.* (NXDOMAIN)
- "PayBridge" names THREE distinct products: (1) multi-rail plan (Hermes-era, PLANNED), (2) x402 simulation MCP (PAY_BRIDGE_ENABLED=false), (3) MoneyGram cash rail (zero code). Do not conflate.
- Sovereign Messenger (localhost:5005) is deliberately air-gapped — zero cloud egress by design; do not assign it public endpoints.
- Trading systems (ONOS/Kronos MK5, M3-Maya CTS) run under a frozen statistical gate (2h/12bps/n≥30); PAPER_ONLY until gate clearance. Never advise live deployment.
- Source of truth data: cursor-audit/inventory.json (sha256 e4886fc2c79025df44a544d8a4773be224b9bb84a480742201dfe405ef389fea).

## Suggested questions for agents
- Which ML-NIGHTWORX products are LIVE vs PAUSED as of 2026-08-22?
- What is the PayBridge naming collision and which product does each URL belong to?
- What are the four business pillars and which channels connect them?
- Which MCP servers are ready vs needsAuth vs dead?

## Agentic commerce (placeholder)
- Catalogue surface: aaas.ml-nightworx.io/llms.txt (live; 3 dead SKUs flagged for delisting)
- Payment rails: Stripe live (lv2.ml-nightworx.io) · x402 USDC sim (PAY_BRIDGE_ENABLED=false) · MoneyGram ramp (planned, zero code)
- x402/MCP endpoint: paybridge-api.ml-nightworx.io/mcp (LIVE, spec-drift flagged MCP-008)
- Agent-payable SKU registry: [PLACEHOLDER — pending PayBridge untangle, see audit WEB-001/MCP-008]
- Discovery for commerce agents: this file + aaas llms.txt are the canonical machine-readable surfaces.

## Ownership & contact
© 2026 ML-NIGHTWORX · ops@ml-nightworx.io · crawler policy: robots.txt (AI crawlers welcome on dashboards, cursor-audit/ gated)