chore: refresh the shipped datasets - #7
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
chore/datasets-refresh
branch
from
August 24, 2026 05:54
4e3609c to
df561a6
Compare
github-actions
Bot
force-pushed
the
chore/datasets-refresh
branch
from
September 7, 2026 10:19
df561a6 to
2914fa6
Compare
The weekly refresh brought a release that moves things the prose had written down. AML.TA0001 is no longer "AI Attack Staging" but "AI Attack Adaptation", and MITRE moved it from twelfth to third, before Initial Access: it is now what you shape before you are in the environment, and keep reshaping while the attack runs. The five techniques it gains say why, three of them about an agent adjusting its own path. The counts move with it. 178 techniques become 197, the ones adapting an ATT&CK technique 37 become 42, and the names shared with ATT&CK 36 become 41. Each of those is stated in prose somewhere and asserted by a test, which is what turned a dataset bump into a red run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EZKZRDMVAdrWUQP2crYVXH
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.
Weekly regeneration of the corpora committed under
frontend/public/. What the build scripts reported:Worth reading the diff for, rather than merging blind: a name that
moves between the two actor corpora changes which spelling
analysts are offered, and therefore which identifier their objects
get.
The frontend tests FAILED against these files. Something written down beside the datasets no longer agrees with them: a name arbitration, or a number in the framework pages. The run log says which. Fix it on this branch rather than merging.