AXIOM · ARCHIVE INTAKE

Drop the mess here.

Inventory first. Judge later. Nothing is moved, renamed, retired or deleted during intake.

This is the first practical step in the Saint John Archive case study: preserve provenance, fingerprint the files, and give AXIOM a trustworthy inventory to reason about.

DISCOVERY ≠ DELETIONEvery file keeps its source name, path, size, type and fingerprint.

01 · LOCAL INVENTORY

Choose files or a folder.

AXIOM inventories locally first. No upload begins until you explicitly approve it.

Drag & drop files here

or choose a source manually

02 · AXIOM STAGING VAULT

Stage the manifest first.

The safest current workflow is to export the AXIOM manifest for any size archive. Optional browser upload is limited to small files because Netlify Functions have a tight binary request limit.

Large PSD/TIFF/CMYK archives: keep the originals on the drive. AXIOM should index them locally first; a later desktop companion will handle large-file transfer without forcing decades of masters through a browser.

Private intake key Preserve source names and never auto-delete

03 · WHAT AXIOM GETS

A governed intake record.

FingerprintSHA-256 exact-match detection.

ProvenanceOriginal filename and source path.

Technical factsSize, MIME type and modification time.

LifecycleStarts as REVIEW / source quality unknown.

AuthorityNo Master assignment without human approval.

Next stepAsset families, better-source discovery and visual similarity.

AXIOM CANON CASE STUDY 001

The Saint John Archive

We didn’t clean the archive for AXIOM. We gave AXIOM the archive as we found it.

AXIOM → ← Back