full-system audit console / rust 0.1.x

See the whole system.Keep the signal.

Omniscient turns Linux inspection into one readable, repeatable surface — hardware, storage, services, network state, capabilities, and the report that connects them.

Deploy the console →View source

17audit modules

10diagnostic domains

2focused scan paths

OMNI/RADAR ● ONLINESCAN VECTOR // 360°

The audit surface

Ten domains.
One system picture.

The Cybercore schema stays the connective tissue: shared color keys, shared tokens, shared operator language. Omniscient makes the signal actionable while keeping the first pass read-only.

01 / DISCOVERY

Hardware core

CPU, USB, PCI, memory, and machine identity.

hw://inventory

02 / PRESSURE

Storage matrix

Block devices, SMART health, and Btrfs snapshots.

io://storage

03 / SIGNAL

Network nexus

Interfaces, sockets, Bluetooth, and connected devices.

net://surface

04 / SERVICES

Daemon watch

Systemd units, kernel logs, and container inventory.

svc://runtime

05 / POSTURE

Security surface

Listeners, firewall state, accounts, persistence, and package integrity.

secure://posture

06 / RESILIENCE

Recovery signal

Filesystem readiness, hardware reliability, performance, and Omarchy health.

system://resilience

07 / REPORT

Health signal

A linked Markdown report with nothing silently hidden.

report://summary

The Cybercore contract

Schema-first.
Operator-ready.

Omniscient reads the same palette contract as every Cybercore surface. The page, the dashboard, and the reports speak in the same tokens — bg, fg, acid, cyan, pink, panel, line, muted.

Paths stay portable through XDG defaults, privileged modules ask clearly, and unavailable tools remain visible instead of becoming false green checks.

schema / cybergrid.json

{
  "schema_version": 2,
  "active": "neon-night",
  "surface": "omniscient",
  "paths": {
    "sysops_root": "~/.sysops",
    "report_root": "$XDG_STATE_HOME/omniscient"
  }
}

Module registry

Every signal gets a name.

Pick a focused pass or run the full system audit. The normal HUD pass covers 16 operational modules; Package Integrity is a separate, deliberate action. Optional tools are reported as optional — never disguised as failure.

Hardware coreCPU · USB · PCI

ready

Storage matrixdisks · SMART · Btrfs

ready

Network nexuslinks · sockets

ready

Container realmDocker · Flatpak · Snap

ready

Services & daemonssystemd units

ready

Kernel logsjournal · dmesg

ready

Bluetooth deepvisible devices

ready

Connected devicesdisplay · audio

ready

Security posturefirewall · kernel · boot

read-only

Accounts & authusers · sessions · SSH

read-only

Persistence watchunits · timers · cron

read-only

Package integritycategories · versions · status · verify

focused

Recovery readinessmounts · Btrfs · trim

read-only

Reliability signalserrors · dumps · sensors

read-only

Performance pulseload · memory · boot

read-only

Omarchy surfaceHyprland · shell · debug

read-only

♥

Health scoresignal · not warranty

live

Readable by design

Scan once.
Keep the evidence.

Every run ends in a linked Markdown report beneath ~/.local/state/omniscient/. The summary keeps command failures, missing capabilities, and health signals in view.

The Omarchy HUD separates RUN FULL AUDIT from PACKAGE SCAN. The package reader groups evidence into ARCH OFFICIAL, OMARCHY, BLACKARCH, CHAOTIC AUR, and AUR / FOREIGN, then marks each version CURRENT or UPDATE AVAILABLE using pacman's own update metadata.

report / latest

PASS  hardware.md
PASS  network.md
WARN  smartctl unavailable
PASS  SUMMARY.md

Operator walkthrough

From scan
to signal.

Audit, repair, live sensors, the journal and 30-day trends in one surface. These captures are rendered from synthetic data by the repository's own showcase script, so no real machine appears in them.