modify documents

docs/RESULTS_SCHEMA.md

@@ -187,6 +187,20 @@ component_labels = ["SF1", "SF2", "SF12", "SM1", "SM2", "SM12", "SS13", "SS23"]
 
 The final component labels should be cross-checked with the accepted Abaqus reference output variables.
 
+## Phase 1 Mandatory Outputs
+The first complete linear static solver path must write:
+- root metadata attributes: `schema_name`, `schema_version`, `solver_name`, `dof_convention`, `sign_convention`.
+- `/model/nodes/ids`
+- `/model/nodes/coordinates`
+- `/model/elements/ids`
+- `/model/elements/types`
+- `/model/elements/connectivity`
+- `/results/steps/<step>/frames/0/fieldOutputs/U`
+- `/results/steps/<step>/frames/0/fieldOutputs/RF`
+- frame attributes for `frame_id`, `step_time`, `total_time`, `increment`, `iteration`, and `converged`.
+
+Stress, strain, and section force outputs may remain optional until the MITC4 displacement/reaction benchmarks are stable.
+
 ## Frame Attributes
 Attach these attributes to each frame group:
 
@@ -248,6 +262,40 @@ Attributes:
 - `comparison_status`
 - `comparison_timestamp_utc`
 
+## CSV Reference Input Mapping
+FESA solver outputs remain HDF5-oriented, but early verification may compare HDF5 field outputs against stored Abaqus CSV artifacts under `references/`.
+
+Initial accepted displacement reference naming:
+
+```text
+references/<case_name>.inp
+references/<case_name>_displacements.csv
+```
+
+`*_displacements.csv` maps to:
+
+```text
+/results/steps/<step>/frames/<frame>/fieldOutputs/U
+```
+
+Required CSV columns:
+
+| CSV Column | HDF5 Field Component |
+|---|---|
+| `Node Label` | `entity_ids` |
+| `U-U1` | `UX` |
+| `U-U2` | `UY` |
+| `U-U3` | `UZ` |
+| `UR-UR1` | `RX` |
+| `UR-UR2` | `RY` |
+| `UR-UR3` | `RZ` |
+
+Rules:
+- CSV files are reference inputs for tests, not the primary FESA result storage format.
+- The comparator must preserve node-label matching and must not rely on row order alone.
+- The comparison report may be stored under `/referenceComparison`.
+- Reaction CSV, stress CSV, or section force CSV formats must be documented before automated use.
+
 ## Naming Rules
 - Use stable ASCII group and dataset names.
 - Use original input labels as attributes when names contain spaces or nonportable characters.
@@ -266,3 +314,4 @@ For large models:
 - Exact mandatory stress/strain/resultant output variables in Phase 1.
 - Whether result files always mirror the model or only store output entity ids.
 - Whether reference comparison results are stored in solver output files or separate reports.
+- Exact naming and column contracts for non-displacement Abaqus CSV reference files.