Neoriris / SolBridge 72-Hour Change Summary

Window summarized: approximately 2026-07-07 through 2026-07-10, America/Chicago.

July 7: Syzygy Becomes A Runtime

SolBridge grew from an entity/action bridge into a broader in-world computer system. The Syzygy Console gained record playback, audio envelopes, six-sided GPIO, note-block input/output, SolNet links, a terminal GUI, and the SolScript event language. Celestial output moved through several guarded render stages until active audio could pulse and color the visible sun or moon without leaving the client sky renderer stuck after playback. Stop/eject handling became fail-closed, note output stopped feeding itself back into the observer, and world command aliases restored practical weather, time, and game-mode control alongside ForgeEssentials.

July 8: Structure Memory And First Autonomy

The recovered Clock Tower became a versioned semantic structure rather than one disposable schematic. SolBridge added named regions, protected areas, lineage stages, comparison commands, anchor-aware schematic placement, and operator-gated large builds. The first autonomy controller added bounded movement, inspection, observation, procedural temporary structures, safe block-by-block materialization, delayed withdrawal, and explanation books left in chests. The decimal clock face was synchronized to Minecraft world time, including immediate reconciliation after time commands.

July 9: Client Visibility And Tunnel Reliability

The client title screen gained measured Cloudflared route readiness instead of a static claim. The monitor opens the Helper-owned local endpoint, performs an actual Minecraft status ping, recovers stale listening endpoints, and stops probing once Ready so it cannot churn a working tunnel. A separate public Clock Tower widget now shows face bits, server state, players, ping, version, and uptime. The mini seven-segment face was rebuilt with equal-length, non-overlapping bars, while foreground Neoriris/Sol splash lines were restored. Syzygy GPIO and nearby note observation also received stricter validation and debounce guardrails.

July 10: Persistent LLM-Governed Free Roam

Version 0.3.25 first moved Free Roam initiation out of local random loops and into an LLM planner. Version 0.3.26 completed that transition and fixed the observed stall: a wander no longer reaches an observation point and remains there indefinitely. Sol now observes for 10 seconds, clears the goal, returns to AUTONOMOUS, and re-arms the scheduler.

Free Roam now behaves as a persistent mode:

• The first LLM decision occurs 5 seconds after arming.
• Quiet windows open every 45-90 seconds.
• Environment changes are retained and considered after a 30-second cooldown rather than being overwritten between checks.
• The LLM is the sole initiator and must choose none, wander, say, whisper, or temporary_build_blueprint through a strict schema.
• Wander is hazard-checked and capped at 24 blocks.
• Autonomous temporary builds use approved local blueprints, last 60 seconds, restore only unchanged Sol-owned blocks, and resume Free Roam after withdrawal.
• Wander arrival does not start a second chained LLM request.
• Follow or Stay discards stale in-flight decisions and withdraws an active mode-bound temporary build.
• Legacy random ambient builds and idle LLM narration are disabled by default.

The interaction is now consistently surfaced as FOLLOW -> STAY -> FREE ROAM -> FOLLOW through right-click, /sol help, /sol status, /sol follow, /sol stay, /sol roam, /sol auto status, and the desktop Minecraft remote.

Backend And Storage Recovery

The Sol data volume had disconnected and reappeared under a new kernel device name, leaving stale mount references and a LiteLLM restart storm. The recovered ext4 filesystem was verified and rebound to /mnt/sol-data without forcing another active session off its desktop mount. Docker/Qdrant, LiteLLM, the agent console, Ollama embeddings, and the Minecraft daemon were restored. Root-local Python runtime fallbacks, bounded service restarts, a systemd automount, and Docker mount coupling now prevent the same failure from silently consuming the root filesystem or looping indefinitely.

DeepSeek R1 Distill 7B was rejected as the shared real-time model after exact-task probes showed hidden-reasoning token exhaustion and structured-prompt echoing. Gemma 3 4B returned valid decisions with materially lower latency and now backs every active generation role, Sol Chat text profile, LiteLLM alias, and the default vision profile. nomic-embed-text remains the 768-dimensional embedding model.

Deployment State

• Active server and client jar: solbridge-0.3.26.jar.
• Jar SHA-256: 6e289b82caf0759b7566303d6ca8b9a4cb827a49c78666768fa0b57a0893dce2.
• Client pack SHA-256: 18dcd91735e6e31c4815e9c98b9573423a6b095782e5e0156d5ba5f929c5962e.
• Server restarted successfully and loaded the world with SolBridge 0.3.26.
• Client restarted, loaded all 18 expected mods, and validated the public Cloudflared Minecraft route.
• Public jar, installer, README, changelog, checksum manifest, page cache key, and generated crawl indexes are aligned.