2bbb1871cc
Architecture restructure from morning review: 1. code/scripts/ subdivided into sim/, reach/, barrier/, plot/. Easier nav; `barrier/` is the natural place for SOS scale-up scripts. 2. Heatup PJ reach variants consolidated behind TOML configs. reach_heatup_pj.jl now takes `--config path/to/config.toml`; configs/heatup/baseline.toml (wide entry, from predicates.json) and configs/heatup/tight.toml (narrow entry, reproduces all-6-halfspaces discharged result). Old reach_heatup_pj_tight.jl and reach_heatup_pj_tight_full.jl deleted (superseded). 3. Reach output .mat files moved from reachability/ to results/. reachability/ now = specs + docs; results/ = ephemeral outputs (gitignored *.mat). README added. 4. OVERNIGHT_NOTES.md archived to claude_memory/2026-04-20-21-overnight- session-summary.md (date range in the filename makes the history clearer). All include() / Pkg.activate() paths in scripts updated for the new depth. Smoke tests pass (reach_operation.jl generates its .mat in the new results/ location; sim_sanity.jl matches MATLAB). Presentation outline for the 20-min prelim talk landed in presentations/prelim-presentation/outline.md. 14-slide assertion- evidence format targeting OT-informed cybersecurity audience. Each slide: one declarative assertion + one figure. Outline includes which figures already exist and which need to be created, timing checkpoints, cybersecurity angle to emphasize, and Q&A prep. New config configs/heatup/with_steam_dump.toml + its companion scripts/reach/reach_heatup_pj_sd.jl (12-state RHS with Q_sg as an augmented bounded parameter x[10] and time as x[11]). Kicks off point 3 from morning review. Next up: scram X_entry expansion (morning point 2) — LOCA scenario + union of mode reach envelopes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
app — Predicate Explorer (Pluto.jl)
A local-server visual companion to reachability/predicates.json. Maps
the FRET-spec boolean predicates to their numerical halfspaces over the
10-state continuous vector, shows mode invariants as conjunctions of
named safety limits, and previews a UI for editing them.
v1: read-only. Sliders display in the edit panel but do not write back to the JSON. v2 will add live write-through. v3 (the dream) will derive halfspaces automatically from the FRET spec.
This is the FRET-adjacent piece — the "hybrid-systems group tab" we talked about. Stand-alone for now; integration into the upstream FRET UI is a later story.
Run
First time:
cd app
julia --project=. -e 'using Pkg; Pkg.instantiate()'
Subsequent:
julia --project=. -e 'using Pluto; Pluto.run()'
A browser window opens (default http://localhost:1234). Pick
predicate_explorer.jl from the file list. The notebook is reactive —
edit any cell, dependent cells re-run.
What you can do today (v1)
- Inspect every operational deadband, safety limit, mode invariant, and mode boundary.
- See the boolean ↔ continuous mapping for each predicate.
- View a 2D projection (T_avg × n) showing the operating polytope.
- Read the reach-status traceability table — which artifact has tried to discharge which obligation, with link.
- Move sliders to feel out the editing workflow.
What lands in v2
- Sliders write back to
predicates.jsonwith an "are you sure" gate. - Diff view: pending changes vs.\ the on-disk version.
- Re-run reach scripts in-place from the notebook.
What's the dream (v3)
- The FRET spec at
../fret-pipeline/pwr_hybrid_3.jsondeclares predicate names without numerical concretization. Could we use a structured ontology of physical bounds (fuel limits, trip setpoints, rate limits) plus the FRET text to derive the concretization? - Round-tripping changes back into the FRET model so the synthesis side stays consistent.
Caveats
- Pluto notebooks aren't great in version control — they're long files with cell UUIDs and order metadata. The notebook is committed because it's small and the cell order matters.
- Manifest.toml is gitignored; regenerate locally.