Repository navigation
Open
Labels
blockedBlocked on an upstream gate or dependencyBlocked on an upstream gate or dependencybugSomething isn't workingSomething isn't working
Description
Problem
The packaged NASim red participant repeats one exploit, while every authored description of that participant names the run_bruteforce_agent baseline. On dev (0272949):
src/raes_adapters/nasim/examples/nasim-tiny/participant/nasim-red-bruteforce.configuration.jsonL18-28 has one value,red-action-contract-address=participant.action-contract.service-exploit.src/raes_adapters/nasim/researcher.pyL232-235 accepts only that contract, and_red_action_requestsendsnormalized_arguments=()(L257), so no target reaches the driver.- The driver resolves a semantic action kind and an optional target to one flat action (
src/raes_adapters/nasim/backend/driver.pyL291-318). With no target it resolves the same flat action on every step: index 4, the exploit on host (1, 0). - The SDL describes the attacker as "run_bruteforce_agent baseline attacker cycling the flat action space" (
nasim-tiny.sdl.yamlL136, L277), ledger rows 16 and 17 (mapping/source-ledger.jsonl) citenasim/agents/bruteforce_agent.py, and the task (nasim-tiny.task.exp.jsonL6,experiment/nasim-tiny.task.exp.yamlL7) names the same baseline. That baseline cycles all 18 flat actions.
A probe recorded in #98 with the pinned nasim 0.12.0 wheel truncated at step 1000 with cumulative reward -1000 and the goal unreached. Every step costs 1 and root is never taken.
The fix changes a packaged configuration and the researcher run path, which the 2026-08-13 hold on #87 does not allow until OpenRAE/rae#1023 is settled.
Scope
- Make the packaged red participant behave as the authored
run_bruteforce_agentbaseline (cycling the flat action space through portable actions and targets), or change the SDL, ledger rows 16 and 17 and the task to describe the behavior that actually runs. - Keep the configuration digest, pack content manifest and spec references consistent with the change.
Done when
- The packaged red participant's behavior and the SDL, ledger and task descriptions agree.
- A test drives the packaged configuration through the researcher run path and fails if every step resolves to the same flat action while the baseline is claimed.
- Pack validation and the release checks pass.
Related
- docs(nasim): inventory evidence-capture requirements #98 (records the finding in the NASim evidence-capture inventory, section 4)
- fix(nasim): reconcile SDL evidence requirements, simulator capture, and backend manifest #87 (the hold), feat(nasim): add the example environment pack and researcher workflow #36
Metadata
Metadata
Assignees
Labels
blockedBlocked on an upstream gate or dependencyBlocked on an upstream gate or dependencybugSomething isn't workingSomething isn't working
Activity