# Historical HTML Claim Review — Batch 07

## Scope

Reviewed `HTML-005` — *Technical Research Report: GCC-4244N Firmware Analysis (B104)*.

Added **34** claim records.

| Status | Count |
|---|---:|
| Validated | 6 |
| Partially corroborated | 7 |
| Historical/Untrusted | 11 |
| Open Question | 1 |
| Rejected | 8 |
| Negative Knowledge | 1 |

## Main findings

The report contains useful early observations, but its final readiness conclusion is not supported.

Supported or substantially supported:

- GCC-4244N is an MN103S-family drive.
- Current 104 analysis contains an effective CDB-backed `0xE7` parser gate.
- Current 104 analysis resolves READ DVD STRUCTURE `0xAD` through table and compare evidence.
- The broad Intel-style flash-command interpretation is plausible.
- RAM-only work must strictly avoid destructive erase/program/confirm commands.
- GCC-4244N 104 remains a strong recipient **candidate**.

Corrected or rejected:

- `0xAD` is READ DVD STRUCTURE, not the opcode name “Report RPC State.”
- A narrow failure to find `cmp 8` cannot prove the handler is absent.
- Loose immediate `0xA3` hits are not SEND KEY handler proof.
- The historical `0x4001719B/0x400171DA` mapping is not the current authoritative parser map.
- Parser recognition does not prove safe SRAM injection.
- A complete static command surface does not prove GDR-8050L `AD/C0` Xbox-auth semantics.
- The `0xFF` flash-reset block is not a demonstrated RAM-execution bridge.
- “READY TO INJECT XBOX FUNCTIONS” is rejected.

## Current evidence boundary

The current Stage5B profile identifies parser gate `0x900386FB`, CDB base `0x894`, tokens `HL`, `IT`, `RPC`, `RPC_JCS3`, and `RPC_SUFFIX`, READ DVD STRUCTURE tier `table_entry_valid`, six cave candidates totaling 141,857 bytes, and recipient status `strong_recipient_candidate`.

It also records `live_safe=false`, `ad_c0_auth_payload_handler_present=false`, and risk flag `ad_c0_auth_payload_not_verified`.

## Firmware identity boundary

The historical document says `B104`; current analysis identifies `104`; current user hardware is expected to run `VB104`. These remain separate provenance labels until exact lineage and byte identity are established.

## Claim index

| Claim | Status | Normalized claim |
|---|---|---|
| HCLM-B07-001 | historical_untrusted | The analyzed target is definitively GCC-4244N firmware revision B104. |
| HCLM-B07-002 | validated | GCC-4244N uses a Panasonic/Matsushita MN103S-family controller. |
| HCLM-B07-003 | partially_corroborated | The GCC-4244N controller should specifically be described as AM33 without qualification. |
| HCLM-B07-004 | historical_untrusted | B104 is significantly more optimized and modular than GCC-4241N A101. |
| HCLM-B07-005 | partially_corroborated | Vendor opcode 0xE7 is the strongest currently identified GCC-4244N 104 parser surface for low-level experimentation. |
| HCLM-B07-006 | rejected | The 0xE7 surface is already a validated payload-injection path. |
| HCLM-B07-007 | rejected | Opcode 0xAD should be named Report RPC State. |
| HCLM-B07-008 | historical_untrusted | Addresses 0x40078B90, 0x40001E48, and 0x4007454C are verified GCC-4244N B104 0xAD dispatcher branches. |
| HCLM-B07-009 | historical_untrusted | An 800-line trace failed to find a direct cmp 8 region-format check. |
| HCLM-B07-010 | negative_knowledge | Failure to find cmp 8 in a narrow linear trace proves the RPC handler is absent. |
| HCLM-B07-011 | partially_corroborated | The compiler modularized the 0xAD handler into disjointed subroutines. |
| HCLM-B07-012 | historical_untrusted | A single 0xA3-like hit at 0x40026124 was a data-reference false positive rather than a command branch. |
| HCLM-B07-013 | rejected | Every occurrence of immediate value 0xA3 should be treated as SEND KEY dispatch evidence. |
| HCLM-B07-014 | historical_untrusted | Call clusters near historical lines 1845 and 5122 contain ten or more calls. |
| HCLM-B07-015 | historical_untrusted | The two call clusters are respectively the main SCSI pivot and media/error-management hub. |
| HCLM-B07-016 | partially_corroborated | The firmware contains static GCC-4244N and 104/B104 identity strings. |
| HCLM-B07-017 | historical_untrusted | The identity table is verified at 0x4001C10B. |
| HCLM-B07-018 | historical_untrusted | B104 identity strings are accessed only through register-relative addressing and have no absolute long-form pointers. |
| HCLM-B07-019 | partially_corroborated | HLDS firmware uses vendor opcode 0xE7 for low-level service, transport, or memory-oriented operations. |
| HCLM-B07-020 | historical_untrusted | A direct cmp 0xE7 at 0x4001719B branches to the GCC-4244N payload handler at 0x400171DA. |
| HCLM-B07-021 | historical_untrusted | The historical handler at 0x400171DA performs classic CDB stack parsing. |
| HCLM-B07-022 | validated | Current GCC-4244N 104 evidence contains a CDB-backed 0xE7 parser gate at 0x900386FB with CDB base 0x894. |
| HCLM-B07-023 | rejected | The current 0xE7 parser evidence is live-safe for arbitrary hardware payload injection. |
| HCLM-B07-024 | validated | Current GCC-4244N 104 evidence resolves READ DVD STRUCTURE 0xAD through table+compare evidence. |
| HCLM-B07-025 | rejected | A complete static command surface proves that GCC-4244N already implements the GDR-8050L AD/C0 Xbox-auth payload behavior. |
| HCLM-B07-026 | partially_corroborated | The reviewed GCC-4244N prep stub does not use the SST 0x555/0x2AA unlock-address protocol. |
| HCLM-B07-027 | open_question | GCC-4244N definitively uses an Intel/Micron CFI flash device. |
| HCLM-B07-028 | partially_corroborated | Bytes 0xFF, 0x70, 0x20/0x80, 0x40, and 0xD0 in the stub are consistent with reset/read-array, status, erase/program, and confirm operations in an Intel-style command set. |
| HCLM-B07-029 | rejected | A RAM-only payload can be made safe by bridging the 0xE7 dispatcher to the 0xFF initialization block while avoiding 0x20/0xD0 erase/confirm commands. |
| HCLM-B07-030 | validated | Avoiding erase/program/confirm commands is required when the experiment is intended to remain RAM-only. |
| HCLM-B07-031 | rejected | The GCC-4244N research state was ready to inject Xbox functions. |
| HCLM-B07-032 | validated | GCC-4244N 104 is a strong recipient candidate with command surfaces, code-cave candidates, and parser evidence, but remains unvalidated for Xbox capability transplantation. |
| HCLM-B07-033 | rejected | B104, 104, B103, and VB104 payloads or live revisions may be collapsed into one deduplicated firmware identity. |
| HCLM-B07-034 | validated | The current expected live revision of the user-owned GCC-4244N fleet is VB104, while the historical B104 research document remains a separate source. |
