modify docu

This commit is contained in:
NINI
2026-06-12 01:15:14 +09:00
parent 742f311be1
commit 066b352fcb
62 changed files with 458 additions and 389 deletions
+1 -1
View File
@@ -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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not approve release readiness.
## Quality Gate
+1 -1
View File
@@ -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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not approve release readiness.
## Quality Gate
+6 -6
View File
@@ -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, HDF5 result schemas, and deterministic CSV view schemas for reference comparison.
description: Use when defining FESA solver I/O contracts, Abaqus .inp keyword subsets, internal model mapping, validation rules, HDF5 result schemas, and reference CSV comparison row schemas.
---
# FESA I/O Contract
@@ -26,7 +26,7 @@ Read these first:
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 HDF5 Schema for authoritative solver output `results.h5`.
7. Define Deterministic CSV View Schemas for `csv/displacements.csv`, `csv/reactions.csv`, `csv/element_forces.csv`, `csv/stresses.csv`, and optional view files.
7. Define FESA HDF5 to Reference CSV Comparison Schema for normalized rows matched against Abaqus CSV files under `reference/<model-id>/`.
8. Define units, coordinate system, component naming, output location, step/frame identity, and ID matching rules.
9. Define validation rules and open issues.
@@ -40,7 +40,7 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with:
- History Data Mapping
- Internal Model Contract
- Output HDF5 Schema
- Deterministic CSV View Schemas
- FESA HDF5 to Reference CSV Comparison Schema
- Validation Rules
- Downstream Handoff
@@ -50,17 +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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not approve release readiness.
## Quality Gate
- Every supported keyword has a documented purpose, required data, and unsupported-case behavior.
- HDF5 schema is the authoritative solver output contract and must carry schema version, step/frame identity, units, coordinate system, output location, and component naming.
- Deterministic CSV view schemas are comparison views derived from HDF5 datasets and must define stable row ordering, ID fields, and component ordering.
- Reference CSV comparison row schema must define stable row ordering, ID fields, and component ordering for matching against Abaqus reference CSV.
- 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 HDF5 dataset paths, deterministic CSV view schemas, ID matching, and tolerance-source constraints to Reference Verification Agent.
Send keyword and schema contracts to Reference Model Agent and Implementation Planning Agent. Send HDF5 dataset paths, reference CSV row schemas, ID matching, and tolerance-source constraints to Reference Verification Agent.
@@ -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, HDF5 result, and deterministic CSV view contracts."
default_prompt: "Use $fesa-io-contract to define Abaqus input, HDF5 result, and reference CSV comparison row contracts."
+1 -1
View File
@@ -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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not approve release readiness.
- Do not decide reference comparison success.
+2 -2
View File
@@ -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/reference HDF5 files and deterministic CSV views as read-only evidence
- Solver results.h5, Abaqus reference CSV files under reference/<model-id>/, and optional FESA debug CSV views 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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not approve release readiness.
- Do not approve reference tolerance success.
@@ -1,6 +1,6 @@
---
name: fesa-reference-comparison
description: Use when running FESA solver HDF5 reference comparison with deterministic CSV view checks, checking stored artifacts, schema, units, ID matching, tolerance metrics, and reference verification status.
description: Use when comparing FESA solver HDF5 results against Abaqus reference CSV files for reference comparison, checking schema, units, ID matching, tolerance metrics, and reference verification status.
---
# FESA Reference Comparison
@@ -18,15 +18,15 @@ Read these first:
- `docs/reference-models/<feature-id>-reference-models.md`
- `docs/io-definitions/<feature-id>-io.md`
- Generated solver result HDF5, normally `results.h5`
- Deterministic solver CSV views when a comparison command materializes them
- Stored `references/<feature-id>/<model-id>/` artifacts
- Abaqus reference CSV files under `reference/<model-id>/`
- Optional deterministic solver CSV views materialized from `results.h5` for debugging or review
## Workflow
1. Follow `ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT`.
2. ARTIFACT CHECK: verify `metadata.json`, required `reference.h5`, generated solver `results.h5`, deterministic CSV view files, schema version, units, coordinate system, step/frame identity, ID matching, output location, component naming, and tolerance source.
2. ARTIFACT CHECK: verify `metadata.json`, `model.inp`, generated solver `results.h5`, `reference/<model-id>/<model-id>_displacements.csv`, `reference/<model-id>/<model-id>_reactions.csv`, `reference/<model-id>/<model-id>_internalforces.csv`, `reference/<model-id>/<model-id>_stresses.csv`, reference CSV schema version, FESA HDF5 schema version, units, coordinate system, step/frame identity, ID matching, output location, component naming, and tolerance policy.
3. Stop with `needs-reference-artifacts`, `needs-solver-results`, or `needs-upstream-decision` when required comparison inputs are missing.
4. COMPARE authoritative HDF5 datasets first, using deterministic CSV view files such as `csv/displacements.csv`, `csv/reactions.csv`, `csv/element_forces.csv`, `csv/stresses.csv`, and optional `csv/strains.csv` or `csv/energy_or_residual.csv` only as stable review/comparison views.
4. COMPARE FESA HDF5 datasets by normalizing their rows and matching them directly against Abaqus reference CSV rows.
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.
@@ -52,7 +52,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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not approve physics validation or release readiness.
## Quality Gate
@@ -61,9 +61,10 @@ 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 `results.h5` and `reference.h5` are authoritative comparison inputs.
- Deterministic CSV view files are derived views only; do not normalize them beyond documented matching and metrics.
- FESA solver `results.h5` is the authoritative solver output.
- Abaqus reference CSV files are the authoritative reference result artifacts.
- FESA debug CSV views are derived from `results.h5` for review only; do not treat FESA debug CSV views as authoritative solver output or reference artifacts.
## Handoff
Send passing reports to Physics Evaluation Agent. Send implementation-owned mismatches to Correction Agent. Send missing artifacts to Reference Model Agent and HDF5/CSV view schema conflicts to I/O Definition Agent.
Send passing reports to Physics Evaluation Agent. Send implementation-owned mismatches to Correction Agent. Send missing artifacts to Reference Model Agent and HDF5/reference CSV schema conflicts to I/O Definition Agent.
@@ -1,4 +1,4 @@
interface:
display_name: "FESA Reference Comparison"
short_description: "Compare HDF5 results"
default_prompt: "Use $fesa-reference-comparison to compare FESA solver results.h5 against reference.h5 and deterministic CSV views."
short_description: "Compare HDF5 with Abaqus CSV"
default_prompt: "Use $fesa-reference-comparison to compare FESA solver results.h5 against Abaqus reference CSV files."
+11 -12
View File
@@ -1,6 +1,6 @@
---
name: fesa-reference-models
description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required reference HDF5 artifacts, deterministic CSV views, coverage matrices, and implementation-planning handoffs.
description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required Abaqus reference CSV files, coverage matrices, and implementation-planning handoffs.
---
# FESA Reference Models
@@ -25,12 +25,11 @@ Read these first:
1. Define reference strategy: code verification, solution verification, and benchmark/reference comparison.
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`, `reference.h5`, deterministic CSV views under `csv/`, and `README.md` unless explicitly not applicable.
6. Define required CSV views `csv/displacements.csv`, `csv/reactions.csv`, `csv/element_forces.csv`, and `csv/stresses.csv` only as deterministic views of `reference.h5`.
7. Define optional `csv/strains.csv` and `csv/energy_or_residual.csv` only when upstream acceptance criteria require them.
8. Define metadata provenance, units, coordinate system, output requests, artifact status, and limitations.
9. Build a Coverage Matrix mapping requirement id, model id, compared quantity, authoritative HDF5 dataset, CSV view file, tolerance, verification method, and status.
4. Define `reference/<model-id>/` artifact bundle requirements.
5. Require `model.inp`, `metadata.json`, `<model-id>_displacements.csv`, `<model-id>_reactions.csv`, `<model-id>_internalforces.csv`, `<model-id>_stresses.csv`, and `README.md` unless explicitly not applicable.
6. Define optional `<model-id>_strains.csv`, `<model-id>_energy_or_residual.csv`, and `<model-id>_<quantity>.csv` only when upstream acceptance criteria require them.
7. Define metadata provenance, units, coordinate system, output requests, artifact status, reference_csv_schema_version, reference_csv_files, and limitations.
8. Build a Coverage Matrix mapping requirement id, model id, compared quantity, FESA HDF5 dataset, reference CSV file, tolerance, verification method, and status.
## Output Contract
@@ -43,7 +42,7 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
- Abaqus Input Requirements
- Artifact Bundle Contract
- Metadata JSON Contract
- Reference HDF5 and CSV View Requirements
- Abaqus Reference CSV Requirements
- Coverage Matrix
- Artifact Acceptance Checklist
- Open Issues and Downstream Handoff
@@ -54,7 +53,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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not compare solver results.
- Do not approve release readiness.
@@ -62,9 +61,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, HDF5 schema version, and CSV view schema version.
- Missing `reference.h5` or required deterministic CSV views keep the model at `needs-reference-artifacts`.
- `metadata.json` includes provenance, Abaqus version/source, units, coordinate system, tolerance, reference_csv_schema_version, and reference_csv_files.
- Missing required Abaqus reference CSV files keep the model at `needs-reference-artifacts`.
## Handoff
Send model order and tests that should fail first to Implementation Planning Agent. Send HDF5 dataset paths, deterministic CSV view schemas, 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 FESA HDF5 dataset paths, reference CSV schemas, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.
@@ -1,4 +1,4 @@
interface:
display_name: "FESA Reference Models"
short_description: "Design reference model bundles"
default_prompt: "Use $fesa-reference-models to design FESA reference model artifact bundles."
short_description: "Design Abaqus CSV reference bundles"
default_prompt: "Use $fesa-reference-models to design Abaqus reference CSV artifact bundles."
@@ -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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not override failed or missing gates.
- Do not publish, deploy, package, tag, commit, or externally release anything unless the user explicitly asks.
@@ -47,7 +47,7 @@ Produce or revise `docs/requirements/<feature-id>.md` with:
- 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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not approve release readiness.
## Quality Gate
@@ -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 HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not approve release readiness.
## Quality Gate