mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
abf99d05fc
Restructured from flat .tex/.pdf files into per-paper subdirectories. Added Antje Worring as co-author on all papers. Synced PDFs to pdfs/ for download site.
36 lines
1.8 KiB
TeX
36 lines
1.8 KiB
TeX
\section{Multi-Agent Coordination}
|
|
\label{sec:coordination}
|
|
|
|
Sovereign agents must coordinate without trusting each other. We define three coordination primitives.
|
|
|
|
\subsection{Cross-Capsule Messaging}
|
|
|
|
Agents communicate via authenticated, encrypted messages routed through their MCP endpoints. Each message is signed by the sender's DID key and encrypted with the recipient's key agreement key:
|
|
|
|
\begin{equation}\label{eq:message}
|
|
m_{\text{enc}} = \text{Enc}(\text{pk}_B^{\text{agree}}, \text{Sign}(\text{sk}_A, \text{payload}))
|
|
\end{equation}
|
|
|
|
Messages are delivered asynchronously. The protocol does not guarantee ordering across capsules---each capsule maintains a local causal order via Lamport timestamps~\cite{lamport1978clocks}.
|
|
|
|
\subsection{Capability Exchange}
|
|
|
|
Agent $A$ can grant agent $B$ a time-bounded, scoped capability in exchange for payment. This is atomic: the capability grant and payment occur in a single C-Chain transaction, ensuring neither party can cheat:
|
|
|
|
\begin{equation}\label{eq:exchange}
|
|
\text{TX}_{\text{exchange}} = \big(\text{VC}_{\text{del}}(B, c, s', t'), \text{Payment}(B \to A, p)\big)
|
|
\end{equation}
|
|
|
|
If either component fails, the entire transaction reverts.
|
|
|
|
\subsection{Shared Workspaces}
|
|
|
|
For collaborative tasks, agents can create shared workspaces---temporary CRDT-synchronized data structures accessible to a defined set of capsules. Access is governed by a threshold policy:
|
|
|
|
\begin{equation}\label{eq:workspace}
|
|
W = \big(\text{CRDT}, \mathcal{A}_{\text{access}}, \pi_{\text{threshold}}, t_{\text{expiry}}\big)
|
|
\end{equation}
|
|
|
|
The workspace is encrypted with a group key derived via multi-party key agreement among the participating capsules. When the workspace expires or the task completes, the data is either archived to each participant's vault or destroyed.
|
|
|