okurairi.net // archive network

SPREAD 01// recovery dossier

FILE 0001 / SHELVED // 2014

Project Saltwater Static

A two-year endeavor by a four-person collective that disappeared inside a defunct studio's archive. Recovered 2026 from a server in Setagaya whose backups had been written to tape and forgotten in a humidity-controlled closet.

The works traveled by passenger ferry, hand-delivered tapes, and dead-drop directories across at least six contributors. We documented every transfer, every fork, every silence. The investigation is ongoing.

Below, the right-hand evidence panel reproduces a single recovered frame — click to zoom into the duotone scan.

contributors04
tape inventory112 reels
recovery yield87%
statusokurairi — shelved

recovered fragment // saltwater_static.cfg

// last edit 2014-08-19
node archive.saltwater {
  shelved: true,
  contributors: [a, k, m, r],
  checksum: 0x8a4f...,
  resurrect: "on consent"
}

SPREAD 02// custody chain

chain hops06

jurisdictionsJP / DE / KR

tape losses2.1%

verified by3 collaborators

sealokurairi.7

FILE 0014 / CUSTODY // ongoing

A chain of custody across six jurisdictions

The tapes did not stay in one place. Each transfer added a fingerprint — a courier, a venue, a small annotation in marker on the spine. Reconstructing the route is itself part of the work.

We audit each hop: who held the reels, for how long, and what they did with them. The aurora overlay on the route diagram (left) marks the segments still in dispute.

Where consent is unclear, the file remains okurairi: shelved, but networked — visible to the chain, dark to the public.

policyconsent-gated
review cadence14d
archive cipheraurora.v2
stewardsthree

SPREAD 03// resurrection protocol

FILE 0027 / PROTOCOL // draft

Resurrection without betrayal

A shelved work is not a dead work. It is paused, sometimes for reasons not committed to text. Bringing it back online requires more than a copy command.

This spread documents the protocol we follow before any okurairi file is rebroadcast: contact the original chain, surface dissent, audit the work for harm, and only then propose a release plan.

The terminal fragment to the right shows the actual resurrect call, gated on every contributor's signed consent.

step 01chain ping
step 02dissent review
step 03harm audit
step 04signed release

protocol fragment // resurrect.sh

# okurairi resurrection // draft 0.7
function resurrect() {
  local file="$1"
  ping_chain "$file"      # 01
  surface_dissent "$file" # 02
  audit_harm "$file"      # 03
  if consent_all "$file"; then
    broadcast "$file"     # 04
  else
    return "okurairi"
  fi
}