# Interim Single-Disk Operating Plan

## Status

Active planning baseline until new physical drives are installed.

## Storage layout

Use most—but not all—of the approximately 900 GB currently unallocated on the
existing 1 TB HDD as a new ext4 data filesystem. Keep the existing operating
system allocation unchanged unless the server preflight proves it is too small.
Leave a modest unallocated reserve and keep at least 15% of the data filesystem
free during normal operation.

Recommended mount point:

```text
/srv/project-frankenstein
```

Recommended top-level layout:

```text
/srv/project-frankenstein/
  repos/
  service/
  artifacts/
    irreplaceable/
    canonical/
    expensive/
    quarantine/
    scratch/
  catalog/
  incoming/
  releases/
    pfes/
    tools/
  recovery/
    git-bundles/
  tmp/
```

The included layout script creates directories only. It does not partition,
format, mount, resize, or erase a disk.

## Filesystem and service choices

- ext4 on the new data partition;
- ordinary SATA/AHCI;
- bare Git or a lightweight Forgejo/Gitea installation;
- no ZFS, hardware RAID, SAS controller, filesystem deduplication, or analyzer
  execution on this 4 GB server;
- Git LFS only for selected medium-sized, commit-coupled binary fixtures;
- disc images and large generated outputs remain in the external artifact store.

## Capacity controls

- below 70% used: normal operation;
- 70–80%: review growth and quarantine;
- 80–85%: stop accepting cheap reproducible outputs;
- above 85%: accept only A0/A1 material after review;
- 90% or more: stop nonessential writes until space is reclaimed.

## Protection status

This is a single physical disk. Git history, same-disk Git bundles, release ZIPs,
and hashes protect against some logical mistakes; they do not protect against
HDD failure, theft, fire, controller failure, or filesystem-wide loss.

Until a second physical disk is installed and verified:

1. do not delete workstation/source originals after server ingest;
2. do not call same-disk copies backups;
3. run regular `git fsck`, hash audits, free-space checks, and SMART tests;
4. preserve A0/A1 source provenance outside the server;
5. treat the server as an additional working/archive location, not the sole copy.
