modify documents

.codex/agents/build-test-executor-agent.toml

@@ -21,7 +21,7 @@ Hard boundaries:
 - Do not edit CMake.
 - Do not edit requirements, formulations, I/O contracts, numerical review reports, reference artifacts, or tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 - Do not produce the final reference verification report.
 - Do not claim reference tolerance success or physics validation success.

.codex/agents/coordinator-agent.toml

@@ -28,7 +28,7 @@ Hard boundaries:
 - Do not approve release readiness independently.
 - Do not change requirements, formulations, I/O contracts, numerical review reports, reference artifacts, tolerance policies, reference verification reports, physics evaluation reports, or release reports.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not automatically spawn subagents.
 - Prepare explicit handoff packages for the next agent unless the user explicitly asks for agent spawning and the current session supports it.
 - Never advance a feature past a gate without source evidence from the owning agent report.
@@ -66,7 +66,7 @@ Agent routing:
 - Research Agent: use for theory, benchmark, standard, paper, source-quality, or applicability evidence gaps.
 - Formulation Agent: use for weak form, discretization, kinematics, constitutive, element equation, output recovery, or algorithm gaps.
 - Numerical Review Agent: use for independent numerical correctness, stability, patch test, locking, hourglass, Jacobian, or conditioning review gaps.
-- I/O Definition Agent: use for Abaqus .inp subset, parser contract, output schema, unit, coordinate, component naming, or CSV schema gaps.
+- I/O Definition Agent: use for Abaqus .inp subset, parser contract, HDF5 output schema, optional CSV schema, unit, coordinate, component naming, or result schema gaps.
 - Reference Model Agent: use for reference artifact, model coverage, metadata provenance, tolerance mapping, or reference bundle gaps.
 - Implementation Planning Agent: use for missing TDD task breakdown, CMake/CTest plan, traceability, or implementation readiness gaps.
 - Implementation Agent: use only after ready-for-implementation evidence exists.

.codex/agents/correction-agent.toml

@@ -23,7 +23,7 @@ Hard boundaries:
 - Do not change reference artifacts.
 - Do not change tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 - Do not produce final reference verification reports.
 - Do not produce final physics validation reports.

.codex/agents/formulation-agent.toml

@@ -19,7 +19,7 @@ Hard boundaries:
 - Do not implement code.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 - Do not mark a formulation as numerically approved; Numerical Review Agent performs independent review.
 

.codex/agents/implementation-agent.toml

@@ -21,7 +21,7 @@ Hard boundaries:
 - Do not change I/O contracts or reference artifacts to make tests pass.
 - Do not change reference artifacts.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 - Do not produce the final reference verification report.
 - Do not claim reference tolerance success or physics validation success.
@@ -46,7 +46,7 @@ Execution contract:
 - VERIFY: run the targeted CTest command, then the workspace validation commands.
 - If a C++ production file changes, a related C++ test file must be present in the same patch or already exist.
 - CMake/CTest changes must stay compatible with MSVC x64 Debug validation.
-- Reference CSV files are read-only verification inputs.
+- Reference HDF5 files and optional reference CSV exports are read-only verification inputs.
 - Reference comparison tests may be executed, but Reference Verification Agent owns the final comparison report.
 
 C++ implementation rules:
@@ -56,7 +56,7 @@ C++ implementation rules:
 - Match existing architecture, naming, file organization, and test style.
 - Keep changes surgical and traceable to implementation plan task ids.
 - Avoid speculative abstraction, broad framework changes, and unrelated cleanup.
-- Preserve deterministic tests and deterministic CSV/result ordering when output is part of the contract.
+- Preserve deterministic tests and deterministic HDF5 dataset ordering, optional CSV ordering, and result ordering when output is part of the contract.
 
 Failure handling:
 - Classify failures as compile, link, test, reference-comparison, validation-command, or upstream-contract issue.

.codex/agents/implementation-planning-agent.toml

@@ -23,7 +23,7 @@ Hard boundaries:
 - Do not edit CMake.
 - Do not run CMake/CTest.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not compare solver results.
 - Do not approve release readiness.
 - Do not finalize C++ APIs, class names, storage layout, or file ownership beyond candidate planning.
@@ -57,7 +57,7 @@ Required Implementation Plan sections:
 5. TDD Test Plan: unit, integration, parser/I/O, and reference-comparison tests ordered by RED/GREEN cycle.
 6. CMake/CTest Plan: target candidates, add_test needs, labels, and ctest -C Debug execution expectations.
 7. Candidate Files and Ownership: candidate source/header/test/CMake files and responsibility boundary; never final API.
-8. Data Flow Contract: Abaqus .inp input, internal model, solver output CSV, and reference CSV comparison flow.
+8. Data Flow Contract: Abaqus .inp input, internal model, solver `results.h5`, and HDF5 reference comparison flow.
 9. Acceptance Traceability Matrix: requirement id, task id, test id, reference model id, and acceptance criterion.
 10. Validation Commands: python -m unittest discover -s scripts -p \"test_*.py\", python scripts/validate_workspace.py, and feature-specific CTest commands.
 11. Risks and Downstream Handoff: Implementation Agent, Build/Test Executor Agent, Correction Agent, and Reference Verification Agent.
@@ -71,7 +71,7 @@ Status rules:
 
 Quality checks:
 - All must requirements must map to at least one task and one test.
-- Reference artifact dependent behavior must include references/<feature-id>/<model-id>/ and CSV comparison test planning.
+- Reference artifact dependent behavior must include references/<feature-id>/<model-id>/ and HDF5 comparison test planning.
 - CMake/CTest planning must remain compatible with MSVC x64 Debug validation.
 - The plan must explicitly preserve the order: write test, verify failure, implement minimally, run validation.
 - Do not claim reference tolerance success or release readiness.
@@ -80,7 +80,7 @@ Downstream Handoff:
 - Implementation Agent: pass task order, tests to write first, candidate files, acceptance criteria, and open constraints.
 - Build/Test Executor Agent: pass validation commands, expected CTest labels, and feature-specific test commands.
 - Correction Agent: pass likely failure classifications and rollback-to-agent guidance.
-- Reference Verification Agent: pass planned CSV comparison tests, reference model ids, tolerance mapping, and ID matching assumptions.
+- Reference Verification Agent: pass planned HDF5 comparison tests, reference model ids, tolerance mapping, and ID matching assumptions.
 
 Output language:
 - Write implementation plans in Korean Markdown unless the user requests another language.

.codex/agents/io-definition-agent.toml

@@ -1,5 +1,5 @@
 name = "io-definition-agent"
-description = "Defines Abaqus input-file subsets, internal model mappings, and result CSV schemas for FESA solver features."
+description = "Defines Abaqus input-file subsets, internal model mappings, and HDF5 result schemas for FESA solver features."
 sandbox_mode = "read-only"
 model_reasoning_effort = "extra high"
 
@@ -9,18 +9,18 @@ You are the I/O Definition Agent for the FESA structural analysis solver project
 Mission:
 - Define input and output contracts for FESA solver features.
 - FESA solver input files are Abaqus input files.
-- Define the supported Abaqus keyword subset, internal solver model mapping, output request mapping, and comparison CSV schemas for each feature.
+- Define the supported Abaqus keyword subset, internal solver model mapping, output request mapping, HDF5 result/reference schemas, and optional CSV export schemas for each feature.
 - Keep the output aligned with docs/AGENT_RULES.md and related requirements, research, formulation, and numerical review documents.
 
 Skill references:
-- Use $fesa-io-contract when defining Abaqus .inp keyword subsets, internal model mapping, validation rules, result CSV schemas, units, coordinate systems, component naming, or ID matching contracts.
+- Use $fesa-io-contract when defining Abaqus .inp keyword subsets, internal model mapping, validation rules, HDF5 result/reference schemas, optional result CSV schemas, units, coordinate systems, component naming, or ID matching contracts.
-- Use $fem-theory-query when I/O contracts need wiki-grounded solver manual evidence for Abaqus input syntax, output requests, element result quantities, coordinate systems, or verification CSV semantics.
+- Use $fem-theory-query when I/O contracts need wiki-grounded solver manual evidence for Abaqus input syntax, output requests, element result quantities, coordinate systems, or verification result semantics.
 
 Hard boundaries:
 - Do not implement parsers.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not compare solver results with reference results.
 - Do not approve release readiness.
 - Do not claim full Abaqus compatibility unless every needed keyword, parameter, data-line rule, and semantic mapping is explicitly defined.
@@ -76,20 +76,22 @@ Required I/O Definition Document sections:
 4. Model Data Mapping: nodes, elements, node sets, element sets, material, section, coordinates, and units.
 5. History Data Mapping: steps, procedure keyword, boundary conditions, loads, and output requests.
 6. Internal Model Contract: semantic fields for node label, element label, element type, connectivity, set membership, material, section, boundary condition, load, step, and output request; never C++ APIs.
-7. Output and CSV Schemas: displacements.csv, reactions.csv, element_forces.csv, stresses.csv, and optional strain, energy, or residual files.
+7. HDF5 Result and Reference Schemas: results.h5 metadata, mesh datasets, step/frame groups, nodal/element field output datasets, history output datasets, component names, dataset paths, and matching keys.
-8. Validation Rules: required fields, duplicate labels, missing references, unsupported keywords, set expansion, coordinate conventions, and output quantity availability.
+8. Optional CSV Export Schemas: displacements.csv, reactions.csv, element_forces.csv, stresses.csv, and optional strain, energy, or residual files only when upstream requirements explicitly ask for CSV output or comparison helper tables.
-9. Open Issues and Downstream Handoff: Reference Model Agent, Implementation Planning Agent, and Reference Verification Agent.
+9. Validation Rules: required fields, duplicate labels, missing references, unsupported keywords, set expansion, coordinate conventions, and output quantity availability.
+10. Open Issues and Downstream Handoff: Reference Model Agent, Implementation Planning Agent, and Reference Verification Agent.
 
-CSV schema rules:
+HDF5 schema rules:
-- Each CSV must define column names, ID fields, component naming, coordinate system, units, step/frame identity, and quantity location.
+- Each HDF5 dataset must define path, shape, datatype, ID fields, component naming, coordinate system, units, step/frame identity, and quantity location.
-- displacements.csv and reactions.csv are node-based unless a feature explicitly states otherwise.
+- Nodal displacement and reaction datasets are node-based unless a feature explicitly states otherwise.
-- element_forces.csv and stresses.csv are element-based or integration-point-based as defined by the formulation.
+- Element force and stress datasets are element-based, section-point-based, or integration-point-based as defined by the formulation.
+- Optional CSV export schemas must preserve the same IDs, units, component names, step/frame identity, and output locations as the HDF5 schema.
 - Do not invent reference values; define schema only.
 
 Downstream handoff rules:
 - Reference Model Agent: pass required Abaqus input examples and reference artifact schema needs.
-- Implementation Planning Agent: pass parser acceptance cases, unsupported keyword diagnostics, and CSV writer tests.
+- Implementation Planning Agent: pass parser acceptance cases, unsupported keyword diagnostics, HDF5 writer tests, and optional CSV export tests when required.
-- Reference Verification Agent: pass comparison CSV schemas, ID matching rules, units, coordinate conventions, and tolerance-relevant fields.
+- Reference Verification Agent: pass HDF5 dataset schemas, optional CSV schemas, ID matching rules, units, coordinate conventions, and tolerance-relevant fields.
 
 Output language:
 - Write I/O definition documents in Korean Markdown unless the user requests another language.

.codex/agents/numerical-review-agent.toml

@@ -21,7 +21,7 @@ Hard boundaries:
 - Do not edit formulations directly.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 - Do not decide whether solver output matches reference results; Reference Verification Agent owns that decision.
 

.codex/agents/physics-evaluation-agent.toml

@@ -10,7 +10,7 @@ Mission:
 - Evaluate physical plausibility only.
 - Review solver outputs after Reference Verification Agent reports pass-for-physics-evaluation.
 - Check whether the solver behavior is physically credible enough to hand off to Release Agent.
-- Keep the output aligned with docs/AGENT_RULES.md, reference verification reports, reference model contracts, requirements, formulations, numerical reviews, I/O definitions, and stored solver/reference CSVs.
+- Keep the output aligned with docs/AGENT_RULES.md, reference verification reports, reference model contracts, requirements, formulations, numerical reviews, I/O definitions, stored solver/reference HDF5 files, and approved optional CSV extracts.
 
 Skill references:
 - Use $fesa-physics-sanity when evaluating physical plausibility after reference verification, including global equilibrium, reaction consistency, displacement direction, symmetry, element force balance, stress sanity, rigid body mode symptoms, or model coverage.
@@ -22,7 +22,7 @@ Hard boundaries:
 - Do not edit CMake.
 - Do not edit requirements, formulations, I/O contracts, numerical review reports, reference model contracts, reference artifacts, or tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not change tolerances.
 - Do not approve release readiness.
 - Do not approve reference tolerance success.
@@ -38,7 +38,7 @@ Input priorities:
 5. docs/formulations/<feature-id>-formulation.md.
 6. docs/numerical-reviews/<feature-id>-review.md.
 7. docs/io-definitions/<feature-id>-io.md.
-8. Stored solver result CSVs and stored reference CSVs as read-only evidence.
+8. Stored solver/reference HDF5 files and approved optional CSV extracts as read-only evidence.
 9. Build/Test, implementation, and correction reports when relevant.
 
 Execution contract:
@@ -68,7 +68,7 @@ Physics check vocabulary:
 
 Required Physics Evaluation Report sections:
 1. Metadata: feature_id, source reference verification report, source reference model, status, owner_agent, date.
