Restructures the flat repo into one folder per session, with a top-level
README.md (the "about sessions" page, also rendered at /docs/sessions/about
by rfc-app v0.19.0+) and a sessions.json title manifest keyed by 4-digit
NNNN. Filenames inside each folder retain the full SESSION-NNNN.M-TRANSCRIPT-…
form (no trim of the SESSION- prefix). Legacy letter-form transcripts, if
any are still at the root, are not moved — the folder convention applies
to the numeric form only.
Session 0017.0; see SESSION-PROTOCOL.md §1 amendment for the binding shape.
Executed in Session 0014.0 (= legacy "Session N"), 2026-05-28. The
session-protocol naming convention switched from alphabetical letters
(SESSION-A through SESSION-M, plus SESSION-M.1/M.2/M.3 subsessions) to
zero-padded 4-digit session numbers with a subagent ordinal suffix
(SESSION-0001.0 through SESSION-0013.0, plus SESSION-0013.1/.2/.3).
Rationale: alphabetical ordering breaks down after Z (does AA sort
before B in a filesystem? a glob?), and the convention doesn't
generalize to deeper structure. The numeric form addresses both, and
the explicit `.0` for the main driver transcript makes the parent-vs-
subagent distinction visible at first glance.
Mapping (all 16 transcripts):
A → 0001.0
B → 0002.0
C → 0003.0
D → 0004.0
E → 0005.0
F → 0006.0
G → 0007.0
H → 0008.0
I → 0009.0
J → 0010.0
K → 0011.0
L → 0012.0
M → 0013.0
M.1 → 0013.1
M.2 → 0013.2
M.3 → 0013.3
This commit uses `git mv` for each rename so Gitea's rename detection
records each as a file-was-renamed event rather than file-was-deleted-
and-recreated. The transcript bodies are NOT rewritten — they still
read "Session I" / "Session M.1" / etc. internally; the body's session
reference and the filename's numeric form are both authoritative.
Readers map back via the table above.
External references to the old paths
(e.g. wiggleverse/ohm-session-history/SESSION-I-TRANSCRIPT-…md) will
404 after this rename. The audit trail is in this git log; readers
who care can trace. No redirect tombstones were added.
The publish-transcript.sh validator was extended to accept both the
numeric form (binding from 0014.0 onward) AND the legacy letter form
(so renamed-old-files remain re-publishable if their content is later
corrected). See ohm-infra/scripts/publish-transcript.sh and
ohm-infra/SESSION-PROTOCOL.md §1 (binding spec) for the new
convention.
Session 0014.0 is the first session to ship under the new naming
end-to-end.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Filename format: SESSION-<letter>-TRANSCRIPT-<start>--<end>.md
where each datetime is YYYY-MM-DDTHH-MM (PST, colons replaced by
dashes for filesystem compatibility, double-dash separator).
The renames preserve git history (every file moved via git mv). The
README's session table now shows the PST window for each session
inline.
Start times are best-inferences from each transcript's narrative;
end times are the file mtime when the transcript was last written.
Future sessions: use the same convention. The publish-transcript.sh
script's filename validator accepts both legacy SESSION-X-TRANSCRIPT.md
and the new SESSION-X-TRANSCRIPT-<times>.md shape.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Bootstrap commit for the public OHM session-history surface. Adds the
nine transcripts that existed at the time of first publish:
- A: git.benstull.org buildout (pre-OHM personal-Gitea infra)
- B: first OHM deployment of rfc-app
- C: rfc-app 0.3.0 + first OHM upgrade
- D, E, F, G: rfc-app + OHM iteration
- H: ohm-rfc-app-flotilla v1.0.0 — operator CLI for OHM deploys
- I: first autonomous-driver session; rfc-app v0.4.0 → v0.13.0 shipped
via parallel forked subagents
Per the v0.5.0 audit pass (recorded in ohm-infra/TRANSCRIPT-PUBLISHING-
PLAN.md), no redactions applied. Future single-session publishes use
ohm-infra/scripts/publish-transcript.sh.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Ben Stull
ben.stull