# Project Frankenstein Git Server Storage Plan (Revision 0.2)

## Status
Draft – Reviewed

## Engineering Revisions

- Treat this document as an operational infrastructure plan, not part of PFES.
- PFES should inherit only durable storage policies.
- Target three copies of critical data (working, local backup, off-server/offline backup).
- Existing 1 TB HDD backs up the critical subset, not the entire archive.
- Introduce stable Artifact IDs alongside SHA-256 hashes.
- Periodically verify backups (restore tests, hash verification, Git integrity checks, SMART).
- Use Git LFS selectively; it is not the primary archive.
- Repository splitting should follow engineering boundaries, not repository size.

## Candidate PFES Storage Classes

### Critical / Irreplaceable
Original firmware, provenance, PFES, source code, unique memory captures.

### Canonical Large
Accepted firmware packages, validated releases, canonical results.

### Expensive but Reproducible
Landmark analyzer runs and selected emulator traces.

### Cheap / Reproducible
Build trees, scratch outputs, temporary extraction directories.

## Relationship to PFES

Keep this document separate from PFES.

PFES should absorb:
- Artifact Lifecycle
- Storage classes
- Provenance policy
- Manifest policy
- Deletion policy
- Backup philosophy

Hardware recommendations remain outside PFES.