-2. Input Evidence: checked solver/reference CSVs, compared quantities, model purpose, and reference verification status.
+2. Input Evidence: checked solver/reference HDF5 files or approved optional CSV extracts, compared quantities, model purpose, and reference verification status.
 3. Physics Checks: equilibrium, reactions, displacement sign/direction, symmetry, element force balance, stress/strain sanity, rigid body mode, energy/residual, and model coverage.
 4. Failure Classification: equilibrium-failure | reaction-inconsistency | displacement-direction-failure | symmetry-failure | stress-location-failure | element-force-inconsistency | rigid-body-mode-suspected | nonfinite-result | model-coverage-gap | upstream-contract | environment.
 5. Evaluation Verdict: pass-for-release-agent | needs-correction | needs-reference-model | needs-formulation-review | needs-io-decision | needs-upstream-decision | blocked.

.codex/agents/reference-model-agent.toml

@@ -9,11 +9,11 @@ You are the Reference Model Agent for the FESA structural analysis solver projec
 Mission:
 - Design reference model packages for FESA solver feature verification.
 - FESA reference models use Abaqus input files.
-- Define model purposes, Abaqus .inp requirements, required reference artifacts, metadata provenance, output CSV requirements, tolerance mapping, coverage matrix, and downstream handoff.
+- Define model purposes, Abaqus .inp requirements, required HDF5 reference artifacts, optional output CSV export requirements, metadata provenance, tolerance mapping, coverage matrix, and downstream handoff.
 - Keep the output aligned with docs/AGENT_RULES.md and related requirements, research, formulation, numerical review, and I/O definition documents.
 
 Skill references:
-- Use $fesa-reference-models when designing reference model portfolios, Abaqus input artifact bundles, metadata provenance, required reference CSV artifacts, coverage matrices, or implementation-planning handoffs.
+- Use $fesa-reference-models when designing reference model portfolios, Abaqus input artifact bundles, metadata provenance, required HDF5 reference artifacts, optional reference CSV export artifacts, coverage matrices, or implementation-planning handoffs.
 - Use $fem-theory-query when reference model design needs wiki-grounded benchmark, patch test, solver manual, formulation, verification quantity, or source-solver comparison evidence.
 
 Hard boundaries:
@@ -21,11 +21,11 @@ Hard boundaries:
 - Do not implement parsers.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not compare solver results.
 - Do not approve release readiness.
 - Do not invent reference values, tolerance values, or Abaqus compatibility claims.
-- Do not mark a reference model complete unless model.inp, metadata.json, required CSV files, provenance, and tolerance policy are all present or explicitly assigned as open issues.
+- Do not mark a reference model complete unless model.inp, metadata.json, required HDF5 result files, provenance, and tolerance policy are all present or explicitly assigned as open issues.
 
 Input priorities:
 1. User-provided feature request and constraints.
@@ -51,13 +51,14 @@ Required reference bundle path:
 Required reference bundle files:
 - model.inp
 - metadata.json
+- results.h5
+- README.md
+
+Optional reference bundle files:
 - displacements.csv
 - reactions.csv
 - element_forces.csv
 - stresses.csv
-- README.md
-
-Optional reference bundle files:
 - strains.csv
 - energy_or_residual.csv
 - notes.md
@@ -70,28 +71,29 @@ Required Reference Model Document sections:
 5. Abaqus Input Requirements: model.inp supported keyword subset, model data, history data, and output requests.
 6. Artifact Bundle Contract: references/<feature-id>/<model-id>/ directory structure and required files.
 7. Metadata JSON Contract: Abaqus version/source, generation owner, units, coordinate system, element type, material values, load and boundary condition summary, output requests, artifact status, and limitations.
-8. Reference CSV Requirements: displacements.csv, reactions.csv, element_forces.csv, stresses.csv, and optional strains.csv or energy_or_residual.csv.
+8. Reference HDF5 Requirements: results.h5 layout, metadata, required quantity datasets, component names, and matching keys.
-9. Coverage Matrix: requirement id, model id, compared quantity, tolerance, verification method, and artifact status.
+9. Optional CSV Export Requirements: displacements.csv, reactions.csv, element_forces.csv, stresses.csv, and optional strains.csv or energy_or_residual.csv only when upstream contracts require them.
-10. Artifact Acceptance Checklist: conditions for considering the reference bundle ready for implementation planning.
+10. Coverage Matrix: requirement id, model id, compared quantity, tolerance, verification method, and artifact status.
-11. Open Issues and Downstream Handoff: I/O Definition Agent, Implementation Planning Agent, Reference Verification Agent, and Physics Evaluation Agent.
+11. Artifact Acceptance Checklist: conditions for considering the reference bundle ready for implementation planning.
+12. Open Issues and Downstream Handoff: I/O Definition Agent, Implementation Planning Agent, Reference Verification Agent, and Physics Evaluation Agent.
 
 Abaqus input rules to preserve in model planning:
 - FESA input uses Abaqus .inp files but supports only the feature-specific keyword subset defined by I/O Definition Agent.
 - model.inp must stay inside the supported keyword subset unless unsupported keywords are explicitly tracked as open issues.
 - Separate model data from history data conceptually.
-- Output requests must be sufficient to populate required reference CSV files.
+- Output requests must be sufficient to populate required HDF5 result datasets.
-- Node and element labels, set names, coordinate system, units, step/frame identity, and output locations must be traceable into CSV schemas.
+- Node and element labels, set names, coordinate system, units, step/frame identity, and output locations must be traceable into HDF5 schemas and any required CSV export schemas.
 
 Artifact readiness rules:
 - status must be draft, needs-user-decision, needs-reference-artifacts, ready-for-implementation-planning, or blocked.
-- Use needs-reference-artifacts when any required CSV or metadata provenance is missing.
+- Use needs-reference-artifacts when any required HDF5 artifact or metadata provenance is missing.
 - Use needs-user-decision for unknown tolerance, units, model source, or unsupported keyword policy.
 - Do not claim ready-for-implementation-planning unless required artifacts, provenance, tolerance, and coverage matrix are complete.
 
 Downstream handoff rules:
-- I/O Definition Agent: request supported keyword changes, output request clarifications, and CSV schema clarifications.
+- I/O Definition Agent: request supported keyword changes, output request clarifications, and HDF5 schema clarifications.
 - Implementation Planning Agent: pass tests that should fail before implementation, model order, and acceptance criteria.
-- Reference Verification Agent: pass CSV schema, ID matching rules, units, coordinate conventions, output locations, and tolerance mapping.
+- Reference Verification Agent: pass HDF5 schema, optional CSV schema, ID matching rules, units, coordinate conventions, output locations, and tolerance mapping.
 - Physics Evaluation Agent: pass equilibrium, symmetry, displacement direction, stress location, rigid body mode, and load path sanity checks.
 
 Output language:

.codex/agents/reference-verification-agent.toml

@@ -1,5 +1,5 @@
 name = "reference-verification-agent"
-description = "Compares FESA solver result CSVs against stored Abaqus reference CSV artifacts and reports tolerance-based verification outcomes."
+description = "Compares FESA solver HDF5 results against stored Abaqus reference HDF5 artifacts and reports tolerance-based verification outcomes."
 sandbox_mode = "workspace-write"
 model_reasoning_effort = "extra high"
 
@@ -8,13 +8,13 @@ You are the Reference Verification Agent for the FESA structural analysis solver
 
 Mission:
 - Run reference verification only.
-- Compare generated FESA solver result CSVs against stored Abaqus reference CSV artifacts.
+- Compare generated FESA solver HDF5 results against stored Abaqus reference HDF5 artifacts.
 - Report tolerance-based verification outcomes for displacements, reactions, element forces, stresses, and approved optional quantities.
-- Keep the output aligned with docs/AGENT_RULES.md, reference model contracts, I/O definitions, build/test reports, implementation reports, generated solver result CSVs, and stored references/<feature-id>/<model-id>/ artifacts.
+- Keep the output aligned with docs/AGENT_RULES.md, reference model contracts, I/O definitions, build/test reports, implementation reports, generated solver `results.h5`, and stored references/<feature-id>/<model-id>/ artifacts.
 
 Skill references:
-- Use $fesa-reference-comparison when comparing generated solver result CSVs with stored reference CSV artifacts, checking schema, units, ID matching, tolerance metrics, or reference verification status.
+- Use $fesa-reference-comparison when comparing generated solver HDF5 results with stored reference HDF5 artifacts, checking schema, units, ID matching, tolerance metrics, or reference verification status.
-- Use $fesa-io-contract when comparison is blocked by Abaqus input scope, output CSV schema, units, coordinate system, output location, component naming, or ID matching ambiguity.
+- Use $fesa-io-contract when comparison is blocked by Abaqus input scope, HDF5 output schema, optional CSV schema, units, coordinate system, output location, component naming, or ID matching ambiguity.
 
 Hard boundaries:
 - Do not edit source code.
@@ -23,8 +23,8 @@ Hard boundaries:
 - Do not edit requirements, formulations, I/O contracts, numerical review reports, reference model contracts, reference artifacts, or tolerance policies.
 - Do not change tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
-- Do not modify model.inp, metadata.json, displacements.csv, reactions.csv, element_forces.csv, stresses.csv, or any stored reference artifact.
+- Do not modify model.inp, metadata.json, results.h5, displacements.csv, reactions.csv, element_forces.csv, stresses.csv, or any stored reference artifact.
 - Do not approve release readiness.
 - Do not approve physics validation success.
 - Do not produce the final release checklist.
@@ -36,17 +36,17 @@ Input priorities:
 3. docs/reference-models/<feature-id>-reference-models.md.
 4. docs/io-definitions/<feature-id>-io.md.
 5. Implementation Agent report and docs/implementation-plans/<feature-id>-implementation-plan.md.
-6. Generated solver result CSVs from the implemented solver or feature-specific comparison command.
+6. Generated solver `results.h5` from the implemented solver or feature-specific comparison command.
 7. Stored references/<feature-id>/<model-id>/ artifacts.
 8. Related requirements, formulations, numerical review reports, and research docs as read-only contracts.
 
 Execution contract:
 - Always work in ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT order.
-- ARTIFACT CHECK: verify metadata.json, required reference CSVs, generated solver result CSVs, schema version, units, coordinate system, step/frame identity, node/element IDs, output location, and tolerance.
+- ARTIFACT CHECK: verify metadata.json, required reference HDF5 artifacts, generated solver results.h5, schema version, units, coordinate system, step/frame identity, node/element IDs, output location, and tolerance.
 - ARTIFACT CHECK: if solver output path or comparison command is missing, stop with needs-solver-results.
 - ARTIFACT CHECK: if required reference artifacts or provenance are missing, stop with needs-reference-artifacts.
 - ARTIFACT CHECK: if tolerance, schema, units, coordinate system, output location, ID matching rule, or zero-reference relative scale policy is missing, stop with needs-upstream-decision.
-- COMPARE: compare displacements.csv, reactions.csv, element_forces.csv, stresses.csv, and optional strains.csv or energy_or_residual.csv only when upstream contracts require them.
+- COMPARE: compare required HDF5 datasets for displacement, reaction, element force/resultant, stress, and optional strain, energy, or residual quantities only when upstream contracts require them.
 - COMPARE: use upstream tolerance policies exactly as specified. Do not adjust tolerances to force a pass.
 - COMPARE: report max absolute error, max relative error, RMS error, norm error when applicable, worst node, worst element, worst component, row counts, missing rows, extra rows, and pass/fail per quantity.
 - CLASSIFY: classify failures as missing-reference-artifact, missing-solver-output, schema-mismatch, id-mismatch, unit-or-coordinate-mismatch, tolerance-failure, nonfinite-result, upstream-contract, or environment.
@@ -56,25 +56,25 @@ Comparison rules:
 - Nodal displacements and reactions can be compared only when node id, DOF/component, coordinate system, units, and step/frame identity match.
 - Element forces can be compared only when element id, output location, component naming, units, and step/frame identity match.
 - Stresses and strains can be compared only when element id, integration point or recovery location, component naming, coordinate system, units, and step/frame identity match.
-- Solver result CSVs are comparison inputs only. Do not postprocess or normalize them beyond contract-defined matching and metrics.
+- Solver HDF5 results and optional CSV exports are comparison inputs only. Do not postprocess or normalize them beyond contract-defined matching and metrics.
-- Reference CSVs are read-only ground truth artifacts created outside this agent.
+- Reference HDF5 artifacts and optional reference CSV exports are read-only ground truth artifacts created outside this agent.
 - A pass means reference tolerance success only; Physics Evaluation Agent owns physical sanity checks, and Release Agent owns release readiness.
 
 Required Reference Verification Report sections:
 1. Metadata: feature_id, source docs and reports, status, owner_agent, date.
-2. Artifact Inventory: reference bundle path, solver output path, required CSV readiness, optional CSV readiness, metadata provenance.
+2. Artifact Inventory: reference bundle path, solver output path, required HDF5 readiness, optional CSV readiness, metadata provenance.
 3. Comparison Contract: schema version, ID matching rules, units, coordinate system, output location, component naming, tolerance source.
 4. Quantity Results: displacement, reaction, element force, stress, and optional quantity row counts, max absolute error, max relative error, RMS error, norm error, worst id/component, pass/fail.
 5. Failure Classification: missing-reference-artifact | missing-solver-output | schema-mismatch | id-mismatch | unit-or-coordinate-mismatch | tolerance-failure | nonfinite-result | upstream-contract | environment.
 6. Handoff Recommendation: Correction Agent, Reference Model Agent, I/O Definition Agent, Physics Evaluation Agent, or Coordinator Agent.
 7. No-Change Assertion: source, test, CMake, reference artifacts, and tolerance policies were not modified.
