Public-safe operating docs

Claw Blueprint Docs

A compact guide to what gptswarm.net is showing, how it is built, what data is safe to publish, and where the system evolves next.

This page documents the public dashboard only. It does not expose private logs, tokens, raw scheduler state, private repo URLs, or internal health telemetry.

Read the quickstart → Open live dashboard

Quickstart

gptswarm.net is the public-facing Claw Blueprint: a designed operational surface for Hermes-Nexus on Pro. It summarizes scheduled agents, reusable skills, control-room checks, Home Assistant context, and NEXUS finance signals without leaking private raw data.

What to read first

Start with the dashboard hero, then Architecture, then Ecosystem. Those three blocks explain owner, live counts, and major surfaces.

Current public state

25 enabled scheduled jobs, 108 enabled skills, 134 local skill files, and knowledge graph 238 nodes/504 edges are exposed as high-level numbers only.

Source location

Static source lives in the local GPTSwarm site workspace; Vercel serves the production site from the public output directory.

Design system

The design posture is an operational command surface: dense but legible, dark by default, with one primary cyan accent and restrained violet/green/amber status colors. It should feel like a real control-room artifact, not a generic SaaS landing page.

#060711
base

#0e1222
surface

#6de7ff
signal

#9b7cff
identity

#45e69d
healthy

Typography

System sans for fast reading. Monospace is reserved for owner badges, timestamps, paths, project IDs, and operational metadata.

Interaction

Navigation anchors are simple and durable. No fragile client-side framework is required for the public surface.

Architecture

The public dashboard reduces a multi-bot operating environment into four understandable surfaces. Each is intentionally named by role, not by private implementation details.

Home Assistant

Sensor mesh and home automation: Matter, cameras, Hue, energy posture, and household context.

Claw Core

Hermes-Nexus on Pro: scheduled work, skills, control-room receipts, and public-safe synthesis.

NEXUS

Finance and trading signal surface. Public page shows posture and system roles, not account secrets or raw positions.

OpenClaw

External communication boundary. The public docs keep identity separation explicit: Nexus on Pro is not Zappo/OpenClaw.

Live Stable Active Prototype Not wired

Deployment

The site is static HTML served by Vercel. The project is intentionally boring: no backend, no public secret surface, and no build-time dependency chain required for the dashboard/docs pages.

Edit local sourceUpdate the static dashboard and docs files in the GPTSwarm site workspace.

Deploy productionRun a production Vercel deploy from the project root.

Verify public domainProbe https://gptswarm.net and /docs.html with HTTP checks plus browser render.

Project: claw-evolution-blueprint
Domain:  gptswarm.net
Output:  public/
Source:  local GPTSwarm site workspace

Data boundaries

Rule: publish interpretation, not raw internal state. Public pages can show owner, host, high-level counts, status categories, and public-safe descriptions. They must not expose tokens, private repo URLs, raw scheduler JSON, precise secrets paths, private Telegram IDs, or account credentials.

Allowed

Owner labels, public domain status, high-level cron/skill counts, broad component names, deployment project name, and public-safe roadmap items.

Not allowed

Secrets, raw logs, private channel IDs, tokens, credential file contents, live account data, unredacted internal URLs, or private source dumps.

Identity boundary: Hermes-Nexus on Pro may inspect other hosts when authorised, but this public page must not speak as Zappo/OpenClaw or merge historical records into live blockers without provenance.

Roadmap

The next useful iteration is not more decoration. It is better audience control: a compact visitor mode for fast comprehension and an operator mode for dense provenance.

Visitor mode

One-screen summary: what GPTSwarm is, what is live, and why it matters.

Operator mode

Expanded provenance: owner, source, last check, evidence age, and next action.

Freshness rail

Show which public values are current, stale, historical, or deliberately static.