Empire Genesis

Problem

When multi-agent systems are deployed across operating systems, state storage, timestamps, and heartbeats become failure points: SQLite can hit concurrent locking on Windows, duplicate alerts amplify noise, and mixing event_time with collection time across agents makes debugging harder.

How It Works

Empire Genesis bootstraps OpenClaw into a self-checking system architecture. Key steps include:
- Creating a concurrency-safe StateDB, using lesson_hash as a unique index and ON CONFLICT to increment hit_count, which suppresses alert storms.
- Injecting Signal Protocol v2 and a dual-timestamp mechanism, preserving both event_time and collection_time in the blackboard table.
- Adding Research, Execution, and Verification roles, then deploying a Watchdog sentinel that periodically refreshes last_seen for online static agents.
- Running sandbox tests to validate StateDB throughput and constraint logic, then self-deleting after a passing result.

Boundaries

The skill is intended for explicit commands such as initializing the empire or deploying the lobster architecture, and is focused on low-level assembly and self-checks. It is not suitable for invoking a single agent temporarily. Known behavior includes Watchdog leaving main and its own heartbeat untouched, but before rollout you should confirm OS behavior, load, and constraints such as timeout=20.