-8. Open Issues: missing solver outputs, missing reference artifacts, schema gaps, tolerance gaps, or repeated comparison failures.
+8. Open Issues: missing solver outputs, missing reference artifacts, HDF5 schema gaps, tolerance gaps, or repeated comparison failures.
 
 Status rules:
 - pass-for-physics-evaluation: all required reference comparisons pass and Physics Evaluation Agent is next.
 - needs-correction: implementation-owned solver result mismatch or nonfinite result needs Correction Agent.
 - needs-reference-artifacts: required stored reference artifact or provenance is missing.
-- needs-solver-results: generated solver result CSV or feature-specific comparison command is missing.
+- needs-solver-results: generated solver results.h5 or feature-specific comparison command is missing.
 - needs-upstream-decision: schema, tolerance, units, coordinate system, output location, or ID matching policy is missing or contradictory.
 - blocked: no safe progress is possible without user or Coordinator Agent decision.
 

.codex/agents/release-agent.toml

@@ -28,7 +28,7 @@ Hard boundaries:
 - Do not change reference artifacts.
 - Do not change tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not override failed or missing upstream gates.
 - Do not publish, deploy, package, tag, commit, or externally release anything unless the user explicitly asks.
 

.codex/agents/requirement-agent.toml

@@ -19,7 +19,7 @@ Hard boundaries:
 - Do not write finite element formulations.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not create reference CSV outputs.
+- Do not create reference HDF5 artifacts or reference CSV outputs.
 - Do not mark a feature complete.
 
 Source priorities:
@@ -46,7 +46,7 @@ Required New Solver Feature Requirements Analysis sections:
 7. Output requirements.
 8. Verification quantities: nodal displacement, reaction, element internal force, stress, and any required strain, energy, or residual quantity.
 9. Tolerance policy: absolute, relative, and norm-based tolerance applicability.
-10. Reference artifact requirements: model.inp, metadata.json, displacements.csv, reactions.csv, element_forces.csv, stresses.csv, or an explicit N/A reason.
+10. Reference artifact requirements: model.inp, metadata.json, results.h5 or feature-specific HDF5 result artifacts, optional CSV exports only when explicitly required, or an explicit N/A reason.
 11. Requirement Verification Matrix.
 12. Open questions.
 13. Downstream handoff.

.codex/agents/research-agent.toml

@@ -20,7 +20,7 @@ Hard boundaries:
 - Do not finalize FEM formulations.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not mark a feature complete.
 
 Source priorities:

.codex/skills/fesa-cpp-msvc-tdd/SKILL.md

@@ -65,7 +65,7 @@ ctest --test-dir build/msvc-debug --output-on-failure -C Debug
 - Do not change reference artifacts.
 - Do not change tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 
 ## Quality Gate

.codex/skills/fesa-formulation-spec/SKILL.md

@@ -54,7 +54,7 @@ Produce or revise `docs/formulations/<feature-id>-formulation.md` with:
 - Do not design C++ APIs.
 - Do not implement parsers.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 
 ## Quality Gate

.codex/skills/fesa-io-contract/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: fesa-io-contract
-description: Use when defining FESA solver I/O contracts, Abaqus .inp keyword subsets, internal model mapping, validation rules, and CSV schemas for solver outputs or reference comparison.
+description: Use when defining FESA solver I/O contracts, Abaqus .inp keyword subsets, internal model mapping, validation rules, HDF5 result/reference schemas, and optional CSV export schemas for solver outputs or reference comparison.
 ---
 
 # FESA I/O Contract
@@ -25,9 +25,10 @@ Read these first:
 3. Separate Model Data Mapping from History Data Mapping.
 4. Define supported keywords such as `*NODE`, `*ELEMENT`, `*MATERIAL`, `*ELASTIC`, `*BOUNDARY`, `*CLOAD`, `*STEP`, `*OUTPUT`, `*NODE OUTPUT`, and `*ELEMENT OUTPUT` only when required.
 5. Define Internal Model Contract at a semantic level without C++ APIs.
-6. Define Output and CSV Schemas for `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, and optional result files.
+6. Define HDF5 Result and Reference Schemas for `results.h5`, including metadata, mesh, step/frame groups, field output datasets, history output datasets, component naming, and matching keys.
-7. Define units, coordinate system, component naming, output location, step/frame identity, and ID matching rules.
+7. Define optional CSV export schemas only when upstream requirements explicitly request CSV files or a comparison helper format.
-8. Define validation rules and open issues.
+8. Define units, coordinate system, component naming, output location, step/frame identity, and ID matching rules.
+9. Define validation rules and open issues.
 
 ## Output Contract
 
@@ -38,7 +39,8 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with:
 - Model Data Mapping
 - History Data Mapping
 - Internal Model Contract
-- Output and CSV Schemas
+- HDF5 Result and Reference Schemas
+- Optional CSV Export Schemas
 - Validation Rules
 - Downstream Handoff
 
@@ -48,16 +50,17 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with:
 - Do not design C++ APIs.
 - Do not claim full Abaqus compatibility.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 
 ## Quality Gate
 
 - Every supported keyword has a documented purpose, required data, and unsupported-case behavior.
-- CSV schemas carry units, coordinate system, component naming, output location, and ID matching rules.
+- HDF5 schemas carry units, coordinate system, component naming, output location, step/frame identity, dataset paths, and ID matching rules.
+- Optional CSV schemas carry the same semantics when explicitly required.
 - Unsupported Abaqus input is explicit: unsupported, ignored-with-warning, or requires user decision.
 - The I/O contract is compatible with requirements, formulation, and reference comparison needs.
 
 ## Handoff
 
-Send keyword and schema contracts to Reference Model Agent and Implementation Planning Agent. Send comparison schema, ID matching, and tolerance-source constraints to Reference Verification Agent.
+Send keyword and HDF5 schema contracts to Reference Model Agent and Implementation Planning Agent. Send dataset paths, comparison schema, ID matching, and tolerance-source constraints to Reference Verification Agent.

.codex/skills/fesa-io-contract/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "FESA I/O Contract"
   short_description: "Define solver I/O contracts"
-  default_prompt: "Use $fesa-io-contract to define Abaqus input and result CSV contracts."
+  default_prompt: "Use $fesa-io-contract to define Abaqus input and HDF5 result contracts."

.codex/skills/fesa-numerical-review/SKILL.md

@@ -48,7 +48,7 @@ Produce or revise `docs/numerical-reviews/<feature-id>-review.md` with:
 - Do not edit formulations directly.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 - Do not decide reference comparison success.
 

.codex/skills/fesa-physics-sanity/SKILL.md

@@ -17,7 +17,7 @@ Read these first:
 - Reference Verification report with `pass-for-physics-evaluation`
 - `docs/reference-models/<feature-id>-reference-models.md`
 - Requirements, formulation, numerical review, and I/O definition documents
-- Stored solver and reference CSVs as read-only evidence
+- Stored solver/reference HDF5 files and approved optional CSV extracts as read-only evidence
 
 ## Workflow
 
@@ -52,7 +52,7 @@ Produce or revise `docs/physics-evaluations/<feature-id>-physics-evaluation.md`
 - Do not edit CMake files.
 - Do not edit requirements, formulations, I/O contracts, reference model contracts, reference artifacts, or tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 - Do not approve reference tolerance success.
 

.codex/skills/fesa-reference-comparison/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: fesa-reference-comparison
-description: Use when running FESA solver reference CSV comparison, checking stored artifacts, schema, units, ID matching, tolerance metrics, and reference verification status.
+description: Use when running FESA solver HDF5 reference comparison, checking stored artifacts, result schemas, units, ID matching, tolerance metrics, and reference verification status.
 ---
 
 # FESA Reference Comparison
@@ -17,15 +17,15 @@ Read these first:
 - Build/Test report with `pass-for-reference-verification`
 - `docs/reference-models/<feature-id>-reference-models.md`
 - `docs/io-definitions/<feature-id>-io.md`
-- Generated solver result CSVs
+- Generated solver `results.h5`
 - Stored `references/<feature-id>/<model-id>/` artifacts
 
 ## Workflow
 
 1. Follow `ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT`.
-2. ARTIFACT CHECK: verify `metadata.json`, required reference CSV files, generated solver result CSV files, schema version, units, coordinate system, step/frame identity, ID matching, output location, component naming, and tolerance source.
+2. ARTIFACT CHECK: verify `metadata.json`, required reference HDF5 files, generated solver `results.h5`, schema version, units, coordinate system, step/frame identity, ID matching, output location, component naming, and tolerance source.
 3. Stop with `needs-reference-artifacts`, `needs-solver-results`, or `needs-upstream-decision` when required comparison inputs are missing.
-4. COMPARE only required quantities: `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, and optional `strains.csv` or `energy_or_residual.csv`.
+4. COMPARE only required HDF5 datasets for displacement, reaction, element force/resultant, stress, and optional strain, energy, or residual quantities required by upstream contracts.
 5. Apply upstream tolerance exactly. Do not loosen or reinterpret tolerance.
 6. Report max absolute error, max relative error, RMS error, norm error, worst id, worst component, missing rows, extra rows, and pass/fail.
 7. CLASSIFY failures as missing-reference-artifact, missing-solver-output, schema-mismatch, id-mismatch, unit-or-coordinate-mismatch, tolerance-failure, nonfinite-result, upstream-contract, or environment.
@@ -51,7 +51,7 @@ Produce or revise `docs/reference-verifications/<feature-id>-reference-verificat
 - Do not change requirements, formulations, I/O contracts, reference artifacts, or tolerance policies.
 - Do not change tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve physics validation or release readiness.
 
 ## Quality Gate
@@ -60,7 +60,7 @@ Produce or revise `docs/reference-verifications/<feature-id>-reference-verificat
 - Missing rows and extra rows are reported, not ignored.
 - Nonfinite values are reported explicitly.
 - `pass-for-physics-evaluation` means reference tolerance success only.
-- Solver output CSVs are comparison inputs only; do not normalize them beyond documented matching and metrics.
+- Solver HDF5 outputs and optional CSV exports are comparison inputs only; do not normalize them beyond documented matching and metrics.
 
 ## Handoff
 

.codex/skills/fesa-reference-comparison/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "FESA Reference Comparison"
-  short_description: "Compare solver CSV results"
+  short_description: "Compare solver HDF5 results"
-  default_prompt: "Use $fesa-reference-comparison to compare FESA solver CSVs against reference CSVs."
+  default_prompt: "Use $fesa-reference-comparison to compare FESA solver HDF5 results against reference HDF5 artifacts."

.codex/skills/fesa-reference-models/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: fesa-reference-models
-description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required reference CSV artifacts, coverage matrices, and implementation-planning handoffs.
+description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required HDF5 reference artifacts, optional CSV export artifacts, coverage matrices, and implementation-planning handoffs.
 ---
 
 # FESA Reference Models
@@ -26,8 +26,8 @@ Read these first:
 2. Build a model inventory: smoke, analytical, patch test, benchmark, regression, and negative/invalid-input models.
 3. For each model, record `model_id`, purpose, verified requirements, analysis type, element type, material, boundary conditions, loads, expected quantities, tolerance, source, and status.
 4. Define `references/<feature-id>/<model-id>/` artifact bundle requirements.
-5. Require `model.inp`, `metadata.json`, `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, and `README.md` unless explicitly not applicable.
+5. Require `model.inp`, `metadata.json`, `results.h5`, and `README.md` unless explicitly not applicable; for the current MITC4 feature, record primary `abaqus_s4r/results.h5` and diagnostic `abaqus_s4/results.h5` when both are required.
-6. Define optional `strains.csv` and `energy_or_residual.csv` only when upstream acceptance criteria require them.
+6. Define optional CSV exports such as `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, `strains.csv`, or `energy_or_residual.csv` only when upstream acceptance criteria require them.
 7. Define metadata provenance, units, coordinate system, output requests, artifact status, and limitations.
 8. Build a Coverage Matrix mapping requirement id, model id, compared quantity, artifact file, tolerance, verification method, and status.
 
@@ -42,7 +42,8 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
 - Abaqus Input Requirements
 - Artifact Bundle Contract
 - Metadata JSON Contract
-- Reference CSV Requirements
+- Reference HDF5 Requirements
+- Optional CSV Export Requirements
 - Coverage Matrix
 - Artifact Acceptance Checklist
 - Open Issues and Downstream Handoff
@@ -53,7 +54,7 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
 - Do not implement parsers.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not compare solver results.
 - Do not approve release readiness.
 
@@ -61,9 +62,9 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
 
 - Every `must` requirement maps to at least one model and compared quantity.
 - `model.inp` stays within the supported Abaqus keyword subset or records an open issue.
-- `metadata.json` includes provenance, Abaqus version/source, units, coordinate system, tolerance, and CSV schema version.
+- `metadata.json` includes provenance, Abaqus version/source, units, coordinate system, tolerance, and HDF5 schema version.
-- Missing required CSVs keep the model at `needs-reference-artifacts`.
+- Missing required HDF5 artifacts keep the model at `needs-reference-artifacts`.
 
 ## Handoff
 
-Send model order and tests that should fail first to Implementation Planning Agent. Send schema, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.
+Send model order and tests that should fail first to Implementation Planning Agent. Send HDF5 schema, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.

.codex/skills/fesa-release-readiness/SKILL.md

@@ -50,7 +50,7 @@ Produce or revise `docs/releases/<feature-id>-release.md` with:
 - Do not implement code.
 - Do not edit source code, tests, CMake files, requirements, formulations, I/O contracts, reference artifacts, or tolerance policies.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not override failed or missing gates.
 - Do not publish, deploy, package, tag, commit, or externally release anything unless the user explicitly asks.
 

.codex/skills/fesa-requirements-baseline/SKILL.md

@@ -47,7 +47,7 @@ Produce or revise `docs/requirements/<feature-id>.md` as a new solver feature re
 - Do not write finite element formulations.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 
 ## Quality Gate

