displacement: drive fuzzing primitives with schemathesis under the adversarial loop #31
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/gauntlet#31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Displacement: drive the fuzzing layer with schemathesis, keep the adversarial loop
From the 2026-06-17 displacement scout.
gauntlet's novel core - the two-role attacker/inspector adversarial MCP loop, role discipline, and holdout evaluation - is worth keeping custom. But the request-generation / API-fuzzing PRIMITIVES underneath overlap mature OSS:
schemathesis- property-based, OpenAPI/GraphQL-schema-driven, strong at semantic errors. Actively maintained 2026.RESTler- stateful (infers request dependency grammar), strong at server errors / deeper coverage.Action (design call, not mechanical)
Keep custom
The MCP role discipline, iteration/holdout records, and the adversarial loop itself.
Caution
New dependency - run
tooling-supply-chain-audit+ pin before adopting.Closing. gauntlet is archived in the June 2026 surface reduction.