# 2026-06-07 Public Spine and Manual Shelf Process Record

## Summary

- Process ID: `FI-PROCESS-2026-06-07-PUBLIC-SPINE`
- Status: active public-site design record
- Related public route: `/hang-on-to-each-other/`
- Related source shelf: `assets/reference/hang-on-to-each-other/`

## What Happened

The `Hang On To Each Other` reference shelf began as a local SLUSH find: a CaseLabs Mercury S8 assembly timelapse recovered from the ExtremeRigs review context. It became the first public technical manual because the original assembly instructions are not present in the local archive.

The homepage then needed a stronger public spine. The important design decision was that the Prelude, `Perspective, Peregrine, and Pang`, should not be buried by newer technical finds. It belongs to Manuscripts as Entry 000. `Hang On To Each Other` belongs to Technical References as Manual 001.

## Design Decisions

- Entry 000 stays first as a Manuscripts/origin entry.
- Technical manuals sit in Technical References, not above the Prelude.
- Field Notes becomes the Matthew Marx live feed.
- Projects carries dossiers and continuity records.
- `What ABOUT Art?` replaces a separate About lane and becomes the about-me/art-life surface.
- `Hang On To Each Other` becomes the credit-and-wisdom layer: third-party references are credited visibly, then translated into useful restoration knowledge.
- Credit is the signal. This is not hidden telemetry or surveillance; it is visible attribution built into the archive surface.
- The top directory should read more like a stacked archive/radio index than a conventional horizontal nav.
- The Tyler Etters stencil mark should lead the landing page visually.
- Body text should move toward a mono archive voice; headings should carry more stencil/editorial weight.

## Why This Matters

The process is part of the artifact. Forgotten Industries is not only the finished site; it is the visible recovery of source material, identity, typography, structure, manuals, credit, and judgment. Documenting these decisions prevents the archive from becoming a flattened portfolio and preserves the logic of how the public surface came to be.

## ATLAS Extraction Candidate

This pattern should be mirrored back into the reusable ATLAS source when that repository is available:

- Treat major archive decisions as artifacts in their own right.
- Preserve the reasoning, not only the final output.
- Keep local project records authoritative, then generalize the method into ATLAS.
- Use process notes when a project changes identity, information architecture, evidence handling, public presentation, or recovery method.