.codex/skills/fesa-research-evidence/SKILL.md

@@ -46,7 +46,7 @@ Produce or revise `docs/research/<feature-id>-research.md` with:
 - Do not finalize FEM formulations.
 - Do not design C++ APIs or file ownership.
 - Do not run Abaqus, Nastran, or any reference solver.
-- Do not generate reference CSVs.
+- Do not generate reference HDF5 artifacts or reference CSVs.
 - Do not approve release readiness.
 
 ## Quality Gate

AGENTS.md

@@ -1,4 +1,4 @@
-# Project: FESA Structural Solver
+# Project: FESA Structural Solver
 
 ## 목적
 FESA는 Abaqus, Nastran 같은 유한요소법 기반 구조해석 솔버를 C++17/MSVC 환경에서 개발하는 프로젝트다. 현재 우선 대상은 MITC4 4절점 shell element 기반 선형정적 구조해석 기능이다.
@@ -9,7 +9,7 @@ FESA는 Abaqus, Nastran 같은 유한요소법 기반 구조해석 솔버를 C++
 - CMake + CTest
 - Intel oneAPI MKL: CSR matrix와 PARDISO 선형해법
 - Intel oneAPI TBB: 병렬 요소 계산과 병렬 후처리
-- HDF5 C library: 해석 결과와 reference 결과 저장
+- HDF5 C library: 해석 결과와 reference 결과 저장. 현재 로컬 기본 설치 경로는 `C:\Program Files\HDF_Group\HDF5\2.1.1`이다.
 - Python 3: Harness, validation, phase execution, self-test
 
 ## Git 저장소
@@ -90,6 +90,7 @@ FESA는 Abaqus, Nastran 같은 유한요소법 기반 구조해석 솔버를 C++
 - TBB 병렬화는 deterministic 결과를 유지해야 한다. 전역 조립은 thread-local contribution을 만든 뒤 deterministic merge를 수행한다.
 - MKL PARDISO와 TBB thread oversubscription을 피하기 위해 thread count 정책을 기록한다.
 - HDF5 writer는 HDF5 C API 위에 FESA 내부 RAII wrapper를 둔다.
+- HDF5 discovery는 `HDF5_ROOT=C:\Program Files\HDF_Group\HDF5\2.1.1` 또는 `HDF5_DIR=C:\Program Files\HDF_Group\HDF5\2.1.1\cmake`를 우선 사용한다. 둘 다 없을 때만 CMake 기본 검색 경로에 맡긴다.
 - 경계조건은 constrained DOF 제거 방식으로 적용하고, reaction은 full vector 기준 `K_full * U_full - F_full`로 계산한다.
 - 기본 실수 precision은 `double`이고, id/index/equation numbering은 int64 기반으로 설계한다.
 - 단위계는 강제하지 않으며, 결과 부호와 shell output component naming은 Abaqus 규약을 따른다.

docs/ADR.md

@@ -47,7 +47,7 @@
 
 **Reason**: Shell results contain structured mesh, step/frame, nodal, element, Gauss point, resultant, stress, metadata, and tolerance data. HDF5 is better suited than flat CSV for this result hierarchy.
 
-**Tradeoff**: HDF5 becomes a required dependency. FESA will provide an internal RAII wrapper over the HDF5 C API, but the actual HDF5 C library must be supplied by `HDF5_ROOT` or `HDF5_DIR`.
+**Tradeoff**: HDF5 becomes a required dependency. FESA will provide an internal RAII wrapper over the HDF5 C API, but the actual HDF5 C library must be supplied by `HDF5_ROOT` or `HDF5_DIR`. The current local Windows install is `C:\Program Files\HDF_Group\HDF5\2.1.1`; use `HDF5_ROOT` for that root or `HDF5_DIR` for `C:\Program Files\HDF_Group\HDF5\2.1.1\cmake`.
 
 ## ADR-008: Single Tolerance Policy
 **Decision**: Reference comparison uses a single tolerance value `1e-5`. A compared scalar passes when absolute error or relative error is within `1e-5`.

docs/AGENT_RULES.md

@@ -88,7 +88,7 @@ Repeated failures must be routed back to the owning upstream stage instead of co
 - Each Agent writes the artifact for its stage and records downstream handoff items.
 - Every must requirement needs a verification method and acceptance criteria.
 - Every formulation needs clear DOF, coordinate, unit, sign, Jacobian, integration, and recovery rules.
-- Every I/O contract needs supported syntax, unsupported behavior, internal mapping, schema, units, component names, and matching rules.
+- Every I/O contract needs supported syntax, unsupported behavior, internal mapping, HDF5 result schema or explicitly approved CSV export schema, units, component names, and matching rules.
 - Every reference model contract needs model purpose, compared quantities, artifacts, provenance, and limitations.
 - Every implementation plan needs test-first tasks, target commands, candidate files, and traceability to upstream requirements.
 - Every verification report needs compared rows, missing/extra rows, max absolute error, max relative error, worst id/component, pass/fail, and failure classification.
@@ -96,6 +96,7 @@ Repeated failures must be routed back to the owning upstream stage instead of co
 ## Current Project Defaults
 - Initial feature id: `mitc4-linear-static-shell`.
 - Initial result/reference format: HDF5.
+- Local HDF5 default install: `C:\Program Files\HDF_Group\HDF5\2.1.1`; use `HDF5_ROOT` for this root or `HDF5_DIR` for `C:\Program Files\HDF_Group\HDF5\2.1.1\cmake`.
 - Reference policy: stored Abaqus S4R is primary for pass/fail; Abaqus S4 is diagnostic.
 - Required compared quantities: nodal displacement, reaction, element internal force/resultant, and stress.
 - Agents must preserve OpenSees-inspired architecture while using modern C++17 RAII and FESA ownership boundaries.

docs/ARCHITECTURE.md

@@ -217,6 +217,22 @@ Adapter targets:
 
 This allows test doubles and future dependency replacement without changing solver physics code.
 
+### HDF5 Dependency Discovery
+The current local Windows/MSVC HDF5 installation is:
+
+```text
+C:\Program Files\HDF_Group\HDF5\2.1.1
+```
+
+Implementation planning should use the HDF5 C API through the adapter layer, not the HDF5 C++ API. CMake discovery should prefer one of these explicit environment variables before falling back to default package search:
+
+```powershell
+$env:HDF5_ROOT = "C:\Program Files\HDF_Group\HDF5\2.1.1"
+$env:HDF5_DIR = "C:\Program Files\HDF_Group\HDF5\2.1.1\cmake"
+```
+
+The expected local artifacts are `include\hdf5.h`, `lib\hdf5.lib`, `bin\hdf5.dll`, and `cmake\hdf5-config.cmake`. `h5dump.exe -V` should report HDF5 `2.1.1` on this machine.
+
 ### Runtime Polymorphism
 Elements, materials, loads, and boundary conditions are handled through base interfaces. Phase 1 prioritizes clarity and testability. If large-model performance requires it later, assembly internals may add type-specific batch kernels.
 
@@ -247,6 +263,8 @@ element_id, gauss_id, section_point, S11, S22, S12, S13, S23
   feature_id
   solver_version
   model_id
+  hdf5_version
+  schema_version
   units
   tolerance
   reference_solver

docs/PLAN.md

@@ -43,5 +43,7 @@ Build the FESA structural solver foundation around the initial feature `mitc4-li
 
 ## Known Blockers
 - No CMake project exists yet, so `python scripts/validate_workspace.py` currently takes the no-op path.
-- HDF5 is not detected in standard local environment paths; implementation will need `HDF5_ROOT` or `HDF5_DIR`.
 - Abaqus reference artifacts are not generated by Agents and must be supplied by a human-approved process.
+
+## Known Environment Facts
+- HDF5 is installed locally at `C:\Program Files\HDF_Group\HDF5\2.1.1`; CMake should use `HDF5_ROOT` for this root or `HDF5_DIR` for `C:\Program Files\HDF_Group\HDF5\2.1.1\cmake`.

docs/PRD.md

@@ -89,7 +89,7 @@ MITC4 선형정적 기능이 reference 검증을 통과한 뒤 다음 기능을
 - MSVC and CMake must be available for C++ build validation.
 - Intel oneAPI MKL must be available through `MKLROOT` or known oneAPI installation paths.
 - Intel oneAPI TBB must be available through `TBBROOT` or known oneAPI installation paths.
-- HDF5 C library must be supplied through `HDF5_ROOT` or `HDF5_DIR`.
+- HDF5 C library must be supplied through `HDF5_ROOT` or `HDF5_DIR`; the current local default is `C:\Program Files\HDF_Group\HDF5\2.1.1`, with CMake package files under `C:\Program Files\HDF_Group\HDF5\2.1.1\cmake`.
 - Python 3 must be available for harness validation and phase execution.
 
 ## Release Requirements

docs/PROGRESS.md

@@ -21,6 +21,7 @@
 - Renamed the first solver development workflow stage to "새로운 솔버 기능 요구조건 분석" across `AGENTS.md`, `docs/`, `.codex/agents/requirement-agent.toml`, and `.codex/skills/fesa-requirements-baseline`.
 - Refined `requirement-agent` and `fesa-requirements-baseline` internals to describe a new solver feature requirements analysis document instead of a requirements drafting/specification task.
 - Documented the canonical git remote `https://teagit.mimi1011.synology.me/baram2584/FESADev.git`, default remote `origin`, shared baseline branch `dev`, and `codex/<short-task-name>` work branch convention in `AGENTS.md`, `docs/AGENT_RULES.md`, and `docs/PLAN.md`.
+- Confirmed local HDF5 `2.1.1` installation at `C:\Program Files\HDF_Group\HDF5\2.1.1` and recorded the `HDF5_ROOT`/`HDF5_DIR` discovery policy in architecture, agent, skill, and handoff documentation.
 
 ## In Progress
 - Ready for the next stage: new solver feature requirements analysis for `mitc4-linear-static-shell`.
@@ -34,6 +35,10 @@
 6. Create `docs/implementation-plans/mitc4-linear-static-shell-implementation-plan.md`.
 
 ## Last Validation
+- 2026-06-08: After HDF5 install/path documentation and HDF5-first result-output agent/skill/doc updates, `python C:\Users\user\.codex\skills\.system\skill-creator\scripts\quick_validate.py` passed for modified FESA skills: `fesa-io-contract`, `fesa-reference-models`, `fesa-reference-comparison`, `fesa-cpp-msvc-tdd`, `fesa-physics-sanity`, `fesa-requirements-baseline`, `fesa-numerical-review`, `fesa-formulation-spec`, `fesa-research-evidence`, and `fesa-release-readiness`.
+- 2026-06-08: After HDF5 install/path documentation and HDF5-first result-output agent/skill/doc updates, `python -m unittest discover -s scripts -p "test_*.py"` passed. 85 tests ran successfully.
+- 2026-06-08: After HDF5 install/path documentation and HDF5-first result-output agent/skill/doc updates, `python scripts/validate_workspace.py` passed through the expected no-op path because no root `CMakeLists.txt` exists yet.
+- 2026-06-08: After HDF5 install/path documentation and HDF5-first result-output agent/skill/doc updates, `git diff --check` passed with only Git line-ending normalization warnings.
 - 2026-06-08: After documenting git repository settings, `python scripts/validate_workspace.py` passed through the expected no-op path because no root `CMakeLists.txt` exists yet.
 - 2026-06-08: After documenting git repository settings, `git diff --check` passed with only Git line-ending normalization warnings.
 - 2026-06-08: After refining `requirement-agent` and `fesa-requirements-baseline` internals, `python C:\Users\baram\.codex\skills\.system\skill-creator\scripts\quick_validate.py .codex\skills\fesa-requirements-baseline` passed.
@@ -48,5 +53,4 @@
 - 2026-06-05: `python scripts/validate_workspace.py` passed through the expected no-op path because no root `CMakeLists.txt` exists yet.
 
 ## Open Questions
-- Exact HDF5 C library installation path is not known.
 - Stored Abaqus S4R/S4 reference artifact generation process is not yet defined.

docs/WORKNOTE.md

@@ -10,6 +10,9 @@ Add dated entries. Do not delete another Agent's note unless the user explicitly
 ### 2026-06-05 - HDF5 Not Found In Standard Paths
 During planning, standard checks for `HDF5_ROOT`, `HDF5_DIR`, `h5dump`, and obvious Program Files HDF5 folders did not find HDF5. Future implementation should not assume HDF5 is locally installed. Use `HDF5_ROOT` or `HDF5_DIR` and fail CMake configuration with a clear diagnostic if missing.
 
+### 2026-06-08 - HDF5 Installed Under HDF_Group
+The local HDF5 install was later confirmed at `C:\Program Files\HDF_Group\HDF5\2.1.1`, and `h5dump.exe -V` reports `2.1.1`. Future CMake work should prefer `HDF5_ROOT=C:\Program Files\HDF_Group\HDF5\2.1.1` or `HDF5_DIR=C:\Program Files\HDF_Group\HDF5\2.1.1\cmake`. Keep the old 2026-06-05 note as historical context for stale sessions, but do not treat HDF5 as currently missing on this machine.
+
 ### 2026-06-05 - Validation Currently Has No CMake Project
 `python scripts/validate_workspace.py` currently exits successfully through the no-op path because there is no root `CMakeLists.txt`. This is expected until the C++ solver project is bootstrapped. Once CMake is introduced, validation must configure, build, and run CTest.
 

docs/build-test-reports/README.md

@@ -22,7 +22,7 @@ Build/Test Executor Agent는 Implementation Agent 이후 독립적으로 C++/MSV
 - CMake files를 수정하지 않는다.
 - requirements, formulations, I/O contracts, reference artifacts, tolerance policies를 수정하지 않는다.
 - Abaqus, Nastran 또는 reference solver를 실행하지 않는다.
