# ADR 0004: Treat Cosmic-client as a pinned binary/content reference only

Status: accepted

Date: 2026-08-20

## Context

`P0nk/Cosmic-client` is the optional client-files reference named for this
project. At pinned commit `6b7328b1593d34a4b134fe6b8a6d20119e526030`, it
contains Git LFS pointers for the original GMS v83 installer, a modified native
Windows executable, and Cosmic-custom WZ files. It does not contain a portable
client source implementation. Its README requires native installation and
hex-editing, warns that the executable is antivirus-flagged, and describes the
custom WZ data as a legacy Cosmic dependency.

The LFS payload could not be retrieved during the audit because the upstream
repository had exceeded its LFS budget. More importantly, repository
availability is not evidence that the operator has the right to redistribute
the proprietary client or game data publicly.

## Decision

Pin the repository commit as a read-only compatibility inventory only.

- Do not execute, patch, ship, decompile, or embed either `.exe` file.
- Do not fetch, commit, convert, or publish its WZ payload as part of an
  automated source build.
- Use the inventory and upstream release pairing only to identify which native
  v83/Cosmic content inputs an operator may need to supply separately.
- Continue to use the AGPL browser client lineage and pinned Cosmic source as
  implementation and protocol authorities.
- Require operator-supplied asset provenance, hashes, schema probes, and
  browser conversion evidence before Stage 7 can pass.

## Consequences

Cosmic-client does not close the legal asset blocker or any feature-matrix row.
If the operator later supplies compatible files, they remain ignored,
read-only inputs and are handled only by the non-destructive Stage 7 pipeline.
