Agentic-Systems on emsenn.net

RimWorld Colony Management as a Model for Agentic Systems

Sun, 05 Apr 2026 00:00:00 +0000

RimWorld is a colony simulation where the player manages colonists indirectly — setting priorities, schedules, and research directions while colonists autonomously execute work. The player never directly controls a colonist’s hands. This constraint produces a management system that maps remarkably well onto multi-agent orchestration, where a harness directs autonomous agents without micromanaging their inference.

¶Work Priorities: The 1-4 Dispatch System

RimWorld offers two priority modes. In simple mode, each colonist toggles work types on or off. In manual mode, each work type gets a priority from 1 (highest) to 4 (lowest), or blank (disabled). A colonist completes all available priority-1 work before touching priority-2 work. Within the same priority level, work types listed further left take precedence.

Tech Messaging Systems as Models for Agentic Coordination

Sun, 05 Apr 2026 00:00:00 +0000

For a distributed heterogeneous agentic system at nation-scale, message-passing is the primary concern: how do agents coordinate when they run in different processes, at different times, under different models, across different sites? Real-world messaging systems have solved slices of this problem. Each brings a pattern the 561 system can adopt.

¶Apache Kafka — log-based messaging

Kafka stores messages as an append-only log partitioned across brokers. Producers write to topics; consumers read by offset, replay at will. The log IS the state — downstream systems derive their view by consuming the log from offset 0. Retention is time-bounded (hours to forever). Ordering is guaranteed within a partition, not across.

OpenHands Architecture Analysis

Sat, 04 Apr 2026 00:00:00 +0000

OpenHands (formerly OpenDevin) is an open-source AI software development platform. This analysis covers the V0 architecture (deprecated April 2026, with V1 migrating to a separate Software Agent SDK). The patterns here remain instructive regardless of version.

¶Runtime Isolation

OpenHands isolates agent execution inside Docker containers. Each agent session gets a dedicated container (openhands-runtime-{session_id}) with its own filesystem, network, and process namespace. The container runs as a dedicated non-root user (openhands, UID 42420) to prevent UID conflicts with the host.