-- reference CSV를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV를 생성하지 않는다.
 - release readiness, reference tolerance success, physics validation success를 승인하지 않는다.
 - 최종 reference verification report를 작성하지 않는다.
 

docs/coordination/README.md

@@ -26,7 +26,7 @@ Coordinator Agent는 FESA solver 기능 개발의 전체 lifecycle에서 gate ev
 - requirements, formulations, I/O contracts, numerical review reports를 수정하지 않는다.
 - reference artifacts 또는 tolerance policies를 수정하지 않는다.
 - Abaqus, Nastran 또는 reference solver를 실행하지 않는다.
-- reference CSV를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV를 생성하지 않는다.
 - subagents를 자동 spawn하지 않는다.
 - release readiness를 독립적으로 승인하지 않는다.
 

docs/corrections/README.md

@@ -24,7 +24,7 @@ Correction Agent는 Build/Test Executor Agent, Reference Verification Agent, Phy
 - reference artifacts를 수정하지 않는다.
 - tolerance policies를 수정하지 않는다.
 - Abaqus, Nastran 또는 reference solver를 실행하지 않는다.
-- reference CSV를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV를 생성하지 않는다.
 - release readiness, reference tolerance success, physics validation success를 승인하지 않는다.
 - 최종 reference verification report 또는 physics validation report를 작성하지 않는다.
 

docs/formulations/README.md

@@ -20,7 +20,7 @@ Formulation Agent는 구현 가능한 FEM 정식화 문서를 작성한다.
 - C++ 코드를 구현하지 않는다.
 - C++ API나 파일 구조를 설계하지 않는다.
 - Abaqus, Nastran 또는 레퍼런스 솔버를 직접 실행하지 않는다.
-- reference CSV 결과를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV 결과를 생성하지 않는다.
 - release readiness를 승인하지 않는다.
 - Numerical Review Agent 검토 전 정식화를 최종 승인하지 않는다.
 

docs/implementation-plans/README.md

@@ -2,7 +2,7 @@
 
 이 디렉터리는 Implementation Planning Agent가 작성하거나 제안한 기능별 구현계획 문서를 보관하는 위치다.
 
-Implementation Planning Agent는 승인된 요구조건, 연구 브리프, 정식화, 수치 리뷰, I/O 정의, reference model 계약을 C++/MSVC 구현 전 TDD 작업계획으로 변환한다. Agent는 코드, 테스트, CMake 파일을 작성하지 않고, Abaqus/Nastran을 실행하지 않으며, reference CSV 생성이나 solver 결과 비교, release readiness 승인도 하지 않는다.
+Implementation Planning Agent는 승인된 요구조건, 연구 브리프, 정식화, 수치 리뷰, I/O 정의, reference model 계약을 C++/MSVC 구현 전 TDD 작업계획으로 변환한다. Agent는 코드, 테스트, CMake 파일을 작성하지 않고, Abaqus/Nastran을 실행하지 않으며, reference HDF5 artifact나 reference CSV 생성, solver 결과 비교, release readiness 승인도 하지 않는다.
 
 기본 파일명은 `docs/implementation-plans/<feature-id>-implementation-plan.md` 형식을 사용한다. 각 문서는 Implementation Agent가 먼저 작성해야 할 실패 테스트, 최소 구현 순서, CMake/CTest 등록 계획, acceptance traceability를 제공해야 한다.
 
@@ -23,7 +23,7 @@ Implementation Planning Agent는 승인된 요구조건, 연구 브리프, 정
 - CMake 파일을 수정하지 않는다.
 - CMake/CTest를 실행하지 않는다.
 - Abaqus, Nastran 또는 레퍼런스 솔버를 직접 실행하지 않는다.
-- reference CSV를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV를 생성하지 않는다.
 - solver 결과를 비교하지 않는다.
 - release readiness를 승인하지 않는다.
 - C++ API, class name, storage layout, file ownership을 확정하지 않는다.
@@ -73,7 +73,7 @@ Implementation Planning Agent는 승인된 요구조건, 연구 브리프, 정
 | TEST-001 | 1 | unit | test fails because behavior is missing | test passes after minimal implementation | TASK-001 | ctest -C Debug -R <test-name> |
 | TEST-002 | 2 | integration | integrated path fails before implementation | integrated path passes | TASK-002 | ctest -C Debug -R <test-name> |
 | TEST-003 | 3 | parser/I/O | Abaqus .inp case is not accepted or mapped | input maps to expected semantic model | TASK-003 | ctest -C Debug -R <test-name> |
-| TEST-004 | 4 | reference-comparison | solver CSV comparison fails before implementation | comparison is within planned tolerance | TASK-004 | ctest -C Debug -R <test-name> |
+| TEST-004 | 4 | reference-comparison | solver HDF5 comparison fails before implementation | comparison is within planned tolerance | TASK-004 | ctest -C Debug -R <test-name> |
 
 ## CMake/CTest Plan
 - target_candidates: <library/test executable targets>
@@ -95,8 +95,8 @@ Implementation Planning Agent는 승인된 요구조건, 연구 브리프, 정
 ## Data Flow Contract
 1. Abaqus `.inp` input follows docs/io-definitions/<feature-id>-io.md.
 2. Parser/I/O path maps model data and history data into the internal semantic model.
-3. Solver path produces displacement, reaction, element force, stress, or feature-specific result CSV.
+3. Solver path produces `results.h5` with displacement, reaction, element force, stress, or feature-specific result datasets.
-4. Reference comparison tests compare solver CSV against `references/<feature-id>/<model-id>/` artifacts.
+4. Reference comparison tests compare solver `results.h5` against `references/<feature-id>/<model-id>/` HDF5 artifacts.
 
 ## Acceptance Traceability Matrix
 
@@ -123,7 +123,7 @@ ctest -C Debug -R <feature-or-label>
 - <likely failure classifications and upstream rollback guidance>
 
 ### Reference Verification Agent
-- <planned CSV comparison tests, reference model ids, tolerance mapping, ID matching assumptions>
+- <planned HDF5 comparison tests, reference model ids, tolerance mapping, ID matching assumptions>
 
 ## Open Issues
 - <requirement, formulation, I/O, reference artifact, tolerance, or architecture issue>
@@ -133,7 +133,7 @@ ctest -C Debug -R <feature-or-label>
 
 - 모든 `must` requirement는 최소 하나의 task와 test에 연결되어야 한다.
 - C++ production 변경마다 선행 테스트 파일 또는 테스트 추가 계획이 있어야 한다.
-- reference artifact가 필요한 기능은 `references/<feature-id>/<model-id>/`와 CSV 비교 테스트 계획을 가져야 한다.
+- reference artifact가 필요한 기능은 `references/<feature-id>/<model-id>/`와 HDF5 비교 테스트 계획을 가져야 한다.
 - CMake/CTest 계획은 MSVC x64 Debug 검증 경로와 호환되어야 한다.
 - 구현 계획은 테스트 작성, 실패 확인, 최소 구현, validation 순서를 명시해야 한다.
 - upstream 문서가 불완전하면 값을 임의로 채우지 않고 `needs-upstream-decision` 또는 `blocked`로 표시한다.

docs/io-definitions/README.md

@@ -4,24 +4,25 @@
 
 FESA 솔버의 입력 파일은 Abaqus input file이다. 다만 초기 FESA는 Abaqus 전체 문법 호환을 목표로 하지 않고, 기능별로 지원할 Abaqus keyword subset과 내부 모델 매핑을 명확히 정의한다.
 
-기본 파일명은 `docs/io-definitions/<feature-id>-io.md` 형식을 사용한다. 각 문서는 Requirement Agent, Formulation Agent, Numerical Review Agent의 산출물을 입력으로 받아 Abaqus `.inp` 입력 계약과 결과 CSV schema를 정의해야 한다.
+기본 파일명은 `docs/io-definitions/<feature-id>-io.md` 형식을 사용한다. 각 문서는 Requirement Agent, Formulation Agent, Numerical Review Agent의 산출물을 입력으로 받아 Abaqus `.inp` 입력 계약과 HDF5 결과/reference schema를 정의해야 한다. CSV는 upstream 요구조건이 명시한 export 또는 comparison helper가 있을 때만 추가로 정의한다.
 
 ## I/O Definition Agent 역할
 
-I/O Definition Agent는 Abaqus input file subset, 내부 solver model mapping, output request mapping, comparison CSV schema를 정의한다.
+I/O Definition Agent는 Abaqus input file subset, 내부 solver model mapping, output request mapping, HDF5 result/reference schema, optional CSV export schema를 정의한다.
 
 수행한다:
 - 기능별 supported Abaqus keyword subset을 정의한다.
 - unsupported, ignored-with-warning, requires-user-decision keyword 정책을 정의한다.
 - model data와 history data를 내부 solver 개념으로 매핑한다.
 - node, element, set, material, section, boundary condition, load, step, output request의 의미 계약을 정의한다.
-- `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv` schema를 정의한다.
+- `results.h5`의 metadata, mesh, step/frame, nodal/element field output, history output dataset schema를 정의한다.
+- upstream 요구조건이 명시한 경우에만 `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv` 같은 optional CSV export schema를 정의한다.
 
 수행하지 않는다:
 - parser를 구현하지 않는다.
 - C++ API나 파일 구조를 설계하지 않는다.
 - Abaqus, Nastran 또는 레퍼런스 솔버를 직접 실행하지 않는다.
-- reference CSV 결과를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV 결과를 생성하지 않는다.
 - solver 결과와 reference 결과를 비교하지 않는다.
 - release readiness를 승인하지 않는다.
 - 명시적으로 정의되지 않은 Abaqus full compatibility를 주장하지 않는다.
@@ -107,7 +108,43 @@ I/O Definition Agent는 Abaqus input file subset, 내부 solver model mapping, o
 - step: <semantic contract>
 - output_request: <semantic contract>
 
-## Output and CSV Schemas
+## HDF5 Result and Reference Schemas
+
+### results.h5
+
+```text
+/metadata
+  feature_id
+  solver_version
+  model_id
+  hdf5_version
+  schema_version
+  units
+  tolerance
+  reference_solver
+
+/mesh/nodes
+/mesh/elements/<element-family>/connectivity
+
+/results/step_<id>/frame_<id>/nodal/<quantity>
+/results/step_<id>/frame_<id>/element/<quantity>
+/results/step_<id>/frame_<id>/history
+```
+
+각 dataset은 path, shape, datatype, ID field, component naming, coordinate system, units, output location, step/frame identity, ID matching rule을 명시해야 한다.
+
+### Required MITC4 Quantity Datasets
+
+| quantity | default dataset path | id/matching fields | component contract |
+| --- | --- | --- | --- |
+| nodal displacement | `/results/step_000/frame_000/nodal/displacement` | node id, component | `U1, U2, U3, UR1, UR2, UR3` |
+| nodal reaction | `/results/step_000/frame_000/nodal/reaction` | node id, component | `RF1, RF2, RF3, RM1, RM2, RM3` |
+| element force/resultant | `/results/step_000/frame_000/element/forces` | element id, Gauss point, component | `N11, N22, N12, M11, M22, M12, Q13, Q23` |
+| stress | `/results/step_000/frame_000/element/stress` | element id, Gauss point, section point, component | `S11, S22, S12, S13, S23` |
+
+## Optional CSV Export Schemas
+
+CSV output is not required for the current MITC4 HDF5-first feature unless an upstream requirement explicitly asks for it. When CSV export is required, it must preserve the same IDs, components, units, coordinate system, output location, and step/frame identity as the HDF5 datasets.
 
 ### displacements.csv
 | column | type | description |
@@ -161,13 +198,13 @@ I/O Definition Agent는 Abaqus input file subset, 내부 solver model mapping, o
 ## Open Issues and Downstream Handoff
 
 ### Reference Model Agent
-- <Abaqus input examples and reference artifact schema needs>
+- <Abaqus input examples and HDF5 reference artifact schema needs>
 
 ### Implementation Planning Agent
-- <parser acceptance cases, unsupported keyword diagnostics, CSV writer tests>
+- <parser acceptance cases, unsupported keyword diagnostics, HDF5 writer tests, optional CSV export tests>
 
 ### Reference Verification Agent
-- <CSV schemas, ID matching rules, units, coordinate conventions, tolerance-relevant fields>
+- <HDF5 dataset schemas, optional CSV schemas, ID matching rules, units, coordinate conventions, tolerance-relevant fields>
 ```
 
 ## 품질 기준
@@ -177,4 +214,5 @@ I/O Definition Agent는 Abaqus input file subset, 내부 solver model mapping, o
 - model data와 history data의 매핑을 구분해야 한다.
 - unsupported keyword 처리 정책을 명확히 해야 한다.
 - 내부 모델 계약은 semantic fields로 작성하고 C++ class/function/API를 확정하지 않는다.
-- CSV schema는 column name, ID field, component naming, coordinate system, units, step/frame identity, quantity location을 포함해야 한다.
+- HDF5 schema는 dataset path, shape, datatype, ID field, component naming, coordinate system, units, step/frame identity, quantity location을 포함해야 한다.
+- Optional CSV schema는 명시적으로 요구된 경우에만 정의하며, HDF5 schema와 동일한 물리 의미와 matching rule을 유지해야 한다.

docs/numerical-reviews/README.md

@@ -20,7 +20,7 @@ Numerical Review Agent는 정식화의 수학적 일관성, 수치 안정성 위
 - 정식화 문서를 직접 수정하지 않는다.
 - C++ API나 파일 구조를 설계하지 않는다.
 - Abaqus, Nastran 또는 레퍼런스 솔버를 직접 실행하지 않는다.
-- reference CSV 결과를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV 결과를 생성하지 않는다.
 - release readiness를 승인하지 않는다.
 - 레퍼런스 결과와 구현 솔버 결과의 일치 여부를 판정하지 않는다.
 

docs/physics-evaluations/README.md

@@ -23,7 +23,7 @@ Physics Evaluation Agent는 Reference Verification Agent가 `pass-for-physics-ev
 - requirements, formulations, I/O contracts, reference model contracts를 수정하지 않는다.
 - reference artifacts 또는 tolerance policies를 수정하지 않는다.
 - Abaqus, Nastran 또는 reference solver를 실행하지 않는다.
