[GH-ISSUE #33] Report truthful segment, section, and memory metadata #23

New issue

Closed

opened 2026-10-15 18:20:04 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:20:04 +00:00

Owner

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

Problem

Segment permissions are currently reported as fixed false values rather than values observed from the binary or analysis provider. Unknown metadata is therefore indistinguishable from a verified negative result.

Agents must never interpret a placeholder as evidence.

Scope

Return actual readable, writable, and executable permissions where Hopper exposes them.
Represent unavailable values as null, omitted fields, or an explicit unsupported capability.
Apply the same rule to section and memory metadata.
Include provenance and provider limitations in the result.
Add fixtures covering executable, writable, read-only, and unavailable metadata.

Acceptance criteria

No permission or memory attribute is fabricated.
Contracts distinguish observed false from unknown or unsupported.
Tests prove parsing and transport preserve all three states.
Real-Hopper verification checks permissions against a known fixture binary.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/33 ## Problem Segment permissions are currently reported as fixed false values rather than values observed from the binary or analysis provider. Unknown metadata is therefore indistinguishable from a verified negative result. Agents must never interpret a placeholder as evidence. ## Scope - Return actual readable, writable, and executable permissions where Hopper exposes them. - Represent unavailable values as null, omitted fields, or an explicit unsupported capability. - Apply the same rule to section and memory metadata. - Include provenance and provider limitations in the result. - Add fixtures covering executable, writable, read-only, and unavailable metadata. ## Acceptance criteria - No permission or memory attribute is fabricated. - Contracts distinguish observed false from unknown or unsupported. - Tests prove parsing and transport preserve all three states. - Real-Hopper verification checks permissions against a known fixture binary.

bsakaguchi

2026-10-15 18:20:04 +00:00

closed this issue
added the
P1: high

area: bridge

bug
labels

bsakaguchi commented

2026-10-15 18:20:06 +00:00

Author

Owner

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

Resolved by #46. Hopper segment and section permissions now use tri-state true | false | null values with explicit hopper-public-python-api provenance and an unavailable-permissions reason; fabricated fixed false values are rejected by boundary tests. Linux real-Hopper verification passed against /bin/true and /bin/ls and checked every returned memory region.

@morluto commented on GitHub (Jul 13, 2026): Resolved by #46. Hopper segment and section permissions now use tri-state `true | false | null` values with explicit `hopper-public-python-api` provenance and an unavailable-permissions reason; fabricated fixed false values are rejected by boundary tests. Linux real-Hopper verification passed against `/bin/true` and `/bin/ls` and checked every returned memory region.

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-15 18:28:32 +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:17 +00:00

[PR #46] [MERGED] Evolve REA into an evidence-backed analysis platform #1811

bsakaguchi referenced this issue

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

[PR #85] [MERGED] feat(analysis): harden agent workflows and evidence boundaries #1823