Add Wargames adversarial scenario contract#60
Open
mdheller wants to merge 8 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the first SCOPE-D Wargames adversarial scenario composition contract.
This is the executable JSON-schema counterpart to the ProCybernetica scenario-boundary doctrine. The new contract makes
AdversarialScenarioa governing composition object over existing Wargames artifacts rather than another ATT&CK coverage cell.Adds
config/schemas/wargames-adversarial-scenario.schema.jsonexamples/scope-d/wargames/wargames-adversarial-scenario.example.jsonexamples/scope-d/wargames/negative-fixtures/adversarial-scenario-attack-only.invalid.jsonexamples/scope-d/wargames/negative-fixtures/adversarial-scenario-memory-writeback.invalid.jsonscripts/validate-wargames-contracts.jsContract semantics
The scenario schema binds:
Safety boundary
This PR adds no runtime, no live collector, no engagement execution, no command execution, no payload delivery, no credential access, no memory writeback, no public report publication, and no downstream activation authority.
The schema deliberately holds these capability exposures at
falsefor Wargames examples.Validator behavior
The Wargames validator now requires the valid scenario fixture to pass and rejects invalid fixtures when:
Next tranche
P0.3: harden SCOPE-D semantic scenario gates further with additional negative fixtures for synthetic promotion and summary-only/model-generated finding promotion.