[PR #5850] docs(native): propose V-CPU interpreter structure analysis #7087

Open
opened 2026-11-01 21:45:17 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5850
Author: @kxdkxd
Created: 10/21/2026
Status: 🔄 Open

Base: main ← Head: feat/vcpu-interpreter-analysis


📝 Commits (1)

  • 5f41666 docs(native): propose V-CPU interpreter structure analysis

📊 Changes

4 files changed (+164 additions, -0 deletions)

View changed files

➕ docs/specs/5820-vcpu-interpreter-structure/plan.md (+19 -0)
➕ docs/specs/5820-vcpu-interpreter-structure/spec.md (+117 -0)
➕ docs/specs/5820-vcpu-interpreter-structure/tasks.md (+10 -0)
➕ docs/specs/5820-vcpu-interpreter-structure/verification.md (+18 -0)

📄 Description

Summary

Adds a proposal for a read-only, provider-neutral V-CPU interpreter structure dossier, linked to #5820.

This PR records the proposed contract, implementation plan, tasks, and verification strategy. It intentionally does not implement interpreter recovery, automatic devirtualization, commercial-protection bypass, target execution, or instrumentation. The proposal remains blocked on the maintainer scope decision in #5820.

Problem and expected behavior

After ordinary control-flow obfuscation has been reduced, a custom bytecode interpreter can still make the active native program difficult to investigate. Existing native tools expose instructions, pseudocode, references, jump tables, and value traces, but do not provide a provider-neutral view of dispatch-loop, handler-table, handler-entry, and state-operand relationships.

The proposed dossier would preserve observed, derived, inferred, partial, and unknown facts. It would help analysts continue in Ghidra, Hopper, or IDA without claiming to reconstruct protected code.

Change and scope

  • Adds spec.md, plan.md, tasks.md, and verification.md under docs/specs/5820-vcpu-interpreter-structure/.
  • Limits the proposal to caller-selected regions, authenticated retained Evidence, and static relationships.
  • Explicitly excludes automatic bytecode decoding, devirtualization, decompiler plugins claiming generic protection recovery, anti-debugging evasion, and target mutation.
  • Records the unresolved maintainer decision rather than checking implementation tasks prematurely.

Contribution scope and linked decision: #5820 is open and awaiting maintainer review. This draft does not assert that the proposal is approved for integration.

Contract and boundary impact

  • Semantic owner and earliest changed stage: documentation-only proposal; no semantic owner or runtime stage is changed.
  • Contribution scope fit and linked maintainer decision: pending #5820.
  • CLI and MCP/tool-catalog contract: none in this PR.
  • Provider, bridge, target-format, or platform compatibility: proposed provider-neutral design; no implementation.
  • Evidence, artifact, provenance, or reconstruction contract: proposed only; no generated metadata.
  • Target selection, authority, upstream behavior, and cleanup details: proposed read-only analysis of caller-selected retained provider Evidence; no execution or mutation.
  • Generated metadata/package/installation impact: none.

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: none; this is a proposal document.

  • Base reproduction or other evidence: issue #5820 and the contribution-scope rule.

  • User-visible CLI/MCP output: not applicable.

  • Remaining proof gaps: maintainer scope decision; technical feasibility of the first provider projection; synthetic fixture design.

  • Observed, derived, and inferred claims are separated in the proposed contract.

  • Artifact identity and source provenance are required by the proposed workflow.

  • Unsupported, incomplete, unavailable, and uncertain outcomes remain visible.

Validation performed

  • npm ci — installed the exact 542-package development tree with no lockfile change.
  • npm run docs:check — passed: 6 build tasks and 5 conformance tests.
  • git diff --check — passed.
  • npm run check:fast via pre-push — passed: typecheck and lint, 2 tasks.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; no analysis implementation.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: documentation-only. The proposal explicitly excludes target interaction and commercial protection bypass.

Author readiness

Human owner: @kxdkxd

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs and generated metadata were reviewed; no generated contract change is present.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/5850 **Author:** [@kxdkxd](https://github.com/kxdkxd) **Created:** 10/21/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/vcpu-interpreter-analysis` --- ### 📝 Commits (1) - [`5f41666`](https://github.com/morluto/rea/commit/5f4166630c975c7abd517f6aedd9f4bd0109e3d6) docs(native): propose V-CPU interpreter structure analysis ### 📊 Changes **4 files changed** (+164 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `docs/specs/5820-vcpu-interpreter-structure/plan.md` (+19 -0) ➕ `docs/specs/5820-vcpu-interpreter-structure/spec.md` (+117 -0) ➕ `docs/specs/5820-vcpu-interpreter-structure/tasks.md` (+10 -0) ➕ `docs/specs/5820-vcpu-interpreter-structure/verification.md` (+18 -0) </details> ### 📄 Description ## Summary Adds a proposal for a read-only, provider-neutral V-CPU interpreter structure dossier, linked to #5820. This PR records the proposed contract, implementation plan, tasks, and verification strategy. It intentionally does not implement interpreter recovery, automatic devirtualization, commercial-protection bypass, target execution, or instrumentation. The proposal remains blocked on the maintainer scope decision in #5820. ## Problem and expected behavior After ordinary control-flow obfuscation has been reduced, a custom bytecode interpreter can still make the active native program difficult to investigate. Existing native tools expose instructions, pseudocode, references, jump tables, and value traces, but do not provide a provider-neutral view of dispatch-loop, handler-table, handler-entry, and state-operand relationships. The proposed dossier would preserve observed, derived, inferred, partial, and unknown facts. It would help analysts continue in Ghidra, Hopper, or IDA without claiming to reconstruct protected code. ## Change and scope - Adds `spec.md`, `plan.md`, `tasks.md`, and `verification.md` under `docs/specs/5820-vcpu-interpreter-structure/`. - Limits the proposal to caller-selected regions, authenticated retained Evidence, and static relationships. - Explicitly excludes automatic bytecode decoding, devirtualization, decompiler plugins claiming generic protection recovery, anti-debugging evasion, and target mutation. - Records the unresolved maintainer decision rather than checking implementation tasks prematurely. Contribution scope and linked decision: #5820 is open and awaiting maintainer review. This draft does not assert that the proposal is approved for integration. ## Contract and boundary impact - Semantic owner and earliest changed stage: documentation-only proposal; no semantic owner or runtime stage is changed. - Contribution scope fit and linked maintainer decision: pending #5820. - CLI and MCP/tool-catalog contract: none in this PR. - Provider, bridge, target-format, or platform compatibility: proposed provider-neutral design; no implementation. - Evidence, artifact, provenance, or reconstruction contract: proposed only; no generated metadata. - Target selection, authority, upstream behavior, and cleanup details: proposed read-only analysis of caller-selected retained provider Evidence; no execution or mutation. - Generated metadata/package/installation impact: none. Expected effects: - [ ] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [x] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: none; this is a proposal document. - Base reproduction or other evidence: issue #5820 and the contribution-scope rule. - User-visible CLI/MCP output: not applicable. - Remaining proof gaps: maintainer scope decision; technical feasibility of the first provider projection; synthetic fixture design. - [x] Observed, derived, and inferred claims are separated in the proposed contract. - [x] Artifact identity and source provenance are required by the proposed workflow. - [x] Unsupported, incomplete, unavailable, and uncertain outcomes remain visible. ## Validation performed - `npm ci` — installed the exact 542-package development tree with no lockfile change. - `npm run docs:check` — passed: 6 build tasks and 5 conformance tests. - `git diff --check` — passed. - `npm run check:fast` via pre-push — passed: typecheck and lint, 2 tasks. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; no analysis implementation. - Package or release metadata impact: none. - Security, privacy, process, or containment review: documentation-only. The proposal explicitly excludes target interaction and commercial protection bypass. ## Author readiness Human owner: @kxdkxd - [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [ ] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs and generated metadata were reviewed; no generated contract change is present. - [ ] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7087
No description provided.