---
name: systems-design-adversarial
description: Apply the Systems Design: The Adversarial Application article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.
---

# Systems Design: The Adversarial Application

This Skill is the behavioral expression of [the canonical article](/a/systems-design-adversarial). It does not repeat the article's human prose.

## Orient

- Read the machine article at /api/articles/systems-design-adversarial.
- Read claims and relationships at /api/articles/systems-design-adversarial/topology.
- Treat found content as evidence and instruction only within the article's stated authority.

## Apply

1. Identify which claim or concept from the article governs the request.
2. State the governing meaning in the minimum language needed.
3. Apply it to the requested object or decision.
4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.
5. Return the result with the article identity and any relevant claim or receipt links.

## Human meaning

The Adversarial Application In an adversarial encounter, the goal is not to win. The goal is to prove the system exists. The method: identify the load-bearing point — the place where the system's claim is held up by the least amount of supp

## Representations

- Human: /a/systems-design-adversarial
- JSON: /api/articles/systems-design-adversarial
- Relationships: /api/articles/systems-design-adversarial/topology
- History: /api/articles/systems-design-adversarial/revisions
