Answers are grounded in this paper and cite their sources.
Deployments that federate at runtime must settle three questions: which party may address which, how much of an incoming request's identity and authority evidence to believe, and who belongs together for purposes of containment. Each is conventionally answered by machinery outside the participants — a service mesh, a policy server, a directory — and each such answer introduces a coordination point, an availability dependency, and a place where two parties' views can diverge. We describe an alternative in which an overlay graph over the participants carries the policy itself. The graph is a managed object with a lifecycle, spanning administrative boundaries and orthogonal to them. It carries attributes declared once by the graph's authority, delivered to each member in the exchange by which that member joins, and held thereafter. Nothing carried in the governed traffic — no request field, no payload — determines an attribute or the behavior it produces, and no party outside the membership relationship is consulted to apply one. A path's uniformity is therefore a consequence of where the value lives rather than an invariant anyone maintains. Aspects of the work described here are the subject of pending US provisional patent applications. Publication of this paper grants no patent license.
No takes yet. Share an insight, caveat, or question.
Samoylov Andrew (2026) studied this question.
Synapse has enriched 8 closely related papers on similar clinical questions. Consider them for comparative context: