本文为原文前 6,000 字符的节选翻译，完整内容请查看原文。

Edge-to-Cloud Swarm Coordination for precision oncology clinical workflows with embodied agent feedback loops

Introduction: A Late-Night Discovery in Distributed Inference It started at 2 AM during a weekend experiment I never intended to run. I was prototyping a multi-agent reinforcement learning setup for a small robotics simulator — nothing clinical, just a curiosity about how swarms of lightweight agents could coordinate inference across heterogeneous compute nodes. I had a Jetson Orin Nano sitting on my desk, a rented A100 in the cloud, and a half-baked idea about splitting a vision transformer’s forward pass across both based on latency budgets.

引言：分布式推理中的深夜发现 这一切始于一个周末凌晨两点的实验，我本无意进行。当时我正在为一个小型机器人模拟器构建多智能体强化学习原型——这与临床无关，仅仅是出于好奇，想看看轻量级智能体集群如何在异构计算节点间协调推理。我的桌上放着一台 Jetson Orin Nano，云端租用了一台 A100，我脑子里有一个半成型的想法：根据延迟预算，将视觉 Transformer 的前向传播过程拆分到两者上执行。

While exploring how to make those agents negotiate which part of the pipeline each would execute, I stumbled on something unexpected: when I gave each agent a small “embodied” feedback signal — a local observation of its own compute, thermal, and memory state — the coordination policy converged nearly three times faster than a purely centralized scheduler. That observation nagged at me for weeks.

在探索如何让这些智能体协商各自执行流水线的哪一部分时，我偶然发现了一个意想不到的结果：当我给每个智能体提供一个微小的“具身”反馈信号——即对其自身计算、热量和内存状态的局部观察时，协调策略的收敛速度比纯粹的集中式调度器快了近三倍。这一发现困扰了我好几周。

Then a colleague in computational pathology mentioned a problem that made my toy experiment suddenly feel urgent. A single whole-slide image (WSI) from a modern digital pathology scanner can exceed 100,000 × 100,000 pixels — several gigabytes of data. Running foundation-model inference over that at the point of care, while a patient is still on the table, is a genuinely hard edge-to-cloud problem.

随后，一位计算病理学领域的同事提到的一个问题，让我觉得这个玩具实验突然变得紧迫起来。现代数字病理扫描仪生成的单张全切片图像（WSI）可能超过 100,000 × 100,000 像素，数据量达数 GB。在患者仍处于手术台上时，在护理点对这些数据运行基础模型推理，是一个真正困难的边缘到云端问题。

And it’s not just pathology. Genomic variant calling, real-time radiomics, intraoperative imaging, and adaptive radiotherapy planning all demand latency-bounded, privacy-preserving, fault-tolerant compute that no single tier can deliver alone. That’s when I started taking edge-to-cloud swarm coordination seriously — not as a distributed-systems curiosity, but as an architectural pattern that precision oncology actually needs.

这不仅仅涉及病理学。基因变异调用、实时放射组学、术中成像以及自适应放射治疗计划，都要求具备延迟受限、隐私保护和容错能力的计算，而单一层级无法单独实现。那时我开始认真对待边缘到云端的集群协调——不再将其视为分布式系统的奇闻，而是将其视为精准肿瘤学真正需要的架构模式。

This article is the synthesis of what I learned building and breaking prototypes over the following months: how embodied agents, hierarchical coordination, and hybrid quantum-classical optimization can be woven into clinical workflows without sacrificing safety or auditability.

本文总结了我在接下来的几个月里通过构建和破坏原型所学到的知识：如何将具身智能体、分层协调以及混合量子-经典优化融入临床工作流程，且不牺牲安全性和可审计性。

Why Precision Oncology Is a Distributed-Compute Problem Before diving into architecture, it’s worth being precise about why centralized cloud inference fails for many oncology workflows. Data gravity and latency. A WSI at 40× magnification is roughly 2–4 GB compressed. Uploading that to a cloud endpoint over a hospital’s contended uplink can take minutes — far beyond the seconds-scale budget for intraoperative frozen-section decisions. Edge compute keeps the pixels local.

为什么精准肿瘤学是一个分布式计算问题 在深入探讨架构之前，有必要明确为什么集中式云推理在许多肿瘤学工作流程中会失败。数据引力和延迟是关键。40 倍放大倍率下的 WSI 压缩后约为 2–4 GB。通过医院拥挤的上行链路将其上传到云端点可能需要几分钟，这远远超出了术中冰冻切片决策所需的秒级预算。边缘计算将像素保留在本地。

Privacy and regulatory constraints. HIPAA, GDPR, and institutional IRBs often prohibit raw patient data from leaving the premises. Federated and split-learning approaches let us send gradients or embeddings rather than images, but that introduces its own coordination complexity.

隐私和监管限制。HIPAA、GDPR 和机构审查委员会（IRB）通常禁止原始患者数据离开场所。联邦学习和拆分学习方法允许我们发送梯度或嵌入向量而非图像，但这引入了其自身的协调复杂性。

Heterogeneity. A hospital might have a handful of GPUs in the pathology lab, a CPU cluster in radiology, and access to a burst-capable cloud region. These nodes differ wildly in memory, precision support (FP16, BF16, INT8), and interconnect bandwidth.

异构性。医院可能在病理实验室拥有少量 GPU，在放射科拥有 CPU 集群，并能访问具备突发处理能力的云区域。这些节点在内存、精度支持（FP16、BF16、INT8）和互连带宽方面差异巨大。

Burstiness. Tumor board reviews, intraoperative consults, and screening campaigns create sharp demand spikes. Static provisioning wastes money during lulls and fails during peaks. The core insight from my experimentation: these constraints are not independent, and treating them separately produces brittle systems. A scheduler that optimizes latency ignores privacy; a privacy layer that isolates data ignores burst capacity. Swarm coordination is appealing precisely because it lets us express all these constraints as a single multi-objective optimization that agents solve locally and reconcile globally.

突发性。肿瘤委员会审查、术中会诊和筛查活动会造成剧烈的需求激增。静态配置在低谷期浪费资金，在高峰期则无法满足需求。我实验的核心见解是：这些约束并非相互独立，单独处理它们会产生脆弱的系统。优化延迟的调度器会忽略隐私；隔离数据的隐私层会忽略突发容量。集群协调之所以具有吸引力，正是因为它允许我们将所有这些约束表达为一个单一的多目标优化问题，由智能体在本地解决并进行全局协调。

The Architectural Blueprint: Three Tiers, One Swarm In my prototypes, I converged on a three-tier topology that maps cleanly onto clinical reality. Each embodied agent in Tier 1 owns a physical device and a local observation vector: compute utilization, thermal headroom, battery (for wearables), network RTT to Tier 2, and a clinical context signal (e.g., “intraoperative, latency budget = 8s”). These agents don’t just execute tasks — they negotiate them.

架构蓝图：三层架构，一个集群 在我的原型中，我确定了一种能够清晰映射到临床现实的三层拓扑结构。第一层的每个具身智能体都拥有一个物理设备和一个局部观察向量：计算利用率、热余量、电池（针对可穿戴设备）、到第二层的网络往返时间（RTT）以及临床上下文信号（例如“术中，延迟预算 = 8秒”）。这些智能体不仅执行任务，还会协商任务。

The coordination primitive I found most effective is a contract-net protocol with embodied bidding. When a task arrives (say, “tile this WSI region and run the tumor-detection head”), a broker broadcasts a call for proposals. Each agent returns a bid derived from its local state.

我发现最有效的协调原语是带有具身竞标的合同网协议。当任务到达时（例如“对该 WSI 区域进行切片并运行肿瘤检测头”），代理会广播提案征集。每个智能体根据其本地状态返回一个竞标。