How alphaindiamike/rm-stack works
rm-stack is a portable, offline requirements-specification tool. An engineer authors an Item concept and HARA, develops shared System safety and architecture data, then derives and checks HW/SW requirements. The UI provides an outline, chapter editor and live summary; projects are local JSON files. The tree and excerpts support the main domain stages, mode/timing tools and derivation coverage, but do not expose every chapter’s runtime wiring, so uncertain links are omitted.
Main entry points: ui_editor.js Chapter editor · main.js App coordinator · model_base.js Document model · validator.js Document validator
Components 19
Application UI
- App coordinator
main.js - Chapter outline
ui_outline.js - Chapter editor
ui_editor.js - Live summary
ui_summary.js
Safety Work Products
- Item & HARA
disciplines/item/hara.js - System work products
disciplines/system - System breakdown
disciplines/system/ch06_breakdown.js - Timing analysis
disciplines/system/ch_timing.js
HW/SW Derivation
- Hardware chapters
disciplines/hardware - HW derivation coverage
disciplines/hardware/hw_inputs.js - Software chapters
disciplines/software - SW derivation coverage
disciplines/software/sw_inputs.js
Validation & Export
- Document validator
validator.js - Requirement grammar
grammar.js - Document export
export.js
Document Core
- Document model
model_base.js - Discipline & chapter registries
chapter_registry.js - JSON persistence
persistence.js
Other components
- Engineer
Connections 22
- Engineer → App coordinator: uses
- App coordinator → Chapter outline: renders
- App coordinator → Chapter editor: renders
- App coordinator → Live summary: renders
- App coordinator → Discipline & chapter registries: lists disciplines
- App coordinator → JSON persistence: saves and loads
- Chapter outline → Chapter editor: selects chapter
- Chapter editor → Item & HARA: edits
- Chapter editor → System work products: edits
- Chapter editor → Hardware chapters: edits
- Chapter editor → Software chapters: edits
- Item & HARA → Document model: shares document data
- System work products → Document model: shares document data
- System breakdown → Document model: updates declarations
- Timing analysis → Document model: reads transitions; writes requirements
- HW derivation coverage → Document validator: requests coverage
- SW derivation coverage → Document validator: requests coverage
- Document validator → Document model: checks document
- Chapter editor → Requirement grammar: validates requirements
- Document export → Document model: exports document data
- JSON persistence → Document model: serializes document
- Live summary → Document validator: shows integrity results