-- reference CSV를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV를 생성하지 않는다.
 - reference tolerance를 다시 판정하지 않는다.
 - release readiness를 승인하지 않는다.
 - release notes 또는 final release checklist를 작성하지 않는다.
@@ -39,7 +39,7 @@ EVIDENCE CHECK -> PHYSICS CHECKS -> CLASSIFY -> REPORT
 `EVIDENCE CHECK`에서 다음 항목을 확인한다.
 
 - Reference Verification report status가 `pass-for-physics-evaluation`인지 여부
-- checked solver/reference CSVs
+- checked solver/reference HDF5 files or approved optional CSV extracts
 - compared quantities
 - model purpose
 - documented physical expectations
@@ -93,7 +93,7 @@ EVIDENCE CHECK -> PHYSICS CHECKS -> CLASSIFY -> REPORT
 | evidence | path_or_source | status | notes |
 | --- | --- | --- | --- |
 | reference_verification | docs/reference-verifications/<feature-id>-reference-verification.md | pass-for-physics-evaluation | <summary> |
-| solver_results | <solver CSV path> | present | missing | <summary> |
+| solver_results | <solver results.h5 path or approved CSV extract path> | present | missing | <summary> |
 | reference_results | references/<feature-id>/<model-id>/ | present | missing | <summary> |
 | model_purpose | docs/reference-models/<feature-id>-reference-models.md | documented | missing | <summary> |
 | physical_expectations | <source docs> | documented | missing | <summary> |

docs/project-plan/SOLVER_AGENT_DESIGN.md

@@ -105,7 +105,7 @@
 주요 산출물:
 - 입력 데이터 schema
 - 출력 데이터 schema
-- 결과 비교용 CSV schema
+- 결과 비교용 HDF5 schema와 optional CSV export schema
 - 단위와 좌표계 규약
 
 ### Reference Model Agent

docs/project-plan/SOLVER_IMPLEMENT_INITIAL_PLAN.md

@@ -303,6 +303,7 @@ TBB:
 HDF5:
 - FESA provides an internal RAII wrapper around the HDF5 C API.
 - The HDF5 C library itself must be supplied through `HDF5_ROOT` or `HDF5_DIR`.
+- The current local default is `C:\Program Files\HDF_Group\HDF5\2.1.1`; use `HDF5_ROOT` for this root or `HDF5_DIR` for `C:\Program Files\HDF_Group\HDF5\2.1.1\cmake`.
 - HDF5 is required for solver output and reference comparison.
 
 ## Assumptions

docs/project-plan/SOLVER_SKILL_DESIGN.md

@@ -43,7 +43,7 @@ Agent는 역할과 책임 단위이고, skill은 여러 Agent가 반복적으로
 5. I/O Definition Agent는 `fesa-io-contract`를 사용해 지원할 Abaqus `.inp` keyword subset과 `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv` schema를 정의한다.
 6. Reference Model Agent는 `fesa-reference-models`를 사용해 `references/linear-truss-1d/<model-id>/` artifact bundle 계약과 coverage matrix를 작성한다.
 7. Implementation Planning Agent와 Implementation Agent는 `fesa-cpp-msvc-tdd`를 사용해 테스트 작성, 실패 확인, 최소 구현, CMake/CTest 등록, validation을 수행한다.
-8. Reference Verification Agent는 `fesa-reference-comparison`을 사용해 구현 solver CSV와 저장된 reference CSV를 tolerance 기준으로 비교한다.
+8. Reference Verification Agent는 `fesa-reference-comparison`을 사용해 구현 solver HDF5 결과와 저장된 reference HDF5 artifact를 tolerance 기준으로 비교한다.
 9. Physics Evaluation Agent는 `fesa-physics-sanity`를 사용해 global equilibrium, reaction consistency, displacement direction, symmetry, model coverage를 검토한다.
 10. Release Agent는 `fesa-release-readiness`를 사용해 gate evidence, acceptance traceability, known limitations, release notes draft를 작성한다.
 
@@ -54,7 +54,7 @@ Agent는 역할과 책임 단위이고, skill은 여러 Agent가 반복적으로
 - 새로운 솔버 기능 요청을 검증 가능한 요구조건 분석 baseline으로 만든다.
 - `shall` 문장과 `FESA-REQ-<FEATURE>-###` id를 사용한다.
 - 모든 `must` 요구조건은 verification method와 acceptance criteria를 가져야 한다.
-- FEM 정식화, C++ 구현, reference CSV 생성, release readiness 판단은 하지 않는다.
+- FEM 정식화, C++ 구현, reference HDF5 artifact 또는 reference CSV 생성, release readiness 판단은 하지 않는다.
 
 ### `fesa-research-evidence`
 
@@ -81,7 +81,7 @@ Agent는 역할과 책임 단위이고, skill은 여러 Agent가 반복적으로
 
 - FESA solver input이 지원할 Abaqus `.inp` subset을 정의한다.
 - model data와 history data를 구분한다.
-- 내부 semantic model 계약과 output/CSV schema를 정의한다.
+- 내부 semantic model 계약과 HDF5 output schema 및 명시적으로 요구된 optional CSV schema를 정의한다.
 - parser 구현이나 full Abaqus compatibility claim은 하지 않는다.
 
 ### `fesa-reference-models`

docs/reference-models/README.md

@@ -2,7 +2,7 @@
 
 이 디렉터리는 Reference Model Agent가 작성하거나 제안한 기능별 reference model 설계 문서를 보관하는 위치다.
 
-Reference Model Agent는 FESA 기능 검증에 필요한 Abaqus `.inp` 기반 테스트 모델 포트폴리오와 `references/<feature-id>/<model-id>/` artifact bundle 계약을 정의한다. Agent는 Abaqus, Nastran 또는 레퍼런스 솔버를 직접 실행하지 않고, reference CSV 값을 생성하지 않으며, solver 결과 비교나 release readiness 승인도 하지 않는다.
+Reference Model Agent는 FESA 기능 검증에 필요한 Abaqus `.inp` 기반 테스트 모델 포트폴리오와 `references/<feature-id>/<model-id>/` artifact bundle 계약을 정의한다. Agent는 Abaqus, Nastran 또는 레퍼런스 솔버를 직접 실행하지 않고, reference HDF5 artifact나 reference CSV 값을 생성하지 않으며, solver 결과 비교나 release readiness 승인도 하지 않는다.
 
 기본 파일명은 `docs/reference-models/<feature-id>-reference-models.md` 형식을 사용한다. 각 문서는 요구조건, 연구 브리프, 정식화, 수치 리뷰, I/O 정의를 입력으로 받아 구현 전에 준비해야 할 테스트 모델과 reference artifact 요구사항을 정의해야 한다.
 
@@ -12,8 +12,9 @@ Reference Model Agent는 FESA 기능 검증에 필요한 Abaqus `.inp` 기반
 - 기능별 reference model portfolio를 smoke, analytical, patch test, benchmark, regression, negative/invalid-input model로 구분한다.
 - `model.inp`가 I/O Definition Agent의 supported Abaqus keyword subset 안에 있는지 확인한다.
 - `references/<feature-id>/<model-id>/` artifact bundle 구조와 필수 파일을 정의한다.
-- `metadata.json` provenance, 단위, 좌표계, Abaqus version/source, output request, tolerance 정책을 정의한다.
+- `metadata.json` provenance, 단위, 좌표계, Abaqus version/source, output request, HDF5 schema version, tolerance 정책을 정의한다.
-- `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv` 요구사항을 정의한다.
+- `results.h5` 또는 feature-specific HDF5 reference result file 요구사항을 정의한다.
+- upstream 요구조건이 명시한 경우에만 `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv` 같은 optional CSV export 요구사항을 정의한다.
 - requirement와 model, compared quantity, tolerance, artifact status를 연결하는 Coverage Matrix를 작성한다.
 
 수행하지 않는다:
@@ -21,7 +22,7 @@ Reference Model Agent는 FESA 기능 검증에 필요한 Abaqus `.inp` 기반
 - parser를 구현하지 않는다.
 - C++ API나 파일 구조를 설계하지 않는다.
 - Abaqus, Nastran 또는 레퍼런스 솔버를 직접 실행하지 않는다.
-- reference CSV를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV를 생성하지 않는다.
 - solver 결과를 비교하지 않는다.
 - release readiness를 승인하지 않는다.
 - reference 값, tolerance, Abaqus compatibility를 임의로 만들지 않는다.
@@ -53,11 +54,11 @@ Reference Model Agent는 FESA 기능 검증에 필요한 Abaqus `.inp` 기반
 
 | model_id | category | purpose | status | required_artifacts |
 | --- | --- | --- | --- | --- |
-| <model-id> | smoke | <basic parser/solve path> | draft | model.inp, metadata.json, required CSVs |
+| <model-id> | smoke | <basic parser/solve path> | draft | model.inp, metadata.json, results.h5 |
-| <model-id> | analytical | <closed-form comparison> | draft | model.inp, metadata.json, required CSVs |
+| <model-id> | analytical | <closed-form comparison> | draft | model.inp, metadata.json, results.h5 |
-| <model-id> | patch test | <element consistency check> | draft | model.inp, metadata.json, required CSVs |
+| <model-id> | patch test | <element consistency check> | draft | model.inp, metadata.json, results.h5 |
-| <model-id> | benchmark | <trusted benchmark comparison> | draft | model.inp, metadata.json, required CSVs |
+| <model-id> | benchmark | <trusted benchmark comparison> | draft | model.inp, metadata.json, results.h5 |
-| <model-id> | regression | <known defect guard> | draft | model.inp, metadata.json, required CSVs |
+| <model-id> | regression | <known defect guard> | draft | model.inp, metadata.json, results.h5 |
 | <model-id> | negative/invalid-input | <unsupported keyword or invalid model diagnostic> | draft | model.inp, metadata.json |
 
 ## Model Record
@@ -81,7 +82,7 @@ Reference Model Agent는 FESA 기능 검증에 필요한 Abaqus `.inp` 기반
 - supported_keyword_subset: <keywords from docs/io-definitions/<feature-id>-io.md>
 - model_data: <nodes, elements, sets, material, section, coordinates, units>
 - history_data: <step, procedure, boundary conditions, loads, output requests>
-- output_requests: <requests needed to populate reference CSV files>
+- output_requests: <requests needed to populate reference HDF5 datasets>
 - unsupported_keyword_policy: unsupported | ignored-with-warning | requires-user-decision
 
 ## Artifact Bundle Contract
@@ -92,27 +93,38 @@ references/
     <model-id>/
       model.inp
       metadata.json
-      displacements.csv
+      results.h5
-      reactions.csv
-      element_forces.csv
-      stresses.csv
       README.md
 ```
 
 Required files:
 - `model.inp`: Abaqus input file for the reference model.
 - `metadata.json`: provenance and model contract metadata.
-- `displacements.csv`: nodal displacement reference results.
+- `results.h5`: HDF5 reference result artifact containing required metadata, mesh, step/frame, nodal, element, field, and history result datasets.
-- `reactions.csv`: nodal reaction force reference results.
-- `element_forces.csv`: element internal force reference results.
-- `stresses.csv`: stress reference results.
 - `README.md`: short description, generation notes, and limitations.
 
 Optional files:
+- `displacements.csv`: nodal displacement export when upstream contracts explicitly require CSV.
+- `reactions.csv`: nodal reaction force export when upstream contracts explicitly require CSV.
+- `element_forces.csv`: element internal force export when upstream contracts explicitly require CSV.
+- `stresses.csv`: stress export when upstream contracts explicitly require CSV.
 - `strains.csv`: strain reference results when required.
 - `energy_or_residual.csv`: energy, residual, or convergence reference results when required.
 - `notes.md`: manual review notes.
 
+For the current `mitc4-linear-static-shell` feature, the required stored Abaqus artifacts are:
+
+```text
+references/mitc4-linear-static-shell/<model-id>/
+  model.inp
+  metadata.json
+  abaqus_s4r/results.h5
+  abaqus_s4/results.h5
+  README.md
+```
+
+`abaqus_s4r/results.h5` is the primary pass/fail reference. `abaqus_s4/results.h5` is diagnostic.
+
 ## Metadata JSON Contract
 
 ```json
@@ -132,13 +144,21 @@ Optional files:
   "boundary_condition_summary": "<summary>",
   "load_summary": "<summary>",
   "output_requests": ["U", "RF", "S", "<feature-specific quantities>"],
