# Phase 0.9E-R2 final provenance decision

Date: 2026-07-19

Primary classification: `LOCAL_BACKUP_UNCORRELATED`

## Decision chain

1. The complete local ADS establishes `MEDIAFIRE_URL_EXACT` for file key
   `jq3fcutuwbb1mrb` and the exact local filename.
2. The exact MediaFire page is still present and establishes
   `MEDIAFIRE_OBJECT_METADATA_BOUND`, but exposes no server digest, exact byte
   count, public uploader, maker, tutorial, or source.
3. The mandatory official Gezine/Y2JB 1.6 4.03 inner differs in size,
   SHA-256, complete bytes, normalized layout, and section hashes.
4. The one justified community backup from owendswang also differs on every
   inner and structural measure.
5. itsPLK is a plausible public source family, but explicitly does not publish
   system backups and supplies no binding to this MediaFire object.
6. Y2X has no current large system-backup asset at its relevant release.

Therefore:

- `OFFICIAL_INNER_BYTE_MATCH`: false;
- `COMMUNITY_INNER_BYTE_MATCH`: false;
- `THIRD_PARTY_REPACK_PROVENANCE_BOUND`: false;
- `SIECAF_STRUCTURAL_RELATION_ONLY`: false;
- `LOCAL_BACKUP_UNCORRELATED`: true.

`LOCAL_BACKUP_NOT_CORRELATED` from Phase 0.9E-R remains historically correct
for the outer-asset analysis. R2 refines the current fail-closed result after
inner, structure, origin, and community correlation; it does not silently
replace the prior record.

## Separate identities

| Question | Result |
|---|---|
| Is the outer ZIP official? | no |
| Is the MediaFire object metadata-bound? | yes |
| Is its maker/source bound? | no |
| Is the inner official/community byte-bound? | no |
| Is even a normalized structural relation established? | no |
| Was this backup restored to the PS5? | `UNPROVEN` |
| Are current PS5 bytes known? | `UNPROVEN` |
| Is firmware-9.60 runtime behavior known? | `UNPROVEN` |

## Phase 0.9F

Phase 0.9F offline design may not be reconsidered. Neither of the entry
conditions is met:

- the inner is not byte-exactly bound to an auditable source family;
- the MediaFire backup is not bound to an auditable maker/release with a
  complete actual bootstrap implementation.

The actual deployed bootstrap, embedded listener closure, autoloader component
manifest, independent recovery, and current device contents remain unproven.
The byte-exact Payload Manager backup remains
`HARD_BLOCKER_FOR_INSTALLATION`.

## Authorization

All device, target-build, transfer, execution, installation, lifecycle,
autoload, device-write, rescue-design, and retry fields remain false. No PS5
action, target code, target artifact, payload, device client, restore, or
execution occurred.