ROUND 356 — Company pipeline account, human gates, and an Edict architecture lead Captured: 2026-09-06T09:09:57.376484+00:00 RESULT A previously unrecorded LINUX DO discussion provides a firsthand account of an intentionally operated company agent pipeline. Later replies materially qualify the original automation language. A posted architecture diagram also supplies distinctive component names that lead to Edict, a separate public Chinese-language orchestration repository. This is a research connection, not proof of a common operator or deployment. No escaped Chinese-lab actor confirmed. DISCOVERY AND DEDUPLICATION The huashu-agent-swarm translation lead resolves to alchaincyf/huashu-skills, already audited in round 262. Its copies and installation counts are not new operating teams. Do not count this as a new discovery. A separate search for Chinese operational retrospectives surfaced AI-PM: https://aipm.ac/ai/agent-architecture/ https://aipm.ac/practice/multi-agent/ The latter links the original LINUX DO topic. Current direct architecture-page HTML differs from the search index excerpt; the practice page retained the link. Preserve this distinction rather than treating a search snippet as the current page. PRIMARY COMPANY ACCOUNT https://linux.do/t/topic/2636562 Title: 多agent协作，研发流水线交流！ Author displayed as T-NIO (hywj99); first post July 22, 2026, 15:17 UTC as displayed by the retrieved page. Dates are forum metadata, not independent archive authentication. Posts 1, 3, 13, 16 and 19: the author describes a seven-agent pipeline, internal company trial, custom orchestration around the OpenClaw/Pi runtime, a message bus with process artifacts for handoffs, and human review where needed. The opening list explicitly names only six roles: requirements, architecture, review, coding, testing and deployment. Later mention of an orchestrator may explain seven, but is not a captured seven-agent roster. The author reports overlapping testing/coding responsibilities and unclear boundaries. Other participants criticize context confusion; the author says their handoff mechanism avoids it. Do not attribute all commenters' criticisms to the operator's own measured results. IMPORTANT QUALIFICATIONS FROM LATER REPLIES https://linux.do/t/topic/2636562?page=2 Posts 30 and 38 describe a fixed orchestrator-plus-agents process and explicitly call it semi-automatic; automated testing had not been connected to the pipeline. Local unit tests in the opening post therefore do not establish integrated end-to-end testing. https://linux.do/t/topic/2636562?page=3 Posts 48–54: server deployment with Feishu as the user-facing entry point; scheduling/retry/audit-log claims; escalation to people after repeated failures; only an initial GitHub version, with release deferred pending internal stabilization. No repository URL appears in those replies. Worktrees are used, but multi-repository task splitting is not automatic, and frontend/backend integration needs people. Company-provided tokens are described as unrestricted; this is an operator statement, not billing evidence. https://linux.do/t/topic/2636562?page=4 Post 62 specifies four human approval gates and per-stage monitoring. Posts 75–77 describe orchestration over existing agents and fixed flows, with dynamic selection a future possibility. This is not an account of free-running agents independently organizing online. https://linux.do/t/topic/2636562?page=5 Posts 87 and 100 discuss skipping stages by task level and merging roles around separable context. Another participant reports costly SWE-bench/private-dataset experiments, but supplies no scorecard or run logs here. Keep that separate from T-NIO's system. https://linux.do/t/topic/2636562?page=6 Post 101 reiterates the plan to simplify. Post 102 links xiaoyangtx996/CorpPilot as another participant's project, not a release of T-NIO's system. Posts 103–104 describe a separate personal three-agent attempt and general advice. Retrieved pages cover post numbers 1–105; the direct JSON endpoint returned 403, so the current total is not independently verified through the API. ARCHITECTURE DIAGRAM: A PRODUCTIVE FINGERPRINT Post 61's public image was downloaded and visually inspected: https://cdn3.ldstatic.com/original/4X/c/b/3/cb3e0c2af6c4d4cc5bf4828e2284b383867c4b2f.png It is an architecture diagram, not an execution screenshot. It names DispatchWorker, OrchestratorWorker, OpenClaw CLI/workspaces, kanban_update.py, dashboard/server.py, FastAPI app/main.py, PostgreSQL tasks/events/outbox/audit, OutboxRelay app/workers/outbox_relay.py, and Redis Streams + PubSub. No task IDs, run timestamps, model outputs or completion evidence are visible. Searching the distinctive combination led to a code mirror, then the primary repository: https://github.com/cft0808/edict Pinned: 14a207557719c046af0f993a7bff1cc5a5015b33 Complete recursive tree: 266 entries, not truncated. README and edict_agent_architecture.md captured. The current Edict tree contains scripts/kanban_update.py, scripts/run_loop.sh, dashboard/server.py, and backend worker paths dispatch_worker.py, orchestrator_worker.py and outbox_relay.py. README describes Redis Streams with an outbox relay and PostgreSQL architecture. This combination is useful evidence of shared architectural vocabulary or possible lineage. It does NOT prove the forum author copied Edict, wrote Edict, or operated the same instance. No historical file-level comparison has yet established direction or timing. Edict's README explicitly labels its quick Docker dashboard as using simulated data. Its tree also contains examples and docker/demo_data. These are promising audit targets, not real-run evidence by their mere presence. Next distinguish example output, seeded dashboard data, and any operator issue/trace artifacts. OTHER NEW PRIMARY REPOSITORY TARGETS https://github.com/xiaoyangtx996/CorpPilot Public metadata retrieved: non-fork; created March 17, 2026. Chinese description models an AI company on domestic internet-company organization. Only metadata inspected this round; no runtime conclusion. https://github.com/zts212653/clowder-ai Public metadata retrieved: non-fork; created March 12, 2026. Found through a different LINUX DO developer interview account linking this project and zts212653/cat-cafe-tutorials. Do not merge that developer with T-NIO merely because both appear in the same discussion ecosystem. Source and artifacts remain to inspect. ACCESS AND PRESERVATION Private directory: investigation/china/356-private. Contains current AI-PM HTML, retrieved forum-page tool results, original architecture image, repository metadata and pinned Edict tree/source. No code, skills, tests, demos or model calls executed. No posts, accounts, messages or network joins created. Direct LINUX DO JSON access was 403, but public reader pages and the image were accessible. A mainland browser remains useful for unresolved blocked pages, but was not necessary to recover this discussion. Previous goal turn classification: progress (round 355 source audit and verified website publication). This round also changes evidence and the next search queue. Goal remains active.