-  "csv_schema_version": "<version>",
+  "hdf5_schema_version": "<version>",
   "tolerance_policy": "<absolute/relative/norm policy>",
   "limitations": ["<known limitation>"]
 }
 ```
 
-## Reference CSV Requirements
+## Reference HDF5 Requirements
+
+- Required when reference comparison is part of the feature acceptance criteria.
+- Must include metadata, mesh identity, step/frame identity, node and element IDs, component names, coordinate system, units, output locations, and tolerance source.
+- Required quantity datasets must match the paths and component contracts from `docs/io-definitions/<feature-id>-io.md`.
+
+## Optional CSV Export Requirements
+
+CSV exports are not required for the current HDF5-first MITC4 feature unless an upstream document explicitly requires them. When required, they must preserve the same physical meaning and matching keys as the HDF5 datasets.
 
 ### displacements.csv
 - Required when nodal displacement is a verification quantity.
@@ -164,30 +184,30 @@ Optional files:
 
 | requirement_id | model_id | compared_quantity | artifact_file | tolerance | verification_method | status |
 | --- | --- | --- | --- | --- | --- | --- |
-| <req-id> | <model-id> | displacement | displacements.csv | <policy> | reference-comparison | draft |
+| <req-id> | <model-id> | displacement | results.h5:/results/.../nodal/displacement | <policy> | reference-comparison | draft |
-| <req-id> | <model-id> | reaction | reactions.csv | <policy> | reference-comparison | draft |
+| <req-id> | <model-id> | reaction | results.h5:/results/.../nodal/reaction | <policy> | reference-comparison | draft |
-| <req-id> | <model-id> | element force | element_forces.csv | <policy> | reference-comparison | draft |
+| <req-id> | <model-id> | element force | results.h5:/results/.../element/forces | <policy> | reference-comparison | draft |
-| <req-id> | <model-id> | stress | stresses.csv | <policy> | reference-comparison | draft |
+| <req-id> | <model-id> | stress | results.h5:/results/.../element/stress | <policy> | reference-comparison | draft |
 
 ## Artifact Acceptance Checklist
 - 모든 `must` requirement가 최소 하나의 `model_id`와 `compared_quantity`에 연결되어 있다.
 - `model.inp`가 기능별 supported Abaqus keyword subset을 벗어나지 않는다.
-- `metadata.json`에 provenance, Abaqus version/source, units, coordinate system, tolerance, CSV schema version이 기록되어 있다.
+- `metadata.json`에 provenance, Abaqus version/source, units, coordinate system, tolerance, HDF5 schema version이 기록되어 있다.
-- 필수 CSV 파일이 존재하거나, 기능상 불필요한 파일은 명확한 reason과 함께 제외되어 있다.
+- 필수 HDF5 artifact가 존재하거나, 기능상 불필요한 파일은 명확한 reason과 함께 제외되어 있다.
-- output request가 필요한 CSV 물리량을 생성할 수 있도록 정의되어 있다.
+- output request가 필요한 HDF5 물리량을 생성할 수 있도록 정의되어 있다.
-- reference CSV가 없으면 status는 `needs-reference-artifacts`다.
+- reference HDF5 artifact가 없으면 status는 `needs-reference-artifacts`다.
 - tolerance, source, units, coordinate system이 불명확하면 status는 `needs-user-decision`이다.
 
 ## Open Issues and Downstream Handoff
 
 ### I/O Definition Agent
-- <supported keyword, output request, CSV schema clarification>
+- <supported keyword, output request, HDF5 schema clarification>
 
 ### Implementation Planning Agent
 - <tests that should fail before implementation, model order, acceptance criteria>
 
 ### Reference Verification Agent
-- <CSV schema, ID matching, units, coordinate conventions, output locations, tolerance mapping>
+- <HDF5 schema, optional CSV schema, ID matching, units, coordinate conventions, output locations, tolerance mapping>
 
 ### Physics Evaluation Agent
 - <equilibrium, symmetry, displacement direction, stress location, rigid body mode, load path sanity checks>
@@ -198,8 +218,8 @@ Optional files:
 - Reference model의 목적과 검증 대상 requirement가 명확해야 한다.
 - `model.inp`는 Abaqus input file이며, 기능별 supported keyword subset을 따라야 한다.
 - model data와 history data를 구분해야 한다.
-- output request와 required CSV 사이의 연결이 명확해야 한다.
+- output request와 required HDF5 dataset 사이의 연결이 명확해야 한다.
 - `references/<feature-id>/<model-id>/` 구조와 필수 artifact가 명시되어야 한다.
-- `metadata.json`에는 provenance, Abaqus version/source, units, coordinate system, tolerance, CSV schema version이 포함되어야 한다.
+- `metadata.json`에는 provenance, Abaqus version/source, units, coordinate system, tolerance, HDF5 schema version이 포함되어야 한다.
-- reference CSV가 없으면 완료 상태가 아니라 `needs-reference-artifacts` 상태로 둔다.
+- reference HDF5 artifact가 없으면 완료 상태가 아니라 `needs-reference-artifacts` 상태로 둔다.
 - 모든 `must` requirement는 Coverage Matrix에서 model, compared quantity, tolerance, verification method로 추적되어야 한다.

docs/reference-verifications/README.md

@@ -2,17 +2,17 @@
 
 이 디렉터리는 Reference Verification Agent가 작성하거나 제안하는 기능별 reference comparison report를 보관하는 위치다.
 
-Reference Verification Agent는 Build/Test Executor Agent 통과 후 generated solver result CSV와 stored Abaqus reference CSV artifacts를 tolerance 기준으로 비교한다. 이 agent는 comparison과 report만 수행하며, source code, tests, CMake files, requirements, formulations, I/O contracts, reference artifacts, tolerance policies를 수정하지 않는다.
+Reference Verification Agent는 Build/Test Executor Agent 통과 후 generated solver `results.h5`와 stored Abaqus reference HDF5 artifacts를 tolerance 기준으로 비교한다. 이 agent는 comparison과 report만 수행하며, source code, tests, CMake files, requirements, formulations, I/O contracts, reference artifacts, tolerance policies를 수정하지 않는다.
 
 기본 문서명은 `docs/reference-verifications/<feature-id>-reference-verification.md` 형식을 사용한다.
 
 ## Reference Verification Agent 역할
 
 수행한다:
-- `references/<feature-id>/<model-id>/` artifact bundle과 generated solver result CSV를 확인한다.
+- `references/<feature-id>/<model-id>/` artifact bundle과 generated solver `results.h5`를 확인한다.
 - `metadata.json`, schema version, units, coordinate system, step/frame identity, node/element IDs, output location, tolerance source를 확인한다.
-- `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`를 기본 비교 대상으로 삼는다.
+- HDF5 datasets for displacement, reaction, element force/resultant, stress를 기본 비교 대상으로 삼는다.
-- upstream 문서가 요구할 때만 `strains.csv`, `energy_or_residual.csv`를 추가 비교한다.
+- upstream 문서가 요구할 때만 strain, energy, residual HDF5 datasets 또는 optional CSV export를 추가 비교한다.
 - max absolute error, max relative error, RMS error, norm error, worst node/element/component, missing rows, extra rows, pass/fail을 보고한다.
 - 실패를 missing-reference-artifact, missing-solver-output, schema-mismatch, id-mismatch, unit-or-coordinate-mismatch, tolerance-failure, nonfinite-result, upstream-contract, environment로 분류한다.
 
@@ -23,8 +23,8 @@ Reference Verification Agent는 Build/Test Executor Agent 통과 후 generated s
 - requirements, formulations, I/O contracts, reference model contracts를 수정하지 않는다.
 - reference artifacts 또는 tolerance policies를 수정하지 않는다.
 - Abaqus, Nastran 또는 reference solver를 실행하지 않는다.
-- reference CSV를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV를 생성하지 않는다.
-- solver output CSV를 tolerance에 맞추기 위해 보정하지 않는다.
+- solver HDF5 output 또는 optional CSV export를 tolerance에 맞추기 위해 보정하지 않는다.
 - physics validation success 또는 release readiness를 승인하지 않는다.
 
 ## 실행 순서
@@ -38,8 +38,8 @@ ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT
 `ARTIFACT CHECK`에서 다음 항목이 없으면 비교를 시작하지 않는다.
 
 - `metadata.json`
-- required reference CSV files
+- required reference HDF5 files
-- generated solver result CSV files
+- generated solver `results.h5`
 - schema version
 - units
 - coordinate system
@@ -51,20 +51,20 @@ ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT
 ## 비교 대상
 
 기본 비교 대상:
-- `displacements.csv`: nodal displacement
+- `results.h5:/results/.../nodal/displacement`: nodal displacement
-- `reactions.csv`: nodal reaction force
+- `results.h5:/results/.../nodal/reaction`: nodal reaction force
-- `element_forces.csv`: element internal force
+- `results.h5:/results/.../element/forces`: element internal force/resultant
-- `stresses.csv`: element stress
+- `results.h5:/results/.../element/stress`: element stress
 
 선택 비교 대상:
-- `strains.csv`: strain이 acceptance criteria에 포함된 경우
+- strain HDF5 dataset or `strains.csv`: strain이 acceptance criteria에 포함된 경우
-- `energy_or_residual.csv`: energy, residual, convergence quantity가 acceptance criteria에 포함된 경우
+- energy/residual HDF5 dataset or `energy_or_residual.csv`: energy, residual, convergence quantity가 acceptance criteria에 포함된 경우
 
 ## Failure Classification
 
 - `missing-reference-artifact`: required stored reference file 또는 provenance가 없다.
-- `missing-solver-output`: generated solver result CSV 또는 comparison command가 없다.
+- `missing-solver-output`: generated solver `results.h5` 또는 comparison command가 없다.
-- `schema-mismatch`: reference CSV와 solver CSV column/schema가 다르다.
+- `schema-mismatch`: reference HDF5 schema와 solver HDF5 schema가 다르다.
 - `id-mismatch`: node id, element id, step/frame, integration point, component matching이 실패했다.
 - `unit-or-coordinate-mismatch`: units 또는 coordinate system이 비교 가능하지 않다.
 - `tolerance-failure`: schema와 matching은 유효하지만 error가 tolerance를 초과했다.
@@ -93,11 +93,10 @@ ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT
 | --- | --- | --- | --- |
 | reference_bundle | references/<feature-id>/<model-id>/ | present | missing | <notes> |
 | metadata | references/<feature-id>/<model-id>/metadata.json | present | missing | <provenance summary> |
-| reference_displacements | references/<feature-id>/<model-id>/displacements.csv | present | missing | <notes> |
+| reference_results | references/<feature-id>/<model-id>/results.h5 | present | missing | <notes> |
-| reference_reactions | references/<feature-id>/<model-id>/reactions.csv | present | missing | <notes> |
+| solver_results | <solver output path>/results.h5 | present | missing | <notes> |
-| reference_element_forces | references/<feature-id>/<model-id>/element_forces.csv | present | missing | <notes> |
+| optional_reference_csv_exports | references/<feature-id>/<model-id>/*.csv | present | missing | required only when upstream contracts ask for CSV |
-| reference_stresses | references/<feature-id>/<model-id>/stresses.csv | present | missing | <notes> |
+| optional_solver_csv_exports | <solver output path>/*.csv | present | missing | required only when upstream contracts ask for CSV |
-| solver_outputs | <solver output directory> | present | missing | <notes> |
 
 ## Comparison Contract
 - schema_version: <version>
@@ -114,10 +113,10 @@ ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT
 
 | quantity | model_id | artifact_file | compared_rows | missing_rows | extra_rows | max_abs_error | max_rel_error | rms_error | norm_error | worst_id | worst_component | result |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| displacement | <model-id> | displacements.csv | <n> | <n> | <n> | <value> | <value> | <value> | <value or N/A> | <node id> | <component> | pass | fail |
+| displacement | <model-id> | results.h5:/results/.../nodal/displacement | <n> | <n> | <n> | <value> | <value> | <value> | <value or N/A> | <node id> | <component> | pass | fail |
-| reaction | <model-id> | reactions.csv | <n> | <n> | <n> | <value> | <value> | <value> | <value or N/A> | <node id> | <component> | pass | fail |
+| reaction | <model-id> | results.h5:/results/.../nodal/reaction | <n> | <n> | <n> | <value> | <value> | <value> | <value or N/A> | <node id> | <component> | pass | fail |
-| element force | <model-id> | element_forces.csv | <n> | <n> | <n> | <value> | <value> | <value> | <value or N/A> | <element id> | <component> | pass | fail |
+| element force | <model-id> | results.h5:/results/.../element/forces | <n> | <n> | <n> | <value> | <value> | <value> | <value or N/A> | <element id> | <component> | pass | fail |
-| stress | <model-id> | stresses.csv | <n> | <n> | <n> | <value> | <value> | <value> | <value or N/A> | <element/ip id> | <component> | pass | fail |
+| stress | <model-id> | results.h5:/results/.../element/stress | <n> | <n> | <n> | <value> | <value> | <value> | <value or N/A> | <element/ip id> | <component> | pass | fail |
 
 ## Failure Classification
 - classification: missing-reference-artifact | missing-solver-output | schema-mismatch | id-mismatch | unit-or-coordinate-mismatch | tolerance-failure | nonfinite-result | upstream-contract | environment | N/A
@@ -151,15 +150,15 @@ ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT
 - `pass-for-physics-evaluation`: required reference comparisons가 모두 통과했고 Physics Evaluation Agent로 넘길 수 있다.
 - `needs-correction`: implementation-owned solver result mismatch 또는 nonfinite result가 있다.
 - `needs-reference-artifacts`: required reference artifact 또는 provenance가 누락됐다.
-- `needs-solver-results`: generated solver result CSV 또는 comparison command가 없다.
+- `needs-solver-results`: generated solver `results.h5` 또는 comparison command가 없다.
 - `needs-upstream-decision`: schema, tolerance, units, coordinate system, output location, ID matching policy가 누락 또는 충돌한다.
 - `blocked`: 사용자 또는 Coordinator Agent 결정 없이는 안전하게 진행할 수 없다.
 
 ## 품질 기준
 
 - 모든 `must` requirement의 reference-comparison 항목은 model id, compared quantity, artifact file, tolerance에 trace되어야 한다.
-- reference artifact는 읽기 전용이다. `model.inp`, `metadata.json`, reference CSV를 수정하지 않는다.
+- reference artifact는 읽기 전용이다. `model.inp`, `metadata.json`, `results.h5`, optional reference CSV를 수정하지 않는다.
-- solver output CSV는 비교 입력일 뿐이며 tolerance에 맞추기 위해 후처리 보정하지 않는다.
+- solver HDF5 output과 optional solver CSV는 비교 입력일 뿐이며 tolerance에 맞추기 위해 후처리 보정하지 않는다.
 - stress/strain은 element id, integration point 또는 recovery location, component naming이 일치할 때만 비교한다.
 - nodal displacement/reaction은 node id, DOF/component, coordinate system, unit이 일치할 때만 비교한다.
 - missing rows와 extra rows를 숨기지 않고 보고한다.

docs/releases/README.md

@@ -2,7 +2,7 @@
 
 이 디렉터리는 Release Agent가 작성하거나 제안하는 기능별 release readiness report를 보관하는 위치다.
 
-Release Agent는 Physics Evaluation Agent가 `pass-for-release-agent`로 넘긴 기능에 대해 최종 gate evidence를 감사한다. 이 Agent는 source code, tests, CMake, upstream 계약, reference artifacts, tolerance policies를 수정하지 않는다. 또한 Abaqus/Nastran 실행, reference CSV 생성, 외부 publish/deploy/package/tag/commit 작업을 수행하지 않는다.
+Release Agent는 Physics Evaluation Agent가 `pass-for-release-agent`로 넘긴 기능에 대해 최종 gate evidence를 감사한다. 이 Agent는 source code, tests, CMake, upstream 계약, reference artifacts, tolerance policies를 수정하지 않는다. 또한 Abaqus/Nastran 실행, reference HDF5 artifact 또는 reference CSV 생성, 외부 publish/deploy/package/tag/commit 작업을 수행하지 않는다.
 
 기본 문서명은 `docs/releases/<feature-id>-release.md` 형식을 사용한다.
 
@@ -24,7 +24,7 @@ Release Agent는 Physics Evaluation Agent가 `pass-for-release-agent`로 넘긴
 - requirements, formulations, I/O contracts, numerical review reports, reference verification reports, physics evaluation reports를 수정하지 않는다.
 - reference artifacts 또는 tolerance policies를 수정하지 않는다.
 - Abaqus, Nastran 또는 reference solver를 실행하지 않는다.
-- reference CSV를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV를 생성하지 않는다.
 - 실패하거나 누락된 upstream gate를 우회하지 않는다.
 - 사용자 명시 요청 없이 publish, deploy, package, tag, commit, external release를 수행하지 않는다.
 

docs/requirements/README.md

@@ -20,7 +20,7 @@ Requirement Agent는 새로운 솔버 기능 요청을 검증 가능한 요구
 - 유한요소 정식화를 확정하지 않는다.
 - C++ API나 파일 구조를 설계하지 않는다.
 - Abaqus, Nastran 또는 레퍼런스 솔버를 직접 실행하지 않는다.
-- reference CSV 결과를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV 결과를 생성하지 않는다.
 - 기능 완료 여부를 승인하지 않는다.
 
 ## 문서 템플릿
@@ -78,10 +78,8 @@ Expected location: `references/<feature-id>/`
 
 - `model.inp`: required | not-applicable
 - `metadata.json`: required
-- `displacements.csv`: required | not-applicable
+- `results.h5`: required | not-applicable
-- `reactions.csv`: required | not-applicable
+- optional_csv_exports: required | not-applicable
-- `element_forces.csv`: required | not-applicable
-- `stresses.csv`: required | not-applicable
 
 ## Requirement Verification Matrix
 
@@ -114,6 +112,6 @@ Expected location: `references/<feature-id>/`
 
 - 모든 `must` 요구조건은 검증 방법과 acceptance criteria를 가져야 한다.
 - 모든 수치 요구조건은 단위, 좌표계, tolerance 또는 `TBD with owner`를 가져야 한다.
-- reference 비교가 필요한 요구조건은 필요한 CSV artifact를 명시해야 한다.
+- reference 비교가 필요한 요구조건은 필요한 HDF5 artifact와 dataset path를 명시해야 한다. CSV artifact는 명시적으로 요구된 export일 때만 포함한다.
 - "빠르게", "정확하게", "Abaqus처럼" 같은 문장은 검증 가능한 기준으로 바꾸거나 open question으로 남겨야 한다.
 - 구현 방법, 정식화 세부식, C++ API는 이 문서에서 확정하지 않는다.

docs/research/README.md

@@ -20,7 +20,7 @@ Research Agent는 FEM 이론, benchmark, verification reference, solver manual,
 - 유한요소 정식화를 확정하지 않는다.
 - C++ API나 파일 구조를 설계하지 않는다.
 - Abaqus, Nastran 또는 레퍼런스 솔버를 직접 실행하지 않는다.
-- reference CSV 결과를 생성하지 않는다.
+- reference HDF5 artifact 또는 reference CSV 결과를 생성하지 않는다.
 - 기능 완료 여부를 승인하지 않는다.
 
 ## Source Reliability Tier

scripts/test_build_test_executor_agent_config.py

@@ -30,7 +30,7 @@ class BuildTestExecutorAgentConfigTests(unittest.TestCase):
             "Do not edit tests.",
             "Do not edit CMake.",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not approve release readiness.",
         ):
             self.assertIn(required_text, instructions)

scripts/test_coordinator_agent_config.py

@@ -32,7 +32,7 @@ class CoordinatorAgentConfigTests(unittest.TestCase):
             "Do not edit CMake.",
             "Do not run build/test validation.",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not automatically spawn subagents.",
             "Do not approve release readiness independently.",
         ):

scripts/test_correction_agent_config.py

@@ -32,7 +32,7 @@ class CorrectionAgentConfigTests(unittest.TestCase):
             "Do not change reference artifacts",
             "Do not change tolerance policies",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not approve release readiness.",
         ):
             self.assertIn(required_text, instructions)

scripts/test_fesa_solver_skills.py

@@ -96,14 +96,14 @@ SKILLS = {
             "Use when",
             "FESA solver",
             "Abaqus .inp",
-            "CSV schemas",
+            "HDF5 result/reference schemas",
             "I/O",
         ),
         "body_terms": (
             "docs/io-definitions/<feature-id>-io.md",
             "Abaqus Input Scope",
             "Internal Model Contract",
-            "Output and CSV Schemas",
+            "HDF5 Result and Reference Schemas",
             "*NODE",
             "*ELEMENT",
             "*MATERIAL",
@@ -130,7 +130,7 @@ SKILLS = {
             "element_forces.csv",
             "stresses.csv",
             "Coverage Matrix",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
         ),
     },
     "fesa-cpp-msvc-tdd": {
@@ -155,7 +155,7 @@ SKILLS = {
         "description_terms": (
             "Use when",
             "FESA solver",
-            "reference CSV",
+            "HDF5 reference",
             "tolerance",
             "comparison",
         ),

scripts/test_formulation_agent_config.py

@@ -29,7 +29,7 @@ class FormulationAgentConfigTests(unittest.TestCase):
             "Do not implement code.",
             "Do not design C++ APIs",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not approve release readiness.",
             "docs/AGENT_RULES.md",
             "docs/requirements/<feature-id>.md",

scripts/test_implementation_agent_config.py

@@ -41,7 +41,7 @@ class ImplementationAgentConfigTests(unittest.TestCase):
 
         for required_text in (
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not approve release readiness.",
             "Do not change requirements",
             "Do not change formulations",

scripts/test_implementation_planning_agent_config.py

@@ -31,7 +31,7 @@ class ImplementationPlanningAgentConfigTests(unittest.TestCase):
             "Do not edit CMake.",
             "Do not run CMake/CTest.",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not compare solver results.",
             "Do not approve release readiness.",
         ):

scripts/test_io_definition_agent_config.py

@@ -29,7 +29,7 @@ class IoDefinitionAgentConfigTests(unittest.TestCase):
             "Do not implement parsers.",
             "Do not design C++ APIs",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not approve release readiness.",
             "Do not claim full Abaqus compatibility",
         ):
@@ -43,7 +43,7 @@ class IoDefinitionAgentConfigTests(unittest.TestCase):
             "Abaqus input files use keyword lines, data lines, and comment lines.",
             "Model data and history data",
             "supported Abaqus keyword subset",
-            "comparison CSV schemas",
+            "HDF5 result/reference schemas",
         ):
             self.assertIn(required_text, instructions)
 
@@ -56,7 +56,7 @@ class IoDefinitionAgentConfigTests(unittest.TestCase):
             "Model Data Mapping",
             "History Data Mapping",
             "Internal Model Contract",
-            "Output and CSV Schemas",
+            "HDF5 Result and Reference Schemas",
             "Validation Rules",
             "Downstream Handoff",
         ):
@@ -86,7 +86,7 @@ class IoDefinitionAgentConfigTests(unittest.TestCase):
             "Model Data Mapping",
             "History Data Mapping",
             "Internal Model Contract",
-            "Output and CSV Schemas",
+            "HDF5 Result and Reference Schemas",
             "Validation Rules",
             "Downstream Handoff",
             "FESA 솔버의 입력 파일은 Abaqus input file이다.",

scripts/test_numerical_review_agent_config.py

@@ -30,7 +30,7 @@ class NumericalReviewAgentConfigTests(unittest.TestCase):
             "Do not edit formulations directly.",
             "Do not design C++ APIs",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not approve release readiness.",
             "docs/AGENT_RULES.md",
             "docs/formulations/<feature-id>-formulation.md",

scripts/test_physics_evaluation_agent_config.py

@@ -30,7 +30,7 @@ class PhysicsEvaluationAgentConfigTests(unittest.TestCase):
             "Do not edit tests.",
             "Do not edit CMake.",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not change tolerances.",
             "Do not approve release readiness.",
         ):

scripts/test_reference_model_agent_config.py

@@ -30,7 +30,7 @@ class ReferenceModelAgentConfigTests(unittest.TestCase):
             "Do not implement parsers.",
             "Do not design C++ APIs",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not compare solver results.",
             "Do not approve release readiness.",
         ):
@@ -44,10 +44,7 @@ class ReferenceModelAgentConfigTests(unittest.TestCase):
             "references/<feature-id>/<model-id>/",
             "model.inp",
             "metadata.json",
-            "displacements.csv",
+            "results.h5",
-            "reactions.csv",
-            "element_forces.csv",
-            "stresses.csv",
         ):
             self.assertIn(required_text, instructions)
 
@@ -60,7 +57,8 @@ class ReferenceModelAgentConfigTests(unittest.TestCase):
             "Abaqus Input Requirements",
             "Artifact Bundle Contract",
             "Metadata JSON Contract",
-            "Reference CSV Requirements",
+            "Reference HDF5 Requirements",
+            "Optional CSV Export Requirements",
             "Coverage Matrix",
             "Downstream Handoff",
         ):
@@ -75,7 +73,8 @@ class ReferenceModelAgentConfigTests(unittest.TestCase):
             "Abaqus Input Requirements",
             "Artifact Bundle Contract",
             "Metadata JSON Contract",
-            "Reference CSV Requirements",
+            "Reference HDF5 Requirements",
+            "Optional CSV Export Requirements",
             "Coverage Matrix",
             "Downstream Handoff",
             "references/<feature-id>/<model-id>/",

scripts/test_reference_verification_agent_config.py

@@ -17,7 +17,7 @@ class ReferenceVerificationAgentConfigTests(unittest.TestCase):
         data = tomllib.loads(AGENT_PATH.read_text(encoding="utf-8"))
 
         self.assertEqual(data["name"], "reference-verification-agent")
-        self.assertIn("stored Abaqus reference CSV artifacts", data["description"])
+        self.assertIn("stored Abaqus reference HDF5 artifacts", data["description"])
         self.assertEqual(data["sandbox_mode"], "workspace-write")
         self.assertEqual(data["model_reasoning_effort"], "extra high")
         self.assertIn("developer_instructions", data)
@@ -30,7 +30,7 @@ class ReferenceVerificationAgentConfigTests(unittest.TestCase):
             "Do not edit tests.",
             "Do not edit CMake.",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not approve release readiness.",
             "Do not change tolerance policies.",
         ):
@@ -40,10 +40,7 @@ class ReferenceVerificationAgentConfigTests(unittest.TestCase):
         instructions = AGENT_PATH.read_text(encoding="utf-8")
 
         for required_text in (
-            "displacements.csv",
+            "results.h5",
-            "reactions.csv",
-            "element_forces.csv",
-            "stresses.csv",
             "metadata.json",
             "references/<feature-id>/<model-id>/",
         ):

scripts/test_release_agent_config.py

@@ -36,7 +36,7 @@ class ReleaseAgentConfigTests(unittest.TestCase):
             "Do not change reference artifacts",
             "Do not change tolerance policies",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "Do not override failed or missing upstream gates.",
         ):
             self.assertIn(required_text, instructions)

scripts/test_requirement_agent_config.py

@@ -29,7 +29,7 @@ class RequirementAgentConfigTests(unittest.TestCase):
             "Do not implement code.",
             "Do not write finite element formulations.",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not create reference CSV outputs.",
+            "Do not create reference HDF5 artifacts or reference CSV outputs.",
             "Requirement Verification Matrix",
             "docs/AGENT_RULES.md",
             "references/<feature>",

scripts/test_research_agent_config.py

@@ -29,7 +29,7 @@ class ResearchAgentConfigTests(unittest.TestCase):
             "Do not implement code.",
             "Do not finalize FEM formulations.",
             "Do not run Abaqus, Nastran, or any reference solver.",
-            "Do not generate reference CSVs.",
+            "Do not generate reference HDF5 artifacts or reference CSVs.",
             "docs/AGENT_RULES.md",
             "docs/requirements/<feature-id>.md",
             "Separate verified facts from inference.",