History

N0zoM1z0 6b1fd166b0 feat(ghidra): define the Windows P0 admission boundary Admit only native x86-64 PE applications when the Ghidra candidate runs on Windows while preserving the existing Linux format matrix. Add precise rejection codes for executable roles and managed targets, publish a machine-readable Windows capability report, and keep missing no-follow, ACL, Unix-socket, and PTY controls as independent observations rather than inferred support.		2026-07-17 03:05:19 +09:00
..
0001-provider-selection-and-analysis-profiles.md	feat(ghidra): define the Windows P0 admission boundary	2026-07-17 03:05:19 +09:00
0002-controlled-replay-authority-and-sandbox.md	feat(application): add isolated JavaScript replay	2026-07-16 15:45:55 +09:00
0003-managed-code-evidence-and-provider-boundary.md	feat(managed): project static evidence into application graph	2026-07-16 21:36:13 +08:00
README.md	feat(dotnet): add managed artifact triage	2026-07-16 17:05:03 +09:00

README.md

Architecture decision records

Accepted decisions describe the architecture that implementation PRs must follow. Acceptance does not by itself mean the behavior is shipped; each record states its implementation status separately.

ADR	Status	Implementation
0001: Provider selection and analysis profiles	Accepted	Foundation shipped; capability work continues
0002: Controlled JavaScript replay authority and sandbox policy	Accepted	Linux x86_64 extracted-module replay shipped
0003: Managed-code evidence and provider boundary	Accepted	PE/CLI triage shipped; deeper contracts planned