Configuration

Tetrapus uses git-backed YAML files for all configuration. Every change is versioned, validated, and hot-reloaded without restarts.

Core Components

Component	Crate	Role
GitEngine	tetrapus-config	Watches config repo, triggers reload on commit
Migrator	tetrapus-config	Schema version migrations across schema upgrades
Validator	tetrapus-config	JSON Schema validation + cross-ref checks
SnapshotManager	tetrapus-config	Point-in-time config snapshots for rollback
SandboxManager	tetrapus-config	Preview config changes before committing

Directory Layout

Text

config/
  sources/          # Data source definitions
  schemas/          # Field schemas per source
  visual-mapper/    # Color/size/opacity mapping rules
  alerts/           # Alert rules + escalation chains
  state-machines/   # FSM definitions + transitions
  zones/            # Geofence &amp; spatial region configs
  scenes/           # Scene layer arrangements
  panes/            # Pane layout snapshots

Hot Reload

The GitEngine watches for commits and pushes validated config diffs to all connected services via the internal event bus. No restart required.

Bash

# Edit config, commit, and it auto-reloads
vim config/alerts/temperature.yaml
git add -A && git commit -m "raise temp threshold"
# Tetrapus picks up the change within 1s

Subsections

Visual Mapper — color, size, and opacity mapping rules
Alerts — conditions, severity, escalation chains
State Machines — FSM definitions with Kanban integration
Zones — geofences, spatial regions, proximity alerts

Questions?

Reach out for help with integration, deployment, or custom domain codecs.

Get Started Request a Demo