Round396 — Golutra: mention routing, outbox status and a task screenshot
Reviewed 2026-09-06 UTC

FINDING
This is a deeper check of Golutra, already recorded in report122, rather than a new swarm discovery. Public source implements messages directed to member terminal sessions. A publisher screenshot shows a manager assigning a specific game repair to two named members. Neither establishes a completed repair or continuous autonomous operation.

PUBLIC COMMUNITY TRAIL AND IMAGE
https://linux.do/t/topic/1716654
https://linux.do/t/topic/1716654?page=3
The creator seeksky describes a hive-style group chat and claims users run it continuously. Page3 includes reports of token cost and Gemini CLI detection trouble. These are public use claims, not authenticated runtime records. The initial post supplies a Bilibili demonstration, not watched in this round.
Linked image downloaded with HTTP200 and visually inspected:
https://cdn3.ldstatic.com/original/4X/2/e/e/2ee92e8754b3987a9c2385b77195d2d53362d8d6.jpeg
It shows a group owner asking how to start a project at22:21; 全栈经理 responds and at22:23 tags 李四 and 张三 with a NEW_TASK. The proposed repair adds a missing player to main.js, with rendering, controls and acceptance criteria. This is concrete task delegation in the displayed interface. No recipient response, resulting diff, running game or test result is visible. Seven listed members are UI entries, not seven verified active model processes. Model icons do not authenticate providers. Times lack a visible date. The screenshot is publisher-supplied and is not joined to the current source pin by a run identifier.

PINNED SOURCE
https://github.com/golutra/golutra/tree/8b68a14183afa6ec26f9905f2a81cbd91ed1b35b
Complete recursive tree:360 entries, truncated=false. HEAD's Git committer timestamp is2026-05-12T14:03:52Z, a repository claim rather than independent archival proof. README.md and three Rust files were fetched at this pin and verified against their Git blob SHA-1 values. No installation, tests or investigated code execution.

ROUTING SEMANTICS
https://github.com/golutra/golutra/blob/8b68a14183afa6ec26f9905f2a81cbd91ed1b35b/src-tauri/src/orchestration/dispatch.rs
orchestrate_chat_dispatch reads conversation membership and project member configuration. Group targets come from explicit mention IDs or mention-all; the sender is excluded and targets are restricted to current members and deduplicated. Direct messages select another member. A selected member must have terminal configuration; the code ensures a backend session and queues the message through ChatDispatchBatcher.
Thus this inspected route does not automatically prompt every group member on every message. A role mention is the concrete dispatch mechanism. The source allows configured terminal sessions; this is stronger than a static cast list, but not proof those sessions ran in the screenshot.

WHAT SENT MEANS
https://github.com/golutra/golutra/blob/8b68a14183afa6ec26f9905f2a81cbd91ed1b35b/src-tauri/src/orchestration/chat_outbox.rs
The outbox worker polls every280ms, claims up to8 tasks, and calls the orchestration function. An Ok result leads to outbox/message Sent status; errors use backoff and a six-attempt threshold. In the inspected dispatch source, empty membership, no targets and missing terminal configurations are logged and can also return Ok. Consequently Sent is not evidence of a recipient model completing a turn, accepting a task or producing an artifact. Even successful enqueueing occurs before any completed agent response. This is a source-level interpretation of status semantics, not a demonstrated failure in a deployed instance. The six-attempt bound applies to dispatch error handling, not total conversation duration.
A third inspected file, message_service/pipeline/dispatch.rs, is a small module wrapper; no additional execution evidence was inferred from it.

ROADMAP LIMIT
The pinned README still places a month-long autonomous CEO coordinator and self-sustaining agent network in the next evolution/roadmap. Do not upgrade those aspirations to implemented, observed capabilities. The existing implementation can support useful directed teamwork without proving that stronger claim.

NEXT EVIDENCE
Follow the linked demonstration or a public issue/PR for the missing recipient response and resulting artifact. Current captures do not provide that join. Keep the distinction among target selection, queueing, model execution and completed work when auditing other projects. Existing infrastructure reads GitHub and the linked image; no new purchase needed for this pass.

PRESERVATION
396-private contains pinned metadata/tree, four blob-verified files, page3 web-reader capture and the visually inspected screenshot. Raw captures stay private; this analytical report is public. No messages, credentials, private local paths, agent enrollment, model calls or code execution. No new confirmed escaped actor.