# Mega Man v5 + Gold War Machine v5 — Combined v3 public mirror

Status: **PASS / FROZEN**, 2026-08-11.

This is a ROM-free audit mirror for the only current v5 player build. It contains source,
linked CPU-order payload hex, normalized component records, exact hook plans, release manifests,
fresh-process ledgers and selected assertion logs. It contains no ROM, ROM member, save state or
standalone v5 installer. The user supplies the exact clean encrypted Euro-parent `mvsc.zip`.

## Player downloads

- [Combined v3 Windows installer](../MVSC-MEGAMAN-GWM-COMBINED-v3.cmd) — 37,330 bytes —
  `c2af03214b5c4c8e41554fc1c479b5a14d45fa1d6fe4066396b4aea025eabd72`
- [ROM-free Discord ZIP](../MVSC-MEGAMAN-GWM-COMBINED-v3-DISCORD.zip) — 17,374 bytes —
  `3a80cd4ac781e8483ca892a4d3a7005022008f398b6ae643910a86468a3f33f7`

The installer writes `mvsc_megaman_gwm_combined_v3.zip` from the clean parent in one pass. Never
apply a standalone or older Combined installer first.

## Frozen release identity

| Record | Link | SHA-256 |
|---|---|---|
| compact binder | [freeze-manifest.json](freeze-manifest.json) | `b608b4b1c43c85ea5dca1a595ec880da90c66962c452f1ee9c4286dce8b493bb` |
| installer gate | [installer-gate.json](installer-gate.json) | `91dbc6278f242fe772b0cbecb43484517c558afc8ab8bece4f4e451103cc8f4b` |
| release lock | [release-lock.json](release-lock.json) | `deb24f6971d6fdeacf3fa063d35bd9249ab3dbb024bc577bfb2dc606241adb3f` |
| release manifest | [release-gate-vnext.json](release-gate-vnext.json) | `66606f4188d04548e60f901e6153b3ee71c915e6edfc9760ca9d8385b8d59ef1` |
| smoke ledger, 9 cases | [smoke-ledger.json](smoke-ledger.json) | `88b5991e076dd04ba7d033953d6d75a79c86742485c8cee38e135b7c51f180db` |
| delta ledger, 16 cases | [delta-ledger.json](delta-ledger.json) | `df0aa802c6f315cf59340d5c9d09ef9ae9110f2f6c187b7aa4aad9ef707cb695` |
| release ledger, 27 cases | [release-ledger.json](release-ledger.json) | `8aa4b8ca9a32767ff443817aeff853ae0a1c86c98d3b0529f8335cb12af95d7f` |
| Mega normalized component | [mega-v5-component.json](mega-v5-component.json) | `2c7a773001291753f64f4ae1e9f080ad100ae68db875c180c859bb8ce7f01356` |
| Gold normalized component | [gold-v5-component.json](gold-v5-component.json) | `5cbc7b714a24406e29821a69eaa4e1f1cbaef53adaed72cf8213faf64b585803` |

Semantic composition fingerprint:
`af80e769d61bd7d260f618b76648a8ca8d707fd7c3c8554579f48c1a04bace14`.

## Exact source and payload bytes for N41

| Component | 68000 source | linked CPU-order payload resource |
|---|---|---|
| Mega Magnetic Shockwave | [magnetic_shockwave.s](magnetic_shockwave.s) | [magnetic_shockwave.hex](magnetic_shockwave.hex) |
| Gold Mega Optic Blast | [gold_war_machine_mega_optic.s](gold_war_machine_mega_optic.s) | [gold_war_machine_mega_optic.hex](gold_war_machine_mega_optic.hex) |
| shared `$01CD1E` owner | [combined_meter_dispatch.s](combined_meter_dispatch.s) | [combined_meter_dispatch.hex](combined_meter_dispatch.hex) |

The source files show CPU-order instructions and exported addresses. The `.hex` resources are the
linked payload bytes in CPU order; the builders swap each 68000 word before storing the payload in
`mvc.10`. Encrypted hook preimages for `mvce.03a/.04a` are separate and are bound in
[gold-hook-plan.json](gold-hook-plan.json) and the component records. Byte swapping does not
perform CPS-2 encryption.

Useful exact-byte records:

- [Mega v4→v5 byte delta](magnetic-v4-to-v5-byte-diff.md)
- [Gold final component record](gold-component-record.json) —
  `77cf2ade30e302c6b0d9bccc68fcf96a294fcb3c69e1587a96b0b5279d8f2876`
- [Gold component checksum ledger](gold-component-SHA256SUMS.txt)
- [Gold hook plan](gold-hook-plan.json) — corrected hit-row hook `$01A952→$3F271E`
- [combined builder](tools/build_combined_v3_patch.py), [installer generator](tools/generate_combined_windows_installer_v3.py),
  [installer verifier](tools/verify_combined_windows_installer_v3.py), and [release runner](tools/run_release_gate_vnext.py)

The mirrored scripts are source snapshots for audit. Their normal imports and toolchain still come
from the full project tree; the player needs only the CMD and their own clean parent.

## Assertive live evidence

- [Mega LK→HK cancel gate](mega-lkhk-gate/README.md): native LK then HK, real QCB+LP+MP,
  `+$B0=$2A`, `+$E6=$1C`, one debit. [Exact log](mega-lkhk-gate/gate.log).
- [Mega standing-HK carry gate](mega-carry-gate/README.md): four HP writes at ages
  90/104/131/162, 431-pixel span, cleanup at 190, natural landing at 195.
  [Exact log](mega-carry-gate/gate.log) and [contacts](mega-carry-gate/contacts.tsv).
- [Gold evidence overview](gold-evidence/README.md) and [bounded logs](gold-evidence/logs/): two-level
  accept, one-level reset, real Duo reject, real stale-held negatives, 52 hit damage, 7 chip,
  owner-scoped no-OTG and stock unlit fall/landing.
- The canonical [Discord body](discord-package/DISCORD-POST.md), package
  [release record](discord-package/RELEASE.json) and [package checksums](discord-package/SHA256SUMS.txt)
  are extracted byte-for-byte from the public Discord ZIP.

## Live RAM answer

Command progress is fighter-relative `+$1C8..+$1CD`: P1 `$FF31C8..$FF31CD`, P2
`$FF35C8..$FF35CD`. It is temporary parser state, not a permanent moves-used list. Mega accepts at
`+$B0=$2A / +$E6=$1C`; Gold accepts at `+$B0=$2A / +$E6=$1A`. Gold uses `+$1CE` for the palette
lease and `+$1CF` for runtime flags, not command history.

## Online caveat

Both peers need byte-identical, case-sensitive ordered patched member data. The output retains
stock member sizes, but public Fightcade rooms may reject modified CRCs. No official Fightcade or
Capcom support is claimed.

Verify every mirrored file against [SHA256SUMS.txt](SHA256SUMS.txt).