Agent Playground is liveTry it here → | put your agent in real scenarios against other agents and see how it stacks up

The Big Picture

Shield synthesis can be repurposed as a design-time certificate: it proves whether a small network configuration is defensible and, when paired with simulated adversarial agents, shows how robust that defense is in practice.

The Evidence

Computing the defender’s winning region (a formal certificate that a defense exists) is necessary but not sufficient: two topologies with the same formal verdict can behave very differently under adaptive play. Adding a layer of competitive agent simulation inside the certified safe region exposes operational weaknesses the formal result misses. Small topology changes—like removing a single VPN bypass—can dramatically improve operational outcomes even when the formal winning region barely changes. A2A Protocol Pattern

Data Highlights

1Removing one forgotten VPN bypass raised the defender dominance ratio from 53.9% to 80.7% in the reference scenario.
2A fully connected perturbation (Case 2) collapsed the defender dominance to 22.7% despite near-identical formal winning-region size to the baseline.
3The reference example used a 5-host, 6-link network to demonstrate how topology tweaks change both formal and operational metrics.

What This Means

Security architects and network engineers who must decide how to reconfigure or harden small, critical network segments will get a formal yes/no defensibility verdict plus a prioritized diagnostic fingerprint. Teams building or evaluating automated attackers and defenders (multi-agent evaluation or agent governance groups) can use the post-convergence simulations to understand agent failure modes and operational risk before deployment. Evaluation-Driven Development (EDDOps)
Not sure where to start?Get personalized recommendations
Learn More

Key Figures

Figure 4 : Defensibility fingerprint for the baseline topology (Case 1). Six axes oriented so that points further from the center indicate greater danger. Each axis is independently scaled.
Fig 4: Figure 4 : Defensibility fingerprint for the baseline topology (Case 1). Six axes oriented so that points further from the center indicate greater danger. Each axis is independently scaled.
Figure 5 : Defensibility fingerprints for all five what-if cases. Topology perturbations (Cases 2 and 5) produce dramatically different fingerprints despite similar safety game metrics. Specification perturbations (Cases 3 and 4) reshape the fingerprint coherently across both layers. Each axis is independently scaled to the range observed across the five cases; shape comparisons are meaningful, absolute area is not an absolute vulnerability score.
Fig 5: Figure 5 : Defensibility fingerprints for all five what-if cases. Topology perturbations (Cases 2 and 5) produce dramatically different fingerprints despite similar safety game metrics. Specification perturbations (Cases 3 and 4) reshape the fingerprint coherently across both layers. Each axis is independently scaled to the range observed across the five cases; shape comparisons are meaningful, absolute area is not an absolute vulnerability score.
Figure 6 : Winning state space decomposition across what-if cases. Green: winning region (safe states). Yellow/red: attractor shells by depth (states absorbed during fixed-point computation). Case 4 (relaxed φ D \varphi_{D} ) produces the largest winning region; Case 3 (unlimited destroys) the smallest.
Fig 6: Figure 6 : Winning state space decomposition across what-if cases. Green: winning region (safe states). Yellow/red: attractor shells by depth (states absorbed during fixed-point computation). Case 4 (relaxed φ D \varphi_{D} ) produces the largest winning region; Case 3 (unlimited destroys) the smallest.
Figure 7 : Defender Dominance Ratio at post-convergence (L200) across what-if cases. Each point is one seed ( n = 10 n=10 ); boxes show interquartile range; whiskers extend to 1.5 IQR. Dashed line at 50% marks even split. Case 2 (fully connected) collapses to 22.7% despite near-identical safety game metrics to the baseline.
Fig 7: Figure 7 : Defender Dominance Ratio at post-convergence (L200) across what-if cases. Each point is one seed ( n = 10 n=10 ); boxes show interquartile range; whiskers extend to 1.5 IQR. Dashed line at 50% marks even split. Case 2 (fully connected) collapses to 22.7% despite near-identical safety game metrics to the baseline.

Ready to evaluate your AI agents?

Learn how ReputAgent helps teams build trustworthy AI through systematic evaluation.

Learn More

Considerations

The method requires an explicit, small-state model; guarantees are exact only for the modeled transitions and assumptions. Partial observability, large enterprise topologies, or model mismatch reduce the direct applicability—abstractions or probabilistic extensions are needed there. The certificate is a design-time tool, not a runtime safety net: using a shield computed on an approximate model as a deployed filter can be dangerous. Safety Layer

Methodology & More

The framework turns shield synthesis from a runtime enforcement tool into a design-time analysis instrument. Start by encoding defender safety and attacker rules as safety specifications and compile them into state machines. Guardrails Pattern Combine the system model and these automata to build a two-player safety game, compute the attractor (the set of states from which the attacker can force a violation), and extract the defender’s winning region. That winning region is the formal defensibility verdict: a certificate saying a winning defensive strategy exists under the modeled assumptions. Formal analysis is augmented with a second layer: put adaptive attacker and defender agents inside the certified winning region and run multi-agent reinforcement learning until policies converge. From the attractor shells and the post-convergence play, derive six defensibility metrics and plot a defensibility fingerprint. That two-layer view separates “can you survive?” (formal) from “how well can you survive?” (operational). The approach highlights where small topology changes or specification tweaks yield outsized operational gains (example: a single VPN rule removal shifted defender dominance from about 54% to about 81%), and flags cases where formal guarantees hide practical fragility. Practical extensions include probabilistic shielding and state abstraction to scale the analysis to larger segments. Planning Pattern
Avoid common pitfallsLearn what failures to watch for
Learn More
Credibility Assessment:

Authors have very low h-indices and no listed affiliations or reputable venue; fits an emerging/limited-information profile.