Cybercore Control Plane

📡 SIGNAL / UPDATES

What changed
in the grid.

The Control Plane update feed tracks new releases, packs, themes, compatibility notes, security signals, and install paths. It is versioned in this repository and can later be generated from GitHub Releases.

LIVE / CYBERCORE CONTROL PLANE

Every theme.
One control surface.

Browse all 312 registry themes, open family explorers, inspect Cybercards, and select a live palette from the browser. The same governed registry drives the Web Kit, native tooling, and installable packs.

Cybercore Control Plane Themes workspace with theme library, application preview, and inspector — **01 / THEMES**Theme library, live application preview, and inspector.

Cybercore Control Plane Creative Forge workspace — **02 / CREATIVE FORGE**Governed creative resources and starter profiles.

Cybercore Control Plane Components workspace with governed component resources — **03 / COMPONENTS**Governed component resources with source previews.

Cybercore Control Plane Effects workspace — **04 / EFFECTS**Motion profiles and Web Kit effect recipes.

Cybercore Control Plane Snippets and Assets workspace — **05 / SNIPPETS + ASSETS**Reusable code, assets, and provenance.

Cybercore Control Plane Sites workspace — **06 / SITES**Repository profiles and fallback contracts.

Cybercore Control Plane Validation workspace — **07 / VALIDATION**Schema, accessibility, provenance, and compatibility gates.

Cybercore Control Plane Publish workspace — **08 / PUBLISH**Versioned kit output, commits, Actions, and Pages deployments.

01 / THE CONTRACT

One file.
Every surface.

Every theme fills the same eleven slots. Five are surfaces and text, six are neons. Apps never hard-code a colour: they read a slot. Click a slot to copy its hex.

schema/themes/cybercore-tech.json

02 / THEME MATRIX

Every family.
Pick your signal.

All 312 Cybercore themes across the full registry, each previewed in its own colours. Click a card to repaint the page. Your choice follows you to every Cybercore site.

03 / MASHUP LAB

Splice two
themes.

A mashup takes the surfaces and text from one theme and the neons from another. Try cyberdyne chrome under synthwave light, or build your own and share the link.

BASE SURFACES · TEXT

ACCENT NEONS

SIGNATURE MASHUPS

BASE × ACCENTLIVE

CPU23%

MEM61%

NET4.2G

PASSschema.integrity0.4 ms

WARNpalette.contrastmuted on panel

FAILlegacy.hardcoded_hex3 found

DEPLOYINSPECTCANCEL

04 / PIPELINE

Edit the JSON.
Never hand-edit anywhere else.

schema/cybergrid.json is the only place a colour or a path is written down. Four runtimes read it, and every downstream tool reads one of those.

LIVE SCHEMA CHECKING VERSION… — families · — source themes · updated — OPEN CANONICAL JSON ↗

05 / DESIGN TOKENS

Same feel.
Every surface.

css/cybertokens.css holds everything that isn't a colour: type scale, spacing, radii and motion, mirrored in schema/tokens.json. Hover the motion lanes to run them.

TYPE SCALE 1.20 · MINOR THIRD

--fs-7Display

--fs-6Heading one

--fs-5Heading two

--fs-4Heading three

--fs-3Lead paragraph

--fs-2Body copy, 16px

--fs-1LABELS AND CHROME

SPACING 0.25REM STEP

--space-14

--space-28

--space-312

--space-416

--space-524

--space-632

--space-748

--space-864

RADII

sharp

sm

md

lg

pill

MOTION HOVER TO RUN

--ease-out · slow

--ease-in-out · slow

--ease-out · mid

linear · fast

06 / COMPONENTS

Cards, badges, tables.
Themed live.

The shared parts from css/cybercomponents.css. Nothing below has a hard-coded colour, so switching themes repaints all of it.

ONLINEnode-07

Darkbox stack

12 services · 3 alerts suppressed · uptime 41d

DRIFTsigilward

Integrity scan

2 modified · 0 deleted · 1 unreadable under /etc

MODULE	STATE	TIME
hardware	PASS	0.8s
network	PASS	1.2s
packages	WARN	6.4s
firewall	FAIL	0.3s
journal	INFO	2.0s

cyberterm — zsh

❯ curl -s localhost:8787/palette/hot_pink?format=all
{ "hex": "ff147f",
  "css": "#ff147f",
  "ansi": "\x1b[38;2;…m" }
❯ cargo run --example list_themes
active: cybercore-tech
count:  93
❯ █

07 / THE GRID

Built on the
same core.

Each of these reads the CYBERGRID palette. Your theme choice is stored once and carried to every project site.

CORE · AUDITOmniscient

A full-system audit tool for the CYBERDECK suite, with readable Markdown reports.

CORE · HUBCyberDeck Hub

A personal cyberdeck build: the central tool hub, tied to this box.

SECURITY · INTEGRITYSigilWard

File-integrity monitor. Baseline a set of paths, then detect drift.

SECURITY · LIVE WATCHArgus

Real-time file-integrity watcher. An inotify daemon and TUI that keeps SigilWard's baseline live.

SECURITY · COMPROMISEUndertow

Rootkit and compromise checks: pacman integrity, SUID, module and persistence drift.

TOOLING · CONTAINERSDockspace

Self-hosted dashboard for docker-compose stacks, built in Rust on CYBERGRID.

INTEGRATIONS · GITCyberFleet

Multi-repo git status from the bar, with a full TUI to fetch, diff and jump in.

INTEGRATIONS · SYSTEMDCyberWatch

Live systemd dashboard for your own services: bar widget plus TUI.

INTEGRATIONS · PLUGINSCyberPlug

Plugin manager for Omarchy. Now ships the bar widget as part of one plugin package.

08 / INSTALL

Jack in.

Pick your runtime. Every path reads the same file, so the colours match whatever the language.

# Cargo.toml
[dependencies]
cybercore = "0.8"

// main.rs
use cybercore::{palette, paths};

println!("{}online{}", palette::acid_green(), palette::RESET);
let sysops = paths::sysops_root(); // ~/.sysops, expanded

// C++
QFile f(":/cybercore/schema/cybergrid.json");
f.open(QIODevice::ReadOnly);
auto doc = QJsonDocument::fromJson(f.readAll());

// QML
property var cybergrid: JSON.parse(cybergrid_json_string)
color: "#" + cybergrid.palette.acid_green

/* load order: reset → tokens → theme colours → components */
@import "cybertokens.css";
@import "cybercomponents.css";

.panel {
  background: var(--panel);
  border: 1px solid var(--line);
  color: var(--fg);
  padding: var(--space-4);
}

# standard library only, Python 3.8+
python3 cybercore_api.py            # http://127.0.0.1:8787

curl localhost:8787/palette/cyan?format=rgb
curl localhost:8787/paths?expand=true
curl localhost:8787/schema

CYBERCORE 0.8.1 / CONTROL PLANE

Install the modular surface.

The Control Plane inventories 287 governed resources and 300 source themes plus 12 signature mashups, with 104 effects, 54 components, 114 snippets, 14 assets, and the CyberDark wallpaper pack.

VIEW THE CORE CRATE ↗

MODULAR CRATES / CRATES.IOcargo add cybercore-core cybercore-effects cybercore-componentsPUBLISH CONTRACT ↗Theme CLI: cargo install --locked cybercore --bin cybercore-theme

04 / CONTROL PLANE

Govern the
whole surface.

The Control Plane is the coordination layer between source files, local tools, public sites, and release artifacts. It keeps creative resources inspectable, versioned, attributable, and safe to move between projects.

01 / DISCOVER

One resource graph

Workspace manifests describe themes, components, effects, snippets, assets, fonts, and site profiles with IDs, versions, paths, licenses, provenance, tags, dependencies, and platform targets.

.cybercore/workspace.json

02 / VALIDATE

Quality before drift

Schema, accessibility, syntax, license, provenance, duplication, compatibility, reduced-motion, preview, and checksum gates turn a creative file into a governed resource.

cybercore-core → validate()

03 / COMPOSE

Build a project surface

Site profiles select a theme, components, effects, assets, motion policy, and fallbacks for each repository without copying the whole catalog into every app.

site.profile → resource IDs

04 / RELEASE

Publish deliberately

Dry-run plans make the release diff visible before a Web Kit, pack, or consumer update is published. No generated plan silently deploys or mutates a repository.

cybercore-publish → plan

SOURCE FILES→MANIFESTS→VALIDATION→PACKS / WEB KIT→CONSUMERS

05 / MODDING SURFACE

Make it
your grid.

Cybercore is designed to be extended without forking the engine. Add a resource, describe it with a manifest, validate it locally, preview it, and publish it as a namespaced pack or project overlay.

NEW THEME

{
  "id": "theme.my-lunar-signal",
  "kind": "theme",
  "version": "0.1.0",
  "status": "review",
  "path": "themes/my-lunar-signal.json",
  "license": "MIT",
  "provenance": {
    "source": "github:you/my-pack",
    "author": "your-handle",
    "license": "MIT",
    "reviewed": false
  }
}

