[GH-ISSUE #20] Introduce provider-neutral analysis capabilities and sessions #15

New issue

Closed

opened 2026-10-15 18:19:56 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-15 18:19:56 +00:00

Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/20

Goal

Generalize the application layer before adding another engine, retaining Hopper as the sole production provider initially.

Scope

Define AnalysisProvider, ProviderSession, capabilities, requests, responses, and errors; isolate Hopper DTOs; support discovery, typed unavailability, multiple artifacts, and multiple provider sessions; preserve CLI/MCP compatibility.

Acceptance criteria

Workflows do not import Hopper-specific types.
Hopper passes provider conformance.
Routing is deterministic and visible in evidence.
Provider-specific enrichment remains possible.

Roadmap expansion

This remains the provider-architecture epic.

Child work

Evidence creation must receive provider identity. Domain and application contracts must not encode Hopper. Capability descriptors declare availability, schema version, boundedness, exhaustiveness, side effects, and limitations. A second production provider remains blocked until these contracts pass conformance.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/20 ## Goal Generalize the application layer before adding another engine, retaining Hopper as the sole production provider initially. ## Scope Define `AnalysisProvider`, `ProviderSession`, capabilities, requests, responses, and errors; isolate Hopper DTOs; support discovery, typed unavailability, multiple artifacts, and multiple provider sessions; preserve CLI/MCP compatibility. ## Acceptance criteria - Workflows do not import Hopper-specific types. - Hopper passes provider conformance. - Routing is deterministic and visible in evidence. - Provider-specific enrichment remains possible. ## Roadmap expansion This remains the provider-architecture epic. ### Child work - [x] #52 - [x] #53 - [x] #49 - [x] #45 Evidence creation must receive provider identity. Domain and application contracts must not encode Hopper. Capability descriptors declare availability, schema version, boundedness, exhaustiveness, side effects, and limitations. A second production provider remains blocked until these contracts pass conformance.

bsakaguchi

2026-10-15 18:19:56 +00:00

closed this issue
added the
area: server

P1: high

area: domain

roadmap

enhancement
labels

bsakaguchi commented

2026-10-15 18:19:57 +00:00

Author

Owner

@morluto commented on GitHub (Jul 17, 2026):

Completed on current . The provider-neutral boundary is now represented by , , , and , with both Hopper and Ghidra production adapters and provider-binding/conformance coverage. Remaining provider-specific capability additions are tracked separately, so this architecture issue no longer needs to remain open.

@morluto commented on GitHub (Jul 17, 2026): Completed on current . The provider-neutral boundary is now represented by , , , and , with both Hopper and Ghidra production adapters and provider-binding/conformance coverage. Remaining provider-specific capability additions are tracked separately, so this architecture issue no longer needs to remain open.

bsakaguchi commented

2026-10-15 18:19:58 +00:00

Author

Owner

@morluto commented on GitHub (Jul 17, 2026):

Correction to the preceding comment: completed on current main. The provider-neutral boundary is represented by src/application/AnalysisProvider.ts, AnalysisProviderRegistry.ts, SessionProviderRouter.ts, and CompositeProvider.ts, with Hopper and Ghidra production adapters plus provider-binding and conformance coverage.

@morluto commented on GitHub (Jul 17, 2026): Correction to the preceding comment: completed on current main. The provider-neutral boundary is represented by src/application/AnalysisProvider.ts, AnalysisProviderRegistry.ts, SessionProviderRouter.ts, and CompositeProvider.ts, with Hopper and Ghidra production adapters plus provider-binding and conformance coverage.

bsakaguchi referenced this issue

2026-10-15 18:28:29 +00:00

[GH-ISSUE #2383] [Tracker] Audit analysis and debugging coverage for the TIOBE top 100 languages (October 2026) #794

bsakaguchi referenced this issue

2026-10-16 21:11:16 +00:00

[PR #15] [MERGED] [codex] Simplify REA onboarding and app targeting #1810

bsakaguchi added

enhancement

and removed

enhancement

labels

2026-10-31 00:28:37 +00:00