summaryrefslogtreecommitdiffstats
path: root/debug/risc-v-gsp-rm-vm/docs/08-ROADMAP.md
diff options
context:
space:
mode:
Diffstat (limited to 'debug/risc-v-gsp-rm-vm/docs/08-ROADMAP.md')
-rw-r--r--debug/risc-v-gsp-rm-vm/docs/08-ROADMAP.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/debug/risc-v-gsp-rm-vm/docs/08-ROADMAP.md b/debug/risc-v-gsp-rm-vm/docs/08-ROADMAP.md
index 5d8a9b1..3a518c4 100644
--- a/debug/risc-v-gsp-rm-vm/docs/08-ROADMAP.md
+++ b/debug/risc-v-gsp-rm-vm/docs/08-ROADMAP.md
@@ -1,16 +1,16 @@
-# 08 — green-eye roadmap
+# 08 — risc-v-gsp-rm-debugger roadmap
> **# TOOL IN DEVELOPMENT - NOT READY YET!** See 00 for status.
> This is the **near-term, committed** roadmap (rungs R0–R7 below). The
> **long-term program** — adversarial firmware navigation, adjacent
> microcontrollers, a non-QEMU custom simulator, a Verilog soft-processor
> environment and the agentic platform — lives in
-> [`../GREEN-EYE-ROADMAP.md`](../GREEN-EYE-ROADMAP.md).
+> [`../RISC-V-GSP-RM-DEBUGGER-ROADMAP.md`](../RISC-V-GSP-RM-DEBUGGER-ROADMAP.md).
> Items here are **not** v0.1. Do not start them ad hoc; each has a gate.
## R0. Product principles
-* green-eye stays a **development tool**: no shipped dependencies, no guest
+* risc-v-gsp-rm-debugger stays a **development tool**: no shipped dependencies, no guest
presence, no kernel-module coupling.
* Fidelity improvements must be *measurable* (metrics table in 06) and must
not slow the fast path (demo + probe) below usefulness.
@@ -72,7 +72,7 @@ only after the guest-bridge work (PLAN B) no longer depends on it.
[20-MCP-SERVER](20-MCP-SERVER.md) for the live tool list, transports and
capability flags. The text below is the original design sketch.
-**Why:** expose green-eye sessions to AI harnesses and other agents under the
+**Why:** expose risc-v-gsp-rm-debugger sessions to AI harnesses and other agents under the
plugin model the user requested.
**Shape:** a plugin (`plugins/mcp_server.py` when built) that wraps the
@@ -101,7 +101,7 @@ step traces already cover the common cases.
## R5. Fuzzing and mutation harness
Use AFL++ QEMU mode (or a custom mutator) against the rehosted firmware's
-RPC input surface, with green-eye recording crash/trap paths and symbol
+RPC input surface, with risc-v-gsp-rm-debugger recording crash/trap paths and symbol
annotation. Requires R1/R2 for stable input plumbing. Output: a corpus of
malformed controls and the firmware's error paths, feeding the emulation's
fail-closed rules (project security hygiene).
@@ -114,13 +114,13 @@ tables. This automates `07-PORTABILITY-PLAYBOOKS` P1–P3.
## R7. Ghidra two-way console
-A Ghidra script/plugin that talks to a live green-eye session (via the CLI or
+A Ghidra script/plugin that talks to a live risc-v-gsp-rm-debugger session (via the CLI or
a local socket) to toggle breakpoints/watchpoints from the decompiler and to
highlight hit addresses. Until then, the hit-TSV + `MarkGreenEyeHits.java`
flow is the supported path.
-## Not on the green-eye roadmap
+## Not on the risc-v-gsp-rm-debugger roadmap
* Graphics/display emulation, Windows guest internals, multi-tenant policy —
these belong to the main project roadmap, not to this analysis tool.
-* Replacing Ghidra: green-eye is the dynamic complement, never a decompiler.
+* Replacing Ghidra: risc-v-gsp-rm-debugger is the dynamic complement, never a decompiler.