1.Create a resource under your pack namespace.

2.Manifest its identity, provenance, license, and compatibility.

3.Validate with the local Control Plane before review.

4.Preview it in Theme Studio and consumer surfaces.

5.Publish a versioned pack or Web Kit plan.

06 / CRATES + PACKS

Install the
signal.

Use only the layer you need, or assemble the full Control Plane. Rust crates provide contracts and embedded assets; governed packs provide portable resources; the Web Kit serves browser consumers without a build dependency.

cybercore-coreWorkspace, theme, schema, path, pack, and validation contracts.cargo add cybercore-core cybercore-effectsGoverned effects with fallbacks and reduced-motion variants.cargo add cybercore-effects cybercore-componentsTheme-driven component CSS and interaction contracts.cargo add cybercore-components cybercore-publishDry-run release plans for packs and Web Kit consumers.cargo add cybercore-publish

THEMESPalette families and editable theme documents. EFFECTSMotion recipes, fallbacks, and reduced-motion CSS. IMAGESCyberDark wallpapers and governed visual assets. COMPONENTSReusable UI contracts and shared styling. SNIPPETSInstallable code patterns with provenance. FONTSTypography resources and licensing metadata.

CONTROL PLANE / PACK INSTALLER

Install a pack into the workspace.

Pack selections stay project-local and reproducible. The installer writes manifests under .cybercore/packs/ and exact versions to .cybercore/packs.lock.json.

        # Install the companion CLI from the registry repo
        cargo install --git https://github.com/cybercoretech/cybercore-packs --package cybercore-pack

cybercore-control pack search cyberdark
cybercore-control pack install cybercore.themes@1.0.0
cybercore-control pack list
cybercore-control pack verify

AVAILABLE REGISTRY PACKS / INSTALL COMMANDS

cybercore-control pack install cybercore.themes@1.0.0

cybercore-control pack install cybercore.effects@1.0.0

cybercore-control pack install cybercore.components@1.0.0

cybercore-control pack install cybercore.cyberdark-wallpapers@1.0.0

cybercore-control pack install cybercore.snippets@1.0.0

cybercore-control pack install cybercore.fonts@1.0.0

cybercore-control pack install cybercore.svg-assets@1.0.0

cybercore-control pack install cybercore.web-templates@1.0.0

07 / PACK NETWORK

A bigger
mod system.

The next step is a first-class pack network: discoverable, namespaced, signed, reviewable, and composable across projects without turning the Control Plane into a monolith.

01Pack registry

A dedicated `cybercore-packs` repository or organization registry with searchable manifests, release channels, previews, and compatibility ranges.

02Namespaces + overlays

Let creators publish `author.pack.resource` IDs, layer project overrides, and resolve collisions without mutating built-ins.

03Trust + provenance

Keep licenses, source URLs, checksums, signatures, review state, and dependency edges visible from discovery to install.

04Install profiles

Define reproducible profiles for a site, desktop, Web Kit, or Theme Studio workspace and lock them to known pack versions.

CYBERCORE

STAT SIGNAL

UPDATE SIGNAL

What changed
in the grid.

Every theme.
One control surface.

One file.
Every surface.

Every family.
Pick your signal.

Splice two
themes.

Edit the JSON.
Never hand-edit anywhere else.

Same feel.
Every surface.

Cards, badges, tables.
Themed live.

Darkbox stack

Integrity scan

Built on the
same core.

Jack in.

Install the modular surface.

Govern the
whole surface.

One resource graph

Quality before drift

Build a project surface

Publish deliberately

Make it
your grid.

Install the
signal.

Install a pack into the workspace.

A bigger
mod system.

CYBERCORE

What changedin the grid.

Every theme.One control surface.

One file.Every surface.

Every family.Pick your signal.

Splice twothemes.

Edit the JSON.Never hand-edit anywhere else.

Same feel.Every surface.

Cards, badges, tables.Themed live.

Darkbox stack

Integrity scan

Built on thesame core.

Jack in.

Install the modular surface.

Govern thewhole surface.

One resource graph

Quality before drift

Build a project surface

Publish deliberately

Make ityour grid.

Install thesignal.

Install a pack into the workspace.

A biggermod system.

What changed
in the grid.

Every theme.
One control surface.

One file.
Every surface.

Every family.
Pick your signal.

Splice two
themes.

Edit the JSON.
Never hand-edit anywhere else.

Same feel.
Every surface.

Cards, badges, tables.
Themed live.

Built on the
same core.

Govern the
whole surface.

Make it
your grid.

Install the
signal.

A bigger
mod system.