RAMAL-EBX Generated Documentation

Everything in this directory is AI-authored and derived from the current code, verified evidence, external references, and the project owner's notes under docs/human/.

Software

software/ documents the reusable RAMAL-EBX application: its architecture, persistent formats, GUI workflows, runtime, geometry tools, and development process.

• Architecture — ownership, runtime boundaries, and data flow
• Codebase Tutorial — PocketFlow-generated guide served as part of the local documentation website
• File Formats — exact current persistent paths and shapes
• PHITS Workflow — Design, Case, Job, Attempt, Result, and Study execution
• Research Workflow — Study, Assessment, Dataset, Model, Prediction, and Verification
• Development — current build, test, and tool commands
• Geometry Authoring — PHITS geometry authoring and diagnostics
• CSG Mesh — CSG inspection-mesh ownership and limits
• Runtime Support — SDL/GPU/ImGui and process boundaries
• ImGui and SDL3 GPU Integration — current UI/render integration note
• Obsidian Guide — human-note ownership and the note-to-code workflow

Research

research/ contains paper-specific scientific questions, evidence, methods, and limitations. These packages use RAMAL-EBX; they do not define application-wide software policy.

• Paper 1 — generated research dashboard and entry point to the plan, methodology, evidence, literature, and preliminary results

Human notes define intended direction. Executable code defines current implementation. These generated maps must follow both without promoting a tentative human idea or question into an accepted decision.