History

Dane Sabo bc3a6028a9 docs: flag soundness, alpha-drift, saturation-hybrid in file headers

Three caveats surfaced during walkthrough lived only in the
conversation transcript before this commit.  Now they live where
future agents and future-me will actually see them:

- reach_operation.m and reachability/README.md state prominently that
  the current reach tube is an over-approximation of the LINEAR
  model, not a sound tube for the nonlinear plant.  Thesis-blocking
  for a real safety claim.  Upgrade paths documented.

- ctrl_heatup.m header and plant-model/CLAUDE.md note that the
  feedback-linearization u_ff assumes exact alpha_f, alpha_c.  Real
  plants drift (burnup ~20%, boron ~10x, xenon).  Robust treatment =
  parametric reach with alpha as an interval.

- ctrl_heatup.m header and plant-model/CLAUDE.md note that sat() is
  formally a 3-mode piecewise-affine sub-system.  Operation-mode LQR
  is dormant (trivially); heatup will need either a dormancy proof
  or explicit hybrid modeling.

README.md top-level now has a run-commands table for the reach
artifacts and a pointer to the soundness status.

Hacker-Split: raise caveats from transcript to artifact so the work
is actually reviewable by people who weren't in the room.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-17 16:15:39 -04:00

2026-04-16-controllers-roughout.md

Initial umbrella repo: thesis + FRET pipeline + plant model with first controllers

2026-04-16 16:24:11 -04:00

2026-04-16-repo-restructure.md

Initial umbrella repo: thesis + FRET pipeline + plant model with first controllers

2026-04-16 16:24:11 -04:00

2026-04-16-session-wrap.md

Initial umbrella repo: thesis + FRET pipeline + plant model with first controllers

2026-04-16 16:24:11 -04:00

2026-04-17-controllers-linearization-and-first-reach.md

docs: flag soundness, alpha-drift, saturation-hybrid in file headers

2026-04-17 16:15:39 -04:00

README.md

Initial umbrella repo: thesis + FRET pipeline + plant model with first controllers

2026-04-16 16:24:11 -04:00

README.md

claude_memory/

Session notes and scratch knowledge that hasn't (yet) earned a place in a CLAUDE.md. Anything that leaves a context window uncaptured is lost forever — this folder exists so session-level insight doesn't evaporate.

Purpose

A Claude context window is finite. Anything an agent figures out in a session that isn't written down is gone when the session ends. The curated CLAUDE.md files hold stable, authoritative knowledge; this folder holds everything else that's still worth remembering.

Pattern

One file per session with non-trivial insight.
Filename: YYYY-MM-DD-short-topic.md. Date first so ls is chronological.
Freeform. Rough edges encouraged. Don't polish — capture.
At minimum, answer: what did we do, what did we decide, what surprised us, what's still open.
Cross-reference files you edited, alternatives you considered, dead-ends you hit.

What graduates vs. what stays

Three futures for a note in here:

Graduates up into a CLAUDE.md (or docs/architecture.md, or a code comment) when the knowledge stabilizes and becomes authoritative. After graduating, consider deleting the note or leaving it as historical context.
Stays here as historical context — useful for "why did we do X last month?" or "what have we already tried?"
Gets deleted when it's no longer relevant (a fixed bug, an abandoned approach, a stale investigation).

The graduation step is a discipline, not automation. When you're finishing a session and think "a future agent needs this to avoid re-discovering it," ask: is this stable enough for a CLAUDE.md, or is it still forming?