fa45e96fd1
journal/ directory, LaTeX-based, dated entries, callout boxes for
derivations / decisions / dead ends / limitations, plus an \apass{}
macro for in-line markers when a later deep-pass is needed.
Retroactive A-style entries for 2026-04-17 (controllers, linearization,
LQR, operation-mode linear reach, Lyapunov barrier) and 2026-04-20
(predicates restructure into deadbands+safety+invariants, OL-vs-CL
barrier analysis, mode-obligation taxonomy, heatup-rate-as-halfspace,
mode_boundaries, first Julia nonlinear reach attempt).
Both entries include derivations written out in math, dead-ends I
hit, code snippets with commentary, figure embeds, and terminal
output where it changed what we did next. The goal is invention-log
depth — readable 4 years from now without the git history to help.
journal/README.md documents the conventions. journal.tex aggregates
all entries into one PDF via latexmk.
Kept claude_memory/ separate as per earlier agreement — those are
short AI-context notes, different audience.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
68 lines
2.0 KiB
TeX
68 lines
2.0 KiB
TeX
% journal.tex — top-level document that aggregates all dated entries.
|
|
%
|
|
% Build:
|
|
% cd journal && latexmk -pdf journal.tex
|
|
% or individual entry:
|
|
% cd journal && latexmk -pdf entries/2026-04-17-controllers-linear-reach.tex
|
|
|
|
\input{preamble.tex}
|
|
|
|
\title{HAHACS Lab Journal\\
|
|
\large PWR\_HYBRID\_3 preliminary example, invention log}
|
|
\author{Dane Sabo, with Claude (Hacker-Split)}
|
|
\date{Started \today}
|
|
|
|
\begin{document}
|
|
|
|
\maketitle
|
|
\tableofcontents
|
|
\newpage
|
|
|
|
\section*{How to read this journal}
|
|
|
|
Each section is a dated session. Sessions are written in two styles:
|
|
|
|
\begin{itemize}
|
|
\item \textbf{Deep (A-style)}: full invention-log depth. Derivations
|
|
in math, code snippets with commentary, figures with long
|
|
captions, dead-ends documented, terminal output included where
|
|
it changes the story. A reader in 2030 should be able to
|
|
rebuild the work from this alone.
|
|
\item \textbf{Narrative (B-style)}: end-of-session notes with
|
|
pointers. Marked with \apass{some detail} callouts for
|
|
content that should be expanded in a later A-pass.
|
|
\end{itemize}
|
|
|
|
Callout boxes signal specific content types:
|
|
|
|
\begin{derivation}
|
|
Mathematical derivations — algebra, integrals, limits. Where they
|
|
matter to the safety claim, they live here in full.
|
|
\end{derivation}
|
|
|
|
\begin{decision}
|
|
Design decisions made during the session, with the rationale and the
|
|
alternatives considered.
|
|
\end{decision}
|
|
|
|
\begin{deadend}
|
|
Approaches that didn't work and why. These are as valuable as the
|
|
working paths — they keep the next explorer from repeating the mistake.
|
|
\end{deadend}
|
|
|
|
\begin{limitation}
|
|
Known-approximate or known-broken behavior. Soundness gaps live here.
|
|
Each limitation ties to a plan or an open question.
|
|
\end{limitation}
|
|
|
|
\newpage
|
|
|
|
% ---- Session entries, in chronological order -------------------------------
|
|
\input{entries/2026-04-17-controllers-linear-reach.tex}
|
|
\newpage
|
|
\input{entries/2026-04-20-predicates-boundaries-julia-nonlinear.tex}
|
|
\newpage
|
|
\input{entries/2026-04-20-evening-mega-session.tex}
|
|
|
|
\end{document}
|