Software Documentation
RAMAL-EBX currently owns Project workspaces, editable PHITS Designs, Project-independent Execution Profile configuration, durable local and remote Calculation lifecycle, verified Result publication, and Raw artifact inspection.
Subsystem ownership
| Subsystem | Owns | Start here |
|---|---|---|
| Application shell | SDL lifecycle, GPU and shader startup, frame loop, Project/Design/configuration navigation, and accessibility | main.odin, app_runtime.odin, editor_shell.odin |
| Session state | Active Project, authoritative Design draft, derived preview scene, Project and Execution Profile catalogs, mesh work, and caches | app_state.odin, editor_state.odin |
| Project storage | Project descriptors, workspace containment, record IDs, timestamps, hashes, exclusive creation, and atomic replacement | project.odin, project_storage.odin, storage.odin |
| Design authoring | Byte-preserving PHITS files, revision-scoped lossless source indexing, structured and exact-source interaction, stale-draft rejection, derived viewport state, and solver validation | design.odin, design_source_index.odin, design_phits.odin, editor_design_ui.odin |
| Execution configuration | Strict local/remote profile schema, built-in completion-adapter compatibility, safe atomic catalog persistence, one-time legacy conversion, and the Project-independent GUI manager | execution_profile.odin, editor_execution_profile_ui.odin |
| Calculation execution | Immutable input capture, per-profile queues, independent local/remote runners, remote reconnection and atomic capture, stop handling, outcome classification, warning and failure evidence, Result publication, and Raw inspection | calculation.odin, tools/remote_calculation.py, editor_calculation_ui.odin |
| Geometry and rendering | Scientific geometry, PHITS translation, CSG evaluation, CPU mesh caches, viewport interaction, output-format readers, and SDL GPU drawing | geometry.odin, csg_mesh.odin, renderer.odin |
Reading guide
Use this source map to locate implementation owners, file formats when inspecting a workspace, and the PHITS workflow when following researcher tasks.
The application is Project-neutral. It validates record syntax, identity, units, consistency, provenance, and declared policy; it must not invent scientific acceptance criteria. Research decisions are edited in research documentation, not in an application Decisions stage.