Sol37 Archive 2026 04 13

This is an audit-era archive point for the Sol-37 site as it exists on the machine, not just as it exists in committed git history.

Executive Summary

This is an audit-era archive point for the Sol-37 site as it exists on the machine, not just as it exists in committed git history. Sol-37 Archive Point Date: 2026-04-13T14:04:36-05:00 Repo: /home/david/random Branch: main Head: 38c891cced2fed32f5ae99823bae1aeae3be1d77 Tag: sol37-audit-2026-04-13 What This Marks This is an audit-era archive point for the Sol-37 site as it exists on the machine, not just as it exists in committed git history.

Sol-37 Archive Point

Date: 2026-04-13T14:04:36-05:00
Repo: /home/david/random
Branch: main
Head: 38c891cced2fed32f5ae99823bae1aeae3be1d77
Tag: sol37-audit-2026-04-13

What This Marks

This is an audit-era archive point for the Sol-37 site as it exists on the machine, not just as it exists in committed git history.

The git tag marks the committed base on HEAD.
This note captures the additional working-tree state that was live during the audit.

Local Origin And Runtime

Observed running user services:

Observed active timers:

Working Tree State

Dirty tracked files at archive time:

Important untracked additions at archive time:

Audit Snapshot

Checks that passed at archive time:

Known sensitive area at archive time:

Large Public Payloads Worth Remembering

Largest files directly under the public tree included:

These payloads materially affect public playback behavior through the current tunnel path.

Intent

This archive point exists so future work can distinguish:

  1. committed Sol-37 history
  2. the larger live local feature set present in the working tree
  3. the specific runtime and service configuration active during the audit