-
Notifications
You must be signed in to change notification settings - Fork 0
docs: consolidate dual roadmaps into ROADMAP.md #68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
6b57c6c
45ad5d6
a30d43f
cbb8893
22cbc40
bf8f42f
572c186
098d0a1
18bc889
6710837
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,6 +14,22 @@ | |
|
|
||
| --- | ||
|
|
||
| ## Priority 0 — Gate (blocks any offensive Active Chain release) | ||
|
|
||
| > Folded in from the qwen-audited roadmap (2026-05-30). The Active Chain — wireless | ||
| > evil-twin + deauth, subnet recon, CVE check, and an autonomous Ollama agent under | ||
| > `modules/active/` + `modules/ai/` — is coded, tested, and committed, but **unreleased | ||
| > and undocumented**. It must not ship until this gate clears. Authorization is a review, | ||
| > not a code flag. | ||
|
|
||
| - [ ] **Legal-boundary review** — `docs/legal-boundaries.md` + SECURITY.md: jurisdiction, authorized-use definition, explicit will/won't-do list for deauth + evil-twin. | ||
| - [ ] **Authorization mechanism** — scope assertion + recorded operator consent that every `modules/active/` module checks before executing (not just a flag). Add a test asserting each active module refuses to run absent an authorized-target assertion. | ||
| - [ ] **Misuse threat model** — model RedOPS pointed at an unauthorized network; document the technical controls that make casual misuse hard. | ||
| - [ ] **Tested egress enforcement** — a test that attempts cloud egress during an active-chain run and asserts it is blocked (local Ollama only). Enforced, not asserted. | ||
| - [ ] **Operator runbook + smoke test** — mock authorized-engagement walkthrough; full-chain smoke test on lab hardware (Alfa AWUS036NHA + Kali) before tagging the release. | ||
|
|
||
| --- | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Missing AI Agent Hardening Tasks from Deleted RoadmapThe PR description states "One canonical roadmap, nothing lost." However, several critical security and reliability tasks from Milestone 2 — Harden the AI agent in the deleted Since these tasks are crucial for safely operating an autonomous agent with offensive capabilities, they should be integrated into
|
||
|
|
||
| ## Priority 1 — Critical (Do Now) | ||
|
|
||
| ### Security and Reliability | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Path and Formatting Consistency Improvements
Repository-Root-Relative Paths:
The paths
modules/active/andmodules/ai/(mentioned in lines 21 and 26) are specified relative to thesrc/redops/directory. However, other paths in this roadmap (such asdocs/legal-boundaries.mdandconfig/pipelines/) are specified relative to the repository root. To maintain consistency and avoid confusion, please update these to their full repository-root-relative paths:src/redops/modules/active/src/redops/modules/ai/Markdown Formatting Consistency:
In line 25,
docs/legal-boundaries.mdis enclosed in backticks, butSECURITY.mdis not. EnclosingSECURITY.mdin backticks (i.e.,`SECURITY.md`) will ensure consistent formatting for file references.